Zebra2 Midi Learn Issues

[kodama]

Heya Urs,

I made a setup on my X-Station that has all of the controls mapped to CC#'s so that I can make some Zebra patches that are as similar as possible in structure to the X-Station control surface.


I'm running into a few issues:

- Some CC#'s seem to not want to map (#123), are there some that are reserved?

- Some parameters that I wish would be midi-learnable are not.

- I wish I could midi map pressure to an X or Y slider.

- Ok the biggie - the X-Station has more than 128 controls when all the menues are used, etc..., so I have to use some controls on CH 2, but Zebra2 apparently sees CH 1 CC# 15 the same as CH 2 CC# 15 ?

[Urs]

Hmm, yes, hmm.

Which ones can't be learned?

-> Using Midi Channels to get 16 times the controls sounds like a good idea. Will see what I can do here...

Urs

[kodama]

I'll check, I know that #123 was one I was having issue with...

[kodama]

Ok, upon further investigation, looks like you have several CC#'s that are reserved for basic midi functions.

It would be nice to get a list of those!

11 = Expression maps to vibrato on oscs
64 = Sustain (I was wondering why I was getting stuck notes and huge CPU spikes)
123 = All notes off?

Any others that are off limits for mapping like a regular CC#?

I really wish a few more parameters were mappable (Filter type select, LFO Wave, etc...)

And now time for some random thoughts:

- Good news! Zebra is no longer crashing Live 6 since I reinstalled, I used it all day & it was solid...

- More good news! Live's Sampler has release velocity, and as you predicted, I really can't find a good use for it, so ummmmmm....

- Is there an example of an OSC has all the basic waveforms? (Sine/Saw/Square/Pulse/Tri)?

[kodama]

Oh yeah, some of the arp controls would be nice to map also (on/off, speed, latch, gate, etc...)