Viper｜1.2.2 update with bugfixes and new skin

[AnX]

For example...I want to run this synth in S1 Pro 64bit...how can I do that?

Buy extra software.

[LeVzi]

As appealing as this is, I am stunned native 64bit is not standard these days. 32bit plugins are virtually defunkt now. Even FL Studio that they said couldn't go 64bit , eventually did.

Using a bridge, as good as jbridge is, (Support for this has all but stopped too) it is not ideal. So I am sorry, I agree that 32bit plugins are not of interest, i'd always look at 64bit native ones ahead of these.

It's a shame because there has been a massive demand for a virus style pluin for ages, but for me, thankfully, Tone2 nailed the hypersaw sound in E2. And that's 64bit native.

[AnX]

Call out the lynch mob!!!

[Synthman2000]

Install JBridge, run JBridge, ask it to scan 32 bit Viper folder, then to create a new "X" Viper 64 bit folder located in your regular VST Plugin folder, done.

All my 32 bit plugins run perfectly in Cubase 9 bridged this way. Of course I prefer unbridged 64 bit plugins, but if Viper is 32 bit, I can live with it. JP6K is 32 bit only and I use it all the time.

Viper seems insanely good. If this can speed up things, go for 32 bit for the release, you can work on a 64 bit version next !

This is positive news.

[Armagibbon]

Call out the lynch mob!!!

Yea get some creepy ass rabbits up in here!

Wait you meant a david lynch mob right?

[Arcvidean]

Install JBridge, run JBridge, ask it to scan 32 bit Viper folder, then to create a new "X" Viper 64 bit folder located in your regular VST Plugin folder, done.

All my 32 bit plugins run perfectly in Cubase 9 bridged this way. Of course I prefer unbridged 64 bit plugins, but if Viper is 32 bit, I can live with it. JP6K is 32 bit only and I use it all the time.

Viper seems insanely good. If this can speed up things, go for 32 bit for the release, you can work on a 64 bit version next !

I'm sorry to report that none of mine did with the jbridge demo in the Cubase 9 demo, so is it hit and miss?

Arcvisean.

[DJErmac]

Well, the only thing I've not specified is this : I use Windows 8.1 Pro 64bit. I canno't confirm it would work with Windows 10. Maybe that's the difference ?

But regarding my experience, 32 bit bridged plugins are not a problem AT ALL under Cubase 9. You need JBridge, end of story. It's an extra step and everybody would love to bypass it, but when there's no way around, then go for it, it works !

[Arcvidean]

Well, the only thing I've not specified is this : I use Windows 8.1 Pro 64bit. I canno't confirm it would work with Windows 10. Maybe that's the difference ?

But regarding my experience, 32 bit bridged plugins are not a problem AT ALL under Cubase 9. You need JBridge, end of story. It's an extra step and everybody would love to bypass it, but when there's no way around, then go for it, it works !

I'm on Windows 10. All my 32 bit plugins were converted to 64 bit by JBridge but were blacklisted by Cubase 9. I was rather disappointed and won't be updating to Cubase 9.

Arcvidean.

[walker1]

Ok, upon release Viper won't do everything what Virus does but actually about 70% of the unique Virus sound is in its fiters and effects which seem to be properly modelled. These pads, plucks, fat basses and floating arpeggios Virus is known for are mostly based on its VA oscillator.

Yes, Virus C which was perhaps the most iconic synth at the time, it had only the classic oscillators, yet it was the most popular legendary hardware synth. Viper has nearly everything that a Virus C has,but has the Hypersaw too (which came with the Virus Ti), and more features are planned after 1.00, but I had to draw the line somewhere, I could develop it forever without ever releasing it.

I think it's good that someone really wants to help musicians make Music. If Viper sounds good then it will be a good addition and I gladly pay the price Adam deserves a medal.

[Synthman2000]

In Cubase you can reactivate them at your own risk. Not something I have tried, despite v9 not officially supporting 32 bit if I understand correctly there is a way to do it as someone seems to have on here using J Bridge, I think it is documented on Steinbergs forum. But it seems somewhat risky to do something that can rock the boat for stability after efforts have been made to try and root out problems.

https://helpcenter.steinberg.de/hc/en-u ... r-Cubase-9



Although the entire point of Cubase going 64 bit is for greater stability if you use 8 and it is fine then there is no real need to upgrade. I can only account for my own experiences, v9 is rock solid.

