Reason: Custom Behringer X-Touch Remote Map Layout

[10/07/2020 Version 6.2] Hey, I’m Jaëxx. This is the 100% free MJ Enhanced Universal Control 8 channel mixer interface for Reason Studios. (The MJ Enhanced Combo Extender is the 16 channel version and the MJ X-Touch Trinity is the world’s first 24 channel version.) This is a remote map and Lua codecs that run on Mackie MCU Pro, Behringer X-Touch, iCon Qcon, PreSonus FaderPort 8 mixers (mixers that run off Mackie’s Universal Control protocol).

Using a Mackie MCU Pro, Behringer X-Touch, iCon Qcon, PreSonus FaderPort 8, the MJ Enhanced Universal Control mixer interface in Reason Studios (regular and suite) is a single native remote map with no additional man-in-the-middle software to run. Nearly all of Reason’s virtual SSL 9000k mixer is fully controllable for all 8 channels. The MJ Enhanced Universal Control controls Reason natively without messing with creating special sequencer tracks or tedious mouse clicking.

This fixes problems like buttons being mapped in the wrong areas, virtually completely eliminates clip LEDs getting triggered, functions missing entirely (like the EQ Q knobs) while adding enhancements and new features, like comp and gate LED meters, redesigned encoder LED display modes, time displayed by default, global solo and mute off functions, enhances the channel VU meters, introduces new rotary encoder LED display modes, FX return encoder LED meters, illuminated select buttons, completely new “alternative text” mode for displaying additional information and added encoder ring master VU out meters. This enables you to control the entire virtual SSL mixer and channel strip settings including channel selection. This article serves also as a guide / general commentary and I’m sharing it free…

Version history

[Edit: 10/07/2020] MJ Enhanced Universal Control version 6.2 includes the MJ Enhanced Combo Extender and MJ X-Touch Trinity files in the installation zip now needed for loading.

[Edit: 09/29/2020] MJ Enhanced Universal Control version 6.1 fixes remote map loading error.

[Edit: 09/26/2020] MJ Enhanced Universal Control version 6.0 adds notification when the mixer isn’t locked to the master mixer section; fixes legacy code in newer Reason versions that caused crashes if individual channel VU meters were too loud; reduces bugs from displaying leftover LCD text when exiting Reason; new green illuminated select buttons; LED time display fix (“01 03” vs “0 1 3”); LED auto-hides minutes and hour; enhanced loop marker LED display; and new method for maintaining remote maps in unison thanks to “RFX”.

[Edit: 05/09/2020] MJ Enhanced Universal Control version 5.0 prevents future versions of Reason from overriding the Mackie files; and a new custom image added.

[Edit: 01/12/2020] Removed outdated part of this page that referenced “optional Lua codecs”. The Lua codecs are mandatory for versions 4.5 and newer.

[Edit: 02/28/2019] Version 4.6 adds ‘ticks’ to the LED beats display. 

[Edit: 03/22/2018] The huge version 4.5 of the MJ Enhanced Universal Control brings more optimized and reliable VU behavior; new rotary encoder display modes with; two completely new, custom-programmed modes; rotary encoder LED FX return meters, FX name LCD display; blank rotaries LEDs turn off; VU out meters; flip mode alternative text display; and new ‘disconnected’ display text.

[Edit 02/20/2018] The mixer’s “DELAY COMP” button used for VST lag compensation issues (introduced in 9.5) isn’t mappable. That means it can’t be added it to the MJ Enhanced Mackie Universal Control map.

Foreword

The MJ Enhanced Mackie Universal Control setup took a very long time for me to do.

[Edit: 02/12/2018] This is a photo in the middle of designing the MJ Enhanced Mackie Universal Control. Three windows of code open in Windows and, because Windows sometimes wouldn’t update the code in Reason reliably, my MacBook Pro with two more windows of code syncing via Google Drive. I also have my iPad at the bottom right open to the image rendering of which buttons light up. And of course, the X-Touch still with  scribble tape used to label temporary buttons.

MJ Enhanced Universal Control mixer interface

All three remote maps (which includes the MJ Enhanced Universal Control) are now being developed in unison.

The MJ Enhanced Universal Control features 8 channels. Of those 8 channels, there’s five global sections.

  • “TRACK” displays 8 channels of compressor meters and compressor on controls.
  • “PAN/SURROUND” gives panning over 8 channels.
  • “EQ” gives gain and invert control over 8 channels.
  • “SENDS” shows the FX send return meters with FX send mute controls on the left extender mixer and on the base mixer gives FX return meters as well as digital scribble strip display of your FX names.
  • “PLUG-IN” gives master bus compressor controls, mastering suite controls and master VU out display.
  • “INST” displays gate meters and gate on controls for all 8 channels.

Pressing the “SELECT” button over a channel illuminates the select button and allows you full control over that channel strip. Changing channel banks retains its native functions in Reason Studios so if a project has more than 8 channels, the channel bank continues to change banks 8 channels at a time.

This article serves as a guide / general commentary and I’m sharing it free…

What the MJ Enhanced Universal Control fixes or adds

“All solos off” and “all mutes off” functions added

This wasn’t present before. On the X-Touch, they’re color-coded: red “SAVE” button for mutes and amber “TRIM” button for solos.

You might think this could get confusing as the buttons are labeled “save” and “trim”, but it isn’t because the buttons around those sections are all typically dark. Once you hit mute on a channel, a new red button lights up on the side of the normally dark area and your brain instantly registers that with being the “all mutes off” button, same for the amber “all solos off” button.

Added comp & gate channel meters

I added comp and gate channel meters. These function automatically and are linked to the virtual SSL mixer’s comp and gate channel LED’s. There was no code in the Universal Control remote map file for this, but in creating the technique for the BCR2000, I was able to get it working here too.

(Edit: 03/22/2018) I programmed two custom, new rotary encoder LED modes. One is an LED meter mode that services the comp, send and VU out meter modes. It fills up a “bar” when receiving signal and, when not receiving signal, goes completely dark. The other mode is dedicated just for the gate meters. It has the animation of the “spread” mode but, when the gate is fully open, the LEDs completely disappear. Other rotary encoder LED modes are visually different from these so it makes these new modes stand out even better.

Button colors match their function (X-Touch specific)

It wasn’t easy figuring out placement, but I made sure each button matches the color of the function you expect. The clip indicator lights up red. The “mute all off” button is red to match the mute buttons, the “solo all off” button is amber to match the amber solo buttons, etc.

Practically every single thing of the virtual SSL mixer is mapped, including oddities like Filters to Dyn buttons. 99% of everything on the virtual SSL mixer is mapped; the other 1% you don’t want mapped.

Changed the time display

This one’s a big time saver. Propellerhead programmed the display to show the annoying bars mode (”34.3.2”) instead of time (”1:34”). Time should always be displayed by default. Bars can be very useful for recording rhythm on time, and so is the metronome (click). But you don’t want the metronome to be on by default and the same for bars. And those of you thinking you can judge a song’s time by bars, you can’t because tempo changes a bar’s time.

I’ve changed this so now it displays time by default (a major time saver in my book).

Clip indicator

I added a clipping indicator and reset button where the scrub button is located. Reason has no way to manipulate clips, notes or other things from MIDI controllers, so a scrub function isn’t needed at all in Reason (and scrubbing the song’s position is pointless).

Clipping LED glitch (completely) eliminated (X-Touch specific)

Master compressor gain reduction and master out displaying on 3 of the VU’s was mainly causing this. When the master out in Reason clipped, it activated clip LED’s on the X-Touch. The Mackie protocol apparently doesn’t support a method for resetting the clip LED’s.

I fixed this by reassigning the VU meters for the channels as they should have been from the start. A channel’s clipping meters will never engage.

Disabled the confusing 1-8 channel LED display

Propellerhead tried to get the LED time display area to show what channel number you’re currently controlling.

The problem is that Propellerhead didn’t create the needed code. Channels 1-8 display correctly, channel 2 displays “2” on the LED. But when you move to another channel bank and select channel number 10, the LED will display “2”. Channel 11 displays “3”, channel 12 displays “4”, channel 17 ”1”, channel 18 “2” and so forth.

This does way more harm than good so I removed this broken functionality. It doesn’t help you know which channel bank you’re on, but it doesn’t make you more lost.

(Tip: I add a number to the first channel of a channel bank in Reason so I can always see which channel bank I’m on. “1Keys”, “9Flute”, etc. So each track on channels 1, 9, 17, 25, etc. It’s unrealistic to number every single other channel though because seven characters is already too limited for channel names.)

