Viper｜1.2.2 update with bugfixes and new skin

[andy4trance]

A bit late to the party but boy this is a great synth for a trance fest. Shortest demo before purchase..

Its intuitive interface layout is inviting to program even preset whores like me.

All presets sound great,big and full (maybe a lot of default compression in the background? ). I don't see many instances fitting in the mix at the same time, which is good for the cpu.

Still scratching the surface but great fun so far.

[Shiek927]

Awfully quiet in Viper land! anything new coming up for this synth?

[Elektronisch]

Awfully quiet in Viper land! anything new coming up for this synth?

Whats wrong with the feature set that it already has?

Also its a 1 person development team, new features requires lots of time and also some research. Its a bit unrealistic to expect something new after 6-7 months of release.

[Echoes in the Attic]

Awfully quiet in Viper land! anything new coming up for this synth?

Whats wrong with the feature set that it already has?

Also its a 1 person development team, new features requires lots of time and also some research. Its a bit unrealistic to expect something new after 6-7 months of release.

Personally I wouldn’t mind see the issue with the saving of the plugin state in hosts getting sorted (as described on previous page). I’d also like the wavetables be exposed for automation somehow (as a second parameter that goes through the waveforms).

[recursive one]

I’d also like the wavetables be exposed for automation somehow (as a second parameter that goes through the waveforms).

Viper doesn't use wavteables. It can only morph between saw and a single-cycle waveform (this morphing may be automated) but you can't scan though a pack of different single cycle waveforms like you do in Serum etc.

[Echoes in the Attic]

I’d also like the wavetables be exposed for automation somehow (as a second parameter that goes through the waveforms).

Viper doesn't use wavteables. It can only morph between saw and a single-cycle waveform (this morphing may be automated) but you can't scan though a pack of different single cycle waveforms like you do in Serum etc.

Sorry replace “wavetables” in my text with “waveforms”. I just meant the list of waveforms that are not the standard ones. I’d like to see that automatable like the standard ones are.

[recursive one]

I’d also like the wavetables be exposed for automation somehow (as a second parameter that goes through the waveforms).

Viper doesn't use wavteables. It can only morph between saw and a single-cycle waveform (this morphing may be automated) but you can't scan though a pack of different single cycle waveforms like you do in Serum etc.

Sorry replace “wavetables” in my text with “waveforms”. I just meant the list of waveforms that are not the standard ones. I’d like to see that automatable like the standard ones are.

So what you want is being able to automate the waveform selector in the classic oscillator?

Yep, this potentially may be interesting

FYI, the classic oscillator in Virus doesn't do that, it acts exactly like Viper classic osc, except that it doesn't load user waveforms

[Echoes in the Attic]

Well I’d like to be able to automate not just the selection of the classic waves but also the other single cycle waveforms. But to be honest it’s not for the sake of automation, it’s to be able to go through the waves from a hardware controller. All the good ones use mapping based on the parameter ID as seen by the daw. Like notation automap, komplete kontrol, nektar, akai etc. Most viper controls are exposed but not the waveforms. That’s one of the main things that can change a sound so it’s nice to be able to go through them from a keyboard controller. Many vst devs overlook this.

[adamszabo]

The last Viper update was at the end of June. I need some rest as well Plus I have to make JP6K into 64 bit too, so Viper will take a break. I do have lots of plans for it though but it takes time. I cannot automate the waveform selection because its dynamic. It means users can have any number of waveforms in that folder, so I wouldnt know how many vaues there can be, and Viper uses standard midi values, so what would happen if the waves exceed 127? You cant scroll more than that.

Regarding the bug, I still need to see a video from someone what happens with the presets reverting back to the first preset.

[Halonmusic]

The last Viper update was at the end of June. I need some rest as well Plus I have to make JP6K into 64 bit too, so Viper will take a break. I do have lots of plans for it though but it takes time. I cannot automate the waveform selection because its dynamic. It means users can have any number of waveforms in that folder, so I wouldnt know how many vaues there can be, and Viper uses standard midi values, so what would happen if the waves exceed 127? You cant scroll more than that.

Regarding the bug, I still need to see a video from someone what happens with the presets reverting back to the first preset.

Are you going to add a feedback oscillator aswell as the other features present in jp8000 to jp6k?

[Echoes in the Attic]

The last Viper update was at the end of June. I need some rest as well Plus I have to make JP6K into 64 bit too, so Viper will take a break. I do have lots of plans for it though but it takes time. I cannot automate the waveform selection because its dynamic. It means users can have any number of waveforms in that folder, so I wouldnt know how many vaues there can be, and Viper uses standard midi values, so what would happen if the waves exceed 127? You cant scroll more than that.

Regarding the bug, I still need to see a video from someone what happens with the presets reverting back to the first preset.

Actually host parameters can be any number of values. Well I don’t remember the max value but definitely in the thousands. Actually you already do this with your other parameters like the basic waveform selector. I don’t have a computer now to check but if I recall correctly it had a thousand or several thousand values in the host parameter but only populated the first few values with the basic shapes (square, saw etc). The rest are just numbers that keep it at the last waveform in the list. That’s a common thing. So if there was a similar parameter for the complex waveforms, whatever that max value is for the parameter, that would be the maximum number of use waves for automation. Even if someone had auromarion on it and then added waves, it wouldn’t change because the max value that the host sees doesn’t change. Does that make sense? Sorry I can’t do screenshots but if you use Ableton live you can see what I mean by enabling automation and switching the basic shapes and you’ll see the slider show up in the expanded device view with only real values arc the very start and then lots of numbers. Same goes for the lfo shape selector I think.

[cleverr1]

My introduction to the Virus was via the Poco, (which is the B). The first patch it plays when loaded is OvertureCK, a classic evolving pad. I've had a go at recreating OvertureCK with Viper.

Is there anywhere we can upload / download to share presets for Viper?

[adamszabo]

I think you can upload presets to kvr somewhere if I remember?

[cleverr1]

uploaded to:
https://www.kvraudio.com/product/generi ... /downloads

[chk071]

You can also download them here, i think: https://www.kvraudio.com/product/viper- ... /downloads