Friday, December 13, 2013

CV: Getting them basics right

How is Control Voltage emulated in Reason ?
What are the differences when compared with real CV ?
Are there any extra features we get when using virtual CV ?
Any limitations if you compare it with hardware CV?
Can it make me a cup of coffee ?

All this (well, almost!) is covered by the latest CV tutorial series at RackExtensionReview:
...and after these, we can start "doing stuff" to and with CV ;)

...and yes, Reason 7 can make you coffee, just find a Coffee machine with MIDI in or...ask your nearest Arduino/Raspberry Pi ‏expert friend to help you out!

Wednesday, November 27, 2013

RackExtensionReview is ON :)

A new site about Reason and Rack Extensions with News, Reviews, Tutorials and Forums was born today.

On the welcoming post, we can read:
«Considering so much has happened, so quickly on the Rack Extension front during the last 16 months or so, I don’t feel like online journalism has kept up with this rapid growth.  There isn’t really a definitive source for info, reviews and just general discussion on this amazing new Reason plugin format.  That is the goal of of RER – we want to be your first choice for reliable and entertaining RE news, reviews, interviews, and tutorials.»
So feel free to check the RER Forums, the excellent first Reviews (more on the way) and the upcoming Tutorials, currently focusing on "Control Voltage" aka CV with more subjects to come in the future.

CV in Reason: Behind those front panels

This first CV oriented tutorial series starts out by exploring all the different ways to control a Reason rack device. Some of those will be revisited in future tutorials to allow a more detailed coverage, going deeper into what's necessary to grasp some of the more mysterious aspects of Reason. might get yourself a free FXpansion TRES mono virtual analog synth ;)

Wednesday, May 1, 2013

"Reason has a rack for that"

Reason 7 is finally here.

I guess some of the new features are too obvious and simple to understand why they are so great.

Channel bus/groups, parallel channels ad-infinitum, Spectral EQ controlling the good "old" channel EQ, audio auto/manual slicing and quantizing, the list goes on... there's even a bonus Instragram-like audio "toy" that... is no toy at all when in the proper hands ;)

But the thing that many were also waiting for years was Reason ability to output MIDI from the sequencer in a proper, easy to configure, easy to use and easy to understand way.

External MIDI Instrument

Reason 7 finally brings us the "little" External MIDI Instrument rack device (EMI for short).

Obvious use? Play your hardware synths :) ...old, new, vintage, digital, analog, mono, poly, big or small MIDI controlled audio generating gadgets, your OP-1's, your... iPad synth apps... even your 2nd laptop running any MIDI playable music app ;)

Not so obvious use? Control any MIDI enabled gear like mixing desks, FX or light boxes, sync/slave them to your Reason sequencer while performing live on stage.

Less obvious uses? Play/Control your soft-synths/virtual instruments through loopback virtual MIDI ports.

You can play/control them either as Standalone synths or using DAWs/Hosts as VST/AU "racks", allowing you to access more than 1 instrument at the same time either through MIDI Channels (1 per instrument) or using various (virtual) MIDI ports (each allowing 16 MIDI Channels)... whatever you DAW/Host allows.

As an example, Kontakt allows stacking instruments and assigning a MIDI Port+Channel per instrument and this is how you're able to play a specific one from Reason, sending MIDI to the respective MIDI Port+Channel pair.

MIDI Clock & Song Position

Besides sending out Note ON/OFF, Note Velocity, Program Change, Channel Aftertouch, Pitch Bend and MIDI CC's (CC 01 = Mod Wheel), Reason 7 makes it possible now to send out MIDI Clock and Song Position.

Keep in mind that EMI enables you to "convert" CV to MIDI CCs, which is kinda cool... playing iPad's Animoog with a Matrix, RPG-8, sequencer track or through the controller keyb while controlling its X/Y pad with Pulsar is always something kinda neat to do ;)

So, sending MIDI Clock out allows us to sync Reason's sequencer Tempo with any external (hardware or software) gear/instruments (or DAWs) that support MIDI Clock input.

This is how you're able to sync your external synth's Arpeggiator, LFOs or step sequencer with Reason's BPMs :)

Here's a quick example of sync'ing an external (software) instrument through MIDI while also playing it through MIDI (video by sinnerfire)

Besides MIDI Clock, another useful info being sent out is Song Position, extremely useful when controlling Rhythm/Drum machines, Sequencers or DAWs that support Song Position (some don't, you'll have to try it or check the specs list).
TE OP-1's Tape mode receives Song Position, so it's possible to sync its "Tape" position with Reason's Sequencer position :)

«Right, so I'm able to play other instruments not on Reason's rack through MIDI but that's not saved into my Reason song!!!»

