KVR Audio

adamszabo · Post by **adamszabo** » Tue Oct 04, 2016 11:58 am

recursive one wrote:As Adam said earlier, the synth is going to have only two oscillator modes, classic (basically it's some kind of advanced VA where you can morph between saw, pulse with PWM and sine, where sine may be replaced by complex waveforms) and hypersaw. Virus TI also has several wavetable oscillator modes, where you can do some really unique things to wavetables, I think these are improssible to model if you don't have the original code and the original wavetables.

Its important to mention that only version 1 will have two osc modes. I am planning to add more ones. I think I have an idea on how to do the rest of the oscs, but if I keep adding features now, then the synth will never be done.

Nielzie · Post by **Nielzie** » Tue Oct 04, 2016 12:33 pm

adamtrance wrote:I spent a lot of time optimizing it as much as I could, while keeping a good balance between cpu usage and a good sound. It should be around the same as massive, in most cases less. Of course, the cpu meter will still rise if you use 8 unison, 64 voices, all the effects, and long release times.

Ok, that's good then, thanks for the info

One other question out of interest. Why did you choose to use FlowStone as a framework for your own coded modules instead of something like, say.. JUCE or something?

SayersWeb · Post by **SayersWeb** » Tue Oct 04, 2016 6:19 pm

recursive one wrote:
phreaque wrote: can't be any possibility to load original Virus presets? Perhaps you can talk to Access regarding this issue?
I guess, this is the thing which has done kinda bad service to DIscoDSP Discovery. It loads Nordlead presets but apaprently interprets them somehow wrong and therefore people talk about it as a failed NL emulation, while in fact it is just a good NL-inspired synth.

I think in the present case the preset import will not make much sence since the plugin doesn't have the original Virus wafeforms, some of the oscillator modes are missing, something may be not exactly modelled, etc.

Maybe offer a patch converter with the disclaimer that patches will not sound exactly the same. I think it would be a huge selling feature since there are so many Virus patches available. I have a Virus TI desktop and would consider buying Viper if I could load up Virus patches. I manage to overwork the Virus on some tracks and would appreciate having a VST to take some of the load.

DiscoDSP not only sounds different, it only sounds good, but not great to my ears. I have it, and a Nord Rack 2. Have never used DiscoDSP in a track.

adamszabo · Post by **adamszabo** » Tue Oct 04, 2016 6:35 pm

Nielzie wrote:One other question out of interest. Why did you choose to use FlowStone as a framework for your own coded modules instead of something like, say.. JUCE or something?

Well, I never in my life wanted to make synths. I had absolutely no idea how to do them, and 6-7 years ago when I got into it, there were no juce tutorials. I remember trying juce once... I couldnt even figure out how you export a vst. So I gave up. Then FL Studio partnered with FlowStone (at the time SynthMaker), and it was exactly the application I was dreaming of. I could write assembly, optimize and write my own code, and I dont have to waste time on technical issues like how can I draw a wave graph on the gui. SynthMaker was perfect, and ive been using it for 6-7 years now, I know it so well that I managed to create this big achievement.

evilplazma · Post by **evilplazma** » Tue Oct 04, 2016 7:11 pm

people are gonna love this beast!

Elektronisch · Post by **Elektronisch** » Wed Oct 05, 2016 7:14 am

As i understand because this is made with Flowstone there will never be 64bit version?

keel · Post by **keel** » Wed Oct 05, 2016 7:30 am

Elektronisch wrote:As i understand because this is made with Flowstone there will never be 64bit version?

Win 32 bit ONLY, and price will be $100

adamszabo · Post by **adamszabo** » Wed Oct 05, 2016 9:09 am

keel wrote:Win 32 bit ONLY, and price will be $100

Yes, it is known to man that anything in 32 bit is automatically crap!

(internet logic...)

Elektronisch · Post by **Elektronisch** » Wed Oct 05, 2016 9:12 am

adamtrance wrote:
keel wrote:Win 32 bit ONLY, and price will be $100
Yes, it is known to man that anything in 32 bit is automatically crap! (internet logic...)

No, but its not very efficient to use via bridges. IL said themself that 32bit plugins in 64 fl studio enviroment will likely use more CPU recources. Also not all DAWs support briding (looking at Ableton, Studio One).

Kumi_27 · Post by **Kumi_27** » Wed Oct 05, 2016 9:18 am

Studio One works with jBridge, for example.

Some "x64" plugins have native 32->64 wrapper built in, so they're not quite 64 bit inside.
Maybe it's some solution to all these "64 bit only" people?
But I don't know, if it's possible for Adam to code something like that.

phreaque · Post by **phreaque** » Wed Oct 05, 2016 9:45 am

The development of 32-64 bridging should be handled to the DAW makers I believe..
For me I'm still using 32 DAWs

Kumi_27 · Post by **Kumi_27** » Wed Oct 05, 2016 9:59 am

phreaque wrote:The development of 32-64 bridging should be handled to the DAW makers I believe..

Sonar, Reaper, Mixcraft or Cubase have built-in bridges. Better or worse.
But some DAWs don't have - and some even don't plan to have in the future.

I was genuinely surprised, when Studio One x64 didn't load any 32 bit plugins. Had to google if I'm doing something wrong, but no... it's a feature

recursive one · Post by **recursive one** » Wed Oct 05, 2016 10:14 am

Well, from my perspective:
I'm addicted to Virus sound but I find the workflow with native plugins much more convenient even despite I have TI working more or less flawlessly. So I'll surely buy Viper if it sounds reasonably close and if I'm able to run it via Jbridge without major issues. USD 100 seems ok for me.

But from the "state of art plugin market" perspective:
- Some DAWs don't have a bridge (Studio One), which means that a user will have to buy a third party bridge or switch to the 32 bit DAW version facing the memory limtations;
- Some DAW developers are ditching 32 bit support at all (no bridges and no 32 bit versions) - Cubase;
- Some of the (potentially competing) plugins are going to be released as 64 bit only - Avenger;
- Some of the potential customers never owned a Virus and feel no magic in this word, for them it would be "yet another va/hypersaw synth" so if they will have to jump through hoops to run it or even to demo it they'll most probably won't even bother.

So well, the tendency of 32 format to become obsolete in next few years seems clear. So making the plugin future-proof should generally be a good idea. I think if it is released as x32 only there may be some sales but at least making an iternal 32-64 bridge, like in Renegade perhaps, may increase the sales considerably.

phreaque · Post by **phreaque** » Wed Oct 05, 2016 10:26 am

Kumi_27 wrote:
phreaque wrote:The development of 32-64 bridging should be handled to the DAW makers I believe..
Sonar, Reaper, Mixcraft or Cubase have built-in bridges. Better or worse.
But some DAWs don't have - and some even don't plan to have in the future.

I was genuinely surprised, when Studio One x64 didn't load any 32 bit plugins. Had to google if I'm doing something wrong, but no... it's a feature

Indeed seems it is a feature to keep things organized..

Add to the list, IL FL Studio as well.. They were the first to add native bridging.

Ableton should really consider adding it. Since the 9.5 I never used Live, it is getting slower and slower. Although I use the 32 bit version to deal with my 32 bit vsts. But seems it tend to deal faster with 64 bit.

TheKid · Post by **TheKid** » Wed Oct 05, 2016 10:31 am

Dying technology? No Mac release possible? Being forced to use a bridge? For 100$? Wow.
I'm glad some DAWs don't support bridging and more and more developers drop 32bit stuff. It's about time 32bit becomes obsolete (just like their 32bit-windows-only-payware-"developers").

Viper｜1.2.2 update with bugfixes and new skin