Backwards compatibility

Sonar can load projects from any previous versions of SONAR, but projects that are saved in Sonar cannot be re-opened in SONAR 1.x or SONAR 2.x. In case you need to open a pre-Sonar project in an earlier version of SONAR, it is recommended that you always create a backup copy of the original project before you re-save the project in Sonar.

Project files saved in Sonar will not open in SONAR 4 or earlier if they reference or include any of the following types of data or information:

32-bit and 64-bit audio clips, including clips and tracks that have been frozen or rendered as 32-bit or 64-bit data.

Audio clips that are not all of the same bit depth.

Patch points.

Project files saved in Sonar will not open in SONAR 5 if they reference 64-bit audio clips.

Project files saved in Sonar that contain multiple automation envelopes per track may appear like automation data is missing when opened in an earlier version of SONAR. To see all automation data for a track right-click on it and choose Envelopes > Show Track Envelopes and then select each envelope that you would like to show.

Sonar project files may contain new features that will be missing if opened in SONAR 5 and earlier, including:

ACT current context.

All AudioSnap data.

Automation Read Enable states.

Clip lock properties.

Preserve Mix between Gain Members setting.

Synth Rack Assignable Controls.

Synth Rack Automation.

Sonar project files may contain new features that will be missing if opened in SONAR 4, including:

Clip effects and clip automation:

Effects are removed.

Automation envelopes are orphaned.

Groups:

Sonar groups are preserved but will not be completely functional in SONAR 4.

Controls may be removed from groups.

Groups can't be added to or changed.

Group names will be truncated.

Sonar 4 may add extra groups to the project.

Re-saving a Sonar project file in an older version of SONAR may permanently remove the project data described above.

Template files saved from Sonar will not load in earlier versions of SONAR. This is because of changes made to Sonar's view persistence code.

 

See:

Known issues

Frequently asked questions