Help! MIDI Mapping Maschine in Reason 6

I'll post this over on the Reason forums too, but am hoping someone can help here.

I'm trying to create a MIDI map using the Maschine Controller Editor for Reason 6 and its different synths, effects and samplers. I've done this so far without any problems on the global controls, but have hit a snag with the synths themselves.

I've mapped, for example, the Malstrom's filter controls to Maschine's surface, but when I create a new Malstrom and make this the active instrument, my mappings only work on the first Malstrom I made. Can you help?

 

Hey @wickedged Im also looking into these parameter alterations in the Reason forums and what not. So far neither has been a huge help, your not alone. Maybe after the 8hr lunch someone may provide some valuable info to set us free. No disrespect to NI, just eager.

 

Have you tried configuring the Maschine controller according to Reason's MIDI implementation chart? For example in Reason 6 CC 79 controls cutoff freq one for each Maelstrom so if you program your Maschine knob to transmit on CC 79 you should be able to control cutoff freq one for any Maelstrom currently selected which sounds like what you are trying to do.

When you get Reason to learn parameters from a Maschine controller it is called "Remote Override Mapping" and is basically overriding Reason's MIDI mapping and assigning one particular CC number to one particular control on one particular Reason instrument and that assignment then works no matter which Reason instrument is currently selected - which sounds like what is happening to you and what you don't want.

I hope that makes sense and works for you. I think the Reason MIDI implementation chart is stored with Reason's other documentation when you install.

 

Two Soldiers - thanks for the reply! I will be trying this tonight and let you know how I go on. If you don't mind I'm going to quote your reply above on the Reason forum if that's OK?

Thanks again!

 

Of course it's okay if you think it's useful. Hopefully it does the trick.

 

Two Soldiers you are a star! This works absolutely perfectly - thank you so much for taking the time to write out the explanation above - exactly what I was looking for and what I couldn't find anywhere else. Cheers!

 

Hello again,

Just checking something through. I've pretty much finished mapping the Malstrom, and have been trying to get my head round mapping the global transport controls at the bottom of the screen. It seems that there are no straightforward MIDI assignments to the Play, Record, Stop, Loop etc. buttons like there are with the individual instruments and effects themselves.

To get around this, on the Reason MIDI Implementation chart there are a number of greyed out parameters which are consistent through all the Reason devices, and never have anything assigned to these directly. What I have done, then, is simply assign the global transport controls to these 'empty' slots, then save the Reason file as my default document.

Does this sound right to you more seasoned MIDI mappers or is there a more effective way of doing it? This is a whole new area for me and I'm about to duplicate this first map for the other devices in Reason, so I just want to double check before I launch into a new instrument.

 

Your plan looks like the way to go as far as I can see.

If you are ever short of CC options it can sometimes work to use MIDI notes at the extreme ends of the range - for example if like me you rarely or never use notes C-2 to E-2 in productions you could assign those notes to the transport controls.

If you find you need to go even deeper it think the way to go is writing your own custom Remote scripts for Reason but that is beyond me.

 

Hey Two Soldiers - can you try something for me? I think I've found a bug in the MIDI Implementation Chart mapping. I'm in the middle of mapping out the mixer channel controls for the main mixer, and although the faders map out without any problems, the buttons don't seem to map for anything.

So for example, FX1 Send level on any active Mixer Channel is mapped to CC15, which maps out fine onto any Maschine controller knob. FX Send On, however, is mapped to CC14 and a straight toggle on/off button, and this is what causes the problem. Mapping this to any button on the controller just doesn't seem to work for me. Can you give it a go and see if the problem reproduces at your end? If it does I'll file a bug report with Propellerheads technical support, because I can't see what else it could be.

Anyway, I'll keep you posted with how it progresses and once its finished I'll post the map up for everyone to share.

 

Yep I can reproduce that here - the FX send levels work as they are meant to but the On buttons and the Pre buttons don't seem to be responding as they should according to the MIDI implementation chart. I confirmed Reason is definitely getting the signal from my Maschine controller so it does look like something gone wrong at the Reason end.

 

Cheers Two Soldiers - just sent the error report to Propellerheads now. They are being *almost* as slow as NI in responding at the moment though, so it could be a while!

 

Was there ever a resolution to this last bit?

Even in Reason 8 I can still map the rotaries fine, but I can't find a way to control the on off buttons on the mixer. For example, compressor on off should be cc 46, but Reason doesn't respond to the signal. I'm not sure how to tell NI Controller Editor to make it a binary on/off as opposed to a rotary midi value.

Has anyone got this to work?