MuTools

MuTools · Post by **MuTools** » Mon Oct 20, 2008 3:17 pm

robenestobenz wrote:Ah, maybe it's because of the expanded menu levels config setting you told me about. I'll check when I get home.

Yes, that should do it.

On which note, I think the mulab.txt settings file is actually quite a good idea for a certain kind of user. It means that the kind of users who like to customise things can still do so, but that the rest don't have to be confronted by option dialogs that are as populous as Tokyo.

Funny expression

On topic: i agree.

MuTools · Post by **MuTools** » Mon Oct 20, 2008 3:18 pm

mutools wrote:
admc wrote:
mutools wrote:
admc wrote:Important: restart MU.LAB after each try, and click on the popup button in the rack immediately.
What do you mean with 'immediately'?
Not the speed of clicking is important, but that you don't click anywhere else before clicking on the popup button.
Ok, could repeat the crash. Researching...

Found the reason.

Will publish an update asap as this is a nasty crash bug.

MuTools · Post by **MuTools** » Mon Oct 20, 2008 3:58 pm

MU.LAB 2.01 has been released.

What's changed:

Tuned: Improved handling of AIFF / WAVE files with an audio data length mismatch
Fixed: Crash bug when using the plugin drop down button on racks
Fixed: Vertical zoom out when no tracks resulted in a weird situation

If you already have installed MU.LAB 2.0, just drag-drop the new application file in the below zips into your current mulab folder:

OSX: http://www.mutools.com/mulab/mulab-201-patch-osx.zip
WIN: http://www.mutools.com/mulab/mulab-201-patch-win.zip

Also the complete packages on the MUTOOLS download page are updated.

robenestobenz · Post by **robenestobenz** » Tue Oct 21, 2008 12:05 am

It might be a design subtlety that I'm not understanding, but I just found that if you have a rack routed to 'audio output' (which MuLab seemed to route automatically, because I just selected new rack & plugin when choosing track target) you can't record any audio. Even if you set the threshold to 0db, it still reports that the recording was too quiet.

MuTools · Post by **MuTools** » Tue Oct 21, 2008 8:04 am

Strange, the recording level has nothing to do with the output of a rack.

Even if you monitor audio input thru a rack, it's only about monitoring, it has no influence on the recording level.

Are you sure you have selected the proper audio inputs to record from? (=> Right-click the record button)

Are you sure the (external) signal path is properly setup.

You can always use a (new) rack to monitor audio input and so to see the level of the audio input signal.

robenestobenz · Post by **robenestobenz** » Tue Oct 21, 2008 10:31 am

mutools wrote:Strange, the recording level has nothing to do with the output of a rack.

Even if you monitor audio input thru a rack, it's only about monitoring, it has no influence on the recording level.

Are you sure you have selected the proper audio inputs to record from? (=> Right-click the record button)

I selected both the track in the composer view, and monitored the input through the rack the selected track was routed to.

mutools wrote:Are you sure the (external) signal path is properly setup.

Yup, because literally, I could record to one track, but not another.

mutools wrote:You can always use a (new) rack to monitor audio input and so to see the level of the audio input signal.

This was what I did! I could see the signal level. The problem seemed to stem from the fact that the new rack I was monitoring and recording to had output set to "audio output". When I switched it to master, it worked OK. Hence my question about whether I'd missed a design intention, or whether this was a bug.

MuTools · Post by **MuTools** » Tue Oct 21, 2008 12:12 pm

I experimented a bit with audio recording using the info you described, but can't find anything wrong.

Can you give me a step by step how to reproduce the issue. Thanks.

MuTools · Post by **MuTools** » Tue Oct 21, 2008 12:14 pm

MU.LAB 2.02 has been released.

What's changed:

Fixed: Dragging rack slot plugins still needed a modifier key

If you already have installed MU.LAB 2.0/2.01, just drag-drop the new application file in the below zips into your current mulab folder:

OSX: http://www.mutools.com/mulab/mulab-202-patch-osx.zip
WIN: http://www.mutools.com/mulab/mulab-202-patch-win.zip

Also the complete packages on the MUTOOLS download page are updated.

robenestobenz · Post by **robenestobenz** » Tue Oct 21, 2008 10:43 pm

mutools wrote:I experimented a bit with audio recording using the info you described, but can't find anything wrong.

Can you give me a step by step how to reproduce the issue. Thanks.

I can't reproduce it in the same project either now... weird. I'll pay more attention next time it happens. It was probably just something I screwed up without noticing.

What I mean with the solo thing, is that if I solo a track, all track speaker buttons remain lit, even though this is the only track now sounding. If I then change the order of the tracks in the composer by dragging and dropping, suddenly the track speakers buttons update so that the only one lit is the one currently solo'd. If I then unsolo the track, same problem until I drag and drop again.

Also, that cool little feature where you could toggle multiple track speaker buttons by dragging a selection box around them has stopped working.

MuTools · Post by **MuTools** » Wed Oct 22, 2008 7:17 am

robenestobenz wrote:What I mean with the solo thing, is that if I solo a track, all track speaker buttons remain lit, even though this is the only track now sounding. If I then change the order of the tracks in the composer by dragging and dropping, suddenly the track speakers buttons update so that the only one lit is the one currently solo'd. If I then unsolo the track, same problem until I drag and drop again.

Mmm, can't repeat that either

When i solo a track, all track speaker buttons are properly turned off, except for the solod track.

Tried it on both OSX as on Windows.

Anyone else having this issue too? (i.e. solo track doesn't redraw track speaker buttons)

Also, that cool little feature where you could toggle multiple track speaker buttons by dragging a selection box around them has stopped working.

Confirmed.

It's a unintended consequence of the simplified drag-to-reorder.

Will be fixed asap.

Thanks.

frollo9386 · Post by **frollo9386** » Wed Oct 22, 2008 8:41 am

mutools wrote:
robenestobenz wrote:What I mean with the solo thing, is that if I solo a track, all track speaker buttons remain lit, even though this is the only track now sounding. If I then change the order of the tracks in the composer by dragging and dropping, suddenly the track speakers buttons update so that the only one lit is the one currently solo'd. If I then unsolo the track, same problem until I drag and drop again.
Mmm, can't repeat that either

When i solo a track, all track speaker buttons are properly turned off, except for the solod track.

Tried it on both OSX as on Windows.

Anyone else having this issue too? (i.e. solo track doesn't redraw track speaker buttons)

solo/unsolo works properly on pc too...

robenestobenz · Post by **robenestobenz** » Wed Oct 22, 2008 11:14 am

frollo9386 wrote:solo/unsolo works properly on pc too...

I'm on PC as well! Windows XP x64... weird. It's always been like that for me in MU.Lab.

The Kob · Post by **The Kob** » Wed Oct 22, 2008 3:46 pm

congrats!!

i'll go and have a play

MuTools · Post by **MuTools** » Wed Oct 22, 2008 4:18 pm

robenestobenz wrote:
frollo9386 wrote:solo/unsolo works properly on pc too...
I'm on PC as well! Windows XP x64... weird. It's always been like that for me in MU.Lab.

Tomorrow i'll test it on a 64bit WinXP system as well, but would be surprised if it makes a difference.

frollo9386 · Post by **frollo9386** » Wed Oct 22, 2008 5:14 pm

robenestobenz wrote:
frollo9386 wrote:solo/unsolo works properly on pc too...
I'm on PC as well! Windows XP x64... weird. It's always been like that for me in MU.Lab.

type error: i was meaning on my pc,

but it's not x64...

MuTools

KVR Audio

MU.LAB 2.0 Release