|
Each new main MuLab version will open sessions made in the previous main version, but might not open sessions made in an older version.
For example, MuLab 4 only opens sessions saved in MuLab 3.2.14 or up.
This is because the MuLab code base is regularly 'cleaned up' from older compatibility code, for reasons of coding efficiency, which is important towards the future of MuLab.
So there might be cases where you'll have to upgrade your sessions towards a newer MuLab version.
If MuLab 4 cannot open an older MuSession file it will tell you which version saved the file, so you know which versions to use to upgrade the file.
You can find the necessary older versions here: www.mutools.com/mulab/legacy-versions.
Registered users who need their old Luna/MuLab key to unlock one of these past versions, mail to  .
From MuLab 2.7 onwards there is the "Upgrade Sessions" function in the FILE/MULAB menu which allows to upgrade all sessions in a folder at once.
So if you have a neatly organized session folder, upgrading sessions can be done quickly.
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.
There might be little sonic differences caused by, for example, changes in the audio engine, the usage of a new DSP algorithm etc.
So 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 session in its original MuLab version if necessary.
Of course, make sure not to overwrite such session by saving it from a newer MuLab as, like most software, MuLab is not backward compatible.
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.
The key versions to upgrade sessions are:
- Luna PR 8.4
- MuLab 1.1
- MuLab 2.04
- MuLab 2.7
- MuLab 3.0
- MuLab 3.2.14
- MuLab 4
Example: Long time ago, you made a cool session in LUNA PR8.4. Now you want to load it in MuLab 4.
Do this:
- Backup the original session (not necessary but highly recommended!)
- Open the session in MuLab 1.1, save it again
- Open the session in MuLab 2.04, save it again
- Open the session in MuLab 2.7, save it again
- Open the session in MuLab 3.2.14, save it again
Now you'll be able to open the session in MuLab 4.
As a general note, please note that there is a huge difference between the M3 internals and the M4 internals. We've done serious effort to give M4 as much compatibility as possible towards M3 sessions and patches.
But it was reasonably impossible to make it 100% perfect.
For example: The M3 ADSR used linear slopes while the M4 ADSR uses logarithmic slopes which sound much better, more natural.
But so there is a little difference in the sound and the envelope times may not feel exactly the same, eventhough M3 patches and sessions are converted as good as possible.
There have been drastic changes in the way pitch and filter modulation is done, and most sessions and patches will stil sound quite alike.
But if the session/patch also uses automation and/or meta-parameters towards these parameters, it was practicaly impossible to realize perfect conversion.
So if you have important M3 sessions/patches, and you want to import them in M4, please do check in detail if everything still sounds as you want.
This can be realized by making a mixdown in M3 and a mixdown in M4 and compare them. Eventually track by track. This will reveal possible differences and so you can further finetune things manually, if the M4 conversion functions would be insufficient for you.
When M4 converts M3 sessions/patches, it will output conversion details into the log file, so if you enable logging, you can view these details in a text editor. This may be helpful in finetuning your M3 sessions in M4.
Notes:
- M3 meta-parameter mappings to ADSR time parameters: The current value is updated, but the minimum-maximum values are not.
- The M4 ADSR use a 0-40 sec range instead of a 0-10 sec range in M3.
- The Oscillator, (Multi) Sample Player and Noise Generator 'Volume' parameter now uses multiplied modulation.
- Oscillator and (Multi) Sample Player: The way Pitch Modulation is done has changed. Patches will be upgraded automatically with exception of meta-parameters mapped to the old "Mod.Depth" parameter.
- The M3 Filter Mod Depth parameter has been removed. This is now done using the source amplitude or using a Modulation Value Mapper.
- The M3 Comb Filter Mod Depth parameter has been removed. This is now done using the source amplitude or using a Modulation Value Mapper.
- MIDI controller mappings are not updated.
- M3 Synthia looses its Tremolo and Limiter when converted to MuSynth. Any automations to the Synthia front panel knobs must be reconnected to a relevant parameter.
- MultiSampla looses its Tremolo when converted to the new M4 MultiSampla.
- When an M3 MultiSampla used pitch/filter modulation, the modulation depth is not perfectly copied into M4.
- Sampla now is a standard MUX. Note you can also use MuSampla to almost do the same job. It depends on what you need.
| 