Reason 3.0

  • Thread starter Thread starter hippie_slayer
  • Start date Start date
H

hippie_slayer

New member
I have recently purchased reason 3.0. Everything works great, except I can't get reason to recognize the sequencer controls on my keyboard. I have a CME UF5, and I got the driver for the UF5, but it still won't recognize it. Has anyone else had this problem? and if so, how did you fix it?
 
There are a set of midi continuous controllers that are designated as switch controllers and that's how Reason 3.0 controls transport functions. For example, CC 89 is play and CC 90 is stop.

Your CME probably sends Midi Machine Control, a separate midi protocol.

If the CME is capable enough to let you reprogram it, contact the Propellerheads web site for a list of transport commands and their corresponding CC numbers. If not, you'll need to find some other way to control the Reason transport functions --- like the Behringer Nano midi controller. It's cheap and easy to program and small enough to fit right on top of your keyboard.


.
 
Look in the manual that came with your CME midi controller.

If it has a section on programming or reprogramming follow the instructions.

Otherwise, you may have to either take my alternate suggestion or continue to control your Reason transport with your mouse.


.
 
It doesn't look like it can be reprogramed, so I guess I'm stuck with using the mouse because I really don't want to spend another $50. Thanks for your help though.
 
right click on the transport control u want to alter select edit remote override mapping click learn from control surface and click the button that corresponds wiht that button i prefer to create keyboard short cuts but thats the best way to make it work
 
X man Da Legend said:
right click on the transport control u want to alter select edit remote override mapping click learn from control surface and click the button that corresponds wiht that button i prefer to create keyboard short cuts but thats the best way to make it work


When I click the button that corresponds with the one in reason, it does not detect any activity. Is my keyboard broken or is there a problem with the software?
 
hippie_slayer said:
When I click the button that corresponds with the one in reason, it does not detect any activity. Is my keyboard broken or is there a problem with the software?
Neither.

X man Da Legend is answering a different question than the one you were asking.

He's telling you how to set Reason up for midi controller overrides, but that doesn't apply in your case.

I found a Behringer Nano at my local GC for $40, and I'll bet with a little negotiation you could find one for less. That will be your most cost-effective option to remotely control Reason's transport buttons.

.
 
Back
Top