M3 Tests

[robenestobenz]

This is what i did in MU.LAB 3.0.26 FREE:

* I opened Intro.MuSession.
* Opened Shortcuts dialog, deleted F1+F2, mapped Alt+S to Generic->Toggle Snap On/Off
* I open first KraftLine sequence, Alt+S works fine

Hmm.. works fine how? Given the part is set to "no grid", logic says snap toggle should have no effect, right?

Did you try binding keys to increase/decrease grid and did these work in the first Kraftline part?

[Improviser]

So far, I haven't played a lot with shortcut preferences (maximum of 16 in Test version, MULAB Free), but just had a quick try to repeat this.

Perhaps the reult is dependent on whether you are choosing 'Toggle Snap ON/OFF' from the "Generic" list or the "Specific" list. Here (in M.3.0.26, on Windows), if I select via "Specific->Sequence Part->Toggle Snap ON/OFF" I can get the behaviour Eggu mentions. If I select via "Generic->Toggle Snap ON/OFF", I get the shortcut working ok in both the Composer and the Note Editor windows.

Not sure whether that's of any help?

Yes, that could indeed explain what Eggu encounters.

But then i hope you see the logic:

If you assign a shortcut to Sequence Part->Toggle Snap ON/OFF, then it only works for sequence parts of course, that's exactly what the specific list is for.

By default, i would recommend to use the Generic shortcuts, but in some cases you might need to define shortcuts more Specificly to avoid ambiguities.

Agreed.

[Eggu} It would be interesting to know if you had selected via "Specific->Sequence Part->Toggle Snap ON/OFF" (intentionally, or otherwise) - and so maybe resolve your 'mystery'.

Les J.

[MuTools]

This is what i did in MU.LAB 3.0.26 FREE:

* I opened Intro.MuSession.
* Opened Shortcuts dialog, deleted F1+F2, mapped Alt+S to Generic->Toggle Snap On/Off
* I open first KraftLine sequence, Alt+S works fine

Hmm.. works fine how? Given the part is set to "no grid", logic says snap toggle should have no effect, right?

The shortcut is executed, so pressing the key has effect, i see "Snap On" or Snap Off" in lower-right info box.

But practically it makes no difference in such situation indeed.

Did you try binding keys to increase/decrease grid and did these work in the first Kraftline part?

Ah, ok, i see what you mean.

I'll update the Intro.MuSession so it has proper grid settings. Something minorly odd slipped into that session during the M3 R&D cycle.

[Eggu]

So far, I haven't played a lot with shortcut preferences (maximum of 16 in Test version, MULAB Free), but just had a quick try to repeat this.

Perhaps the reult is dependent on whether you are choosing 'Toggle Snap ON/OFF' from the "Generic" list or the "Specific" list. Here (in M.3.0.26, on Windows), if I select via "Specific->Sequence Part->Toggle Snap ON/OFF" I can get the behaviour Eggu mentions. If I select via "Generic->Toggle Snap ON/OFF", I get the shortcut working ok in both the Composer and the Note Editor windows.

Not sure whether that's of any help?

Yes, that could indeed explain what Eggu encounters.

But then i hope you see the logic:

If you assign a shortcut to Sequence Part->Toggle Snap ON/OFF, then it only works for sequence parts of course, that's exactly what the specific list is for.

By default, i would recommend to use the Generic shortcuts, but in some cases you might need to define shortcuts more Specificly to avoid ambiguities.

Ok, with generic shortcut it works fine,
and yes, I see the logic,
but I wasn't aware of it up to now.

[MuTools]

Ah, ok, glad this is sorted out

I'm also working on the M3 docs, which will include a page on the shortcuts.

[NBV]

The acces to the pencil tool (double click) is uncomfortable. I suggest a menu like the one in Muzys or earlier mu.lab versions. Sometimes is painful even moving a sequence because, if you are not precise enough with the mouse, your hand-tool (or the arrow-tool) turns into a pencil while you are moving draging the sequence and then its length is changed.

[MuTools]

The acces to the pencil tool (double click) is uncomfortable.
I suggest a menu like the one in Muzys or earlier mu.lab versions. Sometimes is painful even moving a sequence because, if you are not precise enough with the mouse, your hand-tool (or the arrow-tool) turns into a pencil while you are moving draging the sequence and then its length is changed.

The very reason why there is 'only 1 tool' is that tool switching is in the way of making music.

Double-clicking to create new objects is a often used method, also in other software. Note that you can also use [Ctrl]+mouse to pencil around.

We've bee discussing the new editing methods here on the forum, and i thought we made a very nice system, though i can understand that it's difficult to make a system that pleases every-one.

Anyway, feel free to keep on making suggestions.

[cytone]

Jo,

As you enjoy sorting out weird behaviour here's some:

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

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.

Recording from a hardware midi device seems ok, it's with the mouse that causes the problems.

[liquidsound]

The acces to the pencil tool (double click) is uncomfortable. I suggest a menu like the one in Muzys or earlier mu.lab versions. Sometimes is painful even moving a sequence because, if you are not precise enough with the mouse, your hand-tool (or the arrow-tool) turns into a pencil while you are moving draging the sequence and then its length is changed.

That could be a little difficult when you are dealing with monitor resolutions and/or zooming out too much so that objects get too small and the hot spots are very close.
This is where the Mouse Wheel Zooming is incredibly effective.
You can get close pretty fast with it and avoid the Hot spots proximity's sensitivity.

I think that on the wish list is a feature of LMB grabbing/dragging and RMB scroll at the same time to move around so that you can get close and still cover large distances. I am not sure if IT'S on the wish list or I was dreaming....

[robenestobenz]

I'd love a configurable width for part / note edge hotspots myself, as I find them too wide as it is. Of course if my mouse accuracy was decent in the first place it wouldn't matter so much... Which is weird, because you should need more accuracy to select the edges, yet I never have any problem with that.

I think that on the wish list is a feature of LMB grabbing/dragging and RMB scroll at the same time to move around so that you can get close and still cover large distances. I am not sure if IT'S on the wish list or I was dreaming....

[Bonteburg]

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

[Jazz Franco]

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

Can't confirm in OSX10.4. FFOne loads OK, no crashes aftewards.

[Branis]

FabFilter One works fine here in Vista.

[NBV]

We've bee discussing the new editing methods here on the forum, and i thought we made a very nice system, though i can understand that it's difficult to make a system that pleases every-one.

Anyway, feel free to keep on making suggestions.

Yes, that's true, don't worry it's just kinda hard to get used to a new way of doing things. It happens to everyone.

[Eggu]

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.