Loading/Saving take longer in Sonar

  • Thread starter Thread starter 4ever
  • Start date Start date
4

4ever

Member
As I record more and more audio tracks it takes Sonar to load or save the file. Would installing more RAM help a bit? Currently I have 256K. I think I can go up to 512K.

Or is it just a harddrive thing that can't be avoided and has nothing to do with RAM?

It sure is fun inserting new audio tracks every time you want to add more. I couldn't do that in PA9 :p
 
Hope you mean megabytes instead of kilobytes... ;)

It might be both, but adding another 256 MB or RAM couldn't hurt at all!
 
Are you saving these as bundle files (.cwb)? If so, the problem is that the audio must be copied to your hard drive everytime you open the file. The more audio, the longer the process.

Save them as project files (.cwp) and they will open much faster. Bundles are primarily for backup or for transporting between computers.
 
Yes, I meant 256K. Thanks.

dachay2tnr said:
Are you saving these as bundle files (.cwb)? If so, the problem is that the audio must be copied to your hard drive everytime you open the file. The more audio, the longer the process.

Save them as project files (.cwp) and they will open much faster. Bundles are primarily for backup or for transporting between computers.
Click to expand...

Yes, I save them as CWB files. I read over the years that saving as bundle file is the safest way. And it make sense about audio being copied everytime I open the file. My 40Gig hard drive has only 28Gig left about 15 versions of the same song later :D
Now, I'll try saving it in CWP. Thanks for the advice.
 
I just made a post on another thread on the same situation. The bundle file was designed to move your song to another computer only. That doesn't mean that you can't do what your doing. I wouldn't recomend only saving your files as a bundle unless your harddrive space is limited. If you do load as a bundle file, it is going to take forever! My hard drive is limited right now and I just did a album for a client, so I saved each song as a bundle file and saved them to a disk, and loaded them up from there. I have to admit, it's very time consuming!!! I need to just install about 80 more gigs to avoid the hassle!!!;) :)
 
With this bundling-unbundling your HD becomes fragmented very soon so make sure all is OK in this department.
 
I have a question.

When you save as a normal file, the wave files are stored at a central location somewhere (a black box :-). Wave files from your other projects are stored there as well. The question is once you're done with a certain project, eq. you've burned the CD, you need to delete the project. How do you accomplish that? When you delete the project and hit "clean the audio files" will the associated audio files be deleted also? Do you delete the project from Sonar or do you need to use Windows Explorer?
 
First, when are through with a project I would highly recommend you do not just delete the project. Save it as bundle file to a CD-R (assuming it is smaller than 650 MB - if it's larger, well that's for another thread).

How Sonar saves audio depends on whether you are running Sonar 1 or Sonar 2, and if Sonar 2, whether you have chosen the "per project" option for audio.

Assuming you are running Sonar 1 (or you have not selected "per project" in Sonar 2), then yes, ALL the audio from ALL your projects is saved in one single directory.

To get rid of the audio from a single project, delete the project in Windows Explorer and empty the recycle bin. Then open Sonar the run the Clean Audio tool. It will find any audio that has no associated project file (which includes this one since you just deleted it) and remove it.

I have found the tool to be relatively safe over the couple of years I have used Sonar. However, if you still feel unsure, get a copy of Cakewalk Audio Finder tool. That will tell you what audio files are associated with what project files, and you can delete manually.
 
You must log in or register to reply here.
Back
Top