[Edit: 09/26/2020] In designing the MJ X-Touch Trinity, getting the channel select displays is technically possible but not without causing maintenance and reliability problems.

Display additional text information function added

[Edit: 03/22/2018] I added a new function to the otherwise useless flip mode. It’s now possible to see exactly what function may be behind a button that doesn’t have a dedicated text LCD display.

I also modified the code so that the faders stay in place and can still control the fader levels while viewing the alternative flip mode texts.

And I modified the code so that the rotary LEDs turn off, further helping you identify when you’re in the flipped alternative text mode and the rotary knobs are, thus, turned off.

The original flip mode had a (pointless) function where it swapped the functions of the rotary knobs with the fader knobs. The flipped mode now has a new lease on life. You can look at the flip mode if you’re wondering what a button does for the 8 REC buttons.

Eliminated clipping LED’s glitch

[Edit: 09/26/2020] The clipping LED glitch is completely eliminated in version 6.0.

Master compressor gain reduction and master out displaying on 3 of the VU’s was mainly causing this. When the master out in Reason clipped, it activated clip LED’s on the X-Touch. The Mackie protocol apparently doesn’t support a method for resetting the clip LED’s.

I fixed this by reassigning the VU meters for the channels as they should have been from the start. It doesn’t mean you can’t get an individual channel’s output to be so loud where it won’t trigger the clip LED, but that typically shouldn’t happen. Now, when the main VU out clips, it won’t trigger individual channel clip indicators.

EQ “Q” knobs

Propellerhead added all this seldom used stuff like FX Pre’s and Inv button controls but they didn’t include the “Q” knobs for the EQ.

Yeah, I fixed that, Q knobs are now part of the EQ settings.

The “EQ On” and “E” also have dedicated LCD displays, too, so it’s easy to see when the buttons are on.

Fuller text descriptions

Propellerhead cut text super short, much shorter than it needed to be. Most of the time, Propellerhead didn’t even use the full 7 characters. Or they spanned text across multiple LCD windows, which on the X-Touch’s separate digital scribble strips makes text look ridiculous. “Makes t ext app ear lik e garba ge.”

My layout uses the full 7 character space of Mackie MCU Pro, Behringer X-Touch, iCon Qcon, PreSonus FaderPort 8, etc. I also call out text descriptions of what the knobs, buttons and even push encoders and meters do (Propellerhead only called out the knobs, sometimes not even doing that).

I typed out descriptions the way it makes sense to us, Reason users. Knobs on the virtual SSL mixer are labeled the way they appear on the mixer themselves.

Also, absolutely no static text spans across LCD screens, so no words get split between two strips. Hallelujah…

And finally, every single section (TRACK, PAN, EQ, etc) shows a channel’s corresponding digital scribble strip. Propellerhead had two sections not show channel strip info and it was the biggest reason someone would end up lost at where they currently were in regards to channel bank, channel number, etc. Ensuring digital scribble strips appear anytime no matter what you’re doing is vital to being intuitive.

[Edit: 03/22/2018] I also added “disconnect” text when when the mixer disconnects. Text also doesn’t cut text across LCD screens. This area also shows which version of the MJ Enhanced Universal Control is being used.

FX names displayed on digital scribble strips

[Edit: 03/22/2018] The names of the send and return FXs are displayed on the digital scribble strips, making it easy to see where exactly the “Echo” or “Plate” is located at.

Intuitive layout

I poured over the design for weeks to come up with the most intuitive layout given the constraints of the mixer and software. Things are where you expect them to be. Propellerhead had the EQ section was on the send button and the mastering section was on the EQ button.

In my layout, hardly anything is placed behind the push encoders (the push knob buttons) because you can’t see when the functions are on or off until they’re clicked and changed (that’s generally bad design).

When changing the loop positions using the “drop” and “replace” buttons, touch the magnifying icon button at the center of the move arrows to return back to normal mode. Here’s a description of what buttons using the MJ Enhanced Mackie Universal Control for an X-Touch or MCU Pro. Click image for larger view and make sure to zoom in. Layouts for iCon Qcon and PreSonus FaderPort 8 should be similar.

Peter Arvidson shared a button layout rendering for the MJ Enhanced Universal Control running on X-Touch’s (that’s also compatible for the MJ X-Touch Trinity and MJ Enhanced Combo Extender).

Loop marker enhanced

The loop marker display LED has been enhanced over previous versions of the MJ Enhanced Universal Control and MJ Enhanced Combo Extender. The LED markers now display more data (ticks).

Notifications

The MJ Enhanced Universal Control will notify you when it’s not locked to the master mix section.

Redesigned encoder LED display modes

[Edit: 03/22/2018] Propellerhead only used two encoder ring display modes for their remote maps, even though there’s support for five or so modes. Using different LED encoder modes wasn’t working when the MJ Enhanced Universal Control was first released (no idea why, I typed the codes correctly), but now I’ve gotten them working.

I’ve changed most knob LED types to be one single LED. This makes much more sense visually as a knob’s default “home” position may be at 2 o’clock, yet showing an LED “bar” style display that fills up from left to right doesn’t match contextually.

Remapped layouts and added various buttons

I remapped the layouts. Now the dim -20dB is on the group button, click on the click button, preclick to the right of the click button (confusingly called the “solo” button), loop on the cycle (loop) button, undo on the undo button and redo appearing beneath it on the enter button (the mixer has no “redo” label button anywhere).

I added the most useful functionality Reason’s code allowed for while focusing on trying to make the button labels make logical sense.

  • Automation write / “WRITE” (self-explanatory)
  • Alt take / “ALT” (self-explanatory)
  • Overdub / “OPTION” (think ”O” for “Overdub”)
  • Auto-quantize / “LATCH” (MIDI notes “latch” in place)
  • Tap Tempo / “TOUCH” (“touch” repeatedly for “tempo”)
Return and send FX meter LEDs added

[Edit: 03/22/2018] Added return FX meter LED for the encoder LED rings.

This was taken using the MJ Enhanced Combo Extender

In the remote map, you can edit the level, pre and on / off controls of all 8 sends of a channel when in channel select mode (“SELECT” – “SEND” buttons). But when in the general “send” mode, before you could only control the send controls of just “send 1” for all 8 channels at once. I never found this useful. When would you ever want to control just send 1 across 8 channels at once?

Adding in return FX meter LEDs make much more sense. This is really awesome as you really never know what’s going on with those LEDs because they’re not visible most of the time. Before adding this function, I never even knew how the LEDs functioned or how useful they could be for visualizing what’s happening with the FXs.

Rotary LED’s turn off when a rotary has no function

(Edit: 03/22/2018) I was able to get the rotary LED’s to turn off their display when only the “REC” button is being used. The remote map system defaulted to having the one LED encoder light on when nothing was assigned, which made it confusing to know when a knob had no function.

Select button illumination

[Edit: 09/26/2020] MJ Enhanced Universal Control version 6.0 add illuminated select buttons. Such an awesome addition. It’s such a massive boost to the usability of the mixer’s interface.

Time display

The time display’s been fixed. I previously wrote:

“If something is a minute and 3 seconds long, it should be displayed “1:03”. Or, in other DAW’s, time is displayed on the X-Touch as “001 03” or some (smartly) add nanoseconds “001 03 38“. Makes perfect sense. Propellerhead? They display it as “0 1 3”. It looks and ticks by like it’s at “13” seconds since Propellerhead stupidly didn’t code in any zeros between the “1” and ”3”.”

Now the time displays as it should.

Time display auto hides

When the minute or hours are at 0, the display auto hides those numbers. Groovy.

13 seconds
1 minute and 3 seconds
VU meters in every section

Propellerhead only had channel VU meters in three of the five sections. Now, every section displays the channel VU meters as they should.

VU out meters

[Edit: 03/22/2018] I added VU out meters to the Plug-in’s 8th and 9th channel LED encoder rings. Propellerhead had master out VU displaying on the X-Touch’s actual VU meters for two sections, which was causing things to crash. This horrible code and features have been removed and I was able to add back the correct functionality into the encoder rings.

Doesn’t crash the control surface link, doesn’t activate (X-Touch specific) annoying channel meter clip LED’s and it doesn’t take away VU meters of the individual channels.

100% of all functions have text descriptions

When hitting the “select” button for a channel and going into the different modes, when a knob has a function, it’s clearly labeled what it does. Everything is called out.

[Edit: 04/28/2020] In the screen shot above, the mixer’s channels were on an unreleased song when this article was first released. That song’s since been released as Window Fog. Click play below, the very first piano you hear is on channel 2, “1Rhode1”.

