Viper｜1.2.2 update with bugfixes and new skin

[kmonkey]

I'll repeat this every then for less gifted people which still in 2018 can not comprehend: there is a quite universal solution for 32 bit plugins in 64 bit DAW. It is called jBridge, cost 15 eur, take 10 min to set up and around 5 clicks. Works perfect.

[colibri]

No piece of software is perfect, but why don't those who seem only to be capable of complaining

a) find out whether you are within the target group of this synth

b) ACTUALLY try out the demo, including own sound design, that is

c) read the manual

...and finally politely express your thoughts, suggestions, potential issues (with proper reporting of system specs)...

From all that I know Adam has invested a LOT of work, is eager to further improve this release and does not deserve disrespectful bashing certain KVR members seem to love.

[Lorenz @ XARC Mastering]

Just ignore those kind of people that think it´s no work to create something like this and let them use their superb free Reaktor ensembles, easy Even with no custom DSP coding it takes a LOT of work to assemble this in Flowstone to that degree of seriously sounding very close to a Virus (and I am sure because of that that custom DSP was involved). And even with the best synth you will always have someone complaining, you simply can´t make everyone happy and trolls will always be there, that´s what I am trying to say

About 64bit, it will NOT sound better if it was in 64bit instead of 32bit, it just means that the plugin can address > 2GB of RAM, which is not needed for this one at all as it does not deal with samples and just small single cycle wavetables, where one instance will barely take > 100MB at the most. And then there are good 32bit -> 64bit wrappers that are really stable and have already been mentioned + many DAWs support both 32bit and 64bit out of the box with their own super-stable bridges which can easily be used even live (as I do too) (Reaper, Renoise).

Keep up the good work Adam, ignore the trolls, focus on the people that support you and spend your energy on improving the synth or making music - life´s to short to waste it with these "energy suckers".

[fdigl]

isnt flowstone like reaktor?
i mean what i read a little its sound like .
so its ridiculous to ask such a price and you are not coding the synth.
you have hundered of free reaktor ens.

Aaaand you have officially lost credibility. Flowstone is not like Reaktor, that's like saying just cause Cubase and Audacity both deal with audio they're pretty much the same thing. Totally different ballparks here.

Maybe you should do a bit more research before spewing nonsense out of your mouth for once?

[Amram]

isnt flowstone like reaktor?
i mean what i read a little its sound like .
so its ridiculous to ask such a price and you are not coding the synth.
you have hundered of free reaktor ens.

Aaaand you have officially lost credibility. Flowstone is not like Reaktor, that's like saying just cause Cubase and Audacity both deal with audio they're pretty much the same thing. Totally different ballparks here.

Maybe you should do a bit more research before spewing nonsense out of your mouth for once?

i leave u to stick driving in a ford inside but outside look lamburgini :hihi

edit:
"don't prove a clown because he will hate you , prove smart he will love you".

[AnX]

isnt flowstone like reaktor?
i mean what i read a little its sound like .
so its ridiculous to ask such a price and you are not coding the synth.
you have hundered of free reaktor ens.

Aaaand you have officially lost credibility. Flowstone is not like Reaktor, that's like saying just cause Cubase and Audacity both deal with audio they're pretty much the same thing. Totally different ballparks here.

Maybe you should do a bit more research before spewing nonsense out of your mouth for once?

i leave u to stick driving in a ford inside but outside look lamburgini :hihi

It's "lamborghini"... try learning how to spell.

[HcDoom]

Amram is just trolling, ignore him. Synth sounds great!!!

[tristan-]

Very nice! I really like the demo so far. Great GUI! GOOD JOB ADAM!

I really think its tad difficult nowadays to "sell" a 32bit plugin. I think I'll get it nevertheless but still, the fact its not compatible with today's systems right out of the box might interfere with its possibility for great success.

[chk071]

I've waited for the release und really would buy it. But then I've found out: it's a 32bits plugin !!! Sorry, but for me it's inaceptable. I don't want to bridge any VSTi instrument. When a 64bit version is on the market I will buy it but not now.

You're acting like you've just find this out, even though he made it clear from the beginning it will be released as a 32-bit plugin at first. Besides, did you even read the page because it clearly says a 64-bit version is planned.

Well, not everyone reads all 50 posts of this thread, or the OP, before he posts here. Besides, i totally agree with him. But, it's true that this has been discussed to the max here, and needs no further discussions.

