Wrong. It just did.
This is not an official release announcement from Propellerhead themselves, but rather a homebrew solution that allows you, the independent user, to build and shape a new way of working in the Rack that is exactly the way you want it once you set it up.
The way this works is very simple. It is the starting point that you can build off of to craft your own highly specialized production tool for your future projects. Here is how it works.
- Download the attached Zip file, extract anywhere.
- Place the folder "MIDI Node Beta\Remote\Lua Codecs\Raveshaper" into Reason's "Remote\Lua Codecs" directory.
- Place the folder "MIDI Node Beta\Remote\Maps\Raveshaper" into Reason's "Remote\Maps" directory.
Propellerhead Software wrote: OS X
Macintosh HD/Library/Application Support/Propellerhead Software/Remote
Windows Vista/Windows 7
C:/Program Data/Propellerhead Software/Remote
Windows XP
C:/Documents and Settings/All Users/Application Data/Propellerhead Software/Remote
Please note that on Windows, the files are stored in hidden folders, so youʼll have to go into the Folder and Search Options of Windows Explorer and make sure that “Show hidden files, drives and folders” is selected, in case you havenʼt done so already.
- Open Reason.
- Go to "Edit > Preferences > Control Surfaces > Add".
- Select "Manufacturer > Raveshaper".
- Select "Model > MIDI Node Beta".
- Configure the in port and out port to use the physical or virtual MIDI port you will be using to achieve MIDI loopback.
- Open the Reason song file "MIDI Node Beta Test.reason" included in the Zip.
- Configure the External MIDI Instrument's output to use the same physical or virtual MIDI port you are using for loopback.
To connect two controls together, follow these steps:
- Right-click the first control (which will act as master).
- Select "Edit Remote Override Mapping... > Control Surface > Raveshaper MIDI Node Beta".
- Choose your desired source ("Src") control from the "Control" dropdown menu, example: "Src 1".
- Right-click the second control (which will act as slave).
- Select "Edit Remote Override Mapping... > Control Surface > Raveshaper MIDI Node Beta".
- Choose the destination ("Dest") control from the "Control" dropdown menu that has the same i/o number as the source "Src" control, example: "Dest 1".
- Move the first control and the second control will also be manipulated.
What this basic script allows you to do is create something that I'm calling "branched automation". Basically, you can automate a single control on a device, but then create a network of other controls that respond to the current state of the automated control. Imagine synchronized manipulations of multiple device controls that only require the original automation lane in order to happen. The cpu priority that would be given to the sequencer to analyze and carry out all of those automation lanes is prevented from occurring and is instead deferred to the much more sparse and quick to execute surface script(s).
I say "script(s)" because you can load in multiple instances of this script if you want/need more i/o, or have made different modded versions of it that each have special behaviors.
I know some of you are probably saying that this is too difficult and is counter productive when put into practice. But let me counter that by saying you can do nearly anything you want using this approach, whereas the Combinator trades off possibilities in favor of graphic interface. Let me put that another way:
Using this method allows you to learn new ways of working in Reason that no one has ever used before. The limits of mathematics, modern devices, and your own creativity are your only obstacles.
You can mod this so one control spiders out to sixteen, you can expand its capabilities to include support for multiple MIDI channels, notes, velocities; almost anything you want to do in terms of controlling the front face of devices, you now have the power to do. It's in your hands.
Tell me what you think, tell me if it's awful and I'm full of myself, discuss!