M4 Test

[MuTools]

3. The auto expand a track - or track expand to 1-3 set sizes? Useful when one has 15-20 tracks... which I do all the time.

Tracks or Racks?

Tracks as in the left side of the arrange/composition window. Racks already can be reduced and expanded. So when selecting a track (left side of window) they expand to a preset size (1-3) when selecting another track they reduce again to small size and the new track expands. Nice for seeing what you're working on be it midi or audio? That's the way Logic works anyway...

Interesting idea. Added on the WL.

[MuTools]

Explain ...How does note off have anything to do with shifting the beat/note forward from it's current grid position?

pic...

A note has a length, so if you move the note, the ending of the note moves too.

[Bonteburg]

Can you please give me a ultra detailed step by step how i can repeat it with M4.0.107 starting from a clean factory New.Musession. Sorry to ask, thanks in advance!

It's simple - create a new musession, import any audio file to any rack, press 'play entire file' and the sound will stop after the locator at Bar 1 in the default arranger.

Move any of the locators anywhere at all and the problem is fixed until the next session.

The MIDI-forget issue is pretty much a non issue IMO - wouldn't even have mentioned it if it hadnt been for the snazzy new startup dialogue. If it stays in MULAB forever I wouldn't be fussed.

[MuTools]

Can you please give me a ultra detailed step by step how i can repeat it with M4.0.107 starting from a clean factory New.Musession. Sorry to ask, thanks in advance!

It's simple - create a new musession, import any audio file to any rack, press 'play entire file' and the sound will stop after the locator at Bar 1 in the default arranger.

So even no mixdown involved?

This is what i just did:

* New session
* Draw new audio part on track 1 from 1.1.0 to 5.1.0
* Audio part -> Play Entire File
* Press Play

Now the audio file plays, also bar 2, 3 and so on.

Not on your system?

The MIDI-forget issue is pretty much a non issue IMO - wouldn't even have mentioned it if it hadnt been for the snazzy new startup dialogue. If it stays in MULAB forever I wouldn't be fussed.

I agree it's not a showstopper, but i do take it serious.
Unfortunately despite all tests i already did, i still have no clue what's going on. To be continued.

[DHR53]

Explain ...How does note off have anything to do with shifting the beat/note forward from it's current grid position?

pic...

A note has a length, so if you move the note, the ending of the note moves too.

So how would I move the notes to the position/length depicted here with the functions? i.e. a slight shift to the right of the grid?

[plutonia]

3. The auto expand a track - or track expand to 1-3 set sizes? Useful when one has 15-20 tracks... which I do all the time.

Tracks or Racks?

Tracks as in the left side of the arrange/composition window. Racks already can be reduced and expanded. So when selecting a track (left side of window) they expand to a preset size (1-3) when selecting another track they reduce again to small size and the new track expands. Nice for seeing what you're working on be it midi or audio? That's the way Logic works anyway...

Interesting idea. Added on the WL.

I like this idea except i prefer the option of allocating key commands to the vertical/horizontal zooming in on the composer page('+' and '-' at present)

being able to assign keys would be great for zooming in and out once a composition gets more tracks.

sub tracks for automation like those used in logic would also be a useful feature

[pljones]

So how would I move the notes to the position/length depicted here with the functions? i.e. a slight shift to the right of the grid?

By (a) selecting the notes you want affected and then (b) adding bars<dot>beats<dot>ticks to its current position using the "Function->Change times" menu. A positive value added will move the selected event later, negative will move it earlier.

Or turn off the snap to grid, lasso the events and line them up by eye.

Or set the grid size to an appropriate value, lasso, etc...

sub tracks for automation like those used in logic would also be a useful feature

Is that different from MU.LAB's automation sub-tracks?

[DHR53]

MuLab has automation sub tracks yes. The question is how to access/display them quickly while working in the compose window... Logic expands the selected track... then if I press A the automation sub tracks are displayed under the track. And hidden again if I press A again. Nice quick way to show and hide them as needed.

