MuTools

MuTools · Post by **MuTools** » Tue Dec 30, 2008 5:25 pm

Draft info:

Here are links to the first MU.LAB - ReWired test packages:

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

It's called version 2.4 just to be able to release it as a fresh version 2.5.

Note that this test version expires on 15 januari.

How to plug in a ReWire device?

Well, it's as simple as plugging in a VST plugin

In a rack or in the MPA, just as you want.

Note that you can also send MIDI to the slaved ReWire devices

Besides ReWire support, there are a handful of other changes as you can see here: http://www.mutools.com/mulab/changes.txt

The sooner this version is stabelized the sooner we can continue towards 3.0.

So hope the testers among you will find the time to torture this new version so we can kill any bugs asap!

Cheers

MuTools · Post by **MuTools** » Tue Dec 30, 2008 5:33 pm

Unless you input a MU.LAB Unlimited User Key, this version only supports 4 tracks.

That's why the demo session which auto loads on first run doesn't play 100% as tracks are compacted to 4 tracks.

This won't be an issue in the final release.

pljones · Post by **pljones** » Tue Dec 30, 2008 9:25 pm

OK. Quick test and I failed.

Rack A, Reaper with daHornet
Rack B, daHornet

Track 1, first part targets Reaper; second part targets daHornet; same sequence.

Only the second part sounds.

Here's the muSession. (45K)

(Reaper was definitely acting as ReWire slave - MULAB was controlling it play position, etc.)

pljones · Post by **pljones** » Tue Dec 30, 2008 9:32 pm

When reloading the project, the ReWired Reaper didn't reload (which I'd expected it to). There was an entry for in the rack, though. It should also have saved back to the MULAB project (but it prompted with its own "save project" dialog).

I set up another track targetting Rack C with a instance of daHornet, with a send back to Rack A. Until I loaded Reaper, things were fine. On loading Reaper, all sound stopped. (The audio is getting to Rack A (I have the fader mark above the first rack entry) but no signal is getting to Reaper itself.)

I get the feeling MULAB and Reaper aren't playing well.

Second session file. (70K)

muzycian · Post by **muzycian** » Tue Dec 30, 2008 11:45 pm

Take care: In the list editor, double clicking values crashes this mulab 2.4 test version. (no prob in the stable version 2.04)

Calum · Post by **Calum** » Wed Dec 31, 2008 12:48 am

Hi Jo - Season's Greetings!

Not having much luck with this. I just get an "Unable to startup ReWire (error=)" popup alert message when I click on any rack slot. Running on iMac G5 PPC with OSX 10.4.11. Any thoughts?

It's nice to finally see ReWire in MU.LAB but I don't have Live or Reason and there does not seem to be many Rewire slaves out there for MAC users (I found MAX, Reaper and Numerology). For me it would be much more useful to have MU.LAB as a Rewire client/slave. Is this feature in the pipeline?

liquidsound · Post by **liquidsound** » Wed Dec 31, 2008 1:34 am

Upon re-opening a project, Reason was back in the MPA with the same connections but I had to double click it in order to load Reason and the Reason Rack was empty. I had to load manually the Reason project within Reason itself.

MuTools · Post by **MuTools** » Wed Dec 31, 2008 8:31 am

pljones wrote:OK. Quick test and I failed.

Rack A, Reaper with daHornet
Rack B, daHornet

Track 1, first part targets Reaper; second part targets daHornet; same sequence.

Only the second part sounds.

Here's the muSession. (45K)

(Reaper was definitely acting as ReWire slave - MULAB was controlling it play position, etc.)

I rewired reaper in mu.lab and noticed multiple strange things which i think are on reaper's side.

I imported a midi file in reaper, and the same in mu.lab. In reaper it plays a vsti, in mu.lab it plays synthia.

Now when hitting stop, there are hanging notes in reaper.

I also noticed quite some clicks in the sound while reaper was open.

No such things when slaving reason. I think these are reaper issues.

Anyway, towards your report:

I notice that in your musession the first sequence part targets rack A and thus the events go to reaper, the second targets rack B.

The first part doesn't make sound, but that could be normal, it depends on what reaper does with the incoming events.

The second part plays normal here on my system.

