M3 Tests

[sorohanro]

Line Tool...

[bpblog]

this may not be a bug per se, but it seems somewhat illogical to me. when you right-click the timeline and then choose 'edit tempo changes', the following window lets you load/save sequences, quantize notes and such from it's options menu. when you load a sequence, you get a bunch of midi notes chilling where the tempo changes should be.

there's no crash or anything similar involved, but perhaps this should be tweaked. checked v2.7, same situation there, except it couldn't load sequences.

[MuTools]

this may not be a bug per se, but it seems somewhat illogical to me. when you right-click the timeline and then choose 'edit tempo changes', the following window lets you load/save sequences, quantize notes and such from it's options menu. when you load a sequence, you get a bunch of midi notes chilling where the tempo changes should be.

there's no crash or anything similar involved, but perhaps this should be tweaked. checked v2.7, same situation there, except it couldn't load sequences.

The 'logic' behind it is that it's about a tempo sequence.
And so the normal sequence functions are also available to edit the tempo sequence.

Load/Save may be handy sometimes, but i agree Quantize Notes doesn't make much sense there. I'll put a note on the whishlist. For now please just ignore/don't use the irrelevant functions.

[robenestobenz]

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 might be dumb, but split and split selected parts both seem to do the same thing.

One minor peculiarity with the split functionality is that if the cursor is in the timeline area, the split actually occurs at the last cursor position in the composition area rather than where the cursor is now. I'd either have it so it accurately splits using the cursor's horizontal position or disable split when the cursor is in the timeline area.

Also, would it be possible to have split work on the part underneath the cursor, even if there are no parts selected? I think this would be more ergonomic because a) mistakes apart, the user obviously wants to split something, and if there are no parts selected it is reasonable to assume that something is the part under the cursor and b) it's one less step in the operation. When doing multiple splits, like chopping up a loop, this becomes quite a big saving.

[MuTools]

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 might be dumb, but split and split selected parts both seem to do the same thing.

I agree MU.LAB was a bit confusing here. Finetuned in the next version.

One minor peculiarity with the split functionality is that if the cursor is in the timeline area, the split actually occurs at the last cursor position in the composition area rather than where the cursor is now. I'd either have it so it accurately splits using the cursor's horizontal position or disable split when the cursor is in the timeline area.

Next version: Will also work when in Time Bar.

Also, would it be possible to have split work on the part underneath the cursor, even if there are no parts selected? I think this would be more ergonomic because a) mistakes apart, the user obviously wants to split something, and if there are no parts selected it is reasonable to assume that something is the part under the cursor

In the next version, when doing "Split" when no parts are selected, all parts are splitted. This is consistent with e.g. in sequence editor: when no notes are selected and you do transpose, then all notes are transposed.

and b) it's one less step in the operation. When doing multiple splits, like chopping up a loop, this becomes quite a big saving.

That's no prob: Only select the part once and split it up as many times as you want using a shortcut. Please check out the next version 3.0.7 which will be distributed later today (normally).

[MuTools]

M Test 3.0.7 has been distributed.

Besides many other fixes and tunings, Track & Part Targets are back in play and it should all work 100% the same as in M27.

I want to postpone the conceptual talk about this to a later time, say in a couple of months. Be sure i'll then open a topic about it here and be already invited to join the brainstorm at that time

[liquidsound]

Jo the Grid issue is still there.
I though this is what it was going to be implemented.
Anyone please correct me if I am off....

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.

In other words the "No Grid" bottom option in the contex menu becomes only a visual command (show/hide grid' lines) while the Toggle ON/OFF actually turns on the Grid/snap feature.

MUCH BETTER!

The "No Grid" is still killing the Toggle Option which lost its meaning.
Toggle can not be restricted by the "No Grid" it makes no sense

[MuTools]

The "No Grid" is still killing the Toggle Option which lost its meaning. Toggle can not be restricted by the "No Grid" it makes no sense

I'm afraid i don't understand.

How it works now is simple:

Choose Grid = the visual thing
Snap ON/OFF = the snapping thing

If you choose "No Grid", it doesn't make a difference whether Snap is ON or OFF of course, but that's pure logic and doesn't hurt, right?

Maybe i'm missing something?

[TheGuysanIdiot]

The "No Grid" is just a visual thing now it just turns off the grid lines. Some users may wish to see no grid lines on occasion.

But whether "No Grid" should be completely removed from the menu is also a good point.

I am happy to have the option to be able to turn off the visual grid lines so the "No Grid" can stay.

The snap stuff is great.

(And yes I may be missing something also).

What do others think?

OZ

[liquidsound]

This is what I though was the logic

https://www.box.net/shared/x71750m8fu

It makes the Grid Visual On/OFF independent from Snapping and Snapping independent from the Visual

[Nielzie]

MULAB 3.0.7

When right clicking on the grid in the edit menu it sais "Zoom selecteds"

Could be better renamed to "Zoom selection" or "Zoom selected" I think.


I tested some today for the first time and I'm pleasantly surprised how stable and finished it already is. And it's definitely a big step forward from M2 imho

[pquenin]

Bug in 3.0.7 :
Open a new session : the Rack A has a green label.
I add a new track, choose target, new plugin in a new rack : the rack is created with the plugin in the first slot, OK.
Now I give the focus to the new rack : its label become green and a blue line appears around it (I've never notice this in M27).
Then I go to another rack -> it crashes (sometimes I have to switch between racks several times before it crashes).
Well there are other ways to have a crash but this one works for me.
I don't know what is this blue line around the racks, but sometimes it appears after a long time, maybe it is the reason why the crash happen ?

[pquenin]

I see that we can choose a target to a part : nice !
But can we have a tooltip on the part that show its target ???????

[bpblog]

i'm with pquenin on this one, i actually quite miss the lovely part/sequence property panel.

and thanks for bringing the feature back, at least for now!

[bpblog]

tested the grid settings and it's perfect, feels very cosy!
the only problem left from the user-friendly side of things is that there is no visual indication of whether the snap-to-grid is ON or OFF. perhaps the grid lines could be lighter when snapping is off? or a small button next to the loop on/off (this would probably be a far bigger pain to implement)?

the loop on/off button reminded me... i miss the effect that right-clicking the beat measure display had in m2. it used to rewind the track to the begining, and i used to click on it all the time (still do, but that results in a ), like an addict, while working on short loops and bits. in m3, it toggles the clock display on/off. can we have the clock display always on, as it is a very nice combo of clock + beat counter, and bring the old functionality back?