[kmonkey]

jBridge is by far most compatible bridge ever! It is not hit and miss, some people even use it to run buggy 64 bit plugins (because it has plenty of interesting options like run plugin in individual thread, GUI refresh options etc.etc.).

ATM i use jbrdige to run over 35 various plugins with ZERO crashes. VAZ Modular, all Variety of Sound plugins etc.etc.etc.

Highly recommended 15 EUR and i am sure Viper will run in it like a breeze. There is literally no difference (once when set up properly) in running 32 bit plugins in 64 bit host.

I even run 32 bit plugin version of products which are available as 64 bit because 64 bit version had iLok compatibility bug in Ableton and Studio One. Even developers recommended running these plugins as 32 bits overbridged in to 64 bit in these DAWs. Same CPU usage, same sound, same presets management. Everything just works.

Later when one of plugins was fixed (it was ilok error) and could run native 64 bit version without overbridging i simply installed it and session recall works like nothing happened - the point is jBrdige is awesome.

Surely it will work with Viper just the same thing like Viper was 64bit - minus 2++gb RAM access which you don't need for Viper anyway.

[Arcvidean]

In Cubase you can reactivate them at your own risk. Not something I have tried, despite v9 not officially supporting 32 bit if I understand correctly there is a way to do it as someone seems to have on here using J Bridge, I think it is documented on Steinbergs website. But it seems somewhat risky to do something that can rock the boat for stability after efforts have been made to try and root out problems.

https://helpcenter.steinberg.de/hc/en-u ... r-Cubase-9



Although the entire point of Cubase going 64 bit is for greater stability if you use 8 and it is fine then there is no real need to upgrade. I can only account for my own experiences, v9 is rock solid.

I tried to reactivate them but Cubase 9 refused, then I gave up.Not had any problems with 32 bit plugins in Cubase 8.5

Arcvidean.

[Synthman2000]

Sure, ultimately you have to try it and see if it works for your system. Glad it works for you. I have J Bridge here... I used it to run a few memory hog synths when using a 32bit DAW. Unfortunately when I got close to memory limits 3.5GB+ approx I had unpredictable and severe problems.

It may relate to session sizes (I am at 68 stereo track count, 100+ VSTi (30 VSTi) and VST effects/processing/automation/audio tracks/sampler tracks... from multiple developers, 40-50pct CPU here and am about 1/2 way through this tune) It may depend on what you are doing or specific plug ins, or maybe just the Cubase version I was running previously as to how successful bridging is.

I could not pin down the causes I am just glad I have seen the back of the issues. I make sure I finish my productions. I am not running a couple of synths in a 4min session. That is not to be condescending as track count has no bearing on quality or end result in any way just stating how my projects are set up and what my goals are for stability/performance reference point.

[DJErmac]

In Cubase you can reactivate them at your own risk. Not something I have tried, despite v9 not officially supporting 32 bit if I understand correctly there is a way to do it as someone seems to have on here using J Bridge, I think it is documented on Steinbergs website. But it seems somewhat risky to do something that can rock the boat for stability after efforts have been made to try and root out problems.

https://helpcenter.steinberg.de/hc/en-u ... r-Cubase-9



Although the entire point of Cubase going 64 bit is for greater stability if you use 8 and it is fine then there is no real need to upgrade. I can only account for my own experiences, v9 is rock solid.

I tried to reactivate them but Cubase 9 refused, then I gave up.Not had any problems with 32 bit plugins in Cubase 8.5

Arcvidean.

Did the plugin manager see 64 bit plugins when they were blacklisted ?

The reason I'm telling you this is because the last time I tried to reactivate a plugin that failed to reativate, it was my mistake : it was a 32 bit file. So, when you tried to bridge your plugins, maybe that was the wrong folder after all. This already happened to me several times when using JBridge.

Since you have to keep the original 32 bit folder and the new 64 bit folder when you use JBridge, make sure Cubase only scanned the folder that contained the 64 bit files created by JBridge, or they will be blacklisted for sure as the original files aren't modified. Maybe Cubase scanned the folder that contained the original 32 bit files you installed, and you forgot to add the folder that contained the newly created 64 bridged files after that, can't be ?

[trusampler]

How close are we to the demo release, then all the talk can stop about the 32 bit stuff,and judge it for the sound. If it sounds great and is stable,then so be it.