MuTools

robert_p · Post by **robert_p** » Wed May 31, 2023 10:57 am

mutools wrote: Wed May 31, 2023 10:52 am MuLab 9 opens older M8 + M9 project file data, no prob at all about updates.
If you have M4-M7 projects/presets these can be upgraded using M8 and thus make them compat with M9. I fully agree that preserving file compatibility is very important.

That shouldn't be a problem if the "radical" changes would be introduced with MuLab10 - we can have both versions (9 and 10) installed.

P.S. My presets are saved within Studio One as ".preset" files - I only use MuLab's Muxes presets to store my templates.
---

Mu_Presets.jpg

MuTools · Post by **MuTools** » Wed May 31, 2023 11:33 am

robert_p wrote: Wed May 31, 2023 10:57 am That shouldn't be a problem if the "radical" changes would be introduced with MuLab10 - we can have both versions (9 and 10) installed.

M10 will open projects and presets from M9. No need to install them side by side.

robert_p · Post by **robert_p** » Wed May 31, 2023 12:04 pm

mutools wrote: Wed May 31, 2023 11:33 am M10 will open projects and presets from M9. No need to install them side by side.

There is a need, example: Create a project with Kontakt 5, uninstall Kontakt 5, Install Kontakt 6, try to re-open that project - result: plugin not found.

Create project with MUX8, uninstall MUX8, Install MuLab9 Plugin - try to re-open that project....

P.S. I'm talking abut using MuLab Plugin with another DAW, not a MuLab App. And by "Project" I mean "Studio One Project", not a "MuLab Project". And by "Presets" I mean "Studio One Instrument Presets", not "Mux Presets".

MuTools · Post by **MuTools** » Wed May 31, 2023 1:24 pm

That's a DAW aspect, not a MuLab aspect.

robert_p · Post by **robert_p** » Wed May 31, 2023 1:28 pm

mutools wrote: Wed May 31, 2023 1:24 pm That's a DAW aspect, not a MuLab aspect.

That's not MuLab aspect, but that is MuLab Plugin aspect as MuLab Plugin is intended to work with any DAW. If the future MuLab Plugin updates will break the other DAWs projects then the safest way for users is not to install MuLab Plugin updates.

FabBad · Post by **FabBad** » Wed May 31, 2023 1:34 pm

Hi, i noticed something weird with the plugin version.
Loading mux 8 and mulab 9 with a same preset (created with M8), both on the same DAW.
What i found, is that the plugin M9 is detuned by 1 semitone and some cents lower than the original m8 preset, compared side by side and tested on Reaper and FL Studio.
I don’t know why this happens, is maybe a bug?

The weird thing is that on Mulab 9 app doesn’t reproduce.
Can someone confirm?

robert_p · Post by **robert_p** » Wed May 31, 2023 1:42 pm

FabBad wrote: Wed May 31, 2023 1:34 pm Hi, i noticed something weird with the plugin version.
Loading mux 8 and mulab 9 with a same preset (...)

Speaking of the devil

Compatibility issues?

MuTools · Post by **MuTools** » Wed May 31, 2023 2:09 pm

robert_p wrote: Wed May 31, 2023 1:28 pm That's not MuLab aspect, but that is MuLab Plugin aspect as MuLab Plugin is intended to work with any DAW. If the future MuLab Plugin updates will break the other DAWs projects then the safest way for users is not to install MuLab Plugin updates.

From time to time, but only once in 2-3 years and only upon a new main version, there is a new lower limit for the MU file format compatibility, cfr https://www.mutools.com/info/M9/docs/mu ... jects.html

Even in that case (eg DAW projects that used MUX 7) there is an data upgrade path and it is recommended to upgrade your older MuLab files to the newest main version. There are built-in tools to easify such file format upgrade.

And even if you don't, such older project/preset files won't time out as the legacy MuLab versions are carefully preserved for long time backward data compatibility.

