MuLab 10.0.85

[Stephan326]

DAW is working here!!

[sl23]

I have a couple of issues:
First, I've used W1Limiter VST2 extensively throughout many projects, now I've upgraded it, I'm asked to convert to VST3, great work, no problem. Except in one project, I am also asked to convert TyrellN6 VST2 to VST3, trouble is, I don't know which one it is when I'm shown the menu list as there's no way to identify which vst you are actually meant to select for conversion. Could we have a title to show the name of the VST we are supposed to be converting here please.

Second, may be more a VST thing, but still, MuLab has crashed with no way to close except via EndTask in Task Manager.
On trying to update all my projects, I have one that is using Novation's V-Station VST2. Essentially, I have created Junctions to all my VST folders, so as to be able to make them portable for easier backup/reinstallation. This Junction isn't working, but it causes MuLab to hang indefinitely with the error that it can't load the VST. End Task doesn't kill it straight away either.

[sl23]

Hey Jo, don't you deem these two issues worthy of attention?

[MuTools]

Patience pls.

[sl23]

Ah sorry, I saw you'd been here and maybe you weren't bothered with these...

[MuTools]

Trying to use the Parameter Event Generator module to modulate the Triaz plugin. If I attempt this in the rack modular editor then I do not get the full list of automation parameters, starts at 49 and ends at 58, and those that show up don't work. If I set the same thing up in a mux then all 64 automation parameters show up and work. See pics.

Found the cause.
Will be fixed in the next M10.0.44.

[MuTools]

I'm not sure if this is wrong or just not supported behaviour. I'm trying to set up a bank of plugins that will handle ranges of MIDI input - so they process in parallel, effectively as a single plugin.

MuLab plugin 10.0.43 inside Reaper 7.34
Insert a Reaper instrument track with MuLab Plugin VSTi as the instrument
Replace the default MuLab "New Synth" main module with a Rack module
Open up the rack module
- Some of the slots are before the mixer strip, then the mixer strip, then some more after; all shown on the front panel with the "<" where the mixer strip inserts
- Now do some rewiring -- all the existing slots before the mixer strip, rewire to be in parallel (so Event Input 1 to Slot event in for each Slot, Slot audio out to Rack Mixer Strip audio in, Event Input 1 to Mixer Strip event input)
- Front panel doesn't change, which is ... okay. The "<" is still after all the slots above it...
Now copy one of the rewired slots -- it appears after the "<" on the front panel (added at the end).
- It isn't actually wired up
- I can't drag it on the front panel to before the "<"
- So I try rewiring so it's signal flow is before the mixer strip
- It's still shown at the end, after the "<", even though it's logically before the mixer strip

What I'd like is if I copy a slot connected to the mixer strip inputs (directly or indirectly), then it remains before the "<" and also remains connected (to whatever I copied it from's output - it might as well copy the inputs, too). I'd like that to have the effect on the Rack Front Panel that the new slot was in the appropriate place (before "<", if a copy of a slot that was before "<"). So if I have A->B->(mixer strip)->C and I copy B, then A->(B, B(copy))->(mixer strip)->C and B(copy) appears on the fron panel before the mixer strip (here "after A" with no implied ordering in respect of B).

I could hide the "parallel" part in a sub-Mux and stick that in a slot itself, of course...

In MuLab 10 racks still are meant as a user friendly bridge between the non-modular and the modular world. Racks try to comfort the (non-tech) user by avoiding the need for the modular area as much as possible. Eventhough MuLab 10 adds a lot of extra flexibility to racks for the in-between cases, the code that automates a rack's modular routing still assumes seriality of the slots.

If you want parallel parts in a rack then indeed it may be best to put these in a separate MUX in a slot, but that's not an obligation, you will feel whether your custom routing still is managable by MuLab's automated rack routing code or not.

Alternatively you could use "Module Slots" instead of "Rack Slots" since "Module Slots" are not managed automatically and so they may suit better for certain custom rack / MUX setups.

M10 Rack front panels cannot be edited, M10 racks still use a built-in editor.

The front panel order of the rack slots you add in the modular area is not defined by the routing but is defined by the order they were added. Because as you can imagine there can be complex routing cases which would make it impossible to automate the slot ordering. So it's something to be managed by the user who edits a rack's modular structure.

