M3 Tests

[jpumphandle]

Question is: Why would you like to have the next event selected when you delete an event?

I just noticed that it was different. I got in the habit of deleting by just pressing the delete key which used to delete successive notes in the List Editor, now I need to first highlight a group then delete.

[MuTools]

In the next version, the list editor is further finetuned: you can lasso select events without having to hold [Shift]. It now also works as in the piano roll: Lasso select without [Shift] = make new selection, lasso select with [Shift] = build on current selection. This makes it easier to select a bunch of notes and [Delete] them

[liquidsound]

Jo,
any chance to add a way to stretch a Part in the Composer and at the same time move the Part's End-Loop marker (in the Key Editor) and vice versa?
Let me explain.

When I first create a Part, I choose the length that best fit what I have in mind.
BUT
If I want to change the Loop length (Increase) I have two not so practical way of doing it:

Context Menu > Sequence > Functions > Change Loop Length = Results:
The space allocated to the Part it's increased and to be able to use it (in the Key editor while working) I need to Zoom all (little round dot in the right bottom corner)
no problem, just zoom,
BUT
that working space is only virtual (MuLab plays only within visible Parts areas) unless:
I close the Key editor + Modify the Part's length + go back to the Key editor
so

#1
Context Menu
Change Length
Keep working or/and eventually
Close Key Editor
Modify Part's Length
Go back to Key Editor
Back to work...

#2
Close Key Editor
Change Part's length
Back in the Key Editor
Scroll or Zoom all
Move the End-Loop
Back to work.....

What I am getting to is one/Two! possible solutions to increase efficiency and Speed (the power of simplicity):8)

[A]
Changing Loop Length should automatically change the Part's length in the Composer as well, and the Part loops should follow unless I am missing something (about the Part loop usability at this point).

AND!/or...


In the Composer, modifying the Part's length "with a Modifier Key" should move the internal Part loop as well so that when I open the Key editor everything it's in place: Loop Marker at the "new end", the whole Part zoomed.

This makes for a more pleasurable experience and fluidity (work-flow) and would be best if both possible solutions are used to give consistency from the Composer or from within the Key Editor.
MuLab should be as smooth and fluid as possible.

I know... it never ends

[pljones]

In the next version, the list editor is further finetuned: you can lasso select events without having to hold [Shift]. It now also works as in the piano roll: Lasso select without [Shift] = make new selection, lasso select with [Shift] = build on current selection. This makes it easier to select a bunch of notes and [Delete] them

That sounds the "wrong" way around cfr other applications. Normally I'd expect to need to hold a modifier to extend an existing selection.

[MuTools]

Jo,
any chance to add a way to stretch a Part in the Composer and at the same time move the Part's End-Loop marker (in the Key Editor) and vice versa?
Let me explain.

Straight answer:
Chance is low this FR will be implemented soon.
It's unrealistic to add a function for every possible combination of functions. That would bloat the context menus enormously. The possible answer to such FRs would be to implement some kind of User Macros/User Scripts, imho. But this is far from being a top priority. But who knows, one day..?

[MuTools]

In the next version, the list editor is further finetuned: you can lasso select events without having to hold [Shift]. It now also works as in the piano roll: Lasso select without [Shift] = make new selection, lasso select with [Shift] = build on current selection. This makes it easier to select a bunch of notes and [Delete] them

That sounds the "wrong" way around cfr other applications. Normally I'd expect to need to hold a modifier to extend an existing selection.

That will be the case!

Without [Shift] = lasso a new selection
With [Shift] = lasso a selection ontop of the current selection

Just like in the other editors

[pljones]

Next time I'll try to be awake when reading!

[cytone]

In certain Synthia presets such as "Leads - Lab74" when I alter the Fatness control it completely changes the sound (not just fatter).
Is this a bug or am I doing something wrong?

[MuTools]

In certain Synthia presets such as "Leads - Lab74" when I alter the Fatness control it completely changes the sound (not just fatter).
Is this a bug or am I doing something wrong?

To answer the question: None of both

Anyway, you're right, there is 'an issue' with Lab74.

I guess i made the preset before Synthia was totally finished and there is some parameter in that preset that is not available in Synthia's front panel.

So the Lab74 preset has been updated in the next package.

Whcih other Synthia presets did you encounter with a similar issue?

[cytone]

Most of the Synthia organ sounds. I was trying to work out how the sounds were made but it's a secret parameter then.

[liquidsound]

It's unrealistic to add a function for every possible combination of functions. That would bloat the context menus enormously.

Of course not!
I my self dislike long ,deep context menus.
This is why i mentioned the modifier Key while dragging the Part in the Composer. (it was at the bottom of the post).
You almost had it in the 3.0.10 or near versions.

Happy Valentine's Day

[MuTools]

Maybe in a future version, can't promise more at this point.

[MuTools]

in OSX (at least on my machine) drag-n-drop turns to be a little painful, as the zone editor keeps disappearing under the main interface.

Yes, i noticed it too. Will research this and try to finetune this.

Finetuned in the next version.

[liquidsound]

Maybe in a future version, can't promise more at this point.

I got time...
I am planning to stick around for a long long time. M3 is becoming a real unique gem.

[NBV]

Other reports:

1. Virtual MIDI keyboard needs a mechanism to change octaves.

2. The names of numerically named folders (i.e. folders named 01, 02, 03...)
are not displayed in the "file" menu browsers.