Viper｜1.2.2 update with bugfixes and new skin

[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.

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 ?

I imagine what you say is possible. I've never used JBridge before trying the demo so there's plenty of room for user error and these were all 32 bit plugins that are still running with stability in Cubase 8.5 so it seems odd.Unfortunately I imagine the Cubase 9 demo has expired so I can't try the set up again. Expiring demos can be rather annoying. Anyway that's just my little problem and Viper does seem interesting.People can always demo JBridge and Viper at the same time

Arcvidean

[adamszabo]

My plan is end if August if everything goes well, so not long now

[trusampler]

Thanks Adam

[adamszabo]

Will be interesting how it compares e.g to Spire (with the Virus TI filter).

I finally had a chance to react to this, I was away from home for a while. The infecto filter in Spire is not at all like the Virus filter, people dont even bother to compare. Here I ran the noise through the synths filters and compared them. Blue is Spire, red is the Virus, and yellow is Viper. You can see that the Virus filter falls off quicker and is 'warmer' while Spire goes out to the nyquist and thus sounds brighter.

[chk071]

The infecto filter in Spire is not at all like the Virus filter, people dont even bother to compare.

Not quite true. Here is someone who compared the Virus filter to the Spire's Infecto filter:



And, as far as i'm aware of, it was loosely modelled on the Virus filter indeed, hence the name. Just like Spire was in general loosely modelled on hardware synths like the Virus, JP-8k, but also features some stuff present in Sylenth1. Sort of a mélange of different ingredients.

I can't reproduce the stepping in that video though. I really don't know what he did wrong there to produce that. Anyway, back to Viper.

[HunterKiller]

The very bottom and the very top of the Viper filter could use more alignment to the Virus filter. However, looking good so far.

[v1o]

The very bottom and the very top of the Viper filter could use more alignment to the Virus filter. However, looking good so far.

You make it sound trivial

[HunterKiller]

You make it sound trivial

[Bump1]

SQ-80?

???

Ohhhhh NVM....that was a guess lol

I wish it was an SQ80!!!

[Chris-S]

Can it load Virus patches?

[wagtunes]

I have stayed away from this thread since the beginning because the whole thing was depressing. Was really looking forward to this. And up front, Adam, none of what I am about to say is a criticism of you at all. I've read everything you've said about what you've done and why and I agree with you 100%. However, that doesn't change some realities of life.

Quickly. I started doing PC music in order to do RFM for sale. I concentrated almost exclusively on orchestral work for cinema like projects. You know, the big booming horns and timpani stuff that litters lots of movie scores. In order to do this and make use of the top orchestral libraries (yes, did my research before I even put my PC together) I discovered that all the top libraries were 64 bit because of the massive amounts of RAM required. So I had Windows 7 64 bit installed on my brand new PC.

As time went on, I eventually abandoned the cinema stuff and went on to other things, most of which involved using VST synths. Unfortunately, I was still on my 64 bit machine using Cubase 64 bit. So almost all the 32 bit Synthedit stuff that I downloaded from the KVR database simply either didn't work at all or crashed quite often. There were a few exceptions but not many.

I bought JBridge but it didn't really help much. I guess, like you said, because these people didn't know what they were doing.

Eventually, I just gave up and got rid of all my 32 bit synths with just a couple of exceptions that, by some miracle, actually work very well. Still don't know why.

This reality for me is, I am sure, a reality for a lot of other people. And as time goes by, it is going to become a reality for a lot more people.

As much work as you've put into Viper, I want to see you get as much profit out of it as possible. You deserve. Sadly, with it being only 32 bit, you're going to lose a lot of customers, like myself, who would have jumped all over this. How many? I have no way of knowing as I haven't done any extensive research in this area. But look at almost all the major releases that have come out in the last few years. Almost every single one is 32 and 64 bit.

I'm sure this is all stuff that you know already. And I'm sure you have to be at least a little bit frustrated at the situation. That's why I said up front that I don't blame you for any of this at all. You simply made the best of a not so ideal situation.

I hope someday Viper does become 64 bit so I may purchase it, make a great library for it, and make a ton of sales for myself.

I have no doubt that when that day comes (hopefully long before I'm gone) it will be one of the top sellers out there along with synths like Sylenth1 and Synthmaster.

Good luck to you in the future.

[DPhil]

I agree with wagtunes. Long time I haven't updated my plugins, my DAW and my system to keep 32bit plugins working. But then there was the point I just had to switch. It was at the time where devs had products with at least both versions available. Meanwhile more and more abandond 32bit and go straight with 64. I never would go back to the point in time where I had to run things in parallel or bridged. Please consider a 64bit version

[AnX]

Can it load Virus patches?

I dont think it is 100% a virus clone. Its missing some stuff, so would not be practical to import patches.... correct me if im wrong...

[recursive one]

Can it load Virus patches?

I dont think it is 100% a virus clone. Its missing some stuff, so would not be practical to import patches.... correct me if im wrong...

I think Adam said here that Viper won't be loading Virus patches, partly because it misses some of the Virus features, partly because it won't always sound 100% identical at the same settings.

[AnX]

Yeah, kinda what i said