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

jojkobojko wrote: Sat Feb 12, 2022 11:15 am Yesterday I was a little bored, so I made this skin for Viper. Enjoy it guys! :wink:

https://www17.zippyshare.com/v/plTPn5pl/file.html
When I first clicked on download it opened up some crap website, then at 2nd attempt it worked. Just tried the skin, this is excellent, well done. So pleasing and easy for the eyes.

Post

I do Hear a Difference in Sound Compared to Virus C.
The Virus C Sounds Darker and The Oscillators sounds More Glued together While The Viper Sounds More Nasal and Fizzy and Less Glued together on some presets when Comparing Presets.

Could this be because i am Running Viper at 48Khz or does Viper support other Samplerates than 44.1Khz?
Last edited by D-Fusion on Sun Feb 13, 2022 10:28 am, edited 1 time in total.

Post

Edit: nevermind

Post

I'd be interested if those differences could also be heard if one wouldn't know what's the virus and what's viper...

Post

chk071 wrote: Sun Feb 13, 2022 10:27 am Or the difference between the DAC of the Virus, and the DAC of your audio interface.
No it is not he Dac since i am using the DSP Virus C Version So both are vst.
The weird thing is that Some of them are spot on so maybe it is that some of the presets don't set up the Effects and some modulation properly 1:1 Because some of the presets are old.

Post

Did some More Testing and the Virus TI Presets Import are much Closer than the Virus C Patches when i play the same patches on the C and the Imported TI Patches with the same name.

So i Guess this is more of a TI Virus Than C and that there are some differences in the Bank files between those 2.

Post

Yes I did some tests as well. I used the virus c rom in the emulator and the demo version of viper and Adams demopatches. I loaded the fxp bank into viper and the mid bank in the virus c rom. There were some differences and I have to admit that I liked viper more in this test. Don't know if it sounds more like the TI or if the virus c is more like the real thing. But I don't care that much. I think I will get viper during the next sale.

Post

rasmusklump wrote: Sun Feb 13, 2022 2:06 pm Yes I did some tests as well. I used the virus c rom in the emulator and the demo version of viper and Adams demopatches. I loaded the fxp bank into viper and the mid bank in the virus c rom. There were some differences and I have to admit that I liked viper more in this test. Don't know if it sounds more like the TI or if the virus c is more like the real thing. But I don't care that much. I think I will get viper during the next sale.
It is not a bad Buy ;)
I ended up buying it a week ago since he has support to do it from Access Music and i liked the sound of it.
It sounds awesome even when it is not 100% on all presets and i was a little bored here so i had to try some tests here to kill some time :)

My tip is to hunt down Free Ti Banks instead of the B or C Banks since they get closer when they are imported.

Post

With the demo I have to choose my favorite skin each time. Does the regular version keep the skin once chosen?

Post

rasmusklump wrote: Tue Feb 22, 2022 11:53 am With the demo I have to choose my favorite skin each time. Does the regular version keep the skin once chosen?
It seems Viper it cannot save your selected skin automatically on your system so you have to do it manually. Go to the folder where you have the Viper.dll file, and there create a new text file called "guiconfig.txt"

then write on two separate lines, one is the the scaling (1 is 100%) and on the second line the name of the skin file for example Alien:

1
Alien.png

then save it. Next time you open viper hopefully it will load the skin upon loading.
http://www.adamszabo.com/ - Synths, soundsets and music

Post

Thanks very much.

Post

I have noticed that i get Cpu overload when browsing presets in Cubase Elements 11 and Sometimes it Also brings down Studio one V5.5 When Browsing Presets.

This makes me a bit Worried about using it since things like this happens without any Warning except for the Red Overload Dot in the Cubase 11 that happens everytime i change a preset.

Post

adamtrance wrote: Tue Feb 22, 2022 3:11 pm
rasmusklump wrote: Tue Feb 22, 2022 11:53 am With the demo I have to choose my favorite skin each time. Does the regular version keep the skin once chosen?
It seems Viper it cannot save your selected skin automatically on your system so you have to do it manually. Go to the folder where you have the Viper.dll file, and there create a new text file called "guiconfig.txt"

then write on two separate lines, one is the the scaling (1 is 100%) and on the second line the name of the skin file for example Alien:

1
Alien.png

then save it. Next time you open viper hopefully it will load the skin upon loading.
Thanks, it worked.
But I think it is a bad idea to let a plugin write stuff in program files as that's the place plugins are mostly written. This often can cause problems.
Can you please tell me what number 125 % size is?
Thanks in advance

Post

125% should be 1.25

the reason your system could not write can be the system permissions of the DAW you loaded Viper in
I wonder what I want in here
-my site is gone and music a mess

Post

D-Fusion wrote: Wed Feb 23, 2022 9:59 am I have noticed that i get Cpu overload when browsing presets in Cubase Elements 11 and Sometimes it Also brings down Studio one V5.5 When Browsing Presets.

This makes me a bit Worried about using it since things like this happens without any Warning except for the Red Overload Dot in the Cubase 11 that happens everytime i change a preset.
What do you mean "brings down Studio one"? Do you mean it crashes? If it does, please provide more info in which preset exactly so I can check. Regarding the overload, it happens because Viper needs to clculate a ton of things when updating all the parameters at once. This is a FlowStone thing (the development platform), so when you switch presets it has to recalculate the entire signal path again, and you get a 1 sample higher cpu spike. I havent found a solution for this yet but I am aware and trying to find a fix. I did try other things but it introduced other problems, so I had to go with the "less bad" one. The solution in the meantime is to increase your buffersize, or dont play viper while switching presets.

rasmusklump wrote: Wed Feb 23, 2022 3:33 pm Thanks, it worked.
But I think it is a bad idea to let a plugin write stuff in program files as that's the place plugins are mostly written. This often can cause problems.
Can you please tell me what number 125 % size is?
Thanks in advance
No, Viper does not write anything in the program files folder. Viper saves the files in your AppData folder and that is in your My Documents, which also has your windows username in the path. There is a bug with FlowStone that it doesnt like some certain special characters so if your windows username has non english characters like öäëá or something, then the path gets broken and Viper cannot save anything. Thats why I made a workaround for those few people that cannot get it working, so you can fix it by putting the files where the Viper.dll is.
http://www.adamszabo.com/ - Synths, soundsets and music

Post Reply

Return to “Instruments”