Note however you can add a slot before/after an existing slot by right-click on the existing rack slot and choose "Insert Slot Above" or "Insert Slot Below".

In case you copy a rack slot in the modular area it will indeed appear as the last slot, as you noticed. In the next M10.0.44, the context menu of rack slots in the modular area will also contain "Change Slot Index" for cases where you would need that.

I hope all the above clarifies the case you reported.
If i'm missing something, let me know.

[MuTools]

First, I've used W1Limiter VST2 extensively throughout many projects, now I've upgraded it, I'm asked to convert to VST3, great work, no problem. Except in one project, I am also asked to convert TyrellN6 VST2 to VST3, trouble is, I don't know which one it is when I'm shown the menu list as there's no way to identify which vst you are actually meant to select for conversion. Could we have a title to show the name of the VST we are supposed to be converting here please.

Please share a screenshot/screenvideo of this case.

Second, may be more a VST thing, but still, MuLab has crashed with no way to close except via EndTask in Task Manager.
On trying to update all my projects, I have one that is using Novation's V-Station VST2. Essentially, I have created Junctions to all my VST folders, so as to be able to make them portable for easier backup/reinstallation. This Junction isn't working, but it causes MuLab to hang indefinitely with the error that it can't load the VST. End Task doesn't kill it straight away either.

What is a "Junction"?

[paulbreeze]

mklink /j
https://learn.microsoft.com/en-us/windo ... nds/mklink

[pekbro]

Symbolic links have always been kind of a hack imo and unreliable under windows, e.g. they don't really work like the unix equivalent of them. I 'have' used them in the past with older versions of Mulab without any issue, at least in regard to Mulab however...

[dayvyg]

Trying to use the Parameter Event Generator module to modulate the Triaz plugin. If I attempt this in the rack modular editor then I do not get the full list of automation parameters, starts at 49 and ends at 58, and those that show up don't work. If I set the same thing up in a mux then all 64 automation parameters show up and work. See pics.

Found the cause.
Will be fixed in the next M10.0.44.

Awesome! Thanks for hunting that down. Greatly appreciated.

[MuTools]

MuLab does not have specific support for Windows shortcut links.

[MuTools]

MuLab App M10.0.44 beta is available on https://www.mutools.com/mulab/app/lates ... /beta.html

MuLab Plugin M10.0.44 beta is available on https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:

• Enhanced VST3 plugin support: More relaxed with VST3 plugins with odd initialisation behavior. (eg. Red Rock Sound plugs)
• Enhanced VST3 engine: In case a VST3 could not be fully instanciated then in specific cases this could lead to a crash. Fixed.
• Clicking a plugin editor's titlebar or top controls puts the GUI focus on the MuLab side of the plugin editor which makes it react on Esc to close the window or on other shortcut keys.
• Since M9.4.12, the Volume and Velocity Sense parameter controls were missing in the Noise Generator. Fixed.
• In some cases the default rack desk height was too high. Fixed.
• In some cases adding a new track did not work as it should. Fixed.
• In some cases creating a new rack from a MUX preset did not use the custom user rack if that exists. Fixed.
• Modular Area: The context menu of Rack Slots now includes "Change Slot Index".
• When lasso-selecting clips/notes/... very fast, or on a slower system, there could be an visual offset between the lasso and the mouse cursor. Fixed.
• Other small improvements.

[pekbro]

Awesome! vst3 enhancements are working great!

This fix is going to go a long way towards eliminating a bunch of duplicate plugins for me, thanks Jo!

[pljones]

On the subject of the Plugin Manager -- would it be possible to add a "Remove all unrecognised entries"? Or at least allow multiple selection of a range (rather than one by one addition with shift) and delete the selection. (I hit "Add Plugins" on "C:\Program Files" as there are several places under there my plugins get stored.)

Oh... I just noticed that, whilst no "Unrecognised" entries add to Instruments, it looks like they happily get added as Effects.

Name = 7-zip
Folder = /C:/Program Files/7-Zip
File = 7-zip.dll
Bit Size = 64

Plugin Type = VST2 Effect

Type = Not recognized as a valid VST2 Plugin

So "Plugin Type = VST2 Effect" and "Type = Not recognized as a valid VST2 Plugin"?