Hey guys.
 
So i am unable to load a project i'm working on in SonarX3 - it loads a bit, and then hangs.  I noticed that my Disk Space Meter is in the red, so i looked up what that might be about and got this:

Disk Space meter.  Shows the amount of available space on the drive where your wave data directory is located. The tooltip shows the actual remaining disk space on your audio disk.
Haven't found much more than that.
 
In this case, is 'my wave data directory' the audio folder for my project? 
The audio folder for this project has 6 or 7 Gigabytes of recorded audio in it
The project data hard drive (500Gig capacity) has 48.5 G available space.  Is this OK?
 
Does the number of tracks affect the 'disk space'
There are a lot of tracks in this project - would that affect the disk space meter?
 
And finally, what/where is this tooltip that shows 'actual remaining disk space'?
 
Thanks for your help!
 

I think that is an indication that you aren't getting enough drive throughput.
 
I saw in another post where someone had success with increasing the I/O Buffer size in Preferences.  One person suggested 512, and another suggested 1024.
 
Bob Bone
 

Thanks robert_e_bone.  It is/was set to >1024.  Should i try >2048?  How about >4096?
 

The disk activity indicator shows problems with throughput. The OP is complaining that the disk space meter is showing inadequate actual disk space, while some unspecified Windows application is showing that there is plenty of space. One possible explanation is that Sonar may not have permissions required to write to all of the available disk space. 
 
Try running Sonar as administrator (not just a user member of the administrator group). What version of Windows is running? Also explain exactly how you determined the amount of available disk space under Windows.
 
http://windows.microsoft.com/en-us/windows7/how-do-i-run-an-application-once-with-a-full-administrator-access-token
 

I think slarta is on the right path.

I would also be concerned that you only have 48gb left of a 500gb drive. Once a mechanical HD gets over 3/4 full, it's time to do some house cleaning because it's performance starts to degrade after it gets over half full.

Grem
I think slarta is on the right path.

I would also be concerned that you only have 48gb left of a 500gb drive. Once a mechanical HD gets over 3/4 full, it's time to do some house cleaning because it's performance starts to degrade after it gets over half full.

Just what I was going to say, clear what you can off the drive as performance seriously deteriorates on sata drive.
 
If you can afford an SSD drive get one but otherwise if you're running out of room sata drives are very cheap these days.
 
 
Steve

First trouble shooting action is ALWAYS to run a scan disk test.
 
Is it only the one project doing this?
 
And move some of the projects to another disk. If you can load other projects use save-as to another disk.   
 
Defraggers want at least 15% free space.
 
And: make sure the system is not placing a pagefile on the disk.
 

Running Sonar as an administrator is OK for testing. Best not to always do it.
 
Attempt to open the project in sonar's safe mode, disabling all the plug ins.  Do it open fully? if so it is one of the plugins causing the hanging and the disk indicator is just a symptom not a cause.
 
To isolate the plug, open the project in safe mode and only disable one plug at a time.

you can't expect a drive that is 90% full to perform well. you need a new drive to move your audio to. and don't let it fill up more than 50% (rule of thumb from the video side).
 
i just picked up a wd 4gb usb3 for $149. 2gb are under $100.

OOOOOOMGAWD - I shall strive to NEVER post at that time of day again.
 
Please ignore my prior post, as I was thinking it was throughput rather than space that was the issue.
 
I agree that space may need to be either made available on the current drive, or an additional drive added to the system.  Disk Cleanup doesn't take too long to analyze the easy pickings for crap that can quickly be deleted.  (temp files, etc).
 
Hopefully it's that easy to get things squared away - I again apologize for flat-lining during my earlier post.
 
And, @dion16, I think you may have meant TB, rather than GB, for your drive capacities in your post.  :)
 
Bob Bone