Hi everyone,
Upon backing up, when I use File ▸ Backup Project (with “remove unused files”), the project folder is already complete and self-contained, all the used audio files are there.
However, I often read that it’s also recommended to save all audio files via export/multiple/add to cue.
What is the real advantage of doing this if the project is already backed up properly?
Thanks!
Hi, @archetipo
Maybe I am missing something, but I see no advantage whatsoever to add an export process to a properly backed up project, beside using more disk space…
As long as you do, first, Media > Prepare Archive (in case some audio files are outside the project audio subfolder), then, File > Backup Project, you are safe, IMO.
VST plugins over time can become incompatible with newer systems so exporting your VST instruments to audio can future proof them. Also an audio file means it is 100% the same every single time in terms of phase positions, oscillations, etc. So if you want precision every time, then audio files are best. But yes it will take more storage of course.
Beyond what others have mentioned, one big question would be if you expect to use Cubase “forever”. I came to Cubase after at least a decade and a half of SONAR’s having been my DAW (and before that, I was using Passport Designs MasterTracks Pro, albeit alongside hardware MIDI modules and for recording audio). On quite a few occasions I’ve wanted to remix older (SONAR-based) projects, but in Cubase. Depending on my project archival process when any given old project was finished, that can be easier or harder.
Most of the time, I’m not too concerned about the VST plugins as my reasons for remixing often are to improve those ancient mixes with newer plugins and mixing skills. However, especially with VST instruments that may no longer be available to me (e.g. Steinberg Virtual Guitarist and Virtual Guitarist - Electric Edition) and are loop-based (meaning the MIDI can’t recreate the same notes on anything other than those specific plugins), if I hadn’t made a backup that included the audio of those tracks, be it from having frozen it in the project or separately rendered it to audio, I’m out of luck and needing to start from scratch in creating a part to replace that component.
Of course, even if I still wanted to use SONAR for those projects, those specific virtual instruments might no longer be usable. (Interestingly, both VG and VG-EE were still working in SONAR on my 11-year-old Windows 10 system, I think with SONAR’s built-in bridge for 32-bit plugins, but I didn’t find a way to install the plugins at all on my new Windows 11 system.)
The reason I mention the DAW permanence, though, is because, as long as I’ve included a standard MIDI file in my archives, and have underlying audio files in Broadcast Wave format from the original SONAR projects (or, even better OMF archives) I can even grab the underlying files if I can’t open the SONAR project at all.
Experience of remixing some very old projects in the last few years has definitely gotten me making some changes in my Cubase practices, including rendering instrument tracks to audio for mixing (so the actual audio will be included in the archives in project in addition to the disabled virtual instruments). While I do export stems using Cubase’s multiple export facility (mainly for potential sync considerations), I don’t generally export individual tracks, because there will be at least some audio incarnations of each track in the underlying audio files, and those can be available for use whether the Cubase project can be read or not.
Thanks everyone!
Yep, although in my final mixes I always render every VST to audio before the final mix / mastering stage. Once I use Backup Project, everything is exported as audio anyway.
What made me doubt whether I was doing the right thing is this Dom Sigales video https://www.youtube.com/watch?v=P_r5jmw5Ba4 where he suggests to use the backup function but also to export all the single files via Export Cue