Why does archiving sometimes refuse to work? Sometimes it’s no problem at all, other times it just doesn’t.
Can you explain what you mean by “archiving” here? I always use the Cubase backup project feature, and I’ve never had any issues with that.
Ah, could be. Another case of Cubase using strange language. When I think of archiving, I think of archiving project files when the project is finished, and the backup project is perfect for that since you can also have it only included the audio files that are actually in use. These Track Archives are really more like templates, though there is something altogether different that is called track templates (sorry, it is actually “track presets”, not track templates). (I’ve experimented with both a bit, but haven’t made any significant use of them to date.) And, of course, there are project templates, which are another thing, too. ![]()
I have many projects that have been put together over many years. Each of these tend to include files from various different folders.
I go through the project back-up process, followed by “media/archive” and this sometimes results in a nice tidy project folder with all used files contained in the new back-up folder.
Sometimes the “consolidation” refuses to happen, with the used files still being pulled from all over the place.
Ah, okay. The “each tend to include files from different folders” portion would appear to be the complication I never see because every project I do is self-contained in terms of its audio files. For example, if I drag in an audio file from another directory (my main example is an ACID loop that does a verbal count-in), I let Cubase copy it to the project directory. (While I even do this with reference tracks, especially since most reference tracks will be CD quality, so 44.1 kHz, and I work at 96 kHz, I remove any reference tracks from the project before I do the backup to archive the project.)
I just googled the “media/archive” thing to try and understand what you meant, and I think you are probably alluding to “Media/Prepare Archive”, which brings a copy of the files spread across different locations to the current project folder. If so, I think you have the order of operations reversed. You need to do the prepare archive first before doing the project backup. Then the project backup will be able to include the files that had been elsewhere.
Here’s a link to a post on this topic (I’m linking directly to the step on the order, but there is information beyond that post that may also be relevant):
I suspect, if you do the backup first, it is still referencing the files that aren’t already in the project directory from their original locations.
Many thanks Rick - I’ve only done a preliminary check, but I think you are definitely onto something here - I’ll investigate deeper whenever I can.
The procedure I had gleaned did not convey that to me so hopefully my frustration will be solved.
Best regards
Ike