MU.LAB 2.5.10 Released

[MuTools]

MU.LAB 2.5.10 has been released:

• Fixed: Recording events into an existing sequence with a sequence loop didn't properly position the recorded events
• Fixed: Negative music times were not properly displayed
• Fixed: Tempo display color now properly skinnable

If you already have installed MU.LAB 2.5.5 or higher then you can just install the latest application patch following these instructions:

http://www.mutools.com/mulab/mulab-upda ... -patch.txt

That way you don't have to re-setup anything.

If you did not yet install MU.LAB you can download the full package from http://www.mutools.com/downloads.html

[pljones]

I just tried using Reaper as a ReWire slave and seem to have messed up the session file I was working with.
http://www.drealm.info/mu.lab/Overload.zip (2823 bytes)
The above has a short sequence part and nothing else. It started by having an instrument loaded, which played okay. Then I added Reaper. Then I set it looping. At which point it overloaded on hitting play. So I removed Reaper and tried again - still overload. And removed the instrument - still overload. So I saved, close MULAB, restarted and loaded the session - still overload.

[MuTools]

For some reason the composition loop was set to a null loop.

That causes the overload.

Of course MU.LAB should handle such situation more properly.

Will be improved.

Thanks.

[pljones]

Ah, at one point I did reverse the start and end loop marks but I thought I'd fixed that. Thanks!

[rumba_codex]

Hi,

Looked at MU.LAB a while ago - liked the concept but that was it. On a friend's suggestion I've just tested the the latest release and I have to say this is bloody excellent! This is such a nice environment to work in - so simple and easy - such a pleasant change from other hosts that require so much virtual bureaucracy. The GUI is great, too. Just the right vibe. Everything is light and responsive. This version also sounds much better than the earlier versions I tried.

Tech question: Rendering options - why is only 16i/32f and not 24i offered? I'm thinking of cases of building or extending a sample library within a project where you want to keep all files @ 24/48, for instance. Everything ends in integer anyway (once we get to hardware) so is there any advantage of rendering post processed files @ 32f?.

Andrew

[MuTools]

Tech question: Rendering options - why is only 16i/32f and not 24i offered? I'm thinking of cases of building or extending a sample library within a project where you want to keep all files @ 24/48, for instance. Everything ends in integer anyway (once we get to hardware) so is there any advantage of rendering post processed files @ 32f?.

MU.LAB's internal audio engine works with 32 bit floats.

And so exporting into 32 bit floats gives you the exact result as it is rendered internally.

If you would want to have it in 24 bit integers, then i propose you use a wave editor or wave conversion app that can do the conversion from 32 bit float to 24 bit integer, eventually applying a good dithering algorithm.

Does this sound ok to you?

[theorize]

And so exporting into 32 bit floats gives you the exact result as it is rendered internally.

that sound AWESOME to me. I always have to go back amd make craploads of changes because it always sounds way different than in my host. I need to finish up some projects in other hosts so I can get a full song going in Mu