Viper｜1.2.2 update with bugfixes and new skin

[BONES]

Yes, if you bothered to read the thread, Adam says it has always been like that. That's not what worries me.

[Dencheg]

That's amazing news, finally yaaaaaaay
Do you guys (especially Adam the man) know if any new factory bank has been added to show new features?
(Checking in case if I've copied something incorrectly and missing a treat)

[iowastate89]

Screenshot 2023-06-02 101125.jpg

I put the whole folder in the VST3 folder but it won't load in Bitwig. It sees the VST3 but I get an error loading it. Any suggestions? Ableton Live works.

I have never seen that error in my life, and I tested it in Bitwig also. Did you install the c++ redistributable stuff?

Yeah I would have had to when I installed the vst2. I just realized that I didn't remove then old vst2 actually. Not sure if that could cause a conflict. But I don't think my vst2 path is even on. Not home to check yet.

Well ok, I had it show up and trial'ing it with v5 beta 8, and now beta 9 is giving me the same error

[Echoes in the Attic]

Screenshot 2023-06-02 101125.jpg

I put the whole folder in the VST3 folder but it won't load in Bitwig. It sees the VST3 but I get an error loading it. Any suggestions? Ableton Live works.

I have never seen that error in my life, and I tested it in Bitwig also. Did you install the c++ redistributable stuff?

Yeah I would have had to when I installed the vst2. I just realized that I didn't remove then old vst2 actually. Not sure if that could cause a conflict. But I don't think my vst2 path is even on. Not home to check yet.

Well ok, I had it show up and trial'ing it with v5 beta 8, and now beta 9 is giving me the same error

Oh you're getting the same error as me now? I reported to bitwig, you should too..

[strovoknights]

I put the unzipped Viper folder into the VST3 folder, deleted "Viper (64).dll" and "Viper.dll" from the Viper folder, and the VST3 version of Viper started successfully.
I am running Windows 10, Bitwig 5 beta9.

[Echoes in the Attic]

I put the unzipped Viper folder into the VST3 folder, deleted "Viper (64).dll" and "Viper.dll" from the Viper folder, and the VST3 version of Viper started successfully.
I am running Windows 10, Bitwig 5 beta9.

That's what I did. Worked on my surface pro, but not my studio computer.

[izonin]

There's a little bug I found. The state of locked sections is not saved.

1. Turn off a section
2. Lock it
3. Change the preset
4. Save the project

The next time I load the project the section is on (should be off), and the sound has changed.

[rasmusklump]

Besides the flowstone quirks the one thing that prevents me from buying this vsti are two things with the arp.
First: the virus arp has a hold function, why is it missing here?
Second and more important: the viper arp in chord mode gives me the same problems as many other arps in vstis: when I press a chord most of the time the first step of the arp only consists of one of the notes from the chord, presumably the one that got pressed a microsecond before the others. This makes it unusable for performing live.
The virus arp doesn't show this behavior either in the hardware nor the vsti emulator....

[adamszabo]

Besides the flowstone quirks the one thing that prevents me from buying this vsti are two things with the arp.
First: the virus arp has a hold function, why is it missing here?
Second and more important: the viper arp in chord mode gives me the same problems as many other arps in vstis: when I press a chord most of the time the first step of the arp only consists of one of the notes from the chord, presumably the one that got pressed a microsecond before the others. This makes it unusable for performing live.
The virus arp doesn't show this behavior either in the hardware nor the vsti emulator....

The new update in Viper does indeed have a new "hold" function, but its in the polyphony selector, so you can press a note, let go, and it will play forever.

I have never noticed the issue with the Chord mode you described, it seems to work fine on my end, both when playing live or playing the piano roll.

[rasmusklump]

Besides the flowstone quirks the one thing that prevents me from buying this vsti are two things with the arp.
First: the virus arp has a hold function, why is it missing here?
Second and more important: the viper arp in chord mode gives me the same problems as many other arps in vstis: when I press a chord most of the time the first step of the arp only consists of one of the notes from the chord, presumably the one that got pressed a microsecond before the others. This makes it unusable for performing live.
The virus arp doesn't show this behavior either in the hardware nor the vsti emulator....

The new update in Viper does indeed have a new "hold" function, but its in the polyphony selector, so you can press a note, let go, and it will play forever.

I have never noticed the issue with the Chord mode you described, it seems to work fine on my end, both when playing live or playing the piano roll.

Thanks, I will try the hold funktion and play a little bit with the midi settings in Cubase, although the problem als occurs in the patchwork host.
As I said the virus emulation plays the full chords everytime.

[Echoes in the Attic]

FYI my Bitwig issue with Viper was solved by their support by deleting some cache and index files as described here:
This was solved by Bitwig support by following these steps:
https://www.bitwig.com/support/technica ... ng-why-30/

[adamszabo]

FYI my Bitwig issue with Viper was solved by their support by deleting some cache and index files as described here:
This was solved by Bitwig support by following these steps:
https://www.bitwig.com/support/technica ... ng-why-30/

Thank you, I shall add it to my FAQ, it could be useful for others as well!

[rasmusklump]

Besides the flowstone quirks the one thing that prevents me from buying this vsti are two things with the arp.
First: the virus arp has a hold function, why is it missing here?
Second and more important: the viper arp in chord mode gives me the same problems as many other arps in vstis: when I press a chord most of the time the first step of the arp only consists of one of the notes from the chord, presumably the one that got pressed a microsecond before the others. This makes it unusable for performing live.
The virus arp doesn't show this behavior either in the hardware nor the vsti emulator....

The new update in Viper does indeed have a new "hold" function, but its in the polyphony selector, so you can press a note, let go, and it will play forever.

I have never noticed the issue with the Chord mode you described, it seems to work fine on my end, both when playing live or playing the piano roll.

Sorry, no luck.
The hold function is not the same as the arp latch in virus or arp latch in general. The hold function in fact doesn't work at all with the arp as it only plays and holds one note and not all pressed notes.
Also no luck with the chord function I have to press all notes of the chord so precisely that I manage it maybe 1 time out of ten.
Quantized recorded midi works of course.

[Dencheg]

I need more momentum, talks and presence for one of my favorite instruments.
So you guys enjoy Viper? I definitely do
Actually just recently my piano-trained friend tried playing some cool cinematic pads when I showed Viper to her, and she was really pleased by the sound

[tripleflows]

Can someone show an audio / video sample how the famous Overture CK dreamy Virus B / C pad program sounds from Viper?