I have a strange tuning problem/error using zebra2 in VST3 mode with sonar X3:
I insert zebra2 as a simple instrument track in VST3 mode and record for example a bass line in d3. Right after i play the notes zebra2 is detuned to c3. Though it is written in d3 in the piano roll it sounds now in d3. I found out that
1) when I set in zebra under global the pitchbend values (up and down) from 2 to 0, no detuning.
2) when I use zebra in VST3 mode, record the bass line and plug immediately out the midi keyboard before i start the playback, the detuning does not happen. My midi keyboard is the alturia minilab.
3) when I use zebra in VST2 mode, no detuning. problem solved.
I also have the problem that I can not name my patches when I save them (Neither in VST2, nor in VST3 mode). I cant type in a name. I have to type the name I want for example in my search window in my browser, copy the name and paste it in zebra using the mouse menue.
Zebra gets out of tune - not in Demo Mode!
-
- KVRAF
- 4536 posts since 17 Jun, 2013 from very close to Paris, France
You could make a try with a few free hosts, like Cantabile Lite or Chainer or some others.
Here is a list of several VST hosts which are... all free!: No need to multiply at excess those tests, two or three are enough, but they are the good (and often the best) way to begin a diagnostic of a problem, by a so simple but so logical approach.
It is always good to have at least two or three hosts including one or two which are free. That in order to compare the behavior of your VSTs in these different environments. It is generally a very good indication (and sometimes it is THE definitive revelation for the diagnostic) for the developer to tell him "it works good with these two hosts but it works bad with that third one".
Here is a list of several VST hosts which are... all free!: No need to multiply at excess those tests, two or three are enough, but they are the good (and often the best) way to begin a diagnostic of a problem, by a so simple but so logical approach.
It is always good to have at least two or three hosts including one or two which are free. That in order to compare the behavior of your VSTs in these different environments. It is generally a very good indication (and sometimes it is THE definitive revelation for the diagnostic) for the developer to tell him "it works good with these two hosts but it works bad with that third one".
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.
-
- Banned
- 6129 posts since 9 Oct, 2007 from an inharmonious society
-
- KVRian
- 574 posts since 20 Aug, 2013
Use the VST2 version or another host and it won't happen anymore. Sonar seems to incorrectly set the pitch wheel value in VST3 on transport reset, our plugins read the values correctly. Sometime last year, one of our programmers tried to establish contact with Cakewalk in order to sort this (rather 'their') problem out, but we haven't heard back from them since. So... not really much we can do there.
Sonar is one of those hosts that "intercepts keystrokes", that means any keys you press on your keyboard are NOT forwarded from Sonar to the plugin, but Sonar reserves them for itself. So by trying to enter preset names, you're actually (probably) triggering host actions instead. I believe Sonar has a setting hidden away in its options to disable this, but I can't tell you what it's called.
Sonar is one of those hosts that "intercepts keystrokes", that means any keys you press on your keyboard are NOT forwarded from Sonar to the plugin, but Sonar reserves them for itself. So by trying to enter preset names, you're actually (probably) triggering host actions instead. I believe Sonar has a setting hidden away in its options to disable this, but I can't tell you what it's called.