MuTools · Post by **MuTools** » Wed May 31, 2023 2:12 pm

FabBad wrote: Wed May 31, 2023 1:34 pm Hi, i noticed something weird with the plugin version.
Loading mux 8 and mulab 9 with a same preset (created with M8), both on the same DAW.
What i found, is that the plugin M9 is detuned by 1 semitone and some cents lower than the original m8 preset, compared side by side and tested on Reaper and FL Studio.
I don’t know why this happens, is maybe a bug?

The weird thing is that on Mulab 9 app doesn’t reproduce.
Can someone confirm?

Sounds like some samplerate issue to me.
Please provide more details.

robert_p · Post by **robert_p** » Wed May 31, 2023 2:19 pm

mutools wrote: Wed May 31, 2023 2:09 pm From time to time, but only once in 2-3 years and only upon a new main version, there is a new lower limit for the MU file format compatibility, cfr https://www.mutools.com/info/M9/docs/mu ... jects.html

Even in that case (eg DAW projects that used MUX 7) there is an data upgrade path and it is recommended to upgrade your MuLab files to the newest main version.

I'm not sure you understand: upgrading MuLab files has nothing to do with projects created with other DAW's and containing MuLab plugin - the plugin state is loaded from "DAW's Song File", and the DAW doesn't know if MuLab files has been upgraded or not. Also, If the (other DAW) project is created with MuLab9 Plugin - it will be loaded with MuLab9 Plugin even if MuLab10 Plugin is installed. This is the reason to keep booth versions (9 and 10) - uninstalling ver.9 and opening older (other DAW's) project will result with "plugin not found" message. The same applies to MUX presets saved in other DAW's file formats. (Cubase, Bitwig, Reaper, Studio One "instrument presets").

MuTools · Post by **MuTools** » Wed May 31, 2023 2:32 pm

If you have a DAW project with MUX 8 data and you only install MuLab 9 Plugin, MuLab has no prob loading that data. It will be similar for DAW projects with M9 data and using M10.

There only is a possible issue in the DAW not finding the older plugin version but that's a DAW aspect. Eg. MuLab neatly ask the user which plugin to use in that case. If you then point it to the newer version, and the plugin supports backward data compatibility, like MuLab does, then all is fine.

FabBad · Post by **FabBad** » Wed May 31, 2023 2:32 pm

mutools wrote: Wed May 31, 2023 2:12 pm Sounds like some samplerate issue to me.
Please provide more details.

All my setup is running in 48000Hz since 6 months ago aprox. Before was 44100.

Load the same instrument preset in MUX 8 and also in Mulab 9 plugin and test side by side by putting some notes on pianoroll in FL Studio for example.

Edit: yes it is, a Sample rate issue on M9 plugin (just tested by changing it on Fl Studio)

MuTools · Post by **MuTools** » Wed May 31, 2023 2:33 pm

Which instrument preset are you talking about?

FabBad · Post by **FabBad** » Wed May 31, 2023 2:47 pm

A native one, for example the default synth when load on daw.

robert_p · Post by **robert_p** » Wed May 31, 2023 2:48 pm

mutools wrote: Wed May 31, 2023 2:32 pm If you have a DAW project with MUX 8 data and you only install MuLab 9 Plugin, MuLab has no prob loading that data. It will be similar for DAW projects with M9 data and using M10.

There only is a possible issue in the DAW not finding the older plugin version but that's a DAW aspect. Eg. MuLab neatly ask the user which plugin to use in that case. If you then point it to the newer version, and the plugin supports backward data compatibility, like MuLab does, then all is fine.

This is the result of opening Studio One project containing uninstalled MUX8 plugin. There is no such a thing as MuLab9 asking which plugin to use. That's why I need to keep both versions - MUX8 for older projects and MuLab9 for newer.
---

Missing Device.jpg

MuTools

KVR Audio

MuLab 9.1.27 [released]