MuLab 4.3.15 pre-release is available in http://www.mutools.com/mulab/cedar

What's changed since MuLab 4.3.14:

• Event Delay module: In the meta-parameter map editor and in the List Editor etc, the displayed Delay Time value was not the right one. Fixed.
  
• Shortcut Manager: When editing a shortcut, then doing Cancel, then the shortcut list was not refreshed to display the original values.
  
• Parameter Event Generator: When changing connections while editor was open, the parameter list was not updated. Fixed.
  
• VST plugins can now also be opened with the generic editor.
  

If you already have installed MuLab 4.3.14, you can simply update the app/exe file.

Otherwise see http://www.mutools.com/info/docs/mulab/installation.html

The generic VST GUI is the most brilliant idea in years!
In case you can't find it: Open the VST, the Mulab Options button, last entry in the list

Finally i can see real gain values in my favourite VibeEQ!

Thanks Jo, braj
Last edited by AndreasD on Mon Aug 06, 2012 5:58 am; edited 1 time in total

You're welcome

By the way: You don't have to open the default VST editor to open the generic one, it's also available from the VST plugin's context menu itself.

And it's also a shortcuttable function

Of course, the first one I tried didn't work... This was Plogue / Garritan / MakeMusic ARIA Player 1.504. The normal UI loads okay (there's a dialog pop-up warning box, though...). Next I tried simpler instrument (ComboV organ), which worked. Then, Kontakt5 Player... which wouldn't load at all any more. Weird: MuLab finds it... then lists it twice (same happens with my other NI "5" Player products like Reactor). Kontakt 4 (full) loaded up okay and displayed in the generic editor okay (if somewhat overwhelmingly...).

ETA: Didn't mention the pop-up on opening ARIA Player full UI...
ETA: Sorry, I didn't actually mention the error message on trying Kontakt (etc)! It said "Couldn't locate VST plug-in Kontakt 5" with "Locate" and "Ignore" buttons. Using locate to select the DLL gets the same message in response.

I also get this happening for one other plugin:
[VstPlugins.Xml]  <Plug>
    <FilePath>/C:/Program Files/VSTPlugIns/Cakewalk/Dimension Pro/Dimension Pro/Dimension Pro x64.dll</FilePath>
    <FileSize>2470912</FileSize>
    <NumPrograms>1</NumPrograms>
    <NumParams>862</NumParams>
    <NumInputs>0</NumInputs>
    <NumOutputs>2</NumOutputs>
    <Flags>305</Flags>
    <Valid>1</Valid>
    <Enabled>1</Enabled>
    <Selected>0</Selected>
    <InitialDelay>0</InitialDelay>
    <UniqueID>1684893299</UniqueID>
    <Version>1</Version>
    <VstVersion>2400</VstVersion>
  </Plug>
  <Plug>
    <FilePath>/C:/Program Files/VSTPlugIns/Cakewalk/Dimension Pro/Dimension Pro x64.dll</FilePath>
    <FileSize>2470912</FileSize>
    <NumPrograms>1</NumPrograms>
    <NumParams>862</NumParams>
    <NumInputs>0</NumInputs>
    <NumOutputs>2</NumOutputs>
    <Flags>305</Flags>
    <Valid>1</Valid>
    <Enabled>1</Enabled>
    <Selected>0</Selected>
    <InitialDelay>0</InitialDelay>
    <UniqueID>1684893299</UniqueID>
    <Version>1</Version>
    <VstVersion>2400</VstVersion>
  </Plug>
The path ...Cakewalk/Dimension Pro/Dimension Pro/... doesn't exist, so I don't know how it's being generated. There are other .../Cakewalk subfolders and the same issue does NOT happen there.

It's not the same thing with the NI synths, though - they're only listed once in VstPlugins.Xml.

(This is all on my x64 install, not tried the x86.)

???

And are these probs all new since M4.3.15? Everything was working fine before?

Hm, I've not been noticing closely... I'll have to go back and check some earlier versions. Can you think of anything that could have trigger it and I'll start around there, otherwise I'll work back one at a time.

Please email me your VstPlugins.Xml. Thanks.

I found something, see http://www.kvraudio.com/forum/viewtopic.php?p=5028076#502807 6

So this explains part of the issues you reported, but not all as you said that there even is a problem with plugins that are only listed once, right? Can you please double-check that. Then if you're sure there still is another issue than the one i found, please let me know the details. Thanks!

I haven't bothered to update to the latest version(s) as nothing has changed in the Mac version? Correct...

I think many things have changed in the Mac version! Whether they are important to you is up to you of course. Here is the change log: http://www.mutools.com/mulab-change-log.html

Hey did you saw my reply on your post about the sequence browser location?

Is there a way to capture the output of the VST scan? I don't seem to be able to cut-n-paste from that window. I can then clear my set up and rescan, plus produce listings of the folders scanned, along with the resulting XML. But it's probably better to wait for the update now, in case it fixes it.

It's saved in VstPluginScanLog.Txt in the Settings folder. But that file is auto deleted when you close the scan window, because that's the way Mu detects whether there was a crash during scan. So copy it before closing that window. Alternatively you could switch on logging, all vst scan info is also logged.

I understand. Will do.

Maybe just me, but it seems that things are working fine on the PC version but I still haven't received any verification from a Mac user whether their midi keyboards are working, or whether the program unexpectedly crashes upon quitting etc. It would be nice to know this... I have to decide whether I should upgrade my current Mac to a newer model as Snow Leopard is it for my current computer. So a few things like current OSX operating system, and other bugs are of interest to me for future decisions.

I've got the latest version of MuLab running well on Snow Leopard. (I don't want to lose some PPC games when upgrading to newer OSX.)

Midi works well using Edirol UM-1EX interface with my ancient Casio CZ-1.

I have a Edirol PCR-30 which is old, but it's always worked fine until I upgraded to Snow Leopard. Now I have to go into midi setup every time I launch MuLab. Also crashes pretty much every time I leave it running... then quit. But the midi bug is pretty annoying. May be my old keyboard drivers which are 2010 I think. But you're using an Edirol too. Hmmm....