how to receive programme change with zebra 2?

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

Post

I'm trying to integrate zebra 2 into a live set using ableton live. however I don't see how I can get zebra to change patches by receiving programme change messages. It would astound me, if it couldn't do that, but in the manual there's no hint to how to do that whatsoever.

can anyone help me with that?

Post

Program changes are not yet possible in Zebra2. The planning on this is still sort of open.

I personally solved it by using Lives chain device feature. That way you can just add as many Zebras to an instrument channel as you would like, dial in the sound on each of them and then automate the chain selector to switch to the respective instrument.

Make sure to also automate the enable button in Live so only the instance that you would like to play is turned on. That way you only have one instance of Zebra2 going at a time. Great if you want to make sure not to overload the CPU, which is crucial when performing.

Hope this helps.

If you have more questions I'm happy to send you a Live set that's ready to go to show you how it's done.

Best
Hans

Post

thanks for the info, even if it's somewhat of a disappointment.

I'm already doing the chain thing with operator patches (whatever had the ableton guys been drinking when they decided that they didn't want their device patches to be changeable via midi?!!!!), and zebra 2 is just an addition to that live set, so I'm not (yet) relying on using many different patches, which means it's not such a big deal having to do it the other way, but still...

but having to automate it's on/off status kinda takes up a lot of free CCs, if there's many patches, and therefore instances.

Does Zebra use cpu when no midi is being routed to it? I'm also wondering if I can have the same midi cc assigned to different parameters inside the various zebra 2 instances (from within the vsti's midi assignment, not using live's), or whether in that case I would screw up other instances' parameters while manipulating the one that's selected via the chain selector in live...


anyway, Urs, please, please implement program changes!

Post

You don't need CC's to bypass devices in Live at all.

Just program it into the timeline. That's what I'm doing.

I don't ever want to think about turning a sound on or off. That's all being done for me.

I usually don't even know what happens and if the organ that's coming up for the chorus is in Zebra or if it's the B4.

But my shows are usually very straight forward and not pattern based. The songs are fixed and are played as they are on the CD. So this might be different in your case. The I can see how programming on/off info may not work.

Best
Hans

Post

I'm not actually controlling the CCs myself, but from a master midi clip that I feed back into live via midi yoke. I guess the idea is to be more flexible, time-wise, as I can choose when to start the next master midi sequence (that automates all sorts of things). Of course I could always create a second master midi clip, as maybe one channel of automation isn't enough.

cheers

david

Post

davec1 wrote:I'm not actually controlling the CCs myself, but from a master midi clip that I feed back into live via midi yoke. I guess the idea is to be more flexible, time-wise, as I can choose when to start the next master midi sequence (that automates all sorts of things). Of course I could always create a second master midi clip, as maybe one channel of automation isn't enough.

cheers

david
I think the best thing to do is to map a knob in the rack to both the chain selector and to the device on/off switches, and then control that knob with midi. This should be easier (and easier to mess with after you set it up, too).

Post

tylenol wrote:I think the best thing to do is to map a knob in the rack to both the chain selector and to the device on/off switches, and then control that knob with midi. This should be easier (and easier to mess with after you set it up, too).
I disagree, but mainly because I never had a controller that let me jump to a particular value which you need if you know the sound you're going for.

Ok, if it's setup all sequencial maybe, but that sort of defeats the flexibility again.

Best
Hans

Post

wonshu wrote:
tylenol wrote:I think the best thing to do is to map a knob in the rack to both the chain selector and to the device on/off switches, and then control that knob with midi. This should be easier (and easier to mess with after you set it up, too).
I disagree, but mainly because I never had a controller that let me jump to a particular value which you need if you know the sound you're going for.

Ok, if it's setup all sequencial maybe, but that sort of defeats the flexibility again.

Best
Hans
Well, I don't know if its the best thing in general either, but davec1 said they were already using device chains to switch between presets, so what I meant is that if you're doing that, controlling both the chain selector and various on/off switches with a single knob (and then controlling that via midi) is the best way to go.

Post

davec1 wrote:Does Zebra use cpu when no midi is being routed to it?
It seems to, but not a lot. Opening 12 instances of Zebra2 in eXT only bumped up the cpu meter a little on my P4.


Shannon

Post

very angry mobster wrote:
davec1 wrote:Does Zebra use cpu when no midi is being routed to it?
It seems to, but not a lot. Opening 12 instances of Zebra2 in eXT only bumped up the cpu meter a little on my P4.
Yeah, unfortunately a couple of modules can't just go in standby... I work on improvements every now and then but I don't consider it a major issue.

Post Reply

Return to “u-he”