M3 Tests

[TheGuysanIdiot]

Hi bpblog,

Nice idea.

Jo what do you think?

OZ

[Improviser]

I agree OZ, M3 is really looking good.
I'm a long time user of energyXT but Xt has never been as elegant and so intelligently simple as MuLAb and now with the new features in M3 I see no reason to keep using XT no matter how many option it has.
Jorgen is like Jo. He never stops. But what makes Jo so different it's his vision of simplicity and the ability to implement it while accommodating MuLab user's needs.
A winner.

I like your use of the two words "intelligently simple", to describe MU.LAB
I feel a catch-phrase coming on ..
"MU.LAB - The Intelligently Simple Solution".

Les J.

[liquidsound]

I like your use of the two words "intelligently simple", to describe MU.LAB
I feel a catch-phrase coming on ..
"MU.LAB - The Intelligently Simple Solution".

"MU.LAB - The Intelligently Simple Solution".

[sorohanro]

what if the 'no grid' menu item remains untouched, and the 'toggle grid on/off' changes to 'snap to grid on/off' instead? this way we could keep the grid on-screen even when the snapping is off, and have more orientation when adding the human feel by freely moving the notes.

the way things are set up at the moment, when the grid is switched off by either toggling it off or selecting the no grid menu option, the only orientation left on the piano roll are the beat measures i believe. wouldn't it be neat to have a 1/16th grid on-screen even when the notes don't snap to it?

Totally agree.
+1

[MuTools]

what if the 'no grid' menu item remains untouched, and the 'toggle grid on/off' changes to 'snap to grid on/off' instead? this way we could keep the grid on-screen even when the snapping is off, and have more orientation when adding the human feel by freely moving the notes.

the way things are set up at the moment, when the grid is switched off by either toggling it off or selecting the no grid menu option, the only orientation left on the piano roll are the beat measures i believe. wouldn't it be neat to have a 1/16th grid on-screen even when the notes don't snap to it?

This sounds very good!

I'll check it out from the technical side.

[MuTools]

Should be ok in the next version.

Note that if you already have shortcuts to the "Toggle Grid ON/OFF" you'll have to reset this shortcut.

The function now is renamed to "Toggle Snap ON/OFF".

[Bonteburg]

I haven't yet come across the bug where MU.LAB would make little stutter edits in my recorded audio like s-s-s-so.

Though it was/ is(?) a rather elusive little thing. Hard to pin down.

[bpblog]

The function now is renamed to "Toggle Snap ON/OFF".

woohoo! glad we all dig this.

[TheGuysanIdiot]

Yes indeed.

liquidsound for getting the ball rolling in the first place and bpblog for finding the neat solution in the end. You can both take a cookie from the jar and go to the top of the class.

OZ

[MuTools]

I haven't yet come across the bug where MU.LAB would make little stutter edits in my recorded audio like s-s-s-so.

Though it was/ is(?) a rather elusive little thing. Hard to pin down.

Sorry to ask but did you already have a chance to expand your computer's RAM?

[liquidsound]

I wish Jo was in charge of Propellerheads' Reason.... damn!!!!

[sorohanro]

I wish Jo was in charge of Propellerheads' Reason.... damn!!!!

Well, it's even better. He's in charge of Mu.Lab

[liquidsound]

I wish Jo was in charge of Propellerheads' Reason.... damn!!!!

Well, it's even better. He's in charge of Mu.Lab

+1

[robenestobenz]

Apologies if this has already been addressed.

Sub-track bug/freeze:

- If you drag a track onto a subtrack that is visually LOWER in the order than itself, all tracks between the dragged track and the subtrack disappear and the number in the subtrack name changes.

- If you drag a track onto a subtrack that is visually HIGHER than itself, MULAB appears to enter an infinite loop, maxing out one of my CPU cores.

Should it matter, I'm on an Intel Q6600 with 4 gigs of ram, running XP64.

//Edit:

- Split shortcut doesn't work as expected (split at cursor / nearest grid position to cursor as with the context menu option)

- Split function doesn't work at all with sequence notes

- Line tool intersect with the velocity bars loses accuracy if the line extends beyond the velocity/automation lane

I'm loving the improvements!

[MuTools]

Sub-track bug/freeze:
- If you drag a track onto a subtrack that is visually LOWER in the order than itself, all tracks between the dragged track and the subtrack disappear and the number in the subtrack name changes.
- If you drag a track onto a subtrack that is visually HIGHER than itself, MULAB appears to enter an infinite loop, maxing out one of my CPU cores.
Should it matter, I'm on an Intel Q6600 with 4 gigs of ram, running XP64.

Fixed in the next version. Thanks!

Split shortcut doesn't work as expected (split at cursor / nearest grid position to cursor as with the context menu option)

I checked this here and all works as expected.

But there may be some confusion because there are two split shortcuts: "Split" which works on a single part and "Split Selected Parts" which works on the composition.

I've finetuned this in the next version so that there won't be any confusion anymore

Split function doesn't work at all with sequence notes

There is no split function for sequence notes.

Note that it's not because you assign a shortcut to e.g. "Split" that it will work on everything. E.g. you can't "Split" a plug-in. It only works on objects which have "Split" in their context menu. Currently it's only about Compositions/Parts.

Line tool intersect with the velocity bars loses accuracy if the line extends beyond the velocity/automation lane

Finetuned behaviour in the next version.

Thanks!