How to use Reason rewired????

[liquidsound]

Respect for the effort and time you spend trying to help and explain (in great detail) to fellow MuLabrians on this forum liquidsound!

Thank you.
I train CAD designers all day and details are the minimum standard that can be skipped at will but they are there for the ones who needs them...

[liquidsound]

In case you skipped the previous comment here is a copy: You do not need to read it. Is waaaay too long

I can't read the whole text now, but in short there are 3 ways where you could plugin Reason:

1) In a rack slot
2) In a MUX
3) In the Modular Area (will rename it Modular Session Area it think)

Option 1 only allows the use of Reasons main stereo out.

As you want more it's option 2 or 3.

With option 2 you can also use racks in that MUX, but the racks won't be visible in the rackdesk as the rackdesk only shows the racks in the MSA.

So that's why i propose option 3.

Hope this helps.

(going offline now, will be back lateron)

YES. Option 3 is the one I proposed to Trancit so you don't need to read the text.
I guess janamdo didn't read it either (as usual?)

[janamdo]

Hi Trancit!
Done!

Now each Track controls each individual device in Reason and each Reason Devices has a Rack in MuLab!
You can use exclusively MuLab magnificent midi editor and mixer etc.
All your mixing can be done here! Each Reason device has its own Rack!

This is how I use Reason and I must confess that I prefer MuLab built-in synths to the ones in Reason. MuSynth has a superb quality to rival them and Tho, if you will!

Now you can experiment more with combinators etc. Do not forget that you can use Reason inside a MUX as well. MU.LAB IS INSANE!

I hope this helps you to use Reason as an alternative to the method in the MuLab Docs on line if I recall correctly.


I would appreciate if anyone has a better way to do the same thing.

Arrivederci!

Nice done!
Now you can make a submix with racks where (all) reason soundgenerators are routed to .. but how (combining audio outputs from racks to one audio rack output)?

[liquidsound]

Nice done!
Now you can make a submix with racks where (all) reason soundgenerators are routed to .. but how (combining audio outputs from racks to one audio rack output)?

Hi janamdo,
can you elaborate tiny more on this? Aren't they all going to the Master Rack?

[janamdo]

Nice done!
Now you can make a submix with racks where (all) reason soundgenerators are routed to .. but how (combining audio outputs from racks to one audio rack output)?

Hi janamdo,
can you elaborate tiny more on this? Aren't they all going to the Master Rack?

I think it is the same idea as applied in Using A Multi-Out VSTi Within A Rack
Suppose you have 6 audiotracks in reason than you can make say a submix of 3 tracks for reducing CPU processing power ?

[liquidsound]

Nice done!
Now you can make a submix with racks where (all) reason soundgenerators are routed to .. but how (combining audio outputs from racks to one audio rack output)?

Hi janamdo,
can you elaborate tiny more on this? Aren't they all going to the Master Rack?

I think it is the same idea as applied in Using A Multi-Out VSTi Within A Rack
Suppose you have 6 audiotracks in reason than you can make say a submix of 3 tracks for reducing CPU processing power ?

You could but it would be then more practical to route some of your sub mix devices in the Reason mixer first (say the Redrum bass and compressor etc.) and the mixer to your Rack in MuLab unless you want to "juice" them in the MUX .

[liquidsound]

BTW if you want to reduce CPU power, do all what you need in a Combinator first, and then, Target that sub-mix into MuLab. There is nothing out there as efficient as Reason when it comes to CPU. NOTHING!

[cytone]

Just to add to this thread because I got a bit stuck today figuring out how to get stereo output.

The first output is stereo so that can just be connected to a rack.

All the other outputs have to be connected in pairs to a rack for a stereo output. But an additional step has to be done otherwise it will be mono. Right click the red triangle for the Left output and "Edit connection properties". Change the Pan to the maximum left. Do the same for the Right output and set it to maximum right.

[bbreakz]

I don't know if anybody else uses Reason in Mulab but this has helped sort me out today.
grateful to have found it after a search

What I'm not sure how to do yet, is how to control the Combinator rotary knobs with some type of Mux knob - I know what the CC numbers are for the Combinator knob - but haven't figured out how to connect them to a Mux knob... I can draw automation on a track, but sometimes I would like to record mouse movements of the knob in real time

Hi Trancit! Back from dinner. Bad restaurant!

