in order to avoid corrupted projects with glitches, noises, CPU and Disk Cache peaks warnings, …
If you modify files outside Cubase, save them with another name and import them manually inside Cubase after. (ie boring…)
It will work perhaps using Wavelab but all others programs will cause you nightmares and headaches.
I spent one week finding a solution to repair corrupted projects after converting “false” stereo files to mono outside Cubase using Stereomonoizer.
Especially because the warnings Cubase sent you are not appropriate. (CPU peaks, Disk Cache peaks, ppm meters @0dBFS, …)
Maybe you experienced sudden Disk Cache peaks in your projects and perhaps this is simply due to modified files.
See one solution at the end.
It would be nice for a professional program to warn the user that the files inside the pool have been changed and to suggest to update them.
But for the moment, if you change the files outside Cubase, neither the images (.peak files), nor the cache file (.csh) will be updated, and worst, the pool will be unchanged.
Even if you delete the ‘Images’ folder and the *.csh files, all the modified files are not likely to be updated inside the pool, and the project will still be broken.
These solutions are not enough:
- Close the broken project;
- Delete Images Folder;
- Delete corespondings *.csh files;
- Create a Temp folder;
- Move the modified files to this Temp folder;
- Open the project;
- Close the Pop-Up window asking to look for missing files;
- Open all the tracks in the projects window ie open all folders tracks to force rebuild waveforms;
- Open the pool;
- Right Click inside the pool and choose ‘find missing files’;
- Point to the Temp folder, now all the modified files are finally updated in the pool;
- Save the project;
- Close the project;
- Move the all the files in the Temp folder back to their previous location;
- open the project again;
- When the Missing Files Pop-Up window open point to the right folder;
- save the project again.