M3 Tests

[MuTools]

About the scroll/zoom thing :
- Ctrl + MMB + drag : scroll
- Ctrl + RMB + drag : scroll
- Alt+ MMB + drag : scroll
- Alt+ RMB + drag : scroll
--> strange isn't it ?

If you tell MU.LAB that EditorNavigation=MouseWheelScrolls, then everything is inversed. So i think things are logical now, no?

Without a modifier key you have :
- MMB + drag : scroll
- RMB + drag : zoom
--> and it's great because you can access the 2 functions

For me, it must be the same functions, with or without modifier key :
- (Ctrl/Alt) MMB + drag : scroll
- (Ctrl/Alt) RMB + drag : zoom

It's more logical to me !

I see your point, forgot it was about the EditorNavigation=MouseWheelScrolls case.

In the next version, MMB and RMB-drag always have the same behaviour.

Except for the fact that you can doubleclick MMB to zoom out fully. Not possible with RMB as this would hurt the context menu clicking system.

[MuTools]

I really like this M3..

Ladies and gentlemen I hereby declare that from now on I will use MU.LAB as my main DAW

Thanks Nielzie

I hope/whish you and others will have a lot of creative fun with M3

[MuTools]

As we can now split all parts on all tracks with a single split, it should be good to have a way to select all the parts to the right so that we can make room to insert measures. Because there is nothing new in this area in M3...

I still believe it's something essential !
Even the little PDA sequencers have something to insert measures...

I agree. It's on the whishlist. And i'll push its priority.

[liquidsound]

Without a modifier key you have :
- MMB + drag : scroll
- RMB + drag : zoom
--> and it's great because you can access the 2 functions

For me, it must be the same functions, with or without modifier key :
- (Ctrl/Alt) MMB + drag : scroll
- (Ctrl/Alt) RMB + drag : zoom

It's more logical to me !

Imagine when Jo could implement this:
RMB(Drag)+Wheel(Zoom) at the same time!!!

Now we're talking. Move around AND zoom in/out. This would solve the Autoscroll issue and the zoom All (more or less on the last one).

You can't beat that!

Jo can this be done?

[Nielzie]

is it normal when after uninstalling vst plugins and rescanning the plugin folder with MU.LAB that they still show up in the VST plugin Manager?

Only way to make them disappear from the VST plugin Manager is to load the plugin, get an error that the plugin can't be found and let it be disabled in the MU.LAB plugin database

Or delete them from the VstPlugins.Xml file, but I guess it's not meant to do it that way..

Anyone else having this?

[MuTools]

is it normal when after uninstalling vst plugins and rescanning the plugin folder with MU.LAB that they still show up in the VST plugin Manager?

Only way to make them disappear from the VST plugin Manager is to load the plugin, get an error that the plugin can't be found and let it be disabled in the MU.LAB plugin database

Or delete them from the VstPlugins.Xml file, but I guess it's not meant to do it that way..

MU.LAB does not automatically detect when a VST plugin is unstalled.

You can easily remove VST plugins from the database by pressing the [Delete] key.

The other methods you mentioned will work too, but pressing [Delete] is the most comfortable one i think.

In the next version, you can also use the "Remove Broken Links" function via the new Options button.

[MuTools]

Without a modifier key you have :
- MMB + drag : scroll
- RMB + drag : zoom
--> and it's great because you can access the 2 functions

For me, it must be the same functions, with or without modifier key :
- (Ctrl/Alt) MMB + drag : scroll
- (Ctrl/Alt) RMB + drag : zoom

It's more logical to me !

Imagine when Jo could implement this:
RMB(Drag)+Wheel(Zoom) at the same time!!!

Now we're talking. Move around AND zoom in/out. This would solve the Autoscroll issue and the zoom All (more or less on the last one).

You can't beat that!

Jo can this be done?

To answer the very question: Almost everything can be done

[Nielzie]

is it normal when after uninstalling vst plugins and rescanning the plugin folder with MU.LAB that they still show up in the VST plugin Manager?

Only way to make them disappear from the VST plugin Manager is to load the plugin, get an error that the plugin can't be found and let it be disabled in the MU.LAB plugin database

Or delete them from the VstPlugins.Xml file, but I guess it's not meant to do it that way..

MU.LAB does not automatically detect when a VST plugin is unstalled.

You can easily remove VST plugins from the database by pressing the [Delete] key.

The other methods you mentioned will work too, but pressing [Delete] is the most comfortable one i think.

In the next version, you can also use the "Remove Broken Links" function via the new Options button.

Ahh just the [Delete] button.. I should have thought about that

Me and my right clicking habbits again

[MuTools]

Me and my right clicking habbits again

You're 100% right, it should be there. Added to the whishlist.

[liquidsound]

To answer the very question: Almost everything can be done

M v.?

[Bonteburg]

The taget/ sub target system is nice!! It's a rather elegant solution.

I haven't yet come across the bug where MU.LAB would make little stutter edits in my recorded audio like s-s-s-so.

Though it was/ is(?) a rather elusive little thing. Hard to pin down.

Sorry to ask but did you already have a chance to expand your computer's RAM?

I have to admit I didn't get around to do it yet

That said, I can't bring myself to believe it's memory related, as it doesn't happen in Renoise and Ardour, nor indeed when I record MU.LAB's output into Audio Hijack -in which case MU.LAB , Audio Hijack and Quicktime (to provide a click track) put an even greater load on the RAM.

Actually, I think it's kind of similar to the MIDI-recording gap I was talking about - a momentary hang up, imprinted on the recording (you don't hear it whilst recording/ playing, only in the final file).

I would be curious for other OSX users' experiences.

[MuTools]

To answer the very question: Almost everything can be done

M v.?

Unknown. (sorry)

[MuTools]

MU.LAB test 3.0.10 is available in this webfolder: http://www.mutools.com/mulab/azalea

If you already have installed 3.0.7 or later you can simply install the latest application patch.

[Nielzie]

MU.LAB 3.0.10

When I put a vst instrument in a rack I can play with my midi keyboard, but after I use the "replace" function and choose another vst instrument, then there is no sound anymore when playing my keyboard.

Possibly a bug?

[MuTools]

I assume you had the MIDI input focus on the synth-being-replaced.

And so as it was removed, the MIDI input focus was removed too.

I'll try to finetune this.