Well, just like a singer's voice, a guitar or any other acoustic, electric or electronic instrument that you want to add to your Reason song, you need to audio record that performance to become a part of your song as audio tracks, right?

So you'll need to do the same with any of those External MIDI Instruments played by Reason. If you want to capture that audio performance and embedded it in your song, the definitive way to achieve that is to record that instrument audio output into a Reason audio track. Kinda obvious, isn't it? ;P

External hardware instruments are usually a no-brainer: You connect their audio output into your computer's audio interface inputs and record that into an audio track and you're done. Then, just mute the original MIDI source track and keep it just as a backup, in case there's a need to make some changes or tweaks to the MIDI track and re-record that instrument back into another audio take.

So, my Novation X-Station, my TE OP-1, my iPad or even my 2nd laptop running whatever MIDI enabled instrument apps I have, all fit in the above category of easily getting their audio into a Reason audio track, through real audio cables.

Windows users, as a last resort, can also try using their internal audio card through ASIO4ALL, connecting your computer's audio output to your external ASIO audio interface through a cable... as a last resort, keeping in mind that you won't get any miracles regarding audio latency, this way.

«What about all the virtual instruments, soft-synths (VSTs/AUs/Standalones) or DAWs running on the same computer I'm running Reason on?»
Well, this is where it may get a bit complicated (or not), depending on your system, your overall setup, gear, OS, etc...

In this case, the closest to "external hardware" scenario is using 2 audio interfaces.

In my case, I use Propellerhead Balance with Reason and Novation X-Station (that is also an audio interface) as my secondary audio interface.
With this setup, I have the X-Station's audio output connected to Balance on Line 1 through a pair of audio cables and that's how I'm able to record into Reason any soft-synth, DAW or the X-Station's own synth engine into Reason's audio tracks. Kinda straightforward, right? :)

The other option closest to the above is using your ASIO driver's capabilities to re-route audio internally achieving virtual connections between the driver outs into the driver ins... if you're lucky enough to own such audio interface with such capabilities.

I think Focusrite Saffire is an example of such type of audio interface (I never used one, so I'm not sure about this)
EDIT: Just found out that some Focusrite Scarlett interfaces also allow and include this Mix Control application.

The 3rd option is... using virtual audio cables with various good or bad results, depending on your OS and computer capabilities.

This is where Soundflower is mentioned for Mac users, JACK or Virtual Audio Cable for Windows users.

«Does it work ? Can I really use those virtual cabling "hacks"? Is that a reliable way to work properly?»
Maybe for Mac users that usually use CoreAudio's built-in audio, Soundflower is a good solution, but for Windows users, used to real ASIO hardware audio interfaces, you'll notice the drop in quality quite easily.

I've tried JACK a long time ago (so I won't bother retrying it now again) and it wasn't up to the standards I expect of an ASIO level audio interface. Also tried VAC 4.12 yesterday on my 2nd laptop (just a Core2Duo, unlike my main i7 laptop) and it kinda works but, just like JACK, at a very low quality and high latency settings and... not worth the trouble, to be honest.
For me, the best results are achieved with proper hardware audio (ASIO) interfaces and since I have 2 available at all times, that's exactly what I've been using and am happy with :)

If you need (virtual) multi-channels out of a a DAW or standalone synth application into Reason, technically VAC 4.12 can deal with up to 3 wires (i.e. IN-to-OUT) connections of 8 channels each but... like I said, you'll need a lot of CPU power and be extremely lucky and/or knowledgeable to make that bearably work. So not worth the trouble, IMHO.
If you really need inter-app multi-channel audio exchanges, stick with the ReWire technology.

Maybe Reason 8 will strike one of the last surviving ultimate requests for Reason: ReWire Master and then yeah, all we need is a ReWire slave VST Host to tackle this problem properly completely inside-the-box ;)
(*cof*cof* and Video Track(s)!!! *cof*cof*)

If all these "hacks" sound (or act) too troublesome for you, I guess the truth may be that you don't need them anyway. Stick to Reason, stick to Rack Extensions, stick to ReWire and enjoy that easily understandable and stable bliss ;)

Bottom line is... Reason 7 now allows both worlds to be happy: The "the box is my oyster" crowd and the tweakers, tinkerers, hackers, hardware fans to finally properly marry Reason with that other aspect of their music loving interest :)

Tuesday, March 12, 2013

