MU.LAB - ReWired

Official support for: mutools.com
RELATED
PRODUCTS

Post

pquenin wrote:I also have a question : I wan't to use Reason as a rack of synths, and sequence them from Mulab. How do you do to tell Mulab that Track x (or Rack x)in Mulab must send his midi events to Synth y in Reason ? It's possible in Tracktion but I don't see something like this in Mulab.
There may be other ways but here is what I do:
In MuLab I add in the MPA a ReWire > Reason and connect the first Mix L+R output to Rack 1.
In Reason expand the "Hardware Device" (First device on the top) and press the button "Adv. Midi Device"
For each BUS [ A B C D ] you can have up to 16 Reason Synths/Devices to control.
Go to each Channel Button Selector and Pick your device for that MIDI channel.
In MuLab than select as you did the specific channel for each Rack equal to the channel you have just selected in Reason and that Reason Device will play:
[Rack 1 = Ch 1] = [Reason Ch 1 = Thor or something else]
[Rack 2 = Ch 2 or 3 or ....] = [Reason Ch 2 or 3 or... = whatever you have selected there]
For now run your devices through the Reason Mixer and let the mixer be your audio output as usual.
I hope is not confusing.
The thing is that I had to choose as a Target a MIDI Outputs and a Port in my MuLab Racks in order to have everything working without crashes.


Anyhow I am waiting for someone else to come up with a better way or the "Right Way" because I am not sure this is the intended one from Jo.

The beauty of MuLab vs. Tracktion is that Tracktion will steal from you a channel for every single device in Reason even if it is a simple effect in the chain and it is quite easy in Reason to reach 64 devices as you know.
For example if you have a Combinator with 10 devices Tracktion will allocate 10 channels out of a BUS to the Combinator while MuLab will just need a single channel for it. At least as far as I understand Tracktion.
This is very well implemented here. :wink:
Last edited by liquidsound on Thu Jan 01, 2009 10:38 pm, edited 2 times in total.
ABEFLGMOPPRRST :phones:

Post

Thank you liquidsound, it works well now, by using Advanded midi in Reason.
But it means that the midi data are sent to Reason by an output midi port in mulab (and a virtual midi cable behind it), but not by Rewire...
The good thing in your method, as you say, is that you can choose the Reason device for each channel. With "rewired" midi, each device opened in Reason steal a channel and you can reach the limit of 64 midi devices.

I don't use the Reason mixer, but sent each controled device to it's own Reason output so that I can have them back in Mulab in different racks, by connecting each Reason outputs to its own rack in the MPA.

The nice thing is that you can employ the same method in Tracktion too...

Post

pquenin wrote: The nice thing is that you can employ the same method in Tracktion too...
I run a Tracktion Demo and I did not discover the other way. How it is done?
ABEFLGMOPPRRST :phones:

Post

How to sequence a ReWired Reason device:

* Select Reason as the target for that track/part
* Right-click the track/part and choose "Choose MIDI Channel"
* Now you get a long list of all 4080 ReWire MIDI channels, properly named as Reason reports it to MU.LAB.

If you scroll down in the list you should find all your Reason devices.

Note that the order of that list is defined by Reason, not by MU.LAB.

Note about the crashes:

This MU.LAB 2.4 Test A indeed still suffers from instabilities because one of the User Interface subsystems has changed to make it more code-efficient. I'm working on it to stabelize this asap. Thanks for the every bug report!
Last edited by MuTools on Fri Jan 02, 2009 5:21 pm, edited 2 times in total.

Post

The MU.LAB 2.4 Test A packages are removed from the server as Test B is in the pipeline, expected within a couple of hourse.

Post

Updated the MU.LAB - ReWired Test packages:

OSX: http://www.mutools.com/mulab/mulab-24-test-b-osx.zip
WIN: http://www.mutools.com/mulab/mulab-24-test-b-win.zip

Note that this test version expires on 15 januari.

What's changed:
  • Tuned: When ReWire is not installed on the system, MU.LAB alerts about this only once
  • Tuned: Changing the loop locators in the ReWired application now also updates the composition loop in MU.LAB
  • Fixed: Several crash bugs

Post

mutools wrote:How to sequence a ReWired Reason device:

* Select Reason as the target for that track/part
* Right-click the track/part and choose "Choose MIDI Channel"
* Now you get a long list of all 4080 ReWire MIDI channels, properly named as Reason reports it to MU.LAB.

If you scroll down in the list you should find all your Reason devices.

Note that the order of that list is defined by Reason, not by MU.LAB.
Thanks, I've tried this (with 2.4 test B) and it's OK. The problem with this is that you must target Reason directly, so you can't put a midi plugin before reaching Reason (eg : an arpegiator).

