sounds like same issue(?) what I had in FL. Load Viper, play default sound, load factory bank 2 or 3 "on the fly" and Viper says click and sound goes only in left channel. Right channel output goes red and stays there all the time, but no sound. Already reported this here.PiotrPochwat wrote:
1.Sometimes, when I turn on delay in fx section, audio input in viper is crashed, and work only one chanel (right or left) (the same issue is in the reverb) or not play right and left channel and I must reload plugin.
Viper｜1.2.2 update with bugfixes and new skin
-
- KVRian
- 893 posts since 27 Oct, 2004 from Inside the kick drum
-
- KVRist
- 65 posts since 27 Sep, 2010 from European Union
Yes.keel wrote: sounds like same issue(?) what I had in FL. Load Viper, (...) and Viper says click and sound goes only in left channel. Right channel output goes red and stays there all the time, but no sound. Already reported this here.
-
- KVRian
- Topic Starter
- 1238 posts since 29 Sep, 2004
Ok, which version of cubase is that and is it the 32 bit or 64 bit cubase?
http://www.adamszabo.com/ - Synths, soundsets and music
-
- KVRist
- 65 posts since 27 Sep, 2010 from European Union
Cubase 4 32 bit.
-
- KVRian
- Topic Starter
- 1238 posts since 29 Sep, 2004
I updated the demo version, I havent done it yet with the full one yet, can you both try to download the demo and check if this issue happens with that?
http://www.adamszabo.com/ - Synths, soundsets and music
-
- KVRian
- 603 posts since 28 Jul, 2003 from Poland
I've checked both 32 and 64 bit versions in Studio One Pro 4 and delay problems seem not existant here. Looks like Cubase (or FL) related.
-
- KVRAF
- 4536 posts since 17 Jun, 2013 from very close to Paris, France
... or perhaps another common point which is not yet appearant.Roman Wisniak wrote:I've checked both 32 and 64 bit versions in Studio One Pro 4 and delay problems seem not existant here. Looks like Cubase (or FL) related.
Build your life everyday as if you would live for a thousand years. Marvel at the Life everyday as if you would die tomorrow.
I'm now severely diseased since September 2018.
I'm now severely diseased since September 2018.
-
- KVRist
- 65 posts since 27 Sep, 2010 from European Union
adamtrance wrote:I updated the demo version, I havent done it yet with the full one yet, can you both try to download the demo and check if this issue happens with that?
Adam. Demo from this site?
http://www.adamszabo.com/viper/
or demo from the link/the email?
-
- KVRian
- Topic Starter
- 1238 posts since 29 Sep, 2004
The Demo from here: http://www.adamszabo.com/viper/ the link in the email is the full version
http://www.adamszabo.com/ - Synths, soundsets and music
-
- KVRist
- 65 posts since 27 Sep, 2010 from European Union
Ok. Tested and problem with delay and cpu also appear.
-
- KVRian
- Topic Starter
- 1238 posts since 29 Sep, 2004
Do you think you can make me a video because I am pressing the delay on/off as fast as I can but It doesnt get the error for me. Maybe im doing something wrong
http://www.adamszabo.com/ - Synths, soundsets and music
-
- KVRist
- 65 posts since 27 Sep, 2010 from European Union
I have a idea. Please load my preset and midi file in Your DAW and press play. 15 seconds after viper finished plays the midi file, CPU spontaneously is increases. I have core 2 duo, so in your computer with better processor, cpu jump it must be proportionally less than im my computer.adamtrance wrote:Do you think you can make me a video because I am pressing the delay on/off as fast as I can but It doesnt get the error for me. Maybe im doing something wrong
I send the password for the file in a private message
You do not have the required permissions to view the files attached to this post.
Last edited by PiotrPochwat on Wed Jun 06, 2018 7:41 pm, edited 2 times in total.
-
- KVRist
- 65 posts since 27 Sep, 2010 from European Union
Adam
*The cpu jump (15 seconds after viper plays the midi file) is little smaller than the CPU usage when the viper plays the melody. But it is.
*The cpu jump (15 seconds after viper plays the midi file) is little smaller than the CPU usage when the viper plays the melody. But it is.
-
- KVRist
- 137 posts since 3 Aug, 2016 from Germany, Munich
Hi,
I'm demoing version 1.0.2 (64 bit) on Cubase 8.5.30 (64 bit) (Win7) and have a strange problem...
I can
- open an empty project and browse through the presets
- let Cubase play notes I set manually in parts I add to the Viper-track
but I can not
- add a new Viper-track to my existing project and copy any of the existing parts to the Viper-track (to see how they sound with Viper)
- import one single track from the existing project into an empty project with one Viper-track and move the imported parts to the Viper-track
In both cases Cubase crashes and I do not understand why. There are no information in these parts except notes. No MIDI CCs, no automation, nothing.
This problem did not occur when I demoed the 32-bit version. In fact, my existing project already had one Viper-track and it worked fine. After updating to 64-bit, this project crashes if I don't delete the Viper-track. I hope, I could explain myself...
I'm demoing version 1.0.2 (64 bit) on Cubase 8.5.30 (64 bit) (Win7) and have a strange problem...
I can
- open an empty project and browse through the presets
- let Cubase play notes I set manually in parts I add to the Viper-track
but I can not
- add a new Viper-track to my existing project and copy any of the existing parts to the Viper-track (to see how they sound with Viper)
- import one single track from the existing project into an empty project with one Viper-track and move the imported parts to the Viper-track
In both cases Cubase crashes and I do not understand why. There are no information in these parts except notes. No MIDI CCs, no automation, nothing.
This problem did not occur when I demoed the 32-bit version. In fact, my existing project already had one Viper-track and it worked fine. After updating to 64-bit, this project crashes if I don't delete the Viper-track. I hope, I could explain myself...
-
- KVRer
- 5 posts since 1 Jan, 2018
Adam, good to hear you have taken care of the audio glitching on patch changes!
Also sounds like the over-all volume levels are really high in relation to all other VST's on my system. No show stopper, but seems to stand out as something to address in the future.
Chris
Also sounds like the over-all volume levels are really high in relation to all other VST's on my system. No show stopper, but seems to stand out as something to address in the future.
Chris