Zebra: Certain Items Can't Be Mapped?

It seems that certain items in Zebra can't be mapped to Kore. Its probably a function of how that item is programmed in Zebra; and therefore, there is probably nothing we can do about it. But I wanted to know if anyone has successfully mapped such items.

A couple examples:

Under the FX section in Osc1, there are a couple drop-down menus under "FX1" and "FX2". I can't seem to map those.

Any thoughts?

Thanks!

 

None of your dropdowns like that in Zebra can be mapped; Urs didn't design them to be automated.

ew

 

Ah. It would be cool though.

 

Ask Urs- he's pretty open to feature requests.

ew

 

Just to be sure: am I correct in saying that there is not a way to have certain knobs on the Kore controller send MIDI? (I've read the manual and searched, and it doesn't seem like it.)

Zebra does allow you to "MIDI Learn" those drop-downs, so that would possibly be a work-around.

Thanks for your replies.

 

Nope- Kore doesn't do MIDI control.

You can program Kore controls to receive MIDI (thus letting you use another controller for automating Kore), but you can't program them to send MIDI.

However, if you have the full version of Reaktor, you can use kore2midi from Jonathan's toolpack to control the dropdowns.

http://www.nativeinstruments.de/forum_us/showthread.php?t=56884

ew

 

Ohhhh! I forgot about that tool pack!

I just tried it, and it works great!

I created a Multi sound with Zebra and Kore2Midi. Then, I can have a one Kore knob send a MIDI message to a "MIDI Learned" item in Zebra, and another knob controlling a Zebra knob normally.

This is so awesome.

I might end up with a super-cool-comprehensive KSD for Zebra for you guys. Kinda like the one I did for Helix.

Some people might not see the value in having a comprehensive mapping, but I think its really cool.

 

I already did a 27 pager for Zebra 2 (I also asked about why some won't map) - it's in the templates thread. I took a module by module approach so people can move them around depending on the preset.

 

Yeah, I grabbed that a while back. I see the value there.

I just want something more comprehensive. After doing a Kore sound for all of Helix's prams, and experiencing the joy of messing about with that, I decided to try to do Zebra.

I'll post it when (if) I get done.
---
So I just thought about something as I'm messing with this.

I noticed that when I re-install different versions of Zebra, my KSDs don't work with the newly installed version. Moreover, if I uninstall that version, and revert back to the version with which I built the KSD originally, the KSD still doesn't work.

I do not know if this is a function of the plugin (Zebra), or Kore. In any case, its an important consideration.

For example, what if I have tons of KSDs for a plugin, and get the new version of that plugin and they all quit working? Am I SOL?

Does anyone know what Kore's expected behavior is in these cases?

Seeing how often most vendors update their plugins I would assume that this isn't normal behavior.

Thanks!
---
One more Edit: Actually, the original KSD works with the original version of Zebra with which it was created. I just lose the MIDI Learns. That's probably a function of Zebra. I guess.

But the question still remains about how Kore handles different versions of the same plugins.
---
Its also worth noting that I'm having to delete Zebra's KSD in the database cache every time I install a different version. (In order for Zebra to show up in Kore's browser. Maybe those KSDs contain info that Kore needs to handle the original KSD as described above.

BTW: I'm doing these tests by going back and forth between Zebra2.2 and Zebra2.2b7.

My system specs: XP SP2, Intel Quad Kore, 4GB Ram, RME Fireface 400.
---

I tried it again without deleting the cached KSD, and the original KSD still doesn't work.
---
And Kore has renamed the knob "Constant." Weird.

 

So I found the file that Zebra uses to store its MIDI map info; hence, it would make sense that that info is deleted upon a new installation.

Also, it would seem to make sense that Kore can't help it if a developer changes his or her plugin, and how current KSDs would react to those changes.

 

Thing is I did do all of Zebra's params - at least all that would map for all the oscs, mixers etc (every module on the left hand side basically). I found so many of the ones on the right hand side didn't even map to start with so decided not to go there as it had already got to 27 pages (which is more than hosts can even see without rearranging for each patch to bring the 8 most used to the top anyway)

 

Yes, I understand that. But by using Kore2Midi, I'm able to map to Zebra's non-automatable controls. (See above posts.) Zebra allows you to "MIDI Learn" some (or perhaps all) of its non-automatable controls. I'm assuming the modules on the right will behave that way too.

I'm not so concerned about host automation limits. I'm mostly using the comprehensive KSDs to explore the synths--without using the uninspiring mouse.

 

IC