[Zebra] midi learn cc is global?

[padillac]

I used midi learn for the first time today to automate zebra's parameters from renoise. I set CC 3 to control VCF1's cutoff, and it worked fine. I created another zebra instance and created a new patch with a VCF1, and sending this new instance CC 3 changed its cutoff as well. I restarted renoise, created a zebra and added a VCF1, and CC 3 controlled its cutoff once again.

So...I'm not quite sure what to make of this. I was expecting that Zebra's midi learn would be on a per-patch basis. So CC 3 might control filter cutoff on one patch, and oscillator phase on another. But zebra remembered the midi learn, which I confirmed by loading it in live 9, creating a new patch and automating cc 3.

Is that just how zebra works? Is that how all / most plugins work? I was hoping to use different midi learns for different patches but it seems like that's not gonna be the case...

this is ZebraHZ 2.6.1 audiounit if that matters

[EvilDragon]

That's how Zebra works. And IMHO it's better that MIDI learn is global.

If you want to change different parameters with the same CC depending on the patch, perhaps you could use XY pads to assign to various parameters, but MIDI learn each axis to a certain CC. This way you would get 8 CCs that, while being global, control different parameters depending on the patch.

[padillac]

That's how Zebra works. And IMHO it's better that MIDI learn is global.

If you want to change different parameters with the same CC depending on the patch, perhaps you could use XY pads to assign to various parameters, but MIDI learn each axis to a certain CC. This way you would get 8 CCs that, while being global, control different parameters depending on the patch.

I think that's what I'll do and now that I think about it some more it makes sense and is very convenient with dynamic modulators like XY pads. Instead of having notes in each patch on what the different CCs do, I can have a single cheat sheet of CCs to Zebra XY params.

So the next question is how do I see everything that Zebra has midi learned? Is there a file somewhere where all this is saved and I can view / erase any existing mappings?

[whyterabbyt]

I used midi learn for the first time today to automate zebra's parameters from renoise. I set CC 3 to control VCF1's cutoff, and it worked fine. I created another zebra instance and created a new patch with a VCF1, and sending this new instance CC 3 changed its cutoff as well. I restarted renoise, created a zebra and added a VCF1, and CC 3 controlled its cutoff once again.

So...I'm not quite sure what to make of this. I was expecting that Zebra's midi learn would be on a per-patch basis. So CC 3 might control filter cutoff on one patch, and oscillator phase on another. But zebra remembered the midi learn, which I confirmed by loading it in live 9, creating a new patch and automating cc 3.

Is that just how zebra works? Is that how all / most plugins work? I was hoping to use different midi learns for different patches but it seems like that's not gonna be the case...

this is ZebraHZ 2.6.1 audiounit if that matters

If you have a set of global mappings for Zebra, but still want Renoise to use your custom per-patch CC settings, you could always try remapping them to the Zebra globals to suit your preferences using a plugin, for example the midi16CCRouter from Insert Piz here. (http://www.thepiz.org/plugins/?p=pizmidi)

(This would also be useful if you had, say, a controller which sent fixed CCs from knobs, and wanted to change which set of Zebra controls it affected)

[EvilDragon]

So the next question is how do I see everything that Zebra has midi learned? Is there a file somewhere where all this is saved and I can view / erase any existing mappings?

Yes, go to Zebra2.data folder, Support subfolder, and check out file called com.u-he.Zebra2.midiassign.txt.