Trying to figure out how to send patch change requests to Zebra via midi on the Muse Receptor or in Logic. I hate using the mouse to make changes as I have to walk a few feet from my controller back to my computer when running logic. Is there an easy way to set this up?
Thanks for helping a noob.
Will
where can I find midi patch change tutorial
-
- KVRist
- 39 posts since 4 Jul, 2007
-
- u-he
- 30213 posts since 8 Aug, 2002 from Berlin
Zebra doesn't respond to Midi Program Changes by itself. That has been discussed to quite some length here and I've been convinced to put it in. It's just a non-trivial thing to do, but I guess I'll have it done in a few months. (It has been in Zebra 1.x - but it caused a lot of crashes, even *on stage*, so I dropped it)
On AU/MacOS X you can click in Zebra's patch browser and just use the cursor keys. (I've added this to VST two days ago... I'd happily make it available for testing purpose)
Some hosts may process Midi Program Changes for plugins (dunno which and how), but then you have to download the patches in the native format (.fxp for VST or .aupreset for AU)...
On AU/MacOS X you can click in Zebra's patch browser and just use the cursor keys. (I've added this to VST two days ago... I'd happily make it available for testing purpose)
Some hosts may process Midi Program Changes for plugins (dunno which and how), but then you have to download the patches in the native format (.fxp for VST or .aupreset for AU)...
-
- KVRist
- 60 posts since 27 Aug, 2006 from Minnesota
Being able to just assign a midi note or cc to down patch up / patch down would be fine too. This is essentially what I do in Reason for live shows currently. I use the top two keys of the controller (when transposed up an octave) to down up/down on the combinator, and I have basically one patch per song in the set. It works quite well.
Maybe enable midi learn on the left and right arrows?
Maybe enable midi learn on the left and right arrows?
-
- KVRist
- Topic Starter
- 39 posts since 4 Jul, 2007
Second vote for midi learn on the arrows.
This would allow me to chose the buttons of my choice on my keyboard controller (requirement number one) and if I create my own bank, I can scroll through the patches I want during a song (requirement 2) in addition to being able to quickly audition the many great patches in Zebra (requirement 3). Maybe it would be more appropriate to use the word request rather than requirement...
The problem with using the up down arrows in Logic is that sometimes it will switch over to controlling which track you are on instead of the patch change. For this reason it's not effective for scrolling through the patches in Zebra. If I get lost in a patch, which I'm apt to, the arrow keys no longer take me to the next patch.
This would allow me to chose the buttons of my choice on my keyboard controller (requirement number one) and if I create my own bank, I can scroll through the patches I want during a song (requirement 2) in addition to being able to quickly audition the many great patches in Zebra (requirement 3). Maybe it would be more appropriate to use the word request rather than requirement...
The problem with using the up down arrows in Logic is that sometimes it will switch over to controlling which track you are on instead of the patch change. For this reason it's not effective for scrolling through the patches in Zebra. If I get lost in a patch, which I'm apt to, the arrow keys no longer take me to the next patch.
-
- KVRAF
- 10815 posts since 26 Nov, 2004 from UK
Win VST?Urs wrote:(I've added this to VST two days ago... I'd happily make it available for testing purpose)
Subz
-
- KVRist
- 107 posts since 4 Mar, 2003 from Herts. UK
Hi - New user here with Cubase 4.1 on Windows XP.Urs wrote:...
On AU/MacOS X you can click in Zebra's patch browser and just use the cursor keys. (I've added this to VST two days ago... I'd happily make it available for testing purpose)..
Loving Zebra - I can see what all the fuss was about !!
I was slightly disappointed that I couldn't run through the patches using the arrow up/down keys, and would be glad to help by testing this for you.
TonyB.
-
- KVRAF
- 10815 posts since 26 Nov, 2004 from UK
DittoTonyBy wrote:and would be glad to help by testing this for you.
Subz
-
- KVRian
- 710 posts since 17 Jan, 2005 from Amsterdam
+1
At least being able to use the up/down keys would be a huge improvement. That's actually the only really annoying thing about Zebra.
Implementing the MIDI learn function would be even better. Something I wish they'd included in the Cubase MediaBay to be able to easily browse from a remote keyboard.
Cheers,
bM3w
At least being able to use the up/down keys would be a huge improvement. That's actually the only really annoying thing about Zebra.
Implementing the MIDI learn function would be even better. Something I wish they'd included in the Cubase MediaBay to be able to easily browse from a remote keyboard.
Cheers,
bM3w
-
- u-he
- 30213 posts since 8 Aug, 2002 from Berlin
I think Program Changes should be fine.
Changing a patch in Zebra2 is a very cpu intensive task... it's not like switching a patch on a 20-parameter synth... for this reason it has to be executed with a little "lag". Otherwise, if you twist a MIDI knob that triggers dozens of patch changes in an instant, the MIDI scheduler of your host will halt in a temporary deadlock which might inevitably lead to a crash.
The problem is, I have to move the whole execution of patch management from the gui to the dsp part in order to respond to MIDI while the gui is closed. This is a major redesign... it'll take some time but it'll eventually* happen...
As to the test version for keyboard input, I'll upload something as soon as I have some work on Vista... that won't be today but it'll be shortly.
Cheers,
Urs
* note to native Germans speakers: The word "eventually" has nothing to do with "eventuell" - it rather means "endlich" or "irgendwann"
Changing a patch in Zebra2 is a very cpu intensive task... it's not like switching a patch on a 20-parameter synth... for this reason it has to be executed with a little "lag". Otherwise, if you twist a MIDI knob that triggers dozens of patch changes in an instant, the MIDI scheduler of your host will halt in a temporary deadlock which might inevitably lead to a crash.
The problem is, I have to move the whole execution of patch management from the gui to the dsp part in order to respond to MIDI while the gui is closed. This is a major redesign... it'll take some time but it'll eventually* happen...
As to the test version for keyboard input, I'll upload something as soon as I have some work on Vista... that won't be today but it'll be shortly.
Cheers,
Urs* note to native Germans speakers: The word "eventually" has nothing to do with "eventuell" - it rather means "endlich" or "irgendwann"
-
- KVRAF
- 10815 posts since 26 Nov, 2004 from UK
thanks for the info Urs!
keyboard input patch change will be more than good enough for now
looking forward to testing,
Subz
keyboard input patch change will be more than good enough for now
looking forward to testing,
Subz
-
- KVRist
- 60 posts since 27 Aug, 2006 from Minnesota
This is the same in Reason. For instance if a combinator has quite a few devices or even just a sampler with a pretty large sample set, switching patches can take a while. They have a nice little trick to make it pretty useful, which is that if a patch up or patch down command comes in within some small amount of time, it doesn't load the patch and assumes you are scrolling. So you can skip ahead 5 patches almost instantly and then the final patch will load.Urs wrote:Changing a patch in Zebra2 is a very cpu intensive task... it's not like switching a patch on a 20-parameter synth...
Doesn't Live have some problem with program change messages? People certainly complain about those things a lot in the forums there, but I've never used them much so I don't know much about it.