Assigning MIDI CC to Zebra's XY pads: What am I doing wrong?

Official support for: u-he.com
Post Reply New Topic
RELATED
PRODUCTS

Post

So I have created a TouchOSC layout and I have assigned those CC's using Zebra's MIDI Table.

This is what it looks like:

MIDI Table.png

This is what the midiassign.txt file that it created looks like:

midiassign txt.png

I have tested this TouchOSC layout with other plugins, and I can control them without an issue. I have tried all of the options for mode and type for each assignment in Zebra's MIDI Table... What am I doing wrong? :help:
You do not have the required permissions to view the files attached to this post.

Post

Another observation...

When I instead try to use Zebra's MIDI Learn function on any parameter of Zebra2/HZ, using TouchOSC, it doesn't register. If I use another controller such as my keyboard's mod wheel, it does register.

If I use the DAW's MIDI learn, it registers messages from TouchOSC. If I use the MIDI learn of other plugins, it also registers TouchOSC.

I'm not sure what is going on there and if this info points at anything that might be going on...

Post

Sounds like an issue with MIDI Channel?

Post

And critically what DAW are you using?
Cubendo blocks it unless you disable QuickLearn (or use to)
rsp
sound sculptist

Post

Thanks for the replies!

TouchOSC is sending MIDI channel 1 and that's what Zebra is receiving. Zebra seems to receive standard MIDI assignments from TouchOSC just fine, such as mod wheel.

I'm using the VST with Reason. I just checked the AU with GarageBand...and it works there. So I guess there's something going with Reason that I need to figure out. Thanks!

Post

This is indeed a Reason specific issue.

Reason does not allow CC messages to be sent directly to the plugin, thus our MIDI learn feature can not work.
One needs to use Reason's own "Remote" feature in order to control plugin parameters via MIDI CC.

I tried this, but wasn't able to assign both X and Y of an XY pad to a MIDI controller. It seems Reason recognizes the XY pad as a single parameter, so one can only assign the X axis to a CC.

Pretty unfortunate, but there is nothing we can do about it, as long as the plugin isn't allowed to receive CC data.
That QA guy from planet u-he.

Post

It's being unreasonable. :lol:

Post Reply

Return to “u-he”