Viper|1.2.2 update with bugfixes and new skin

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS
Viper

Post

adamtrance wrote: Sun Jun 11, 2023 10:02 am You just mentioned that you are no developer, so you probably didnt read this yet: https://forums.steinberg.net/t/vst3-and ... all/201879

Lots of devs had issued with VST3 and Midi as you can read through that thread. If you use a VST3 plugin which has midi they used some hacks or something to get it working, but I dont know, I dont understand the VST SDK, I can only use codes that are available in FlowStone. I will ofcourse try to help the dev as much as I can so they can add it. I obviously had two choice: hold back the VST3 version until midi is implemented properly (and when will that happen?) or release the VST3 now and let people play with it already. Which is better?
Please not that topic from 2019 again. A lot has changed since, including full midi 2.0 support amongst other things. Since then many synths migrated to vst3. And also, most midi plugins went vst3 too, which would be kinda impossible if vst3 didn't support midi.

And yes, many devs had issues. Which is not crazy considering the complexity of vst3, and the lack of proper documentation from Steinberg (which they solved for a big part). But there is a big difference between 'having issues' and what you said, and i quote :
"Midi CC does not work with the VST3 version yet, because Steinberg removed it from their VST3 specification", which is simply not the case.

By now almost all my synths and midi plugins are vst3. None of them have issues with midi cc's. You are the last one to go vst3, and the only one that has these problems. And i know that you are depending on Flowstone. Which is unfortunate in this case as Viper is an awesome synth and deserves so much more. Just like JP6K btw.

Anyways, i won't bother you further. For now i just keep using the vst2, and keep living with Flowstone's quirks.
The loudness war is over, loudness has won

Post

You are making it sound like I am deliberately not supporting Midi in VST3 just to f*ck with people. As I said I can only do so much. In FlowStone I can call the midi input function, which will grab the steinberg shit for handling the midi. Thats as deep as I can go, the rest is up to FlowStone. If its not available in VST3 then its not my fault.

I asked the FlowStone dev about the link IMidiLean thing linked in previous posts and this is what he had to say:

"Essentially there is no Midi-CC anymore, the Host maps the CC to a parameter and you essentially get preset param changes like as if it was automation. You can setup a midi-cc to param mapping in a plugin that the host uses by default (https://steinbergmedia.github.io/vst3_d ... pping.html). I guess the midilearn you linked to, allows to re-initialize the mapping part of the host, so the host asks the plugin again, how the default mapping should look like. However this whole system is not compatible with the way FS is setup. We would have to have a midi-cc number input directly on a preset primitive..."

So I will believe the FlowStone developer when he says there is no Midi in VST3 anymore. In all your VST3s you have, they all use this preset parameter hack so no there is no Midi CC in vst3. So the only thing I can do is wait if maybe one day this shit will get addressed in VST3 in FlowStone, or we can use the VST2 for midi, or simply link your parameters INSIDE the Daw rather than directly in the VST.
http://www.adamszabo.com/ - Synths, soundsets and music

Post

I did resist a long time because of flowstone but during the next sale a copy will be mine :-)

Post

rasmusklump wrote: Mon Jun 12, 2023 3:25 pm I did resist a long time because of flowstone but during the next sale a copy will be mine :-)
Good choice, you will have a lot of fun with it ;)
http://www.adamszabo.com/ - Synths, soundsets and music

Post

I haven't dig deeper in Viper for sweet juice so far,but will use it more this summer,cause need that Viper vibe for euro dance / house / whatever style i am cooking :)
After that,probably late autumn will make a soundset for it,following the feelings it gives me during the summer diging :):):)
Some synths are capable of diversity,other fit well specific genres,Viper seem to have both in it's dna,cause classics like Sylenth1,V-Station and Synth1 are limited in some aspects,mostly waveforms and mod matrix for more complex sounds.
The problem using too many synth is that you can lose the right feeling of the track,the right vibe...
I like to combine 2 or 3 synths as main stage and something in addition just to touch the main sound.
Probably the best way to advertise my nonlinear dynamics is to use it in a track,where to focus on the moments where it most useful and distinguish and Viper seems like proper tool for that .
Cheers :)

Post

adamtrance wrote: Sun Jun 11, 2023 11:25 pm I asked the FlowStone dev about the link IMidiLean thing linked in previous posts and this is what he had to say:

"Essentially there is no Midi-CC anymore, the Host maps the CC to a parameter and you essentially get preset param changes like as if it was automation. You can setup a midi-cc to param mapping in a plugin that the host uses by default (https://steinbergmedia.github.io/vst3_d ... pping.html). I guess the midilearn you linked to, allows to re-initialize the mapping part of the host, so the host asks the plugin again, how the default mapping should look like. However this whole system is not compatible with the way FS is setup. We would have to have a midi-cc number input directly on a preset primitive..."
That's a shame. What it obviously means is that there won't be any VST3 made in Flowstone synths which offer MIDI learn functionality, even though it's part of the VST3 SDK.

Sure, VST2 won't go away tomorrow, but, in the long run, that's a bad limitation.

Post

This is interesting. I don't currently use VST3, but what are the downsides of mapping the CC to parameters? Wouldn't it be essentially the same as MIDI-learn?

Post

chk071 wrote: Mon Jun 12, 2023 8:57 pm That's a shame. What it obviously means is that there won't be any VST3 made in Flowstone synths which offer MIDI learn functionality, even though it's part of the VST3 SDK.
I wouldnt say "never". There wasnt 64 bit in FlowStone, and then it happened. There was no VST3, and now there is. So there is always a chance, we just have to be patient and enjoy what we have right now.

izonin wrote: Mon Jun 12, 2023 9:53 pm This is interesting. I don't currently use VST3, but what are the downsides of mapping the CC to parameters? Wouldn't it be essentially the same as MIDI-learn?
Nothing... In every daw you can already link parameters to your midi controller, so its basically the same thing. The only difference is that its not the plugin that does it, its the host.
http://www.adamszabo.com/ - Synths, soundsets and music

Post

I used to have a skin that was white and brown but it's not in the factory skins. Anyone know where that was from? And is it compatible with 1.2?

This one:
Screenshot 2023-06-17 230223.png
You do not have the required permissions to view the files attached to this post.

Post

Echoes in the Attic wrote: Sun Jun 18, 2023 4:11 am I used to have a skin that was white and brown but it's not in the factory skins. Anyone know where that was from? And is it compatible with 1.2?

This one:
Screenshot 2023-06-17 230223.png
The URL for additional skins are listed on the Viper facebook page.
I will send you the link
The skins are also compatible with 1.2 surely.
Viper, Nordlead 2X, Moog Little Phatty Stage II, Synapse Orion Platinum

Post

Adam is the skin abo still compatible with 1.2 or would it hide any new buttons or controls? Also why not include in factory skins for those who don't have facebook?

Post

Echoes in the Attic wrote: Sun Jun 18, 2023 2:25 pm Adam is the skin abo still compatible with 1.2 or would it hide any new buttons or controls? Also why not include in factory skins for those who don't have facebook?
Yes, the skin is still compatible with the new version. It is not included in the factory content because I did "borrow" skin elements from the Virus plugins, and I dont want to get on their bad side, so I shared it elsewhere other than my official site. I have uploaded it to Dropbox also so you dont need facebook: https://www.dropbox.com/s/y5gts4iipjc0rhb/VirSkin.zip
http://www.adamszabo.com/ - Synths, soundsets and music

Post

adamtrance wrote: Sun Jun 18, 2023 2:34 pm
Echoes in the Attic wrote: Sun Jun 18, 2023 2:25 pm Adam is the skin abo still compatible with 1.2 or would it hide any new buttons or controls? Also why not include in factory skins for those who don't have facebook?
Yes, the skin is still compatible with the new version. It is not included in the factory content because I did "borrow" skin elements from the Virus plugins, and I dont want to get on their bad side, so I shared it elsewhere other than my official site. I have uploaded it to Dropbox also so you dont need facebook: https://www.dropbox.com/s/y5gts4iipjc0rhb/VirSkin.zip
Can you upload your win 95 skin again as well?
:hyper:

Post

rasmusklump wrote: Sun Jun 18, 2023 3:28 pm Can you upload your win 95 skin again as well?
:hyper:
sure: https://www.dropbox.com/s/spz6obuz1dgfif9/Viper95.zip
http://www.adamszabo.com/ - Synths, soundsets and music

Post

Thank you.

Post Reply

Return to “Instruments”