Zebra2 : THE go to synth?

[spuddle]

Oh Urs, those random notes that the demo plays after 15 minutes, are the velocities random too?

These notes are not random... not completely... it's a progression of c-e-b-r-a where only "r" is a random note

the velocities are just those of the keys pressed...

Urs

Damn my ears, you have a wacky sense of humour

Oh, I'm trying to find out how to specifically choose a CC# for the XY pads (opposed to just MIDI learn) is that possible? *scrounges for the manual*

------------
[edit]
No manual for demo or did I miss something?

[bmrzycki]

Oh, I'm trying to find out how to specifically choose a CC# for the XY pads (opposed to just MIDI learn) is that possible? *scrounges for the manual*

Heya spuddle,

The manual is online, at the The Zebra2 HTML Manual or the Rough PDF Manual. It's the same manual for the demo or a registered user.

Now that you have those, you won't find a way to set a MIDI CC in it.

If you're not afraid of using a text editor you can edit

Code: Select all

MAC: /Users/[username]/Library/Application Support/u-he/com.u-he.Zebra2.midimap.txt
PC: C:\Program Files\u-he\Support\com.u-he.Zebra2.midimap.txt

Add the lines below. The numbers on the left of = are CC numbers. Put anything from 0-127 on that side.

Code: Select all

102=PCore:X_1 //Core:X1
103=PCore:Y_1 //Core:Y1
104=PCore:X_2 //Core:X2
105=PCore:Y_2 //Core:Y2
106=PCore:X_3 //Core:X3
107=PCore:Y_3 //Core:Y3
108=PCore:X_4 //Core:X4
109=PCore:Y_4 //Core:Y4

When saving midi CC numbers in the Zebra interface, it doesn't allow you to share CC numbers with multiple targets. I've never tried putting the same number twice in the text file so I don't know if it would work. You also can't assign anything but CCs (NRPNs for example) that I'm aware of.

[chardin]

http://echikung.com/zebra/newdrum5.mp3 (Zebra with external reverb)

This is great!

[spuddle]

Oh, I'm trying to find out how to specifically choose a CC# for the XY pads (opposed to just MIDI learn) is that possible? *scrounges for the manual*

Heya spuddle,

The manual is online, at the The Zebra2 HTML Manual or the Rough PDF Manual. It's the same manual for the demo or a registered user.

Now that you have those, you won't find a way to set a MIDI CC in it.

If you're not afraid of using a text editor you can edit

Code: Select all

MAC: /Users/[username]/Library/Application Support/u-he/com.u-he.Zebra2.midimap.txt
PC: C:\Program Files\u-he\Support\com.u-he.Zebra2.midimap.txt

Add the lines below. The numbers on the left of = are CC numbers. Put anytong from 0-127 on that side.

Code: Select all

102=PCore:X_1 //Core:X1
103=PCore:Y_1 //Core:Y1
104=PCore:X_2 //Core:X2
105=PCore:Y_2 //Core:Y2
106=PCore:X_3 //Core:X3
107=PCore:Y_3 //Core:Y3
108=PCore:X_4 //Core:X4
109=PCore:Y_4 //Core:Y4

When saving midi CC numbers in the Zebra interface, it doesn't allow you to share CC numbers with multiple targets. I've never tried putting the same number twice in the text file so I don't know if it would work. You also can't assign anything but CCs (NRPNs for example) that I'm aware of.

This is a bit awkward in practice.

Isn't there any way to manually select the CC$ that the XY pads will be bound to? I make extensive use of XY pad on my Korg Padkontrol as well as the joystick on my Ztar and I would like to save this setting per-patch..

Did I miss something or is editing the text file every time you want to perform with it the only way to do it?

[himalaya]

http://echikung.com/zebra/newdrum5.mp3 (Zebra with external reverb)

This is great!

It's just inspired ! The pattern and the sound.

[bmrzycki]

This is a bit awkward in practice.

Isn't there any way to manually select the CC$ that the XY pads will be bound to? I make extensive use of XY pad on my Korg Padkontrol as well as the joystick on my Ztar and I would like to save this setting per-patch..

Did I miss something or is editing the text file every time you want to perform with it the only way to do it?

I've asked Urs for midi map presets as well. He's said he need to rethink the Z2 midi implementation a bit. As for today the midimap is global and the only way I've found to set a specific CC# to a parameter is through editing the textfile above.

One thing I've done to avoid editing the file is I've set up the 8 faders on my keyboard to have the same CC#s as the 8 presets for my XY pad. This way I can use the right-click context menu within Z2 and move the faders to get the right CC#s. If I try assigning from the XY pad directly sometimes the Y axis is the first CC# sent and that's set to X.

It's not perfect but Urs said he will eventually get to it. Now that he has another employee maybe it'll happen faster!

[spuddle]

Ah, that's a good idea, I didn't think of it. A good work around for now.

Gogogo Urs, have fun at NAMM and I look forward to the updates

[Howard]

If I try assigning from the XY pad directly sometimes the Y axis is the first CC# sent and that's set to X.

Learn MIDI CCs using the x/y KNOBS in Z2 instead of the pads.

[bmrzycki]

If I try assigning from the XY pad directly sometimes the Y axis is the first CC# sent and that's set to X.

Learn MIDI CCs using the x/y KNOBS in Z2 instead of the pads.

The problem is not on the receiving end, it's on the sending end. Trying to only send the X or the Y with my Kaoss Pad is almost impossible. Sometimes it takes me as many as 5 tries to get the X-axis CC to be the first CC sent. I know it's a quirk of the hardware but it's a good example why it'd be nice to be able to actually type a CC#. But then again, I don't mind editing a text file.

[z15]

These notes are not random... not completely... it's a progression of c-e-b-r-a where only "r" is a random note

How about a feature request? Replace the first C with a silent note aka rest aka... Z

[Urs]

These notes are not random... not completely... it's a progression of c-e-b-r-a where only "r" is a random note

How about a feature request? Replace the first C with a silent note aka rest aka... Z

or three of them Zzz