Also here is the correct syntax for changing time (moving a note as depicted here) FYI anyone who hasn't figured this out like me! Ha!

That's 0.0.30



Thanks PLJ

[Reincke]

When I switch the rack desk to windowed mode and minimize it after that, the taskbar appears, but it's empty - there is no rack desk icon in it. An intended behavior?

Hi Jo, I would expect, that a windowed rack desk does appear in mulabs task bar when minimized, as in M3. But it doesn't. Any idea 'bout that? I liked this feature for two reasons:
- my netbook display requires enough space for tracks
- sometimes the level meters swallows too much CPU power when not minimized

[MuTools]

When I switch the rack desk to windowed mode and minimize it after that, the taskbar appears, but it's empty - there is no rack desk icon in it. An intended behavior?

Hi Jo, I would expect, that a windowed rack desk does appear in mulabs task bar when minimized, as in M3. But it doesn't. Any idea 'bout that? I liked this feature for two reasons:
- my netbook display requires enough space for tracks
- sometimes the level meters swallows too much CPU power when not minimized

Yes i've taken note on the WL.
Until i found a solid solution, please use a shortcut for now, so you can easily show/hide the windowed rack desk. Hope that works for you.

[MuTools]

Also... I've created a cmnd. key for "set position as a way to navigate through the timeline since there is no way to go one bar at a time say... but the dialog that pops up doesn't let me type in a number. Like 10, for bar 10? Or even a way to go one bar at a time with the arrow keys... I have to keep moving 1/4 bar at a time to go say 10 bars? I'd like to use that as a way to navigate quickly in addition to markers. Would be nice if it popped up and let me type in a number.Thanks!

See http://www.mutools.com/mulab/docs/gui-info.html bottom of the page.

[Reincke]

Yes i've taken note on the WL.
Until i found a solid solution, please use a shortcut for now, so you can easily show/hide the windowed rack desk. Hope that works for you.

Alrightee!
BTW: I noticed an improvement in performance of M4 compared to M3 :tu::tu:. Please keep on considering this for further development 'cause of "weak cpu" users like me.

[DHR53]

Also... I've created a cmnd. key for "set position as a way to navigate through the timeline since there is no way to go one bar at a time say... but the dialog that pops up doesn't let me type in a number. Like 10, for bar 10? Or even a way to go one bar at a time with the arrow keys... I have to keep moving 1/4 bar at a time to go say 10 bars? I'd like to use that as a way to navigate quickly in addition to markers. Would be nice if it popped up and let me type in a number.Thanks!

See http://www.mutools.com/mulab/docs/gui-info.html bottom of the page.

I would like to suggest this dialog would be great for quickly moving to a "bar" location in the composition window of say, a 65 bar song... i.e. I use my cmnd. key to pop this up and go to say bar 45. But I can't see myself ever saying go to bar 45 beat 4 tick 150? I think if the dialog is used for navigation it should be set at the bar scale. Another dialog to navigate within a "sequence" like this seems to make more sense. Although I realize this functions on a wide scale, it seems too much information for a simple function. Maybe when it pops up it default to "highlighted"... so you can type in any detail you want?

[MuTools]

When you simply type 45 it will be interpreted as bars.
The points to separate Bars-Beats-Ticks are not necessary. The first point, if any, is for separating Bars<->Beats, the second point, if any, is for separating Beats<->Ticks.

[DHR53]

Hmmm... when the dialog box opens, it's not active to type something in. I have to dbl. click, then another box pops up which I can type a number in? Seems strange to have another dialog box when the first dialog should be "active"? Then when I've typed in a number... I have to "select" ok. Hitting the return key doesn't close the dialog? Lot of clicking to move 20 bars at a time...

Also, the scroll screen behavior seems to turn on and off? I turn it on (cmnd. key) and it scrolls for a certain distance but won't go all the way to the end of the song. I have to turn it back on again? How's that work?

Thanks!