New: Reason 7 & Reason Essentials 2

  • MIDI OUT (to finally play/control hardware/software instruments/devices)
  • Audio slicing (almost ReCycle style)
  • Audio quantization (make those MIDI instrument recordings tight and more...)
  • Convert sliced audio clips into REX loops
  • Spectrum Analyzer (floating, resizable window)
  • Visual EQ (over the Spectrum Analyzer)
  • Group mixer channels (remember the "P-LAN" at the back?)
  • Parallel channels (audio through to another Mix Channel)
  • Imports "your music library and web formats" audio (mp3wmam4a, etc...)
  • Enhanced Factory Sound Bank (new loops and drum kits)
  • The new Audiomatic Retro Transformer effect (?)

Reason Essentials 2
  • FREE upgrade for existing ReE owners
  • Audio slicing (almost ReCycle style)
  • Audio quantization (to make those external instrument recordings tight)
  • Convert sliced audio clips into REX loops
  • Imports "your music library and web formats" audio (mp3wmam4a, etc...)

Monday, February 25, 2013

Rack Extensions: The Remote side of it... Part III

Q4: Is there a place where I can simply pick the Remote templates I need for the Rack Extensions that I own and edit it to work with my own controller ?

A4: Yes, here: Rack Extensions: Remote Map Scopes list

A Propellerhead User Forum (aka PUF) thread mainly dedicated to keep an updated list of the correct Company and RE IDs to be used in the Scope lines in the .remotemap files.

As an added bonus, it's also slowly turning into a Remote Template repository for the released Rack Extensions (as much as I and any other volunteers are able to keep adding templates to it).

Q5: How do I use a "Remote template" ?

A5: Ok, try these steps:

1) Find the .remotemap file you're using for your MIDI controller by checking these paths on your system:

on Mac OSX:
Library:Application Support:Propellerhead Software:Remote:Maps

on Windows:
%ALLUSERSPROFILE%\Propellerhead Software\Remote\Maps

which usually translates to:

on Windows Vista or Windows 7:
C:\ProgramData\Propellerhead Software\Remote\Maps

on Windows XP or 2000:
C:\Documents and Settings\All Users\Application Data\Propellerhead Software\Remote\Maps

2) In there, you should find a folder per controller brand. Open the folder for your controller brand.

3) In there, locate a .remotemap file related with the model of your controller.

4) Make a backup copy of that file (just in case anything goes wrong, you can simply replace it with that backup)

5) Edit the file with a text editor (don't delete anything inside!) and go to the end of that file. Be prepared to add some text at the end.

6) Now, go to the Forum thread mentioned above and look for the Remote Templates you're interested in (try this with just one and if it works, the rest uses the same process)

7) Copy all the text inside the "Code" blocks in the post and paste it in the Remote Map file you're already editing.

8) Now, one way to know the control names the Codec+Map developer gave to your Controller knobs, buttons, faders, etc. is to look to other existing Scopes. The "map" lines use this format:
Map [TAB] [Control Name] [TAB] [TAB] [Remoteable Name]
So, each of these lines say "Map my controllers knob/fader/button X to this rack extension remoteable Y"

Say you have a control named Knob 1 and you want to map it to a Rack Extension remoteable named Filter Cutoff, all you have to do is find the line on your recently pasted Remote Template that looks like this:
//Map [TAB] _control_ [TAB] [TAB] Filter Cutoff
And change it to:
Map [TAB] Knob 1 [TAB] [TAB] Filter Cutoff
Notice how I removed the initial "//" characters to make that line active (lines starting with // are comments) and changed the "_control_" to "Knob 1".

So this kind of editing for the rest of the controls of your controller that you notice are used in the other Scopes (other mapping blocks related with the other Reason devices).

Be extra careful not to remove any existing TAB character, respecting the format shown above.

9) When you're done, save that .remotemap file.

10) Start Reason and check if all this trouble worked :)

If you're already running Reason, then use this little trick to re-load that Remote Map:

Go to Edit, Preferences..., Control Surfaces and locate the controller you've been editing the map.
Uncheck the "Use with Reason" check mark and check it again. This will reload the recently edited map file.

You can keep using this trick while keeping the map file open in the file editor. Each time you save a change, do this uncheck/check thing and it'll get re-loaded into Reason.
If there's something wrong with the changes you did, Reason will "complain" with an error warning (a big red cross button) that you can press to see what's wrong.
Try to fix the issue, if you understand what you did wrong, save the file and try again the reload trick.
If you're unsure what's going on and you're getting nowhere with your edits, maybe you should close the editor, replace the file with the early backup (the original map file before your edits), use the reload trick to use that and... ask for help here :)

I'll soon add some snapshots and provide a more detailed explanation to this process, if needed (i.e. if anyone complains that this doesn't work or it's too confusing).

Good luck and... if you do your own Remote Templates, please check the existing list and if it's a new one, post it. This should be a community effort to try and "fix" something some (fortunately not all) RE Developers keep forgetting to add to their documentation: Their Rack Extension Remote Implementation list.