Click to play in new window

Some features did more harm than good

Just because something can be mapped to a button, doesn’t mean it should. Car manufacturers could place additional buttons to control the car’s horn in the back seats… but they don’t do it because some things do more harm than good. Same is true with Reason.

Here’s some of the things that could be placed and why they weren’t.

Changing mastering / device / FX patches

There’s no labeling for these buttons and, in testing, songs were nearly ruined accidentally changing patches without realizing the wrong buttons were hit before saving projects. Nightmare.

[Edit: 09/26/2020] This feature is present on the MJ Enhanced Combo Extender and the MJ X-Touch Trinity.

Saving

There is a “SAVE” button on the mixer but this is way too dangerous of an option to have as a one-touch button. Since I can’t add in a two button press combination sequence, there’s no save button functionality. You’re welcome.

MIDI track mute / solo

This is one of those features that seems like it would work well, but it doesn’t because of the nature of having to be on a selected track in the sequencer and issues with multiple MIDI lanes, etc..

There’s no dedicated button label for it and, in testing, MIDI tracks were constantly getting accidentally muted and unmuted so I removed MIDI track mute / solo functionality.

Tempo Up / Down

Seems like it would be a useful function, but there’s no button labeled and, in testing, it was too easy to accidentally change the tempo.

Tap tempo, on the other hand (“TOUCH” button) makes more sense as pressing it once or even twice in a row accidentally won’t change the tempo. And if using the tap tempo feature, having a button to press is more ideal than clicking a mouse or tapping a touchpad.

Target Track Enable Monitoring

This would be useful on the mixer, no doubt… but accidentally activating this feature can cause screeching feedback and there’s no clear button label to assign this to (making accidental presses even more likely).

Automation As Performance Controllers

This is the feature where automation data will be inside MIDI note clips instead of outside. I hate automation data being inside MIDI note clips and, since there’s no clear button label for this, it isn’t included.

Things Propellerhead didn’t code support for at all

Color-changing digital scribble strips (X-Touch specific)

This one isn’t on Propellerhead. Color changing scribble strips aren’t part of the Mackie protocol and X-Touch’s only show multi-colored channel strips when connected to xAir mixers *rolls eyes* and no other DAW’s. For all intents and purposes, pretend the X-Touch doesn’t even have color changing digital scribble strips. (I personally think colored digital scribble strips look tacky. Makes the X-Touch look less like a Mackie contender and more like a Fisher Price rival.)

Dedicated bus control

There’s no function in Reason to switch to just bus channels. Too bad… Reason is begging for behind-the-scene updates!

Keyboard key functions

Same situation here; Reason’s remote mapping can’t assign functions like ”F6” (rack view), “Z” (zoom view), “F8” (tools pop up) or a host of other useful things.

View changing

We already know the view changing function keys aren’t available, but there’s also no way to set up view changing directly in the remote map files. In future updates, Reason needs these aspects updated, not more bloated synths.

Zoom functions

These features are supported by other DAW’s but Reason lacks general zoom controller support (not just Mackie). Reason needs an overhaul to support things like this.

How to install the MJ Enhanced Universal Control remote map

Click the link below to download the zip file.

mjenhancedmackieuniversalcontrol.zip

Windows

Extract the contents of the mjenhancedmackieuniversalcontrol.zip file. Open the “2 MJ Enhanced Universal Control” folder, where you’ll find a “Remote” folder.

In a new window, navigate to the location of Reason’s configuration folder C:\ProgramData\Propellerhead Software\. The files will be hidden so here’s how to unhide them.

Copy remote maps

From the “2 MJ Enhanced Universal Control” folder, navigate to “\Remote\Maps\Mackie\” and copy the files. Then paste them to “C:\ProgramData\Propellerhead Software\Remote\Maps\Mackie\” folder. Select yes to replacing all files, no duplicates can be kept in the same folder or Reason may not correctly work.

Copy codecs

From the “2 MJ Enhanced Universal Control” folder, navigate to ”\Remote\Codecs\Lua Codecs\Mackie\” and copy the files. Then paste them to “C:\ProgramData\Propellerhead Software\Remote\Codecs\Lua Codecs\Mackie\” folder. Select yes to replacing all files, no duplicates can be kept in the same folder or Reason may not correctly work.

macOS Catalina and newer and / or Reason 11 or newer

Extract the contents of the mjenhancedmackieuniversalcontrol.zip file. Open the “2 MJ Enhanced Universal Control” folder, where you’ll find a “Remote” folder.

In a new window, navigate to the location of Reason’s program at “Macintosh HD\Applications”. Right click on your Reason program (i.e. “Reason Suite 11”) and select “Show Package Contents”.

Copy remote maps

From the “2 MJ Enhanced Universal Control” folder, navigate to “\Remote\Maps\Mackie\” and copy the files. Then paste them to the folder inside the Reason application to “Contents\Resources\Remote\DefaultMaps\Mackie\” folder. Select yes to replacing all files, no duplicates can be kept in the same folder or Reason may not correctly work.

Copy codecs

From the “2 MJ Enhanced Universal Control” folder, navigate to “\Remote\Codecs\Lua Codecs\Mackie\” and copy the files. Then paste them to the folder inside the Reason application to “Contents\Resources\Remote\DefaultCodecs\Lua Codecs\Mackie\” folder. Select yes to replacing all files, no duplicates can be kept in the same folder or Reason may not correctly work.

macOS High Sierra and older and / or Reason 10 and older

Extract the contents of the mjenhancedmackieuniversalcontrol.zip file. Open the “2 MJ Enhanced Universal Control” folder, where you’ll find a “Remote” folder.

In a new window, navigate to the “Macintosh HD\Library\Application Support\Propellerhead Software\Remote\”.

Copy remote maps

From the “2 MJ Enhanced Universal Control” folder, navigate to “\Remote\Maps\Mackie\” and copy the files. Then paste them to “Macintosh HD\Library\Application Support\Propellerhead Software\Remote\Maps\Mackie\” folder. Select yes to replacing all files, no duplicates can be kept in the same folder or Reason may not correctly work.

Copy codecs

From the “2 MJ Enhanced Universal Control” folder, navigate to “\Remote\Codecs\Lua Codecs\Mackie\” and copy the files. Then paste them to “Macintosh HD\Library\Application Support\Propellerhead Software\Remote\Codecs\Lua Codecs\Mackie\” folder. Select yes to replacing all files, no duplicates can be kept in the same folder or Reason may not correctly work.

Reason configuration

Now Reason MUST be fully restarted in order for the Lua and MIDI codec files to take effect. It may be best, especially on macOS, to fully restart your computer to ensure Reason isn’t still running in the background.

Open Reason and right click an empty area of the virtual SSL’s mastering section and select “Lock [the name of your mixer]” to keep your MCU Pro or X-Touch locked to the mixer.

Using the MJ Enhanced Universal Control is an absolute joy

Getting the X-Touch was one of the best purchases I’ve made. It helps make my music come alive. When people come over, of all the hardware of my small, corner studio, the Behringer X-Touch is the always the thing that people remember the most.

(Edit: 03/22/2018) The sides of the X-Touch and X-Touch Extender can be removed so that they rest flush against devices. Here’s what they look like.

I’d also like to see pictures of people’s desk or studio setups using the X-Touch, so send them my way.

The evolution of the MJ Enhanced Universal Control

[Edit: 09/26/2020] I no longer use the MJ Enhanced Universal Control. But… for good reason; I’ve evolved it into the MJ X-Touch Trinity, a 24 channel behemoth and a world’s first for Reason Studios. If it wasn’t for how great the MJ Enhanced Universal Control performed, I would have never bothered evolving it from an 8 channel to a 16 channel to final 24 channel version. The great news is that all three versions are being developed and maintained in unison. So improvements to the MJ X-Touch Trinity are shared to the MJ Enhanced Combo Extender and the MJ Enhanced Universal Control (when possible).

MJ X-Touch Trinity 24 channel full control Reason mixer interface

Just like my music, I’m sharing this 100% for free

I’m sharing this with people for free because I want others to have a good experience with Reason. If you liked this, check out my music on Apple Music, Spotify, YouTube and other places. If you hear something you think people will enjoy, I’d appreciate it if you shared it with them.

Here’s GT Bray, one of my ambient songs created with this remote map. Click play…

Click to play in new window

Later. – MJ