I have also notice this : when the sequencer IS PLAYING and I move the song position pointer to another location in Reason, it follows well in Mulab, but then in Reason, the song position pointer go back to his previous location and don't move anymore, until the song reach this point. I don't know if it's a Reason or Mulab issue. My version of Reason is 3.0.4.

Post

pquenin wrote:Thanks, I've tried this (with 2.4 test B) and it's OK. The problem with this is that you must target Reason directly, so you can't put a midi plugin before reaching Reason (eg : an arpegiator).
Mmm, true.

I'll have to think more on this.
I have also notice this : when the sequencer IS PLAYING and I move the song position pointer to another location in Reason, it follows well in Mulab, but then in Reason, the song position pointer go back to his previous location and don't move anymore, until the song reach this point. I don't know if it's a Reason or Mulab issue. My version of Reason is 3.0.4.
I tried this with MU.LAB 2.4 Test B and Reason Demo 4.0.1 and everything seems fine here.

Post

Updated the MU.LAB - ReWired Test packages:

OSX: http://www.mutools.com/mulab/mulab-24-test-c-osx.zip
WIN: http://www.mutools.com/mulab/mulab-24-test-c-win.zip

Some nice changes:
  • New: You can drag&drop MuSession files onto MU.LAB
  • New: You can drag&drop vst plugin DLL files onto the MPA
  • New: Sequence function: Thin Out Selected Events which can be used to reduce MIDI controller data
  • Tuned: Changing the start of a part now keeps the content of the part at the original position!
  • Tuned: When doing Mixdown and any parts are selected, now you get a question about it instead of an alert
  • Tuned: Improved version information when opening older unsupported MuSession files
  • Fixed: Crash bug when changing the start locator in a sequence without loop
  • Fixed: In some cases, events were unintendedly processed by multiple plugins, e.g. automating the send level of a rack send also automated the next send level in the rack

Post

Hi and a happy new year!

In the latest test package, on OSX, I open a new session, click on a rack and it tells me "cannot startup rewire (error=)".

Have a nice day! :D

By the way, the knight-rider song, where has it gone? :(

Post

Are there any ReWire applications installed on your system?

Post

mutools wrote:
pquenin wrote: I have also notice this : when the sequencer IS PLAYING and I move the song position pointer to another location in Reason, it follows well in Mulab, but then in Reason, the song position pointer go back to his previous location and don't move anymore, until the song reach this point. I don't know if it's a Reason or Mulab issue. My version of Reason is 3.0.4.
I tried this with MU.LAB 2.4 Test B and Reason Demo 4.0.1 and everything seems fine here.
Hmmm, I have done the same test (with the same Reason song) in Tracktion, and there is no problem, so it must be a Mulab issue.
With Mulab, when the sequencer IS PLAYING, if I move in Reason the song position pointer after it's actual position (on the time line), the Mulab's song position pointer move to this new location, and the 2 ones go on together : OK.
If I move in Reason the song position pointer BEFORE it's actual position, the Mulab's song position pointer move to this new location and start moving on (it's OK), but in Reason, when I release it, the song position pointer doesn't stay at the new location but move to its previous location and wait until the one in Mulab reach this location, and then they go on together...
I don't know if it's clear...

Post

mutools wrote:Are there any ReWire applications installed on your system?
Reaper and Bidule. :)

Post

mutools wrote:Updated the MU.LAB - ReWired Test packages:

OSX: http://www.mutools.com/mulab/mulab-24-test-c-osx.zip

Some nice changes:
  • New: You can drag&drop MuSession files onto MU.LAB
When I open test c, I get the following error message:

"The session is made with an older version of MU.LAB : MU.LAB Unlimited R&D 20081008 (build 8 Oct 2008). Please use the intermediate versions of MU.LAB to upgrade the session file."

Rewire appears to be working well with this version. "The Ugly VSTi Interface" and "HostX" are working as expected as Rewire devices, including midi send and mixdown.

Post

Updated the MU.LAB - ReWired Test packages:

OSX: http://www.mutools.com/mulab/mulab-24-test-d-osx.zip
WIN: http://www.mutools.com/mulab/mulab-24-test-d-win.zip

If you already have installed a previous 2.4 Test version, you could just install the latest application patch from:

OSX: http://www.mutools.com/mulab/mulab-24-t ... -patch.zip
WIN: http://www.mutools.com/mulab/mulab-24-t ... -patch.zip

2 little changes:

* Fixed: When the alert "Cannot startup ReWire (error=)" pops up, the error code now is properly displayed

* Fixed: This version doesn't complain about any MuSessions made with the MU.LAB 2.0x

Post Reply

Return to “MuTools”