This is the way I rewire Reason but I am sure that it can be done differently.
I am just stuck with this method because it works for me from the beginning and I like to use Reason as a collection of individual VSTs.

The other way is to use it as a complete unit going through one rack, as I understand it, in sync with MuLab sequencer.

Here we go:

Open Mu.Lab first and open a New Session.
Open the MPA, the Modular Area in the Edit Menu.
Right click anywhere on an empty spot preferably on the top area.
A small context menu appears and choose: Add Module.
A long context menu appears and under ReWire choose Reason.
A long Module appears with the name Reason.

So far so good... Next

Before anything else, connect the first (left) RED output of the Reason Module to the RED top triangle of Rack A.
Double click the Reason Module: Reason will launch and open with a Default template which I have no idea what will be because it has to do with the way you set up Reason.
Whatever template loads up I need you (for this exercise) to delete everything including the mixer.

You should be left with only the Hardware Device in the Reason Rack.
The Hardware Device should display " ReWire Slave Mode". If not, something went wrong and you may have to Quit all programs and repeat from the very beginning.

Stay in Reason and Create a Thor. TAB to show the back and open the hardware device in order to see the cable connections. Thor is on Output 1 and 2.
Create another device. Try not to create a subtractor right now because we want only stereo devices. So get a Malstrom.
Connect the Maltrom outputs to the hardware device to output 3 and 4.
You can now add more if you want, adding one by one to the hardware device. No effects yet please. (keep short for now)
(If you want you can use Reason effects by inserting them in the audio chain between the Thor, for example, and the Hardware device.)

Go back to MuLab (be careful not to close Reason by accident) and in the Modular Area connect the second AND third RED triangle of the Reason Module to the RED top triangle of Rack B.
If you have loaded more devices in Reason then keep on going: 4 & 5 to Rack C etc. It would be better not to run out of Racks yet...

If you want you can close the MPA. Up to you.

Right click Track A (it says Rack A) and Choose Target Module: Select Reason.
Do the same for Track B and Track C if you have more Reason devices.

After this, Right click again on Track A (now the name has changed to Reason)
and Choose Midi Channel. Here you need to go down until you get to Bus 6 where you will see the names of the Reason devices, Thor, Malstrom etc.

(Do not choose Hardware Interface. Also if you had insert the effect as mentioned above after Thor you would see it in the Bus 6 list together with the other devices but you would still select the Synth, no the effect).

Select Thor and click OK.
Go to Track B and repeat and choose Malstrom.
If you have more, keep on going.

Done!

Now each Track controls each individual device in Reason and each Reason Devices has a Rack in MuLab!
You can use exclusively MuLab magnificent midi editor and mixer etc.
All your mixing can be done here! Each Reason device has its own Rack!

This is how I use Reason and I must confess that I prefer MuLab built-in synths to the ones in Reason. MuSynth has a superb quality to rival them and Tho, if you will!

Now you can experiment more with combinators etc. Do not forget that you can use Reason inside a MUX as well. MU.LAB IS INSANE!

I hope this helps you to use Reason as an alternative to the method in the MuLab Docs on line if I recall correctly.


I would appreciate if anyone has a better way to do the same thing.

Arrivederci!

[MuTools]

What I'm not sure how to do yet, is how to control the Combinator rotary knobs with some type of Mux knob - I know what the CC numbers are for the Combinator knob - but haven't figured out how to connect them to a Mux knob... I can draw automation on a track, but sometimes I would like to record mouse movements of the knob in real time

Use a MIDI Controller Generator module in the same MUX as the Reason ReWired module. Connect that MCG to Reason Rewired. Then also connect that MCG to a meta-parameter of that MUX. Now you can automate and live play that MUX meta-parameter which will generate the right MIDI CC messages to Reason ReWired.

[bbreakz]

What I'm not sure how to do yet, is how to control the Combinator rotary knobs with some type of Mux knob - I know what the CC numbers are for the Combinator knob - but haven't figured out how to connect them to a Mux knob... I can draw automation on a track, but sometimes I would like to record mouse movements of the knob in real time

Use a MIDI Controller Generator module in the same MUX as the Reason ReWired module. Connect that MCG to Reason Rewired. Then also connect that MCG to a meta-parameter of that MUX. Now you can automate and live play that MUX meta-parameter which will generate the right MIDI CC messages to Reason ReWired.

Great thanks gonna try this tonight!!