M3 Tests

[theorize]

I hope this new way of choosing subtargets is more comfortable.

I noticed this and thought, "Oh, that's a lot nicer" but had no reason to use it at the time and forgot to comment! But yes, it looks like it'll be a lot more comfortable here, too.

ditto

[theorize]

Jo when you dropped the first beta i thought i read something about having relative paths... how extensive is this? Can I set it up and run it from a jump drive and it will remember where all my plugins are? Remember everything like sample folders (favorites)and so on? It always was really, really, really annoying that tunafish would always have me find all the plugs i used. Now that it supports MME I can take it anywhere, wouldn't mind going over to the university so I can be connected to the internet while doing sound design.

[Stephan326]

Setting keyboard shortcuts now works!!!

[liquidsound]

Setting keyboard shortcuts now works!!!

[liquidsound]

The Plug-Slot has two Hot Spots: the Name and the Arrow.
Previosly we comment on the option of 1 click=Open(Show) and 1 click=Close Plug-in and obviously you said the that if a Plug-in is hidden from another, by clicking once the Plug-in closes without being able to bring it to the front.
I agree.

But since we have 2 Hot Spots (Name and Arrow) and since the Arrow works with "1 click mode" and the Name with "2 clicks mode" then we can use the "Arrow 1 click mode" for the Quick Open/Close Plug-In method while the "Name 2 clicks mode" for the Open(Show)/Show method.

It may sound confusing but as of now we have 2 Hot Spots doing the same thing for no apparent reason.

At least we could have two choices: Open/Close & Open(Show)/Show.
No matter what we do with the "Name 2 clicks mode" the Plug-in is always there for us.

ReCap:
ARROW = Open/Close (Superb for quick checks of the Plug-in settings)
NAME = Open(Show)/Show (Right now it doesn't close it anyway...)

and of course you can always close the Plug-in the traditional way by the Close Box or... the Arrow!

The less we move the mouse around, the better the work-flow.

I wanted to elaborate on this to make sure we looked at it once more with alternatives before closing the subject until M5

[MuTools]

Jo when you dropped the first beta i thought i read something about having relative paths... how extensive is this? Can I set it up and run it from a jump drive and it will remember where all my plugins are? Remember everything like sample folders (favorites)and so on? It always was really, really, really annoying that tunafish would always have me find all the plugs i used. Now that it supports MME I can take it anywhere, wouldn't mind going over to the university so I can be connected to the internet while doing sound design.

MU.LAB tries to use relative paths if possible.

This means files/folders that are in/below the mulab application folder or in/below the mulab library folder, or when saving patch files that are in/below the patch file folder.

Best thing you ca do is to try it out.

Make a comfortable MU.AB installation on a USB drive and switch it around. If should work well. Of course you'll have to update the audio setup on each computer but that's logical and inevitable. If you put your favorite VST plugins inside a "VstPlugins" folder in the Mulab application folder, MU.LAB will also use a relative path for your VST plugins and so they'll be found on every system. Note however that it also depends on the VST pluging itself, for some plugins put files that they need somewhere on the computer, and switching the USB stick to another computer may not include such files. Anyway there are many VST plugins that are 'independent' and can travel with MU.LAB to many computers.

[MuTools]

The Plug-Slot has two Hot Spots: the Name and the Arrow.
...
ReCap:
ARROW = Open/Close (Superb for quick checks of the Plug-in settings)
NAME = Open(Show)/Show (Right now it doesn't close it anyway...)

Sounds confusing to me. What do others think?

I wanted to elaborate on this to make sure we looked at it once more with alternatives before closing the subject until M5

Sure! That's what this forum is for

It's a pitty that i cannot immediately realize the open-close editor thing as that sounded like a good idea. Maybe i'll find a solution for the close-hidden-window issue lateron.

[Nielzie]

Could it be a particular VST plugin of mine causing the trouble Yes, that's possible, it's even very probable.

Ok I will look into it. I remember I had the same issue in M2 the first time. Strange thing is I do now use completely different Sytnhs and effects, but it's still probable that it's one of the plugins of course. But why only the fist time, are vst only scanned once in MU.LAB? When going from free version to full and I was rescanning there was also no crash anymore. So it probably did not a complete scan and only looked for new plugins?

What's wrong with [Ctrl]+drag part to copy a part? And if it's about extending a sequence part loop, simply drag its end further to the right so it loops longer.

Nothing wrong with it of course. It took me some time to find out I had to do it that way though. As a Windows user it just feels more natural to richt-click on the segment and find the most useful options in the menu. I'm looking at this from the viewpoint of a "newbie" vst host user who is only used to Windows programs and behavior.

In my dayjob I'm a Windows systems administrator, maybe that's why I look at it like that. That's probably why I asked about an installer option too.

See the Transport Panel, CPU meter is below the tempo

Ahh I had not even noticed Why isn't it on default showing the percentage in figures (that's why I didn't notice I guess)?

[MuTools]

Ok I will look into it. I remember I had the same issue in M2 the first time. Strange thing is I do now use completely different Sytnhs and effects, but it's still probable that it's one of the plugins of course. But why only the fist time, are vst only scanned once in MU.LAB?

When MU.LAB notices that there is a crash while scanning, it will skip that VST next time.

See the Transport Panel, CPU meter is below the tempo

Ahh I had not even noticed Why isn't it on default showing the percentage in figures (that's why I didn't notice I guess)?

I try to make MU.LAB as graphical as possible i.e. the lesser text, the better.

[Nielzie]

I really like this M3..

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


Bye bye EnergyXT2 and Orion 7... just uninstalled

[pquenin]

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 !

[pquenin]

I really like this M3..

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


Bye bye EnergyXT2 and Orion 7... just uninstalled

How can you live without the great Orion internal synths ?
Don't desinstall it but use it in Rewire mode !

[pquenin]

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...

[Nielzie]

I really like this M3..

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


Bye bye EnergyXT2 and Orion 7... just uninstalled

How can you live without the great Orion internal synths ?
Don't desinstall it but use it in Rewire mode !

Don't worry, I also have them separate as vst's

[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..