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. Any suggestions?
 
 

I found something new out: When I disable in sonar in the preferences my arturia minilab in the midi outputs, no detuning.
 
Edit: At the first glance it works, but at any time (when i use some fx) the detuning suddenly happens.

Try this - go to Sonar Preferences>Project>MIDI and remove the check box for Zero Controllers When Play Stops, then click Apply.
 
I had a similar issue with Reaktor, and it was due to the above setting - from something in the particular Reaktor Ensemble that I had loaded.
 
If the above does not address your issue, you can always put the check back in the box and click Apply again to undo my suggested change.
 
Bob Bone
 

Sounds like you may have had a pitch bend event in your MIDI track you didn't know was there. Easiest way to find such a thing is using the filter options in the Event List view. 
 
Another possibility is that you've accidentally set a control to MIDI Learn. Look for a file ending in ".midimap.txt" (I forget the whole name) in the Zebra folder and delete it, which will cancel any MIDI control assignments.
 
As for the inability to type certain characters into Zebra's patch dialog, that's a longstanding issue. Somewhere on the U-He support forum at kvr there's a detailed explanation, although searching old threads there is difficult now due to the recent site makeover, making most Google results invalid.
 
It's not a problem for me because I do my patch programming in standalone, outside of SONAR. On the rare occasions when I want to save a patch inside a SONAR project, I open Notepad, type in the name there and then copy-and-paste into Zebra's dialog.

I thought there was a Give Keystrokes to Plugin command, or something like it.  It might be a button in the plugin when it opens.
 
Bob Bone
 

Yes, there is an option to give keystrokes to the plug-in. IIRC, the problem is the plug-in spawns a dialog which does not inherit the keystroke setting.

robert_e_bone
Try this - go to Sonar Preferences>Project>MIDI and remove the check box for Zero Controllers When Play Stops, then click Apply.

Thx! Now zebra works fine in VST3 mode. But what does this setting mean? Do I have some other disadvantages now?

bitflipper
Sounds like you may have had a pitch bend event in your MIDI track you didn't know was there. Easiest way to find such a thing is using the filter options in the Event List view. 
 
Another possibility is that you've accidentally set a control to MIDI Learn. Look for a file ending in ".midimap.txt" (I forget the whole name) in the Zebra folder and delete it, which will cancel any MIDI control assignments.
 
As for the inability to type certain characters into Zebra's patch dialog, that's a longstanding issue. Somewhere on the U-He support forum at kvr there's a detailed explanation, although searching old threads there is difficult now due to the recent site makeover, making most Google results invalid.
 
It's not a problem for me because I do my patch programming in standalone, outside of SONAR. On the rare occasions when I want to save a patch inside a SONAR project, I open Notepad, type in the name there and then copy-and-paste into Zebra's dialog.

Thx for your answer too! Did you mean midiassign.txt? Thats the content of my midiassign.txt:
 
"1:74=VCF1:Cut, normal, 0, Continuous7bit, Yes //Filter1:Cutoff
1:74=VCF1:Cut, normal, 0, Continuous7bit, Yes //Filter1:Cutoff
1:71=VCF1:Res, normal, 0, Continuous7bit, Yes //Filter1:Resonance
1:18=VCF5:Cut, normal, 0, Continuous7bit, Yes //Filter5:Cutoff
1:74=OSC1:WNum, normal, 0, Continuous7bit, Yes //Oscillator1:WaveWarp"

None of those would have affected pitch, so that's not your problem.
 
The zero-controllers option means all the CC values are set to zero when you stop playback. It's usually not going to cause a problem one way or the other and no big deal whether SONAR does it or not.
 
With the option turned on, it means that if you had the sustain pedal down when playback stopped, the note will stop immediately rather than sustain. Or if a note had been playing with the pitch wheel in play, it will return to its non-pitch-bent value. With the option turned off, the sustain and pitch controllers continue to be in effect. In some cases this can result in "stuck" notes, but that's about the worst that can happen.

That is generally true, and having the default set to Zero All Controllers... is fine, BUT sometimes certain presets of certain modules react to the mod wheel being set to zero, and if the mod wheel is for some reason assigned to either pitch or volume, this can and does cause weirdly hard to track down unwanted changes to the sounds.
 
In my case, I had it happen with the Reaktor module, Carbon synth, Steam Pipe ensemble.  It would change the pitch by a half-step after I would use the mod wheel and then stop playback.
 
FINDING the cause of this issue drove me nuts, until some kind soul (Billy Arnell) set me straight by suggesting I see if changing the Zero All Controllers to remove the check would fix it - and it did.  :)
 
Soooo, I pass that along, once in a while, as it sometimes IS the culprit.
 
To the OP, glad you have it working now.
 
Bob Bone