MuLab 9.3.18 - VST3 plugin support

[digaldeman]

https://www.youtube.com/watch?v=V8gWvlEkkrk

Jo, did you make that beat in the video? It's hot! You should keep using it for future MuTools videos.

[mutools]

Would an upgrade have taken patches for MuVerb and turned them into MUX patches?

Even if that would be the case (pure theoretically, didn't research it), then this does not affect any project data. The error message you posted can only appear upon loading a host DAW project / host DAW preset. Anyway, it's indeed an odd situation and it feels like there is some mix up somewhere.

I'll see if I can find the log... I'm hoping I can find the Reaper track (big project - over 80 tracks) and then which patch on the track has the failure...

Ok i now understand you use the term "patch" also for host DAW data.

Anyway, i hope the relevant log file will help sorting this out.
Note that each DLL (MuVerb, MUX 8 Plugin, MuLab 9 Plugin) has its own installation folder and its own log file. But the tool DebugView shows everything together so that may help too.
https://learn.microsoft.com/en-us/sysin ... /debugview

[mutools]

https://www.youtube.com/watch?v=V8gWvlEkkrk

Jo, did you make that beat in the video? It's hot! You should keep using it for future MuTools videos.

Thank you

[ortseam]

https://www.youtube.com/watch?v=V8gWvlEkkrk

Seeing my favorite VST3-s in Mulab ecosystem looks like magic! Thank you so much!!!

[pljones]

Note that each DLL (MuVerb, MUX 8 Plugin, MuLab 9 Plugin) has its own installation folder and its own log file. But the tool DebugView shows everything together so that may help too.
https://learn.microsoft.com/en-us/sysin ... /debugview

DebugView says the *.txt Mu* log files are invalid - did you mean to use it to capture the error at the time?

[mutools]

It's not that you have to open the MuLab log files with Debugview, that won't work of course, no it's about launching Debugview and watch the log messages in realtime. You will see all log messages of all MuVerb / MUX / MuLab 9 instances and other apps and plugins as they're sent to Windows via OutputDebugString.

[pljones]

OK, I'll give that a go -- I got the pop-up but no MuLab log had appeared at the time (I've no MuVerb log directory, even - all MuVerb preferences are defaults).

[pljones]

OK...

Code: Select all

Opening Reaper project
[5268] New MU VST plug instance 
[5268] MuTools VST plugin MuVerb global init 
[5268] AppFilePath=/C:/PFx64/VST Plugins/MuTools/MuVerb Win64 VST/MuVerb.dll 
[5268] AppFilePath exists 
[5268] Gonna get desktop path 
[5268] Gonna init prefs & settings 
[5268] Gonna define graph folder 
[5268] Gonna read settings 
[5268] Gonna init sub-systems 
[5268] VST Host Vendor = Cockos 
[5268] VST Host Product = REAPER 
[5268] VST Host Version = 7010 

... and then it stops with the pop-up. Clicking OK, it continues with loading. The next pop-up appears without mention in the log of MuVerb.dll.

[mutools]

Ok, that doesn't tell much.
I'm afraid i can't help much more with this.
If good old MuVerb (built with the legacy M7 codebase) says there is a data error, well it means there is a data error somewhere. It's unclear who is repsonsible for that data error. (DAW / MuVerb / User)
No, i don't think MUX 8 or MuLab 9 have mangled MuVerb's data as that data comes from the host DAW, and because MUX 8 and MuLab 9 are completely separate DLLs that are independent from the MuVerb DLL.

[mutools]

EDIT: Strange: my other PC doesn't give the same error - same version of Reaper and same version of MuLab Plugin.

To bypass the problem and continue on the music project:
What about replacing the M7 MuVerb in the bad project by a MuLab 9 Plugin and setup M9 Plugin as a MuVerb and use the good project (on the other computer) to copy paste the MuVerb values into the M9 MuVerb?

I'll have to check both PCs are pointing at what's meant to be the same user library and same project library.

Note that that error message has nothing to do with MuVerb's / MUX's / MuLab's library. The data error is in the data that is sent from host DAW to plugin, not in a library preset file.

[pljones]

The data error is in the data that is sent from host DAW to plugin, not in a library preset file.

Which is part of what's so odd -- it's the same data, the same programs...

But yes, I'll try to find the MuVerb instance and replace it. (Just well over half the tracks have a MuLab Plugin instance containing multiple MUX containers... so finding it will be interesting... I'll start looking in the simple tracks, I think.)

Anyway, no problem - it's probably something I broke somewhere that's causing the different behaviour between the two setups. Not everything is shared (the binary and factory libary installs are separate, plus the MuVerb user library installs).

EDIT: Fixed it. Having thought I'd updated all instances of MUX 8 to MuLab 8 Plugin, I deleted MUX 8 on one PC but not the other... But no! I'd not. Now the project loads okay, having re-installed MUX 8. So I've found once instance, just got to find the other...

EDIT-2: OK, both were MUX 8 instances with Basic Effect from the factory library loaded (doing nothing - 0dB gain) - so no hint of MuVerb around...

[oldguy]

Awesome on VST3 support!

I'd been waiting for a while to upgrade from 8 to 9, and now have done so. Very much appreciated!

-Oldguy

[mutools]

MuLab App 9.3.18 is available on https://www.mutools.com/mulab/app/lates ... index.html

MuLab Plugin 9.3.18 is available on https://www.mutools.com/mulab/plugin/la ... index.html

What's changed:

Saved projects / presets with certain CLAP plugins (eg TAL Reverb 4) did not properly reload. Fixed.

[pekbro]

Thanks for vst 3 support jo, great job!

I am having some trouble with Red Rock Sounds vst 3 plugins all of them crashing MuLab 9.3.18 every time under win 10. thanks...

https://redrocksound.pro/en/macwin/

0x000014E8 11:58:32:692 Gonna load DLL C:\Program Files\Common Files\VST3\RRS EQ3 VST3_64.vst3
0x000014E8 11:58:32:769 Loaded DLL at 00007FFF3DE90000 = 000000079CFA0000
0x000014E8 11:58:32:770 DLL base address = 00007FFF3DE90000 = 000000079CFA0000
0x000014E8 11:58:32:770 DLL image size = 15806464
0x000014E8 11:58:32:770 DLL end address = 00007FFF3EDA3000 = 000000079DEB3000
0x000014E8 11:58:32:770 DLL entry point = 00007FFF3DF397AC = 000000079D0497AC
0x000014E8 11:58:32:770 Gonna lookup Vst3 'InitDll'
0x000014E8 11:58:32:771 Vst3 Cat=Audio Module Class
0x000014E8 11:58:33:113 Error Vst3[991] 1
0x000014E8 11:58:33:113 Error VPM[1544]
0x000014E8 11:58:33:113 Error Vst3[991] 1
0x000014E8 11:58:33:113 Unload plugin RRS EQ3 VST3_64
0x000014E8 11:58:33:235 Couldn't create VST3 instance for RRS EQ3 VST3_64

[mutools]

Thx pekbro for the report. Taken note.
The next 10 days i'll be mostly offline for a break.
I'll have a look at this afterwards.