Disk full????

[gugu]

Hi,
I've got a new strange problem. When I record something (no problem when I import files), PT gives me a error message "disk full".

For instance I have a one minute recording on the empty disk (new session):

- My 4.5 Gb drive info tells me there's only 2Meg left (???)
- The audio files and the session have a normal size.
- Norton Disk Doctor says everything's OK

I use a G3 266 beige, Mac OS 8.6, 256M Ram, PT 4.3 / AM III / Quantum Atlas II AV 7200.

This system has been running fine for months.

Thanks for any idea.
Jean

[alldaywire]

i use a beige G3 also with similar memory, speed, etc.


This problem happens to me also sometimes. However, usually I find an audio file that for some reason will have an excessively wrong file size like 500 MG or 800 MG, when it should only be 10 or 20 MG. This audio file shouldn't be so large. To fix the problem, I simply drag the excessive file to a zip disk (which corrects the file size), delete the excessive file from the hard drive, then drag the corrected file back from the zip. The correct file size will now be represented. Did you understand? Hope it works for you.

[gugu]

Thanks for this reply, but I made tests where the audio files were correctly sized and however the disk info said it was full (with one minute of stereo audio).

regards
Jean

[Disco_Doctor]

If you disk says it is full, then it probably is. What happened is probably this: if Pro Tools crashes while recording, you will end up with an audio file on your hard drive that takes up the whole drive. Do a find file on your hard drive - search for files bigger than like 100,000KB. It's likely in your situation that you'll find a single file that is around 4GB. That file is corrupt - you can delete it and recover your hard drive space.

If the file has really important data in it and you can't afford to lose it, there is a way to save it - but I can't remember what the trick is. Give tech support a call...

[sound_mann]

I've had the same problems as Disco_Doctor. The solution works fine. Try reformatting your drive. I've found that to work.

[gugu]

Thanks guys.

I reformatted (low level) my drive, and it seems that the problem is solved. (may be a bad block...)

Jean