M7 Docs Upgrading MuProject Files   


From time to time the MuTools codebase is cleaned up in order to keep it light and fresh towards future developments. Sometimes this means removing old code sections which were specific for maintaining compatibility between old project/preset file formats. For example MuLab 7 can only load projects saved with MuLab 4.2.0 and up. No panic though, this does not mean you cannot open older projects in MuLab 7 anymore, it only means that for such old projects there is an extra step. The extra step is that the old project is first opened and resaved eg with MuLab 4.5 (which still contains that compatibility code) and so then it can be opened with MuLab 7.

Practically: If MuLab cannot open an older MuProject file it will neatly tell you which MuLab version saved the file, and which MuLab versions you need to use to upgrade the project. FYI: You can also open a MuProject file in a text editor so to quickly see with what version it was saved. Attention: Do not edit nor save the file with a text editor though as it will become unreadable because the text editor most probably will add extra data which is unknown by MuLab.

There also is an easy function to upgrade all your projects in one go: MULAB menu -> "Upgrade Projects". So if you have a neatly organized project folder, upgrading projects is quick and easy.

You can find the necessary older versions here: www.mutools.com/mulab/legacy-versions.
Registered users who need their old MuLab key to unlock one of these past versions, mail to .

Note that, although MuTools will always try to maintain as much sound compatibility as reasonably possible between successive versions of MuLab, it's possible that a newer version of MuLab does not sound 100% the same as a previous version because of little sonic differences caused by, for example, changes in the audio engine, the usage of a new or improved DSP algorithms etc. Again that's rather exceptional and should minimal. But if you are into professional production and perfect version management is important to you, then it's recommended to keep your different MuLab versions on file so that you can open a certain project in its original MuLab version if necessary. Of course, make sure not to overwrite such project by saving it from a newer MuLab as, like most software, MuLab project files are not forward compatible eg. you cannot open a MuLab 7 project file in MuLab 6. Alternatively, you could also mixdown tracks in the older MuLab version and import the audio files into the new MuLab version to preserve the exact same sound.

Note that before MuLab 6.4 "projects" were called "sessions" and the session files had extension ".MuSession". Now MuLab projects have the extension ".MuProject". The change in terminology has no impact on the content of the MuSession/MuProject file.


M7.0 Specific Notes

  • The Rim808 en Snare808 factory samples sound a little bit different (better!) than in M6. To keep it exactly the same as in M6, open the project/preset with M6 and copy the sample into the project's Audio sub-folder or embed the sample in the project/preset file.
  • The Tom909 factory sample sounds different (better!) than in M6. To get it more or less the same as the M6 version (but preserve the better quality): Pitch it down by +-300 cents and make it shorter. To keep it exactly the same as in M6, open the project/preset with M6 and copy the sample into the project's Audio sub-folder or embed the sample in the project/preset file.
  • The M7 factory piano sample set has slightly changed, improved. However if you really want a perfect copy of M6 Stand-In piano, copy the original Stand-In Piano sample folder in your UserLibrary/Sample/Tones/Pianos/ sub-folder. M7 will check this location and use it when it exists.
  • Some audio samples of the Pure demo project have been replaced by (new) factory samples.
  • When used on stereo signals the Audio Envelope Follower and Level Compressor modules may sound a little bit different as in M6, depending on the stereo signal.

Table Of Contents