I just noticed that one of my projects started to be slow to work with.
It’s a 35 track audio only project. No VSTi’s.
2 FX tracks for reverb sends (Reverence), and two FX tracks for delay sends.
Waves SSL channel on nearly every track. A few other VST inserts here and there.
Looking at the project file, I see it has grown to 43Mb. Is this normal?
What kind of info is recorded into this file?
Btw, saving to a new project name gives the same file size.
Running Cubase 5.5.2 32-bit on Win 7 64-bit
I don’t think that the content of AUDIO-folder has got anything to do with this issue; Project file only is supposted to save the LINKS to the corresponding audio files, and where to place them, and the event info + FX + GROUPS + all that. The guy was talking about the PROJECT FILE (.cpr) and not the size of the whole folder (including the audio material).
Cubase doesn’t save the audio data in the project file. Or how the heck do I know anyway, but it sure shouldn’t!
I noticed the very same thing with my CPR-files. About 5-15MB of size, which seems weird. I can’t figure that what kind of crap Cubase saves inside the project file, but I’ll look into it and post here if I find the solution.
OK, I’m pretty sure what takes so much space on the Project file; You see, Cubase (like all the other DAWs too) make a graphical images of the waveforms that are used in the project. So it means that no one DAW draws the Wave Image info “on-the-fly” since this would render your PC very, very slow, since this is not a fast task by any means.
It’s a looooot faster that it makes a graphical picture of all the audio files, so that you can, say, zoom in/out fast and all that. So as my earlier DAW saves the Image files in its own directory, I’m pretty sure that Cubase saves them with the actual Project file.
You can notice the rendering of the WAV Image file when you like import audio into your project and insert them on the multi-track. Then Cubase shows the text inside the event that reads something like “calculating image data” or something. Can’t remember.
And as I compared the size of the actual audio data to the project file size, they really seem to be related. I mean that if for example your audio data amount gets double, the size of the project file also gets about twice as big. So there’s really no way to circumvent this. It’s very normal behaviour.
If you projects get way too slow, consider investing on like 4 similar and fast hard-drives and configurating them as RAID0 - like I did. RAID0 means that PC reads and writes from and to all disks at the same time. RAID0 is also called as STRIPE SET. So if you have 4 hard drives in RAID0, they are exactly 4 times as fast as a single hard drive but of course the size of the RAID0 is also 4 times bigger.
The downside of this is, that it’s not very redundant; if one hard-drive of the RAID0-set fails, then all the data from all the other disks is useless and everything is lost. So that’s why I’ve got an external USB hardrive taking backups of all my files every single day.
Oh, that I didn’t know… I use also VariAudio very much so that’s probably one reason. What data actually of VariAudio does it save to the project file? It takes suspiciously much of space then, if it is really that…
Let’s hope that Steiny’s people will see this thread.
Sorry, sorry, sorry! The PEAK DATA FILES (audio image file) are NOT saved within the project file. I checked out one of my projcet’s folder and they are saved under the “IMAGES”-folder.
Don’t really know what kind of crap it saves in the Project file then :\ My projects started saving slowly (not too slow but so that I noticed it) and since I have my auto save value as 2 minutes, it started bugging me enough. Would be nice to know how to make the CPR’s smaller.
It would actually be nice I wonder where Cubase consumes all the PC’s power but I once had this tiny little software named SAWPlus32 and hell if I’d do ANY KIND of a downmix with that old software with my current workstation, the downmixing would be finished in 1-3 seconds.
Of course Cubase is “a BIT” more complex software so I’m sure the power is used conveniently. But anyhow, some things would be so nice to know. Like, for example, this problem with the huge Project files…!?
Variaudio might be a good tips.
2 vocal tracks have quite a bit of tweaking in Variaudio done to them, and it seems it might be after this the projectfile started to grow in size (but I can not confirm this at the moment).
Why save this kind of information in the project file…?
Well, I don´t really know, but it seems like a good idea if you open the file on a different computer or exchange projects with someone else, you´d probably want the Variaudio editing to be ported over…!?
Well, of cource one want’s the variaudio editing to be a part of the project, but adding this to a sidefile would make saving the project quicker. The Variaudio file should only be updated when one does Variaudio editing.
It is very annoying to have the whole project hang for the time it takes to save the project, and with the 43Mb file it takes some time.
…of cource all this only makes sense if Variaudio data is actually included in the project file.