M3 Tests

[liquidsound]

My dHell laptop keybord died! Got a new one. Now back to M3.

Jo, now we have the option to Ctrl+LMB add note and Part! Fantastic. It covers many more users habits.

An extra fine tuning needs to be done though.

Option 1: (Write and drag around = like real world of pen and paper.)
LMB double click = Add Note /Part
RMB = Drag

Option 2: (Write and Zoom !? = Non consistent with Option 1.)
Ctrl+LMB one click = Add Note/Part
Ctrl+RMB = Zoom...

This is not necessary because the zoom is already with Shift+RMB and it is consistent with Option1 and Option 2.

So Option 2 Ctrl+RMB is a repetition of Shift+RMB. Confusing!

Option 2 should be behave like Option 1 but geared to users that are used to single click. Hence the Ctrl+RMB should still Drag around.

In this way all users regardless of their habits (Single or Double Click) are going to Zoom and Drag the same way).

WorkFlow...

[MuTools]

When you put your mouse at the beginning of a part the arrow changes into a pen but if you use the pen to extend the part to the left, nothing happen. The same thing for a note is OK : the note is extended to the right. It's OK also in the multisaple editor.
So it must be a bug he he !

What kind of part are you trying to extend to the left? Audio or Sequence part?

Note that the extend-to-the-left feature always tries to keep the current content at the same position.

So if you have an audio part that already plays the audio from the start, extending such audio part to the left doesn't have any effect as the part is already playing from the start. Maybe an timed-auto-hide alert should be given in such case to avoid confusion?

I was just tring this with a empty sequence part.

Will finetune this.

[MuTools]

A strange request, I'm not even sure it's possible. It could probably be a unique feature in comparison with other daws, but..

Could it be possible to calculate and show the amount of cpu usage per Rack? So a little cpu meter bar in every rack?

If even possible, I'm not asking to implement this right now, but I thought it would be an interesting and clever little idea..

Measuring CPU weight costs CPU cycles. It's not much, but when the system must measure all plugins individually, it will increase the overall CPU load. Don't want to go that path.

Note that you could always try to measure an individual plugin's CPU weight by muting all others, i.e. try to 'solo' the plugin.

[MuTools]

When I double click on the grid in a track outside of the area between the loop pointers I only get a "open/new sequence" list after dragging an area right after the double click.

When I double click on the area within the range of the loop pointers I don't have to drag an area to do this.

Is this supposed to be?

Yes.

I took me a while to understand the difference of behavior.

Strange, i think it's very logical.

Note that, when doubleclicking within the loop, you can still drag a part if you would not want it to go from loop start to loop end.

[MuTools]

I also got some crashes lately in M3, but I had forgotten to turn on the logging

You don't have to start logging unless there is a specific reason for it. So don't worry about it. If in some situation i think the log file could help to locate a prob, i'll ask it. But the Mulab log does not log the crash details themselves.

EDIT2: Ahh I narrowed it down to one particular session It's a session where I use one synth (Zebra2) in rack A and one synth (MicroTonic) in rack B. Both only have one little sequence in the track yet.. So it's only a short loop actually.

When I have this session open and I choose in the menu for open session or open recent session, MU.LAB instantly crashes I do see the "opening a new session will close this session" dialog screen just before the crash.

I guess it can't be Zebra2 or MicroTonic as these are very widely used instruments, so other users would have reported this earlier?

After restarting MU.LAB it askes to load the autosaved version of the latest session, but then another session then the one I had openen when it crashed opens.

Could you please email me that session, so i can try it here. Thanks.

[MuTools]

My dHell laptop keybord died! Got a new one. Now back to M3.

Jo, now we have the option to Ctrl+LMB add note and Part! Fantastic. It covers many more users habits.

An extra fine tuning needs to be done though.

Option 1: (Write and drag around = like real world of pen and paper.)
LMB double click = Add Note /Part
RMB = Drag

Option 2: (Write and Zoom !? = Non consistent with Option 1.)
Ctrl+LMB one click = Add Note/Part
Ctrl+RMB = Zoom...

This is not necessary because the zoom is already with Shift+RMB and it is consistent with Option1 and Option 2.

So Option 2 Ctrl+RMB is a repetition of Shift+RMB. Confusing!

Option 2 should be behave like Option 1 but geared to users that are used to single click. Hence the Ctrl+RMB should still Drag around.

In this way all users regardless of their habits (Single or Double Click) are going to Zoom and Drag the same way).

WorkFlow...

Pfew, man, not sure if i get it.

As far as i understand i want to reply that :

1) The scroll-zoom behaviour depends on the "EditorNavigation" preference!
2) Drawing parts/notes and zooming/scrolling are 2 different things
3) [Shift]+RMB is not a supported action. At this point it defaults to the same as [Ctrl]+RMB, but if you think that's confusing, i'll make sure it's only about [Ctrl]+RMB.

[MuTools]

Regarding drawing the part name at the left or centered: Some like it, some like it not.

I've checked a bunch of other hosts/daws and they all draw it at the left side.

I think i'll follow the standard. So i'll undo the experiment with drawing it centered.

The improvement that the name always is visible will stay though.

[Improviser]

Regarding drawing the part name at the left or centered: Some like it, some like it not.

I've checked a bunch of other hosts/daws and they all draw it at the left side.

I think i'll follow the standard. So i'll undo the experiment with drawing it centered.

The improvement that the name always is visible will stay though.

I've no particular preference, left or centre (happy with either), but would just mention that when I have a part which starts at 1.1.000, I find the part-name a little easier to read if I insert 2 or 3 spaces in front of the name when typing it.

To me, it looks cleaner than when the name appears up against the 'boundary' with the left pane. Maybe having the name moved slightly to the right could be a default , or an option ?

