MuLab 10.0.85

[mgiambro]

Nice work! The ability to have sub racks is a great addition.

[MuTools]

Still - those options are a bit odd though

Those options only appear in special cases when you have been editing the modular routings inside a rack, and when switching the rack fader position is ambiguous and MuLab needs to know what you want. See this example:

[pekbro]

Maybe a modular level in the browser for M11. You could build querries, have list and
file browser output objects for mixed media etc. That could make for some interesting and complex project management if anyone desired that. Personally my projects are too small to need managing.

Anyway just saying, even if its too soon.

[sl23]

Why not go the whole hog and make the entire gui a mux!

Everything could be arranged how you want then. Imagine the gui fully configurable like a front panel!

You could have tabbed modular areas, tabbed composers or projects, add two or more browsers, one above the other, etc

[pekbro]

my thinking is that a node based interface
would help many make sense of what is
basically database manipulation. You could
have project specific views, preset and sample management etc. All at the same time.

[oldcastle]

Hei Jo,

This did not happen with v9.6, but it is happening with v10.

2024-11-06_21-16.png

[TorresBob88]

Why not go the whole hog and make the entire gui a mux!
Everything could be arranged how you want then. Imagine the gui fully configurable like a front panel!

Thats what keeps us from breaking the whole thing.

But yeah, if I had my ultimate druthers, I would probably move and remove a few things around in the top bar. Not because it would be "better", but just to personally suit myself. I would reduce the entire GUI to the 3-4 things that I know how to use.

[sl23]

Same here.

[MuTools]

When loading an old project (from 9.5) with vst3 plugins not yet added in the database, the dialog says simply "missing vst3 plugin" without identifying which one. Missing vst2 and CLAP plugins are identified in their missing plugins dialog box. In version 9.5 they were all identified.
This was also an issue in version 9.6

Will be fixed in M10.0.9.
Thx for reporting this.

[MuTools]

Does anyone know. Can each lane now have its own audio output in the rack mux?

I'm not sure what you mean. Please elaborate, maybe using a screenshot if that would help clarifying.

[MuTools]

Hei Jo,
This did not happen with v9.6, but it is happening with v10.
2024-11-06_21-16.png

Sounds like something specific to your system / that plugin.
Maybe you had this plugin inside your M9 folder, now copied the PluginDatabase.xml from M9 to M10 but did not copy the plugin itself? (just a draft thought)
If in doubt feel free to email me the relevant log file, i'll have a quick look at it.

[focusrite]

Does anyone know. Can each lane now have its own audio output in the rack mux?

I'm not sure what you mean. Please elaborate, maybe using a screenshot if that would help clarifying.

When there is am audio sequence you have multiple lanes. I would like to assign an input to each lane to be able to process them with different fx.

[Cochrane]

Hi,

a little question (with no immediate solution I suppose): from version 14, Cubase has 'officially' abandoned VST2 (yes, I know that on PCs I can re-enable them, at least for now...): are there plans for releasing MuLab as a VST3 native plugin? If yes, in what timeframe?

Thanks,
Cochrane

[MuTools]

A VST 3 version of MuLab Plugin surely is planned. But at this point no time estimation yet. Best to switch on VST 2 support in Cubase 14 for now.

[MuTools]

When there is am audio sequence you have multiple lanes. I would like to assign an input to each lane to be able to process them with different fx.

Ok i now clearly understand your question.
Such feature is currently not yet in there, but i expect it to be realized at some point, it would be logical, natural and fun.