u-he

jyoung50 · Post by **jyoung50** » Fri Jan 04, 2008 4:59 am

I just purchased Zebra 2 and I've been slowly getting familiar with it using Cubase 4.1 on the Windows platform. One thing that I've noticed is that when I configure a parameter to learn a MIDI control that this setting is not being preserved between sessions of Cubase. IOW if I close my project and open it up again I have to "teach" the parameter to respond to the same MIDI control again. Do I need to save the preset or shouldn't this setting be saved along with my project?

politcat · Post by **politcat** » Fri Jan 04, 2008 6:02 am

it works ok for me here, zebra remembers in reaper and ableton live when I re-open a project

Howard · Post by **Howard** » Fri Jan 04, 2008 8:25 am

Problem confirmed. Cubase 4 / Zebra2.2 forgets...

Urs · Post by **Urs** » Fri Jan 04, 2008 11:08 am

Hmmm. It should be saved globally.

When you MidiLearn a Parameter in Zebra and then close Cubase, what does com.u-he.Zebra2.midimap.txt located at C:\Program Files\u-he\Support say when opened in WordPad?

Later,

Urs

jyoung50 · Post by **jyoung50** » Fri Jan 04, 2008 6:31 pm

The file is empty.

jbnumb · Post by **jbnumb** » Fri Jan 04, 2008 6:34 pm

I have the same problem using Reaper.

jyoung50 · Post by **jyoung50** » Sat Jan 05, 2008 5:12 pm

Urs wrote:Hmmm. It should be saved globally.

When you MidiLearn a Parameter in Zebra and then close Cubase, what does com.u-he.Zebra2.midimap.txt located at C:\Program Files\u-he\Support say when opened in WordPad?

I checked this file this morning and now it contains this line:

20=OSC1:WNum //Oscillator1:WaveWarp

But, Zebra still appears to have a learning disorder.

Mr-Bit · Post by **Mr-Bit** » Sun Jan 06, 2008 6:19 pm

I have a similar problem in that CC 64 is permanently assigned to env1 dec,the midimap file is blank. I have deleted the file and assigned a different CC number but CC 64 is still persistant

Mr-Bit · Post by **Mr-Bit** » Sun Jan 06, 2008 6:21 pm

Forgot to say I'm using XP VST

Urs · Post by **Urs** » Sun Jan 06, 2008 6:25 pm

Mr-Bit, have you tried to unlearn it? - Right-click decay knob and choose "Midi Unlearn"...

Mr-Bit · Post by **Mr-Bit** » Sun Jan 06, 2008 6:48 pm

yep unlearned, saved live project, reopened and it still responds to cc 64 and the midi map text file is empty?

Urs · Post by **Urs** » Sun Jan 06, 2008 6:55 pm

Mr-Bit wrote:yep unlearned, saved live project, reopened and it still responds to cc 64 and the midi map text file is empty?

Dude, that's weird... does the knob actually move?

Uhm... CC64 is the Hold Pedal... this is hard wired... could it be that?

Mr-Bit · Post by **Mr-Bit** » Sun Jan 06, 2008 7:14 pm

No the knob doesn't move I'm using all 128 cc's and have no way of filtering out cc 64

Mr-Bit · Post by **Mr-Bit** » Sun Jan 06, 2008 7:22 pm

AH Doh! your right its the hold /sustain

jyoung50 · Post by **jyoung50** » Sun Jan 06, 2008 11:51 pm

I'm using CC 20 to control the Wave on OSC1. I still have to set the VST control to learn that # before I can record or automate between opening my project.

u-he

KVR Audio

Zebra not remembering what it learned