u-he

liars&ashes · Post by **liars&ashes** » Fri Jan 26, 2007 12:39 am

raikard233 wrote:Check the midiport input on the right high corner of the wrapper.
Be sure that is set to --- (no input).
Sometimes i use a midiout channel with the midi out port set to the same value of the midi in port of a wrapped multipart synth channel.

Can you send me the .flp file?
I can try to see if the problem remain on my pc and if i can resolve.

----Having the midi port set at -- didn't help. Pm me your email and I'll send you the .flp file. Thanks.

Jeff

Urs · Post by **Urs** » Fri Jan 26, 2007 2:30 am

First off, it sounds like an accidental MidiLearn. Quit the host, delete all com.u-he.Zebra2.midimap.txt you can find, launch host and see what happens.

Another idea... have you loaded a .tun file? (Sounds stupid, but could be)

Later,

Urs

liars&ashes · Post by **liars&ashes** » Fri Jan 26, 2007 3:41 am

----I found this one 123=OSC1:Dtun //Oscillator1:Detune and a VCA one and 2 others. Deleting all 4 of them seemed to solve the problem. However, how can I keep that from happening again ? Like why were those there to begin with ?

Jeff

Urs · Post by **Urs** » Fri Jan 26, 2007 11:52 pm

liars&ashes wrote:----I found this one 123=OSC1:Dtun //Oscillator1:Detune and a VCA one and 2 others. Deleting all 4 of them seemed to solve the problem. However, how can I keep that from happening again ? Like why were those there to begin with ?

Jeff

My plugs used to activate MidiLearn just by a right-click on a knob. So, right-click and turning ModWheel is a quite easy way to midilearn a knob, even without noticing.

So, since Z2.1 there's always a contextual menu. You have to make the choice before MidiLearning which should mostly prevent any unaware assignments... somewhen later this year I'm gonna add yet another thing to prevent this while at the same time extending the functionality of Midi CC assignments...

Later,

Urs

liars&ashes · Post by **liars&ashes** » Sat Jan 27, 2007 12:40 am

Urs wrote:My plugs used to activate MidiLearn just by a right-click on a knob. So, right-click and turning ModWheel is a quite easy way to midilearn a knob, even without noticing.

So, since Z2.1 there's always a contextual menu. You have to make the choice before MidiLearning which should mostly prevent any unaware assignments... somewhen later this year I'm gonna add yet another thing to prevent this while at the same time extending the functionality of Midi CC assignments...

Later,

Urs

----Oh, o.k., well as long as I can say I did it accidentally, and yer fixing or have fixed it anyways, then no worries, back to yer vacation.

Jeff

tribalogical · Post by **tribalogical** » Fri Feb 09, 2007 11:25 pm

hmm, maybe this was already mentioned somewhere in the *38* pages of replies..... if so, sorry in advance... here goes....

Regarding version numbers... in the Finder on Mac, Zebra 2.1 displays the wrong version numbers. They show up as 1.2 (AU), and 1.0 (VST) respectively... drove me to double-check I'd gotten the right ones installed...

A minor issue, but, well, you know...... I'm probably flogging an old horse (or zebra?) here...

Of course, they both properly show v2.1 in the plugin interface itself....

peace,
tribalogical

adam standring · Post by **adam standring** » Fri Feb 23, 2007 3:17 am

I think this must be a bug that is still in 2.1 - Each time I close the GUI in Ableton and then re-open it, the state of the window when it was last closed is not preserved. Everything is reset and you cannot tell which patch you are editing or use the < and > buttons to scroll to the next patch in the selected bank (a Default sound is selected instead).

Can you fix this, Urs? It seems to be a major functional issue.

luCiPHer · Post by **luCiPHer** » Fri Feb 23, 2007 12:10 pm

adam standring wrote:I think this must be a bug that is still in 2.1 - Each time I close the GUI in Ableton and then re-open it, the state of the window when it was last closed is not preserved. Everything is reset and you cannot tell which patch you are editing or use the < and > buttons to scroll to the next patch in the selected bank (a Default sound is selected instead).

Can you fix this, Urs? It seems to be a major functional issue.

that is not limited to live, zebra behaves like that in all hosts.

Urs · Post by **Urs** » Fri Feb 23, 2007 1:09 pm

Hmmm. It *should* remember the current state with everything gui... and does so in Logic 7.2... maybe it's a bug in the Win version?

spritex · Post by **spritex** » Fri Feb 23, 2007 1:20 pm

I was wondering about that too, just yesterday. Must be a Windows thing, then.

dlandis · Post by **dlandis** » Fri Feb 23, 2007 6:51 pm

Hi Urs:

Is Zebra 2.1 out for Windows yet (or just Mac)? The review in KB just mentioned the Mac (I think).

Dan

dlandis · Post by **dlandis** » Fri Feb 23, 2007 7:34 pm

OK, I dizzed out. I read above about the Win version. Sorry, it's been a rough month.

Is a Karma okay for the dinosaur rebate? How 'bout a PT Cruiser?

Dan

dlandis wrote:Hi Urs:

Is Zebra 2.1 out for Windows yet (or just Mac)? The review in KB just mentioned the Mac (I think).

Dan

Urs · Post by **Urs** » Fri Feb 23, 2007 8:36 pm

Dan, Karmas (we're talking Korg?!?) are always welcome! Nice machines!

u-he

KVR Audio

Zebra2 Latest Version: 2.1 - Jan 19 2007