128 archived comments

  1. I personally tested that the remote map is working for Reason 10 (I own Reason 9.5 currently and don’t have plans to own Reason 10). This is expected, as Propellerhead, for better or worst, doesn’t update the way Reason works with hardware for new versions. So when hardware works with one version of Reason, it typically means it’ll work for all future versions (Reason 11, 12, 13, etc).

  2. I’m having trouble getting anything related to the SSL mixer to respond to my x touch. Did I miss something? No dice on meters, fader banks, panning, eq, etc. The drop and replace for placing L and R markers are working, so I know I’ve got the mapping files replaced. I’m in reason 10.

    1. Someone else hit me up describing a similar situation. His situation was that he had forgotten he remote override mapped functions from a previous mixer. I assume you aren’t in the same situation. What happens when you remove the custom remote map files, do your fader banks, etc start working?

      1. I did have that happen, but clearing the remote over rides did not do it. I noticed if I change the files and restart, Reason will message “enter your password so it can make changes”. I’m wondering if it’s reverting the files? Overall the x touch is behaving like an m audio axiom, where only the Reason devices are fully mapped out and everything else doesn’t respond. The only way I can get the faders in the mix window to move is if I map them.

      2. Perhaps a better question, similar to the bcr2000 issue is: How does one prep the focussed SSL channel for midi control through Mackie Control, is it the same process? My x touch seems to behave exactly like the bcr2000, changing its lay out for every device selected. I’d have to make a midi track for every channel strip to be able to control it. I feel like this would be an obvious option in the Additional remote overrides menu, but of course its not! I see how I can map it to change the current synth patches and etc. but no controls for the ssl, other than the control that moves the yellow focus icon back and forth, and a control to move it 8 strips at a time. Is it something to do with this?

      3. I Think I got it (I’m at work [should be working but this is erking me] so cant test it now) but found this. https://forum.reasontalk.com/viewtopic.php?t=7343641 Looks like you need to select the focus as “master section” for it to work with the SSL Mixer. Some how I have to make the master section a focusable midi track…I’ll update later. Thanks for your pioneering work Jaexx!

        1. Hey B. Thanks. Did you make sure to right click an empty area of the SSL mixer (typically towards the very right) and select “Lock to X-Touch” (whatever your mixer is named in Reason)? Sounds like you did but figured I’d mention that.

          Also, you should make sure your account name in Windows is an administrator and not simply a user. Let us know the outcome.

          1. That fixed it! My work around is to create a track/midi lane for the Master Section, (did this by automating the master fader then deleting the automation lane). I like this method as you can still cycle through the rest of the track/midi lanes and the X Touch will remap to those rack devices. I found this article https://www.soundonsound.com/techniques/hacking-remote-files-reason from SOS about custom mapping any rack device including extensions and existing maps. Hope this helps anyone who gets stuck at this point!

  3. One last question, how do you keep the parameter’s name always displayed? Is that within the Lua Codec or a mapping trick?

    1. If I understand your question right, you hit one of the “SELECT” buttons on whichever channel you want to control, then hit the button again to return to the normal mode.

      1. I mean as far as the actual “programming” steps you had to take to tell the controller to always have those parameters displayed under the knobs. I set up my own remote map for a Rack Extension, but the parameters only show up when I move the knob or fader. I love how you got them to always be displayed so I’m not guessing before turning.

        1. It’s all contained in the remote map file. I don’t recommend using the X-Touch as a universal controller though, I recommend using something like an Ableton Push or NI Maschine and Retouch Control as a universal controller.

          1. Thanks man, much appreciated. I figured as much, I just can’t figure out the right group define or something to get it to display. Yeah I just took a look at your set up, I think a nice universal controller set up with will have to be my next addition.

      1. One question, when you cascaded your X Touch w/an an extender did you have to create an additional remote map file or did you just install it as an additional Mackie controller in order for it to read so you can bank up/down channels????

        1. Lotta’ bad news for all of you Extender hopefuls… I didn’t have an Extender. And bad news, Reason can’t do normal software cascading with the Mackie Control protocol. And, even more bad news, not only is a separate remote map needed. The most bad news of all?? Using an Extender (Behringer X-Touch Extender at least) will crash in Reason.

          Don’t worry, good news, I bought an X-Touch Extender two weeks ago. Better news, I fixed the crashing issue. Even better news than that, I created an even more powerful and feature-packed remote map from scratch. Best news of all, I’m nearly done writing the article and it and the remote map be posted in a couple days.

  4. Boom, the MJ Enhanced Combo Extender. https://www.jaexx.com/blog/r

    Without the MJ Enhanced Combo Extender, you wouldn’t be able to use X-Touch and X-Touch Extenders in Reason without crashing. It includes all these awesome enhancements.

    Not only is that exciting in itself, but I’m bringing many of these enhancements to the MJ Enhanced Universal Control. The completely new “flip mode alternative text” will be even more useful for the MJ Enhanced Universal Control since it’s more limited on text space. I’ll be updating this page and the MJ Enhanced Universal Control remote map, but it’ll take a few weeks.

    The new additions I’ll be adding really are awesome… but I’ve pushed against the confines of what’s possible within Reason and the Mackie Protocol. As exciting as this update will be, I think we’ve reached a limit on new improvements.

  5. Version 4.5 of the MJ Enhanced Universal Control is out now. This has been a really, really big update. Each time I felt I was ready to post it, I kept comin’ up with new things to include. Again, I think I’ve pushed the remote map and Lua system about as far as it can go so don’t expect me to be able to keep doin’ new things like this.

    A big change this time is that I’ve done some custom programming of the lua codecs. Before, only two encoder modes were being used. Now there’s 8-9 encoder modes with two new LED modes I was able to program from scratch, so I’m really proud of that feat (since I don’t know any coding languages and get by via reverse engineering).

    The new alt-text mode really is gonna’ help you all out. Now you don’t have to memorize where things are in regards to the channel controls; 100% of everything used in the channel controls have dedicated texts, either in normal mode or in the new alternative text (“FLIP”) mode. And… the code nearly wouldn’t let me do this… the faders still work as normal in flip mode. With the inclusion of the new “turn off encoder LEDs”, things are even more intuitive.

    I think y’all are gonna’ love this update. If you haven’t, check out my music and share it with some people you know. jaexx.com/where-to-listen.html

  6. This sounds amazing! Is there a way to use this with Ableton and or Studio one? Cheers

  7. Having read this article, I’m planning to purchase an X-Touch since what you have done is absolutely awesome and seems to give me what I’ve been looking for with the Reason DAW. Congratulations.

    1] I have a question on the extent of control that’s possible outside of the SSL functions and into a) Reason basic instruments and basic effects, b) Rack Extensions and c) VST instruments & effects. Would the control of any of this be possible with an X-Touch as modified by your code?

    2] If the answer is no or partially no, would you regard the remote maps and codecs that you’ve created as modifiable by a reasonably competent coder? If the answer to that is yes, then you might be open to accepting contributions of code snippets from the user community that would enable you to constantly update your package to become even more amazing? Let’s say for example that I’ve purchased a copy of Serum from Xfer Records (also awesome by the way) and I could hack an extension to your remotemap. Somebody else might want to do something for Expanse Hyperwave etc – you could end up with a pretty impressive library…. Does that seem possible from where you are?

    3] I’d like to know if it’s possible for users to contribute something back to you for creating this package – have you thought of that?
    (PS I’m assuming I go ahead and buy this X-Touch).

    1. Hey B, thanks for the nice words. The MJ Enhanced Universal Control still contains the configuration to control most older virtual devices (Subtractor, Scream 4, etc) that Propellerhead coded originally. But most new devices aren’t included because, frankly, motorized mixers should always be controlling the mixer.

      Instead, the device you’re looking for would be a true universal controller… which I happen to be involved with. Here’s the links…

      https://www.jaexx.com/blog/r

      https://www.jaexx.com/blog/r

      As far as giving something back, I work and share this for free because of my true passion for all this. Check out my music and share it with others. Search my third album, “Sound-sized Treats”, on Spotify & Apple Music.

      1. Hi J, most excellent response. If I ever thought you were brilliant at just one thing, I have now had my brain reset. What you are doing and have done for Reason is first class. I hope you are recognised and appreciated by Propellerheads?

        OK, I now understand how you are set up, and where the limitations arise with what can best be done on which controller. That was really helpful for me and thank you again.

        Regards
        Bob

  8. Works like a charm! Your remote was the reason i bought a X-Touch + the Extender. Couldn’t be happier! Dennis Lenz's home studio with X-Touch, Extender and three displays

  9. I bought an X Touch last week and installed your remote map and it’s AMAZING! one thing, and maybe it’s me but there doesn’t seem to be any mapping for the release knob on the ssl buss comp. There’s control for everything else but the release. Am I missing something?

    1. I don’t have my X-Touch available right now, but I don’t think there was room to fit controls such as the buss comp release knob for the MJ Enhanced Universal Control. It exists (has room) in the MJ Enhanced Combo Extender, however. https://www.jaexx.com/blog/r

  10. Version 4.6 adds ‘ticks’ to the LED beats display. Eric Segal helped get the ticks display working, right on man.

  11. The installation is different also, now the codec files are required for installation. Instead of having two versions of VU meters, now there’s just one unified version (less enhanced). The files can now all be installed by dragging one “Remote” folder, which will install the multiple files in the correct directories.

  12. I have an issue where the channel 8 Fader “fights you” it’s as if the fader is receiving a Hold State and when you move it, your basically forcing it to move. This only seems to happen In Reason. In Pro Tools it’s fine. It only happens if there are 8 or more tracks.

    1. I’ve experienced this with my own X-Touch(s) (with the stock remote map also). Out of all the people who’ve contacted me (publicly and privately) about X-Touch’s and Reason, no one’s ever mentioned a similar issue. I narrowed the issue down to “weird” electrical power. I tested an additional X-Touch in my place and it had the same issue you described (but on all faders). Taking the X-Touch to a new location, the issue disappears. I’ve used my X-Touch at around 9 different locations and it works flawlessly.

      At my place, no other devices have issues (including Behringer’s BCF-2000 motorized mixers). I tested plugging the X-Touch(s) into different outlets and get different degrees of the same result. I eliminated the issue being another electronic device in my place causing the issue by turning off all circuit breakers except one that contained nothing else plugged in besides the X-Touch(s); issue still persisted.

      I eliminated the theory of it being wireless (radio) interference by connecting an extension cord from another building and running it into my place with all my electronics on; the issue disappeared.

      It definitely is something to do with the electrical properties of my place, which I should add doesn’t suffer from brownouts, power fluctuations or other issues I can tell. I tested the power draw with an ohmmeter from different outlets and found nothing out-of-place. In fact, it’s one of the best places I’ve lived in terms of “electrical quality-of-life”. Yet something in my place’s electricity is causing the issue.

      Whether or not you’re havin’ the same issue, I can’t say (but I suspect you are). I only use Reason, I don’t use or own other DAW’s. But I tested the issue in Ableton Live and Reaper. The issue didn’t happen in Live but (if I remember correctly) did happen in Reaper.

      I found a solution by using a rack device power conditioner, a LiveWire PC900. I talk about it here. https://www.jaexx.com/blog/s

      The PC900 gets its power from a extension cable that snakes along the baseboard to a nearby outlet that isn’t on the same circuit as the massive amount of studio devices around the studio rack. The PC900 then exclusively powers the X-Touch and X-Touch Extender mixers. The issue’s 99% eliminated using this method. I’ll go weeks without trouble; when an issue happens, it’s only for about three minutes or so.

      So yeah, that’s what’s up. I’ve been privately contacted by at least 50 people regarding the X-Touch and Reason; no one’s had this issue. Behringer’s support (2 years ago) never heard of this issue and, of course, can’t replicate it. I think the issue lies in the way the X-Touch was made (or Mackie’s Universal Control protocol coding) and the way Propellerhead (badly) programmed Reason’s support for hardware mixers. (I suspect Mackie MCU Pro’s would act the same way in my place.)

      Would this stop me from recommending X-Touch’s? Freak no. I absolutely recommend X-Touch’s, I love them. If my X-Touch’s got stolen I’d buy’em again in a heartbeat.

      1. I notice that Fader 8 does not transmit the “touch/untouch” signal via MIDI. Even if I pull the fader knob and touch the metal directly. Additionally the X-Touch is plugged into a UPS that conditions the power. Thanks for your work on this project.

        1. That sounds like a completely different issue then. Does this happen with the default remote map? Do you have another computer to install Reason on to test your X-Touch with? Have you checked to make sure a family of leprechauns isn’t nesting inside? My money’s on leprechauns.

  13. Thanks Jaexx, really good work !!!
    I have the issue of clip led, reset button do not works.
    I use your codec with free midistroke on Mac, so i have mapped the function button for view and other utility.
    PS: Sorry for my band english.

    1. Hey P. Is it the clip LED in Reason, or the channel clip meters (those can only be reset by power-cycling X-Touch’s)?

  14. Hey Jaëxx!! Im so glad i found this. The map works great However, I have the X touch One. Obviously much less functional version. My question: Being that the X touch One is missing a pretty large part of the master section(Specifically the encoder assignment section) is there a way to use my useless function keys as encoder assignment keys? Keep up this awesome work and the great music! Thanks!

    1. Hey Z. If I remember correctly, there wasn’t a way to use them in the remote map. So I don’t think you can. Try remote override mapping them to something. If they can be override mapped, maybe that’s a way to get some extra functions in there. If not, then they absolutely can’t be controlled via remote maps.

  15. Hi mate, thank you very much for your work and effort!
    Maybe it would be a nice thing to have an overlay created that is specific customized for this mapping that you created (if it is necessary).
    Then you could sell it through this page, for your efforts.

    btw. i read this in a thread at KVR audio:

    To get the scribble strips in colour (and even then only 16 it would seem) the unit will need to use either the ethernet or midi ports since the xctl protocol does not offer usb as a choice. To offer usb as a choice this would need to be added to the firmware.

    1. Hey RecordFactory. Yeah, overlays would be a good idea. Although knowin’ me, I’d still offer’em up for free. I like the idea of givin’ back.

      And yeah, that’s my understanding about how the X-Touch’s colored digital scribble strips work. I have a strong feeling that Behringer is keeping the color-changing options reserved as a way of pushing people into buying X-Touch Air’s, similar to how Apple keeps iMessage locked to Apple devices.

      So although X-Touch’s may be coded to work over Ethernet or midi ports, I see no reason a firmware update couldn’t change them to work over USB. It’s either a conscious choice on their part, or maybe the engineering team isn’t staffed to integrate things like this (they seem over-taxed as it is).

      1. X-Touch controller with colored scribble-strip displays

        hi mate!

        a follow up: someone else is messing with it as well, looks nice though colored scribble strips 🙂
        checkout this thread over at reasontalk forum

  16. Hello and thank you for your work. I have a X-touch One and uses a slight modified version of your lua script. I was abled to alter between gain and pan on the only rotation knob using the function buttons F1 and F2. I’m not so good at Writing Lua scripts and my vision was to have the function buttons F1 to F6 for changing between the Groups Gain, Dynamic, EQ, Inserts, Send and in the end the Pan/Width. To alter the rotate button to a certain function in a Group use the Arrow up/down buttons. For example you pressed the F3 for EQ and using Arrow up/down to change between the different eq knobs.
    I have seen a lot of comments on the internet about bad functioning on the Mackie Control in Propellerhead Reason and sorry to say the X-touch controllers are not selected as peoples first choise because of that. I am satisfied with the X-touch One and wished the Propellerhead to engage them selves more in making a better functioning between Reason and Mackie Universal Control. Attached a Picture on my homestudio
    Mathias Lindgren's home studio with displays, controller surfaces and speakers
    /Mathias (Sweden)

    1. Hey Mathias. Thanks for sharin’ the photo. That’s a cool setup you got there. And that sounds like awesome work you did getting an X-Touch One workin’ like that. It looks like you’ve got your setup optimized for what you need it for. If someone’s using an external mixer like you are, I can see the appeal of an X-Touch One.

      1. Hello mate, Have finished my modified version of modified mixer map for Xtouch One. Almost all functions are in place. Something that disturbs me is the wrong values when switching to for example the Eq when the values in the lcd display under the rotation knob doesn’t match the value in propellerhead. When moving the mainfader it´s the same value in the lcd screen as in Propellerhead. fix? is it possible to rewrite so the scaling is correct?

        /Mathias

        1. Hey M. I’m fairly certain this issue lies in the Lua script as I remember running across code that referenced values and how they get displayed to the digital scribble strips.

  17. Hi Jaexx, I tried to update from an older version of your Lua script. However every time I open Reason now it asks me for permission to make changes and then reverts your scripts back to factory settings. Now i can’t seem to get the x touch to work in Reason at all anymore. Please help!

    1. Fixed it already – so it was a bad idea to replace the entire Mackie folder on Mac OSX because Reason needs that .png file to open the codecs. Once I replaced the missing files, it jumped back into action. Many thanks for the update.

        1. For Mac OS I recommend to manually bring each file into their folders. Copying the whole folder over will delete all of the other codecs and wreck the current set up…I always have a clone of my hard drive and was able to retrieve everything.

          A custom Jaexx Mackie.png file would be fitting!

  18. Yo Jaexx
    Congrats on this really awesome – apparently first working as expected – script for the x-touch.
    whould it be possible to add some functionality to the “function” buttons? as far as i see they are without functionality for now.
    because i whould need something to control the rotaries and buttons of the channel strips at the same time, like hit F1, to set the rotaries and clip buttons of the surface to control rotarie 1 and button 1 of each channel strip. Hit F2 to control rotarie 2 and button 2 of each channel strip and so on. this is my request (if you take any at all :/ :P), because i have almost no knowledge in coding

    cheers, aiden

    1. Sorry about the first reply, Disqus had an issue with the reply.

      I wish the function keys could be seen in Reason, but they’re invisible to Reason. There’s a lot of buttons that are invisible to Reason (I described this in more detail in the article).

      1. Oh so it might be impossible to use those buttons? I though another idea was it to hit “SEND” once to to access the controls they whould have normally. Hit it a second time to make the rotaries and rec buttons control rotarie 1 and button 1 of the mix/audio channels. A third time for rotarie 2 and button 2 …

        1. It is impossible for practical purposes. A MIDI interface could be set up as a middleman, like how the PusheR team does getting the Ableton Push working with Reason, but that’s not practical.

          1. Currently in Reason 11 Suite, they are recognised when pressed in the ‘Edit Remote Override Mapping’ dialog – Does that mean they have been made available in 11, or is the availablility in the override settings not connected to the ability to map in the codec? Excellent work on everything else btw!

          2. Hey M. Yeah, during Reason 8 those buttons couldn’t be seen by Reason (not sure why). But after version 9 or 10 they’ve been able to be seen and can be mapped via a remote map. The only issue is that things like switching windows views isn’t supported by the remote map set up of Reason and I can’t assign key strokes within the remote map.

  19. Those on macOS, if the “copy folder” method causes issues, try manually copying over the files directly.

  20. Reason 11 Suite notes: (Re: Mac OS). With Reason 10, the location of the maps and codecs was Library-App Support-Prop Software, etc. If the MJ map is there, you will probably find that it does not load up in Reason 11. In Applications, right-clicking “Reason Suite 11” and choosing “Show Package Contents” you find another “Remote” folder. In that, there’s a “Default Codecs” folder, and a “Default Maps” folder. At least in my case, this is where Suite 11 is looking for maps. I replaced the codecs, and the map with the MJ files there. Problem solved. The MJ map is fantastic. BIG thanks to Mixer Jaexx for making this map. I like the MCU Control Pro. But MJ, honestly, you make great points about the X-Touch vs Mackie, and it makes me want one..

  21. I have this issue where if the VU meter goes too high I get an error:

    The “X-Touch” control surface did not respond properly and has therefore been inactivated.
 More information can be found in the control surface preferences dialog by clicking on the red error symbol next to the control surface.

    When I do that it reads :
    There is an unknown problem with the control surface or the selected MIDI ports.

    I’d like to see if the factory VU lua codec would work better but i don’t see the “Factory VU” or “Enhanced VU” folders you were talking about in your post.

    1. The factory codec codecs are found inside the zip folder “3 Factory Settings”, “Remote”, “Codecs”, “Lua Codecs”, “Mackie”.

  22. First of all a huge thanks for your work.
    Massive work it must have been 🙂
    I have one question : if I want to record the automation of my faders in the SSL mixer. Is there a quick way to create sequencer tracks for all of them?
    Or do you do that ALT + Clicking them?
    (or don’t you do that at all)

      1. Thanks for the quick reply!
        I still have a lot to figure out, but so far a lot looks like working as expected.
        One thing I do have doubts (if I did everything correctly) are the remapped buttons in modify, automation etc.. Like ‘group’ being mapped to -20db
        If I press group nothing happens, what part of the movie could I have skipped?

        1. It could be existing remote override mapping. I’d start with a demo song, locking Reason’s mixer to your hardware mixer and seeing if the same thing happens. You may also try removing any other music hardware from Reason. I’d also disconnect all other music hardware (physically) to see if theirs a conflict and reboot Windows. It could also be due to something weird with your Reason’s preferences (installed files) which may require a reinstall of Reason and / or Windows (not something I recommend unless a last resort). If you have a second computer (even if it is older and can barely run Reason), you may want to try installing everything and see if the problem is duplicated.

          1. I ended up re installing reason completely.
            Making sure I deleted all the hidden folders as well (app data, local user data etc. etc.)
            Buttons now work like they should.
            I think it might be the existing mappings, as I have been using some other devices prior to the X Touch
            Now I just have to get all the preferences right again.
            Thanks a lot for your support!

          2. I have made a short post on my website about the X-Touch + Reason and you are (of course) mentioned quite often!
            I have added your mapping image too, (with credits), if that is not ok, please let me know. I will have to make my own in that case.
            http://www.tricks-and-tips….

          3. Hey P. Glad you got it workin’. Crazy you had to nuke Reason, I suspect maybe 1% of people end up having to do that. But sometimes things get weird with programs and technology in general like that.

            You did a great write up in your post, I also liked your video. I agree with your statements regarding the X-Touch. Now you’re next big music purchase will be transitioning from an X-Touch solo to X-Touch + Extender. My combo extender map greatly enhances functionality. But focus on gettin’ to know all the functionalities of the solo mixer as you’ll soon understand how awesome getting an extender will be.

          4. Hahahahaha. Thanks!
            Who knows what the next purchase might be 🙂
            Maybe a USB controller (keyboard) that has good touch pads for drums. (my Oxygen 49 lacks those)
            I do have one question. Any chance you add horizontal zoom to the jog wheel?
            (combined with a button press or so)
            That is the main mouse usage for me right now when I’m in the sequencer.
            No idea if it is hard to make such thing.

          5. I don’t believe I can add that as the job wheel’s needed for position jogging. I use a knob on the Ableton Push 1 (running PusheR) in conjunction with the X-Touch’s to control horizontal and vertical scrolling. I recommend your next purchase be a Push 1 or 2 running PusheR.

          6. Thanks for the tip.
            The Push is out of my league for now.
            First I want to get a better USB keyboard .
            So I will dive into that 🙂

      2. I did put both the codec files in the lua folder (first moved the old ones)
        As well as the remotemap file.

        1. Hard to say. The first thing you should try is to make sure the MJ Universal Control map really is loaded up. If you’re using macOS and Reason 11, that combo definitely is causing some installation difficulties.

          1. It does show your name in the scribble strip displays. I’m on Windows + Reason 10
            Can I check something to see where it went wrong?

  23. MJ Enhanced Universal Control’s been updated to version 5.0. Version 4.5 worked in early versions Reason 11.0, but Reason was causing some remote maps to not load (updating the factory file version numbers wouldn’t always work and sometimes causes issues in Reason 9.x). This was happening to non-factory remote maps reported by others (I experienced it too).

    At some point between Reason 11.0 and 11.2, the issue in Reason seems to be fixed. Now that the issue seems to be gone. Update to the MJ Enhanced Universal Control 5.0 for versions of Reason newer than 11.

  24. Regarding Reason’s reliability with remote maps, I think versions of Reason, possibly as early at 10.x leading up to 11.1x, where causing issues with remote maps. I tried installing multiple remote maps repeatedly (creating some new remote maps code) under Reason 11.2 and I didn’t experience issues like i have in past versions of Reason (dating back to version 6). So this may mean something in Reason’s been improved.

  25. Hi – I was really keen to use this because Reason’s map is so confusing, but it’s not clear if you’ve updated the map recently. I tried with Reason Suite 11.3.3d10 but I got an exclamation icon appear on the control surfaces page, complaining about these lines in the map file I assume – map entry with unknown mode. Perhaps Propellerhead changed something about the control surface implementation? I’d have thought you’d get the same problems using it yourself?

    1. Hey N. Yeah, it should work for the latest version. I say “should” because I’m I tested the MJ Enhanced Universal Control 5.0 three weeks ago on Reason Suite 11.3.x. Now, however, I’m building a massive update for the MJ Enhanced Universal Control, the MJ Enhanced Combo Extender and… a completely new remote map. So my MJ Enhanced Universal control is a prototype version. I’ll be releasing a version update for the MJ Enhanced Universal Control “when it’s done”. I’m developing all three remote maps in unison using a new method so that each remote map should get updated and released at once. The plan is to release this big update in like three weeks.

      But since you’re havin’ issues, I’ll try to get stuff rollin’ quick.

      1. No urgency of course – I didn’t mention I’m using Mac OS 10.15.6 but no idea why that should make a difference either. If I have some time I could remove the offending lines to see if the rest of the mapping works, I’m just unfamiliar with the mapping language. Have you thought of “open sourcing” the map – something like Github might be beneficial for collecting patches from other users but it might be more than you have time for…

        1. I just loaded up the MJ Enhanced Universal Control version 5.0 under Reason Suite 11.3.3d10, no issues. The problem seems to be on your end. One piece of advice is to make sure you don’t have any copies of any of the remote maps in the same location. Haven’t seen this issue with X-Touch or MCU Pro’s, but I have seen this with other remote maps. To clarify, I’m nearly 100% certain this isn’t anything in the code throwing those line-errors.

          Don’t expect the MJ Enhanced Universal Control 6.0 to fix your issue, whatever’s happening for you will likely still be happening. You gotta’ fix this issue or it’ll keep happening.

          I’ve noticed some people have had more difficulty on macOS. Some people’s fix was to… (are you sitting down?) …reinstall Reason. Ain’t sayin’ you’re at that point yet, though. But, to clarify, I’ve ran the MJ Enhanced Universal Control version 4.5 on macOS (pre-Catalina)… I actually coded that version on the Neonote (my MacBook Pro Retina).

          Try making sure Reason is completely exited, rebooting, then remove the remote maps and the Lua codecs, reboot again, install them again, start Reason.

  26. Hey yooo… I just released the biggest update the MJ Enhanced Universal Control’s ever seen. Big, bad version 6.0. I thought I hit the limit with version 4.0. But now, with version 6.0, this might truly be almost at the ceiling for adding new features or fixing existing issues. I gotta’ few ideas and things I haven’t had time to test out, so there’ll likely be a version 6.5 or 7.0 in the future… But this may be the end of what “enhancements” I can bring to the MJ Enhanced Universal Control.

    MJ Enhanced Universal Control version 6.0 adds notification when the mixer isn’t locked to the master mixer section; fixes legacy code in newer Reason versions that caused crashes if individual channel VU meters were too loud; reduces bugs from displaying leftover LCD text when exiting Reason; new green illuminated select buttons; LED time display fix (“01 03” vs “0 1 3”); LED auto-hides minutes and hour; enhanced loop marker LED display; and new method for maintaining remote maps in unison thanks to “RFX”.

  27. You hear about that new thing that came out for Reason Studios? Someone made a way to have a 24 channel motorized mixer that fully control Reason’s virtual SSL mixer natively via a single remote map, a world’s first. It’s pricey though, the interface costs $349 with a special promo price of $249. …Oh no, wait, it’s actually 100% free. The MJ X-Touch Trinity. Boom. https://www.jaexx.com/blog/

  28. Version 6.1 fixes a bug that was preventing the remote map from loading (code from the MJ X-Touch Trinity was causing it).

    1. Same error previous update, this i s the log (Reason Suite last update):
      Failed to load control surface: Mackie, Control.
      Map File Errors:
      Line 95: Map entry with unknown mode.
      Line 96: Map entry with unknown mode.
      Line 97: Map entry with unknown mode.
      Line 98: Map entry with unknown mode.
      Line 99: Map entry with unknown mode.
      Line 100: Map entry with unknown mode.
      Line 101: Map entry with unknown mode.
      Line 102: Map entry with unknown mode.
      Line 351: Map entry with unknown control surface item.
      Line 355: Map entry with unknown mode.
      Line 381: Map entry with unknown control surface item.
      Line 385: Map entry with unknown mode.
      Line 411: Map entry with unknown control surface item.
      Line 415: Map entry with unknown mode.
      Line 441: Map entry with unknown control surface item.
      Line 445: Map entry with unknown mode.
      Line 471: Map entry with unknown control surface item.
      Line 475: Map entry with unknown mode.
      Line 501: Map entry with unknown control surface item.
      Line 505: Map entry with unknown mode.
      Line 531: Map entry with unknown control surface item.
      Line 535: Map entry with unknown mode.
      Line 561: Map entry with unknown control surface item.
      Line 565: Map entry with unknown mode.
      Line 589: Map entry with unknown mode.
      Line 671: Map entry with unknown mode.
      Line 672: Map entry with unknown mode.
      Line 691: Map entry with unknown mode.
      Line 773: Map entry with unknown mode.
      Line 774: Map entry with unknown mode.
      Line 793: Map entry with unknown mode.
      Line 875: Map entry with unknown mode.
      Line 876: Map entry with unknown mode.
      Line 895: Map entry with unknown mode.
      Line 977: Map entry with unknown mode.
      Line 978: Map entry with unknown mode.
      Line 997: Map entry with unknown mode.
      Line 1079: Map entry with unknown mode.
      Line 1080: Map entry with unknown mode.
      Line 1099: Map entry with unknown mode.
      Line 1181: Map entry with unknown mode.
      Line 1182: Map entry with unknown mode.
      Line 1201: Map entry with unknown mode.
      Line 1283: Map entry with unknown mode.
      Line 1284: Map entry with unknown mode.
      Line 1303: Map entry with unknown mode.
      Line 1385: Map entry with unknown mode.
      Line 1386: Map entry with unknown mode.

  29. The MJ Enhanced Universal Control 6.2 now requires additional files for loading. Make sure these files are loaded or the remote map won’t load.

  30. Got an email from someone who tested out their iCon Qcon Pro G2 (and the extender versions) and said it works with the MJ X-Touch Trinity (24 channel version). So this should mean the iCon Qcon Pro G2’s will work with the MJ Enhanced Universal Control.

    As a side note, the PreSonus FaderPort 8 should work just as well. Be cool if someone tests it out and gives their feedback.

  31. For the MJ Enhanced Universal Control, I’ve updated the installation methods to reflect changes in how macOS Catalina and newer and Reason 11 (regular and Suite) and newer use a different process.

  32. Jaexx

    Great work on this, I got my X-Touch today and have been messing with Reason for a couple of hours.
    Not sure if I’ve missed it, but is there a button or method to ‘cancel’ the move L and R loop marker once you have pressed either Drop or Replace in the transport section? Currently I tried pressing again to toggle, and trying a few other buttons, but I can’t seem to see how it is cancelled, as it’s currently locking the jog wheel to moving the selected loop marker instead of reverting back to moving the main cursor, and locking the time / bar display to showing the location of the loop marker too rather than live timing during playback.

    Sorry if it’s something obvious!

    1. Hey M. Yeah, it’s not too obvious (originally set up by Mackie or Reason) but you press the magnify button that’s in the middle of the arrow buttons to the left of the jog wheel. You know you’re in the default mode when the button lights up blue.

  33. Hi Jaexx!

    First off – fantastic job of customizing this and allow us ‘outboard gear freaks’ to venture into our DAWS with a more musical and hands on approach – currently making my own custom stickers to litter over my brand new X-Touch, akin to your new mapping layout! Just one thing I have noticed however…If I went on the web for a few minutes, the X-Touch then fails to respond when I go back to the Reason window again (scribble strips , meters still show however, just all buttons fail to respond). Any ideas as to what this could be? It’s like it’s temporarily ‘disabling’ the codec files and then failing to read them again when going back to Reason. Not super critical, as deactivating / activating the control surface – or a simple on/off maneuver brings it back to life. Just a bit ‘annoying’ shall I say.

    Thanks for all your hard work! You could definitely make a business from all your skills buddy!

    Regards,
    Martyn

    1. Hey Martyn. Yeah, totally, it is like being able to work with our music in a more musical and hands-on approach. One of the things I love most about these mixers is the digital scribble strips.

      Speaking of digital scribble strips, I ain’t sure what’s goin’ on with your set up. Man, I’ve given it some thought but I just don’t know. My X-Touch’s (first 8 channels, then 16 channels and now 24 channels) haven’t done what you’ve described. I use my X-Touch’s all the time when Reason’s not the main focus. My X-Touch’s will run for days (with Chrome in the foreground, Reason on another virtual space in Windows) without issue at times. When something breaks the connection to the mixers, it’s usually the result of a USB device connecting or disconnecting. You’re also the first to report a specific issue like this.

      Do you get any messages in Reason when this happens?

      1. Hmmm, tricky. Thanks for looking into this. Maybe It is something to do with my computer and not the RemoteMap etc. I will keep on fiddling around and see if this issue springs up again. No prompt from Reason when the issue occurs. Thanks again Jaexx!

  34. HeyJaexx, I’ve been using it for a week now and it rocks! The UC would be almost worthless for Reason users without your script, but with it’s a great controller. Already noticed an improvement in my mixing flow and quality, just because this enables me to work hands-on and mix with my ears. More support on mapping options from Reason Studios would be great, enabling the F-buttons for example. If only they would link it to the regular F buttons on the keyboard you could change view, show the tool window, open/hide browser etc. Also supporting zoom options would improve the workflow significantly. Hope the guys at RS are aware how this would help a lot of producers. Thanks and keep up the good work!

    1. Totally. Havin’ those function keys and zoom supported would be so nice. Or if they don’t wanna’ invest in enhancing the remote protocol (remote maps, codecs, etc), find a manufacturing partner (like Akia) to create an Ableton Push-style universal controller.

      1. Yeah that would also be great! But a lot of manufacturers seem to develop controllers mostly aimed on live situations or hybrid surfaces. Which I partly understand since advertisements with guys rocking the stage with a controller are probably more appealing. What I especially like about the X Touch is that it has this typical mixer feel and layout. Nevertheless I am convinced that if RS would succeed to find/support a 3rd party developer to make an SSL style controller Reason as a DAW would become much more competitive to others.

        1. That’s a great point regarding live performing being a huge factor in designing an Ableton Push-style controller. And I feel you on the physicality of a hardware mixer. It’s awesome. Like how my Korg padKontrol matches the physicality of the Kong (no surprise since the padKontrol was what people at Propellerhead used during the Kong’s development).

          That’s one of the things unfortunately like 99% of people forget in this whole “leaving Reason for another DAW” debate is the mixer. There’s lots of benefits for moving to other DAW’s, but one thing is that their mixers are nothing like Reason’s virtual SSL 9000K (unofficial) emulation. Even if it wasn’t modeled off the 9000k, just the layout of it and its function is so amazing. And because the virtual mixer’s interface mimics hardware it’s easy to translate that to hardware control.

          And then, when not using a hardware mixer or desktop with dedicated monitors (yo), using Reason’s mixer on a laptop is a joy. https://www.jaexx.com/blog/

  35. Hi Jaexx
    Can I use the mapping to control X-Touch One as well? I don’t know if I do something wrong but it won’t work. I copied the content into the mackie folder, created a new control device and signed mackie to the master control. No button is functioning

  36. Hi Jaexx,

    :: APPRECIATION POST: UPDATE A YEAR ON ::

    After a year of using your custom maps, I have to say it’s a real game-changer for me. Thanks again for all your hard work on this and bridging the “gap” between Reason and external mixers…something that they so desperately need to sort out. It’s MUCH appreciated! Much love.

    Martyn

  37. Hey Jaexx,

    Quick one: how do we use the expression pedal / foot switches from X-TOUCH in Reason? Doesn’t seem to respond in Reason when I plug in my sustain pedal…any ideas? Also, does the X-TOUCH allow you to configure the CC somehow?

    From what I can tell, there is no MIDI editor for X-TOUCH (only for ‘one’ / ‘compact’) and am at a loss as to how to use these.

    Kind regards,

    Martyb

    1. “Rear Panel Switch A” and “Rear Panel Switch B” is what these controls are identified as in Reason. I’ve personally tested them on my X-Touch and with an (undisclosed brand) mixer. You can remote-override map them to something, such as the play button (it’ll only play your song, pressing the switch again won’t stop the song). But a big problem is that, in Reason, remote-override mapping something like the transport’s play button from the SAME device that already has that control called out disables the remote map’s function. So when I remote-override map a sustain pedal (“Rear Panel Switch B”) for the play button from the MJ Enhanced Universal Control, the sustain pedal will now play the song but the mixer’s transport play button no longer functions.

      I tested this out with my custom remote mapped Korg padKontrol; it has transport controls remote mapped. So I remote override mapped the play button in Reason to a different button on the padKontrol and lost control of the normal remote mapped play button.

      Now, what about if I were integrate something like a play button for the foot switches for the MJ Enhanced Universal Control? Can’t do it ‘cuz Propellerhead’s (now Reason Studio’s) remote system won’t allow duplicate control. Hardware like the Panorama P1 is different, I’ve successfully remote mapped different parameters between their paging system.

      So although I can think of lots of things I can remote map to the foot switches, they’re all already remote mapped to the buttons (and placing those controls on the foot switches instead of the console buttons would be stupid).

      So what’ll you do if you want to use your foot controllers to do something like map the record and stop functions? If you’re in a situation where you’re away from your mixer, such as in a recording booth, simply remote override map it for the time being. Or… or… much better? Connect those foot switches to something else (like a MIDI keyboard) other than your mixer and then remote override map them. That way you’ll retain control of your mixer’s functions.

      1. Thanks for your reply, Jaexx. Much appreciated. Think I will use my MIDI keyboard to use such switches / pedals from now on – X Touch doesn’t make it easy to use mixer and pedals simultaneously in Reason!

  38. This seems so awesome! What a job you’ve done, saving us who can’t program this thing a bunch of tears of frustration. I don’t know if it’s just me, but I can’t download the zip-file. It won’t open or download at all when I click the link. Did it get disconnected or something?

    1. I have had the same problem. You have to right click on the link and save the link. This was the only way I could download the file using Win10 with Google Chrome.

  39. this is a gift from god.
    is there a map of the features in detail? ive read the info and i know most of the features, but i’m not 100% sure. a “manual” would be great
    Thank you for this its so much fun to mix in reason

    1. oh one thing i use a extender (left) and the xtouch and when mixing channel 9 (1 of the basemodel) the clip led lights up… do i something wrong?

      1. Regarding a manual, I’ve thought about it but it’s a lot of work on top of what I’ve already spent in my free time. And the manufacturers haven’t even bothered doing a manual. And I’m not sure regarding the clip lights.One of things I had done was cut little squares of black electrical tape and place them over the clip LED of each channel. IF you look closely at my photos you may notice it, they’re pretty much hidden.

        1. ok, i was just triggered and thought,maybe my xtouch is faulty or has issues with the connection… thanks for your amazing work… this is next level in Reason 🙂

  40. I’ve come back to Reason after a notable break – updated to Reason 12 and now getting the same errors in the map file that Turbopage mentioned some time ago. Is this project still live? It was magnificent in Reason Suite 11 (where it still works) but in 12.5 just errors. I fully appreciate it was a project in your own time and effort Jaexx, just wondered if it’s still getting any attention given it’s still as relevant and useful. I even tried to find documentation on the remotemap file syntax etc to try and fix myself (I’m a software dev), but there just doesn’t seem to be anything out there other than ancient stuff going back to Reason 4. If you have anything to hand even, but aren’t putting the time in yourself, and wou’dnt mind sharing, I’d happily tinker myself!

    1. Hi, it works (in 12.6 on Windows for me) but Reason has changed where the maps and codecs are stored.

      You need to use the folders in C:Program FilesPropellerheadReason 12 (DefaultCodecs and DefaultMaps).

      If you are using OSX unfortunately I cannot assist.

  41. Hi Jaëxx,
    I get some questions on my XTouch video showcasing your great codec about Reason 12.
    Unfortunately I had to sell my X Touch some time ago, so I can’t test myself (I’m still missing it, so maybe I’ll try and get one back) but do you know ‘if’ the codec works with R12?
    Thanks a bunch (also for you immensely great work)
    Peter

  42. I had everything working correctly. Was in the process of setting templates. Rebooted Reason 12 to make sure everything took… Nothing took… lolNow Reason will not recognize the X-Touch again and I get the following error below:
    i.e. I have uninstalled reason several times, removed all local files etc.

    Remote Codec Errors:
Failed to run .luacodec file: mackie.luacodec
    mackie.luacodec, remote_supported_control_surfaces() surface #2: cannot open picture file: mackiecomboright.png

  43. I tried to install using Reason 12.6 and I don’t think it works. First off the Remote folder was empty (not hidden)… the folder is empty. So I copied the folders in and started up Reason. I get an X in the MIDI tab where I previously had a green check. Getting “invalid mode” errors. If I remove the folders, I’m back to green but your mappings aren’t loaded. Any help would be greatly appreciated. I’ve used this on previous versions and it worked great. Thanks!

    1. Hi, it works (in 12.6 on Windows for me) but Reason has changed where the maps and codecs are stored.

      You need to use the folders in C:Program FilesPropellerheadReason 12 (DefaultCodecs and DefaultMaps).

      If you are using OSX unfortunately I cannot assist.

Archived discussion — new WordPress comments are disabled.