Regarding the Flowstone thing: The way i understood it, the sound producing, and sound mangling elements of this synth have been coded by Adam himself, and Flowstone is rather the framework for stuff like GUI drawing, host integration, and finally compiling the plugin formats. So, like the first versions of Sylenth1, before Lennard ported it from SynthEdit. I still think the way Flowstone, SynthEdit, or also Reaktor (AFAIK) work seems to be misunderstood. Yes, you can build a synth completely without coding your own stuff, but, you can also go as deep as you can get, and code your own modules, and stuff. There's basically no difference between a "natively" coded plugin, and a Flowstone or SynthEdit plugin. Anything could be coded in it.

[adamszabo]

isnt flowstone like reaktor?
i mean what i read a little its sound like .
so its ridiculous to ask such a price and you are not coding the synth.
you have hundered of free reaktor ens.

Best post of the day, love it

Here is a screenshot of the filter in Viper, I am truly sorry I can only code in Ruby and Assembly, and they are not "coding" enough for you.

On to the topic, Adam, can you add Patch sorting by Name in the browser ?

I have no idea, I havent checked yet but its a good idea! I also thought about dragging preset order around in the browser but I havent had time to think about this yet.

did you even read the page because it clearly says a 64-bit version is planned.

planned , you can plan something also 5 years and after the 5 years you can make a plan for another 5 years .

planned does not mean that it will happen anytime soon .

I posted a screenshot of the 64 bit Viper running on my computer, so please check it and stop spreading rumors around that it will come in 5 years.

I really think its tad difficult nowadays to "sell" a 32bit plugin. I think I'll get it nevertheless but still, the fact its not compatible with today's systems right out of the box might interfere with its possibility for great success.

I am 100% fully aware of that, but I had to make a choice. Either everyone can wait many months more until I finish the 64bit as well, or I release the 32bit first and later the 64. I went with the second option.

Regarding the Flowstone thing: The way i understood it, the sound producing, and sound mangling elements of this synth have been coded by Adam himself, and Flowstone is rather the framework for stuff like GUI drawing, host integration, and finally compiling the plugin formats. So, like the first versions of Sylenth1, before Lennard ported it from SynthEdit. I still think the way Flowstone, SynthEdit, or also Reaktor (AFAIK) work seems to be misunderstood. Yes, you can build a synth completely without coding your own stuff, but, you can also go as deep as you can get, and code your own modules, and stuff. There's basically no difference between a "natively" coded plugin, and a Flowstone or SynthEdit plugin. Anything could be coded in it.

Yes, thats exactly the case with Viper. FlowStone is just a framework to host my own code, every line of code is written from scratch, people assume I just connected some stock modules and shit together and bam, €89 synth, how dare i!

[tehlord]

To be honest, except for "i play a whole song with one note" excessive sound designer patches, i don't see much use for layers in a synth at all. In a track context, it surely won't matter if you use multiple instances, or multiple layers. No offense intended, just a different opinion here.

As a sound designer, I agree.

I would much rather have more oscillators in a single layers (with flexible routing) than less oscillators, but multiple layers of them.

Pads are one reason I like layers.

You don't need layers if you have enough oscillators and decent routing.

[Arcvidean]

I get a blank screen in Cubase 8.5 Windows 10 64 bit, bridged by Cubase 8.5. I was able to play the factory presets in the Cubase drop down menu, it sounded very nice. However further explorations were inhibited by the blank GIU. I have had no other problems with 32 bit plug ins which I still run.

Arcvidean

[adamszabo]

Ok thank you, I shall investigate

[Arcvidean]

Thanks, that would be nice.

Arcvidean.

[Touch The Universe]

To be honest, except for "i play a whole song with one note" excessive sound designer patches, i don't see much use for layers in a synth at all. In a track context, it surely won't matter if you use multiple instances, or multiple layers. No offense intended, just a different opinion here.

As a sound designer, I agree.

I would much rather have more oscillators in a single layers (with flexible routing) than less oscillators, but multiple layers of them.

Pads are one reason I like layers.

You don't need layers if you have enough oscillators and decent routing.

What's great about layers also is the extra envelopes and lfo's, as well the extra oscillators. I too like the layers approach particularily for pads, but one can also get pretty creative with filters and resonance levels across layers for leads and basses if they can be tied to a master source like the modwheel or a macro.