|
Reason 2.5- Controller problems!!
|
View this Thread in Original format
| Olly Lewin (Dj) |
| Hi. I use reason 2.5 to produce trance music but I have this really anoying thing that happens when I try to use MIDI to control filters etc... I've got an evolution MIDI keyboard and a KS4 hard synth. I use the KS4 to record my music (mmmmm.... Semi-weighted keys... NICE!) and the evo to do filters etc. Now, when I set reason up to use the evo I do all the normal stuff. Enable midi remote and all that... When I record a change though, another part of the synth changes, even though I've not asked this to be controlled by MIDI. I've tried everything I know, (Not alot admitidly) but cant figure this out. Maybe a stored preset or something in the evo? God knows!! This means I have to use the damn mouse instead resulting in some ermmm... well interesting filter sweeps!! Anybody got any Idea whats happening? |
|
|
| Invertika |
Its happening because each knob and fader in Reason has its own midi Control Change (CC) number already assigned. A CC channel is basically one of 127 channels that the controller data is sent along. Eack knob on your evo also tranismits on one of the 127 CC channels, and so if you enable midi remote etc to control the filter cutoff for instance, the particular CC channel of the knob on your evo might also correspond to the oscillator tuning or something.
The only way i can see around it is to look in the Reason folder and there should be a pdf file called 'midi implementation charts' or similar. Each synth and each controller is listed with its particular number. In my experience often certain functions have the same number, for instance i've found that filter cutoff is often mapped to CC channel 74...
Its then a matter of editing on the evo to make each knob transmits on a neutral CC channel, or on the channel you wish to control. The manual for the evoulution explains this, and i had my old evolution set up to fit perfectly for the reason devices i used the most.
Its a bit complicated i know, but its quite easy to get around once you do it once or twice. |
|
|
| Invertika |
:crazy: EDIT
The above is one way to do it, but the long messy way...i just had a look and reliased why
Go to the prefs and make sure that the midi input AND midi remote control are set to the evoulution. Then, go to options and select 'enable midi remote mapping', then also 'edit midi remote mapping'. Click on the particular device you want to change, then click the knob you want to map. Click 'learn from midi input' and move the knob you want to use, and it should remember it. Then the only problem comes from if you also have that device selected for midi in the sequencer window, if you take it off there then the messages shouldnt clash |
|
|
|
|