MuTools · Post by **MuTools** » Wed Dec 31, 2008 8:38 am

pljones wrote:When reloading the project, the ReWired Reaper didn't reload (which I'd expected it to).

No, that is not the case.

ReWire does not have a protocol to save the ReWire slave data within the ReWire master project.

ReWire typically works like this:

1) plug in ReWire slave in the master
2) open the ReWire slave application (if not opened automatically)
3) eventually open a project in the rewire slave
4) ...play...
5) save the project in rewire slave
6) close the rewire slave (before closing the master!!)
7) save/quit the rewire master

This is standard for all ReWire masters.

I set up another track targetting Rack C with a instance of daHornet, with a send back to Rack A. Until I loaded Reaper, things were fine. On loading Reaper, all sound stopped. (The audio is getting to Rack A (I have the fader mark above the first rack entry) but no signal is getting to Reaper itself.)

Please note that a ReWire device has no audio input.

Only a MIDI input and audio outputs.

Could that explain it?

MuTools · Post by **MuTools** » Wed Dec 31, 2008 8:43 am

Calum wrote:Hi Jo - Season's Greetings!

Not having much luck with this. I just get an "Unable to startup ReWire (error=)" popup alert message when I click on any rack slot. Running on iMac G5 PPC with OSX 10.4.11. Any thoughts?

A question: Do you have any ReWire slave applications on your system?

I guess no.

If that's the case, then it's technically "normal" that this alert pops up.

But of course it's not very user friendly in such case, so i'll take note of this.

It's nice to finally see ReWire in MU.LAB but I don't have Live or Reason and there does not seem to be many Rewire slaves out there for MAC users (I found MAX, Reaper and Numerology). For me it would be much more useful to have MU.LAB as a Rewire client/slave. Is this feature in the pipeline?

Sorry, but that's not on the plan. MU.LAB will only support ReWire mastering.

MuTools · Post by **MuTools** » Wed Dec 31, 2008 8:44 am

liquidsound wrote:Upon re-opening a project, Reason was back in the MPA with the same connections but I had to double click it in order to load Reason and the Reason Rack was empty. I had to load manually the Reason project within Reason itself.

Normal. Please see my earlier post.

Calum · Post by **Calum** » Wed Dec 31, 2008 5:41 pm

mutools wrote: A question: Do you have any ReWire slave applications on your system?

Yes, "Numerology" and now "Ugly VSTi Interface". Logic Express can access both as slaves so ReWire is definitely up and running.

Calum · Post by **Calum** » Wed Dec 31, 2008 7:51 pm

Calum wrote:
mutools wrote: A question: Do you have any ReWire slave applications on your system?
Yes, "Numerology" and now "Ugly VSTi Interface". Logic Express can access both as slaves so ReWire is definitely up and running.

Fixed!

I noticed an error message in the "Ugly VSTi Interface" status window (unable to load ReWire dll) so I installed the Reason demo to try and fix it and ReWire is now working as it should. MU.LAB now sees Reason, Numerology and Ugly VSTi Interface as ReWire devices.

I have not yet been able to record ReWired audio into MU.LAB (I just get a buzzing sound) but I'm sure I will figure it out.

MuTools · Post by **MuTools** » Thu Jan 01, 2009 10:33 am

First of all: Happy Newyear to you all

Hope 2009 will be a healthy, productive, fun and musical year

Calum wrote:I have not yet been able to record ReWired audio into MU.LAB (I just get a buzzing sound) but I'm sure I will figure it out.

You cannot yet 'record' plugins or ReWired devices.

If you want to capture the sound of a plugin/device, then you can use Mixdown (File menu -> Mixdown)

Cheers!

pquenin · Post by **pquenin** » Thu Jan 01, 2009 7:04 pm

I have found this bug in Mulab 2.4 :
I select Track 1 and choose Midi Chanel 1. I select Track 2 and choose Midi Chanel 2. Now, I select Track 1 again and select Midi chanel 1 : ok. I select Track 2 again and choose Midi chanel 2 : a serious error has occured.
There's no need to have a rewired application loaded, you can reproduce this with an empty projet (I am on Windows Vista).

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.

Happy new year to you at Mutools and everybody here at KVR !