If not, I'll happily continue to do it manualy, as it's just one of my little preferences !

Les J.

[MuTools]

Yes i know what you mean, you're right, will finetune this.

[liquidsound]

My dHell laptop keybord died! Got a new one. Now back to M3.

Jo, now we have the option to Ctrl+LMB add note and Part! Fantastic. It covers many more users habits.

An extra fine tuning needs to be done though.

Option 1: (Write and drag around = like real world of pen and paper.)
LMB double click = Add Note /Part
RMB = Drag

Option 2: (Write and Zoom !? = Non consistent with Option 1.)
Ctrl+LMB one click = Add Note/Part
Ctrl+RMB = Zoom...

This is not necessary because the zoom is already with Shift+RMB and it is consistent with Option1 and Option 2.

So Option 2 Ctrl+RMB is a repetition of Shift+RMB. Confusing!

Option 2 should be behave like Option 1 but geared to users that are used to single click. Hence the Ctrl+RMB should still Drag around.

In this way all users regardless of their habits (Single or Double Click) are going to Zoom and Drag the same way).

WorkFlow...

Pfew, man, not sure if i get it.

As far as i understand i want to reply that :

1) The scroll-zoom behaviour depends on the "EditorNavigation" preference!
2) Drawing parts/notes and zooming/scrolling are 2 different things
3) [Shift]+RMB is not a supported action. At this point it defaults to the same as [Ctrl]+RMB, but if you think that's confusing, i'll make sure it's only about [Ctrl]+RMB.

Ups! Sorry I didn't realize that Shift+RMB defaults to [Ctrl]+RMB.

What I was thinking was that for users with 2-Click Habit they can write a note and then drag around(RMB), which is what we have know : Prefect!

For users with 1-click habit (Reason users for example) they could write and Drag pressing the [Ctrl]+RMB without press/release & press/release etc. the [Ctrl} key.

By having the [Shift] key doing the zooming as of now the the RMB if free for this kind of behavior for both types of users.

This is what I have noticed by being a user with both habits
Anyway it's not a Big Deal. Eventually it's just a matter of getting used to a sets of tools. (But I think it's always better to voice an opinion. You never know it could turn out to be a good one)

BTW (question from a non-tech user) when you say "EditorNavigation" preference! do you mean that is written in Stone or it's something that it's in a text file and can be individually adjusted by the user?

Thanks Jo for giving us so much leeway in asking for features specially in the work-flow which is what is beginning to be the major difference in all Those Blow-out application out there.
They're having the same issues. Features after features but the work-flow is going in the other direction.

MuLab is making a Real Difference.

[liquidsound]

Once I press the Record button there is no way to stop MuLab from going. This is due to simplicity, I think, because MuLab doesn't have a Stop button and I like that.
This behavior is good for it allows recording in and out while MuLab is playing.

But if MuLab is not playing (I am starting a new recording from the beginning or from a specific location) and I change my mind I must wait, and the Cursor has moved from that position from which I wanted to Record from.

Maybe there could be a feedback that tells MuLab when we (re-)press the "activated" Record button: "IF the Cursor is not moving THEN Stop, ELSE, keep going."

[sorohanro]

Once I press the Record button there is no way to stop MuLab from going. This is due to simplicity, I think, because MuLab doesn't have a Stop button and I like that.
This behavior is good for it allows recording in and out while MuLab is playing.

But if MuLab is not playing (I am starting a new recording from the beginning or from a specific location) and I change my mind I must wait, and the Cursor has moved from that position from which I wanted to Record from.

Maybe there could be a feedback that tells MuLab when we (re-)press the "activated" Record button: "IF the Cursor is not moving THEN Stop, ELSE, keep going."

???
The play button is actually a play and stop button.
You press it once = play
You press it second time = stop

Also works like almost all programs, press space bar for play/ stop.

[gemada]

I mean this:

When pasting parts/notes, the paste position is not defined by the playback cursor, but rather by the mouse cursor (snapped to grid)!

Jo, thanks for the tip.
IMHO the paste position should be defined by the playback cursor. Using mouse cursor for that just seems "weird" and confusing to me...

[liquidsound]

Once I press the Record button there is no way to stop MuLab from going. This is due to simplicity, I think, because MuLab doesn't have a Stop button and I like that.
This behavior is good for it allows recording in and out while MuLab is playing.

But if MuLab is not playing (I am starting a new recording from the beginning or from a specific location) and I change my mind I must wait, and the Cursor has moved from that position from which I wanted to Record from.

Maybe there could be a feedback that tells MuLab when we (re-)press the "activated" Record button: "IF the Cursor is not moving THEN Stop, ELSE, keep going."

???
The play button is actually a play and stop button.
You press it once = play
You press it second time = stop

Also works like almost all programs, press space bar for play/ stop.

What you are saying it's all valid up to the point of:

>MuLab is not playing
>I am ready to record
>I press RECORD
>MuLab is doing "Countdown" (nothing is happening yet)
>I change my mind I want to stop (several reasons exists to stop...)
>I press RECORD again = It deactivates but MuLab engine still going
OR
>I press PLAY before or after RECORD = MuLab engine still going
>Now MuLab will start AND only then I can stop it and the cursor has moved away from the original position.

This means I need to RePosition the cursor.
If this is at the beginning of the composition it is easier but if it's in the middle somewhere than is not practical at all.

[sorohanro]

I don't think I understand your problem.
I always press the spacebar and everything stops. As for "I need to RePosition the cursor. If this is at the beginning of the composition it is easier but if it's in the middle somewhere than is not practical at all."... how is that ?
1 - You have bar numbers so you know where you are.
2 - You have the "snap to grid" option, so the cursor snap to the beginning of the bar you were starting the recording.