MuLab 10 Files Corrupting?

[KJ Breaker]

My MuLab 10 Files are corrupting when I save them, opening them or the backup file results in "Cannot open Project", then it launches the New template.

[MuTools]

Do this:

• Restart MuLab
• Open such project that doesn't open
• After clicking the error alert, goto MuLab menu -> Tools -> Keep Log
• Quit MuLab
• Now goto your MuLab/User/LogFiles folder and zip the most recent log file, which should match the date and time you launched MuLab for this test.
• Attach the zipped log file to your reply here.

[KJ Breaker]

Here it is

[MuTools]

The issue is related to Ozone 9 Imager.
This will need more research.

Until then you can try this to open the project file anyway:

• Start MuLab with a New Project
• Goto MuLab menu -> Tools -> Command Line
• Enter this command: "confirm load plugins"

Now try reopening that project but skip Ozone 9 Imager.
If it still doesn't open then retry opening but also skip any other plugins.

[MuTools]

PS: For research please also share the "Investigation.MuProject" file as a zip

[MuTools]

I tried Ozone Imager 11 (the current version) and it works fine as expected here, including saving and reopening a project that is using it. Are you sure you are using the latest version of Ozone Imager?

That said, i'm still interested in your "Investigation.MuProject" file that fails to open so it can be researched more in depth.

[KJ Breaker]

It might be a saving issue, as I did a "save" then a "save as" and named it "Investigation Backup.muproject", and the backup opened, but the normal file did not. I have also overwritten the version of "Investigation.muproject" that I gave you the log of, but I've attached another project with the same issue as well as its log.

[MuTools]

Thanks for the files.
Again this seems to be related to the Ozone 9 plugins. (i suspect Ozone 9 Dynamic EQ in this case).
As i wrote earlier i tried Ozone Imager 11 and that worked fine.
Maybe it's related to the Ozone 9 plugins.
I'd like to check that but they are not available anymore, right?

[KJ Breaker]

Yeah, they're a legacy product, but only from 2019, and I don't really feel like spending $660 to upgrade to 11

[MuTools]

I've contacted Native Instruments with a request for an Ozone 9 license so i can research this.

The next MuLab update will also do more detailed log output when loading & saving VST3 data, in order to narrow down the problem.

What about the VST2 version of the Ozone 9 plugins, does those work fine?

[MuTools]

Native Instruments kindly provided a Ozone 9 research license and so i checked using Ozone 9 in MuLab 10, including saving and reopening. It all works as expected, no errors, no data corruption.
That's using Ozone 9 version 9.13.0.2768.

Are you sure to use the very latest version of Ozone 9?
If yes then please download MuLab 10.0.85 and repeat your test and if you can repeat the data corruption issue then before quitting MuLab go to MuLab menu -> Tools -> Keep Log and then email the most recent MuLab log file in your MuLab/User/LogFiles subfolder to
It's important to do the O9 saving and reloading in the same MuLab session so that this log file contains all log info about the saving and about the loading.

[KJ Breaker]

Sorry for being a while, I just moved to Cubase because my father bought me a license.
MuLabs is amazing, easy to learn and use with its visual mux system, I'm very torn between moving to Cubase and staying on Mulabs, but unfortunately I can only pick one for use and I have to go with Cubase as I'm working towards being a movie composer and it has the tools I need. Thanks for being so helpful as well.

[MuTools]

Thanks for sharing your current decision honestly and transparently.
Also thanks for your appreciation for MuLab.
Note that you can still use MuLab Plugin inside Cubase

Wish you good luck and lots of creative joy

[KJ Breaker]

Thanks so much, I will have a look at MuLab Plugin, I didn't know what it does, but I had a look and you can open MuLabs Projects inside it just like standalone, right?

[MuTools]

Indeed. It's MuLab inside Cubase.