u-he

spidergod · Post by **spidergod** » Mon Jul 05, 2010 3:32 pm

Hello

Just wondering can the x/y pads in zebra 2 be controlled by midi cc data ?

e.g is there a midi cc map ?

I like to use noatikl and that can send midi cc data (e.g for alchemy moving x pad any amount I have it setup in the midi map to use 102, then use an lfo in noatikl to send the info out on 102)

can this be setup in zebra 2?

cheers

bmrzycki · Post by **bmrzycki** » Mon Jul 05, 2010 4:19 pm

There is no default midi map. Just right click on the hockey puck slider of the XY and choose "learn X" or "learn Y" and then move the controller of your choice. Done.

spidergod · Post by **spidergod** » Mon Jul 05, 2010 4:31 pm

only problem is I will be using software to send the midi cc data, not a hardware controller

e.g an lfo sending midi cc data

bmrzycki · Post by **bmrzycki** » Mon Jul 05, 2010 4:37 pm

Midi data is midi data. Doesn't mater what generates it. Chose midi learn, then turn on the midi producing LFO. If the routings in your DAW are correct you'll see the puck start to move.

spidergod · Post by **spidergod** » Mon Jul 05, 2010 4:42 pm

bmrzycki wrote:Midi data is midi data. Doesn't mater what generates it. Chose midi learn, then turn on the midi producing LFO. If the routings in your DAW are correct you'll see the puck start to move.

will see what happens & report back

spidergod · Post by **spidergod** » Mon Jul 05, 2010 4:51 pm

limited success

I can only setup 1 axis to work at a time and not get all 4 pads working at the same time.

cannot see a way of assigning a midi channel per x/y pad

e.g midi channel 2 > midi cc data > x position on pad 1
midi channel 3 > midi cc data > y position on pad 1

etc

if I could do that I would be very pleased

bmrzycki · Post by **bmrzycki** » Mon Jul 05, 2010 4:56 pm

Zebra currently doesn't allow you to assign the same CC# to multiple targets. It also doesn't care what channel midi data comes in on. Midi channel 3 CC 9 is identical to Midi channel 4 CC 9.

Easiest way to do what you're doing is:
X1: CC 100
Y1: CC 101
...
X4: CC 106
Y4: CC 107

spidergod · Post by **spidergod** » Mon Jul 05, 2010 5:04 pm

bmrzycki wrote:Zebra currently doesn't allow you to assign the same CC# to multiple targets. It also doesn't care what channel midi data comes in on. Midi channel 3 CC 9 is identical to Midi channel 4 CC 9.

Easiest way to do what you're doing is:
X1: CC 100
Y1: CC 101
...
X4: CC 106
Y4: CC 107

ok not sure how I can do that at present.

I have setup 2 voices in the software program and is sending midi cc data on 102 and also on 103

how can I choose in zebra how it can see that?

e.g how can I set X1 to see CC 102
and Y1 to see CC 103

Cannot see a way of assigning the actual value when I right click on the pad

cheers

bmrzycki · Post by **bmrzycki** » Mon Jul 05, 2010 5:12 pm

spidergod wrote:ok not sure how I can do that at present.

I have setup 2 voices in the software program and is sending midi cc data on 102 and also on 103

how can I choose in zebra how it can see that?

e.g how can I set X1 to see CC 102
and Y1 to see CC 103

Cannot see a way of assigning the actual value when I right click on the pad

cheers

I think you misunderstood me. What I meant was you will need 8 CC sources if you want to modulate all 8 axes. There is no way to use 2 LFO CC generators and have all the axes move.

You can get around this by having more LFO sources on different CC channels.

If you are only sending on 102 and 103 you can only modulate 2 destinations on the XY pads. But that's the whole point; you module the puck and then you set up multiple modulation targets in the X/Y panel. There isn't 1 -> many CC modulation support but there is 1 -> many parameter automation support.

spidergod · Post by **spidergod** » Mon Jul 05, 2010 5:19 pm

ok what I would like to do is get the x and y pluck moving on pad 1 first

I think the problem is that the software I am using you can only have one instance but you can setup varying amounts of LFO's sending midi cc data

I do not think it is going to work how I want which is a pity.

bmrzycki · Post by **bmrzycki** » Mon Jul 05, 2010 5:37 pm

Ok. Here's how I'd get what you asked for. First, make sure your LFO generators are transmitting on separate CC channels.

1. Turn off all LFO CC generators.
2. Switch to Zebra, open the Performance Pane.
3. Right-click on the first puck and select "MidiLearn X Axis" on XY1
4. Switch to the LFO chosen to module X1 and turn it on.
5. Verify in Zebra X1 is oscillating.
6. Switch back to LFO X1 and switch it off.
7. Switch back to Zebra and select "MidiLearn Y Axis" on XY1
8. Switch to the LFO chosen to modulate Y1 and turn it on.
9. Verify Zebra Y1 is oscillating.
10. Turn on LFO X1 as well.
11. Verify both X1 and Y1 are oscillating.
12. Repeat these steps for XY2 - XY4, taking care to select separate CC channels for each additional LFO.

I've done these exact steps with Reaper's JS LFO CC generator and it works perfectly.

experimental.crow · Post by **experimental.crow** » Mon Jul 05, 2010 5:41 pm

spidergod wrote:ok what I would like to do is get the x and y pluck moving on pad 1 first

I think the problem is that the software I am using you can only have one instance but you can setup varying amounts of LFO's sending midi cc data

I do not think it is going to work how I want which is a pity.

for your software , each voice has two micro controllers ...
each micro controller can be set to any midi cc # ...

so , for voice 01:
set one micro controller to midi cc# 101 , and midi learn that to Pad 01 / X
set the other micro controller to midi cc# 102 , and midi learn that to Pad 01 / Y ...

rinse , and repeat , using the incementral midi CC# , as required ...

you can also use the two user envelopes provided , in much the same manner ...

spidergod · Post by **spidergod** » Mon Jul 05, 2010 5:52 pm

fantastic

took a little while for zebra 2 to see the midi cc data, but once it did worked perfectly

hmmm time to look into zebra 2 a bit deeper

pdxindy · Post by **pdxindy** » Mon Jul 05, 2010 5:55 pm

spidergod wrote:ok what I would like to do is get the x and y pluck moving on pad 1 first

I think the problem is that the software I am using you can only have one instance but you can setup varying amounts of LFO's sending midi cc data

I do not think it is going to work how I want which is a pity.

If you can do multiple lfo's, it should work...

set up LFO1 to send cc#100
setup LFO2 to send cc#101

Do midi learn on the X/Y pad X axis and start LFO1
Do midi learn on the X/Y pad Y axis and start LFO2

If you cannot do this for some reason... you can still accomplish what you want by editing the midi map text file

On Mac it is user/library/application support/u-he/zebra2.midimap.txt (don't know the path on the PC)

If I remember correctly, this would be the syntax for midi cc# 100 controlling the X axis on the first X/Y pad:

100=PCore:X_1 //Core:X1

spidergod · Post by **spidergod** » Mon Jul 05, 2010 8:04 pm

yeah it is now working which is fantastic.

the possibilitys that this opens up are going to be sweet.

u-he

KVR Audio

zebra 2 x/y pads and midi cc automation