M3 Tests

[MuTools]

Add a VST instrument
Setup a track of about 20 bars and just add one long note
Start recording and with the mouse on the VST panel move any control like mad to record lots of data

What happens depends on the VST

With Wusikstation and Firebird even though I recorded 20 bars of automation it only actually recorded a few bars near the end

Issue fixed in the next version, thanks for spotting.

With other VST's such as CM Dominator and the Elektrostudio synth pack after maybe 10 bars Mu.Lab starts to slow down and eventually the VST controls get unresponsive.

Hey that's strange, i'm not sure whether this one will be fixed by the fix mentioned above. And i can't seem to easily find/download CM Dominator (bundled with CM) and the Elektrostudio synth pack (where is the dl link?) to check it out. So please retry with the next test version 3.0.27 coming one of the days.

[MuTools]

Question: Would it be better to unfold all context menus by 1 level by default?

[MuTools]

Question: When recording MIDI events into a new sequence, then MU.LAB automatically sets loop locators for that new sequence. Is that ok, or would it be better just to store the recording without loop locators. Then you can always add looping if you want of course.

[Improviser]

Question: Would it be better to unfold all context menus by 1 level by default?

I would definitely vote YES.

Presumably, the level of unfolding would also remain configurable via "UseUnfoldedContextMenus=" in MULAB.Txt ?

Les J.

[MuTools]

But is it possible to select a part of a midi controller track,
e,g, a section of pitch events ? (lower part in note editor) ?
There you are always in "pencil mode".

Hold [Shift].

In the next version, this confusing issue has been fixed/tuned for the Event Graph Editor has much more consequent tool behaviour, similar to the composer, piano roll etc

[MuTools]

I would definitely vote YES.

Presumably, the level of unfolding would also remain configurable via "UseUnfoldedContextMenus=" in MULAB.Txt?

Sure, it stays configurable, it's just about changing the default.

[MuTools]

With other VST's such as CM Dominator and the Elektrostudio synth pack after maybe 10 bars Mu.Lab starts to slow down and eventually the VST controls get unresponsive.

Hey that's strange, i'm not sure whether this one will be fixed by the fix mentioned above. And i can't seem to easily find/download CM Dominator (bundled with CM) and the Elektrostudio synth pack (where is the dl link?) to check it out. So please retry with the next test version 3.0.27 coming one of the days.

It's a different issue. Researching...

[MuTools]

new strange snap issue:

grid setting 1/16th, draw one 1/16 note, set snap=OFF.

--> shorten the note a little bit at the end,
try to move the beginning of the note a little bit to the right
--> this does not work (it behaves like snap=ON).
move the beginning of the note a little bit to the left: it works.

==> if a note is shorter (or equal) than 1/16 and in between two 1/16 bars,
then the left side of the note is snapping, though snap=OFF

==> seems to be similar with other grid settings (e.g. 1/8th),
moving complete note seems to be no problem.

Will check.

[Improviser]

Question: When recording MIDI events into a new sequence, then MU.LAB automatically sets loop locators for that new sequence. Is that ok, or would it be better just to store the recording without loop locators. Then you can always add looping if you want of course.

My sequencing exploits are just a hobby. The sort of thing I'll be doing is trying to simulate the sound of Big Band, Dixieland Jazz, standards, etc, and I don't envisage using looping a lot.

So, if loop indacators were not automatically set, I probably wouldn't miss them !

Many other people may have a different view, and really I could live with either method.

Les J.

[cytone]

Question: When recording MIDI events into a new sequence, then MU.LAB automatically sets loop locators for that new sequence. Is that ok, or would it be better just to store the recording without loop locators. Then you can always add looping if you want of course.

Although I haven't been using MU.LAB for that long I've been more likely to adjust a parts size without wanting it to loop so +1 to this idea from me.

[liquidsound]

Question: When recording MIDI events into a new sequence, then MU.LAB automatically sets loop locators for that new sequence. Is that ok, or would it be better just to store the recording without loop locators. Then you can always add looping if you want of course.

Definitely!

Recording in the composer allows us to adjust the recording until done but if the loops are created then I need to go in the key editor every single time I modify the Take.

Even the "Set Length" of the Part's loop that is automatically set at the moment of the Part creation is a kind of a "push to loop style composing".... An image MuLab should not display if it needs to appeal to all kinds of musicians...

[jpumphandle]

Definitely!

Recording in the composer allows us to adjust the recording until done but if the loops are created then I need to go in the key editor every single time I modify the Take.

Even the "Set Length" of the Part's loop that is automatically set at the moment of the Part creation is a kind of a "push to loop style composing".... An image MuLab should not display if it needs to appeal to all kinds of musicians...

I totally agree with Liquidsound - No autoloops. This really screws things up when doing multiple takes.

M3.0.26 ...
In the process of weighing in on this I also looked into the CM Dominator (available on all the latest CM disks). It does seem to have a problem handling the GUI display after many bars have been recorded. However, I recorded many 'mouse' moves which seem to record accurately, but the GUI display lags. This did not seem to occur in another VSTi (TAL-Elek7ro).

[MuTools]

With other VST's such as CM Dominator and the Elektrostudio synth pack after maybe 10 bars Mu.Lab starts to slow down and eventually the VST controls get unresponsive.

Fixed in the next version 3.0.27.

[MuTools]

There was a strange bug in the earlier MU.LAB versions where it would crash on loading FabFilter One. I eventually found the workaround of placing an instance of it in the MPA and save that in the default project.

Then with the advent of 3.20 it was gone and I could load FabFilter without a problem.

The issue is again present in 3.26 - it's no biggie, I'm just doing the MPA trick again. I just wonder what's changed.
Marco

Based on the other reactions it seems to be a system/plugin specific issue

I'll try to give FabFilterOne on OSX a check at later time.

[MuTools]

new strange snap issue:

grid setting 1/16th, draw one 1/16 note, set snap=OFF.

--> shorten the note a little bit at the end,
try to move the beginning of the note a little bit to the right
--> this does not work (it behaves like snap=ON).
move the beginning of the note a little bit to the left: it works.

==> if a note is shorter (or equal) than 1/16 and in between two 1/16 bars,
then the left side of the note is snapping, though snap=OFF

==> seems to be similar with other grid settings (e.g. 1/8th),
moving complete note seems to be no problem.

Fixed in the next version 3.0.27.