Zebra 2.3.1 on Receptor unable to keep learned MIDI assignem

[o8o8]

Let us know how it works today!

...'tell you what: it simply works ...

...now, where is that listing of controls within Zebra2...or is it try&err to find out which element has which assignment (eg. what is VCC, and which one is it?)...

...if there is no such listing: dont bother! - having eight parameters assignable per Zebra2-instance via the X-Y-control is a huge advance already...

...btw., in the above you can leave out the routing via Live in case you dont want to record your inputs - just tell MIDIPipe to send the recreated MIDI to your selected output directly...

...to recap:

MIDI-interface -> MIDI-IN -> MIDIPipe* -> (Live ->) MIDI-OUT -> Zebra2 (on Receptor)

*where MIDIPipe looks at the incomming CC and resets it to the default CC, but on a different channel for each instance of Zebra2

...Urs, while i managed to handle this problem for the moment, could you anyway look into why the MIDI-assignments are not saved on the Receptor?

TIA.

[aMUSEd]

This reminds me of the same issue I brought up in Kore 2. Maybe some hosts handle the XY's differently? - everything else is assignable but not the XY's (at least only for the life of the open project)

[bmrzycki]

...now, where is that listing of controls within Zebra2...or is it try&err to find out which element has which assignment (eg. what is VCC, and which one is it?)...

If you download the Zebra2 2.3 preinstalled zip there's a filein Zebra2.data/Support/com.u-he.Zebra2.publicparams.txt that looks to have the names of all the parameters you can midi map.

Code: Select all

...snip...
3: PCore:X_1:"X1"					//PCore: Core->X1
4: PCore:Y_1:"Y1"					//PCore: Core->Y1
5: PCore:X_2:"X2"					//PCore: Core->X2
6: PCore:Y_2:"Y2"					//PCore: Core->Y2
7: PCore:X_3:"X3"					//PCore: Core->X3
8: PCore:Y_3:"Y3"					//PCore: Core->Y3
9: PCore:X_4:"X4"					//PCore: Core->X4
10: PCore:Y_4:"Y4"					//PCore: Core->Y4
...snip...

Looks to me like the format is parameter_number: name:"description" //comment
You just want the "name" field.

Hope that helps and I hope your mappings are still working a-ok.

[Urs]

com.u-he.Zebra2.publicparams.txt

This should also be in the normal version somewhere, no?

It's the editable parameter list. If you want a cutoff parameter automatable in Live, simply swap the *number* of one of the first 128 parameters with that of the cutoff parameter.

What I havn't done yet is making the parameter names editable. This is due to some problems in some hosts that don't accept long parameter names. Gotta fix this up and then document the feature...

Urs

[fas1piano]

are the automation parameter akronyms documented anywhere? would be a good first step!

[Urs]

are the automation parameter akronyms documented anywhere? would be a good first step!

Just save a preset as "h2p extended" and open in text editor - there you've got all modules and parameters explained!