ChuckU
New member
I am using a fairly old desktop PC, but have been running fine until a few months ago. Lately, I have been getting Dropout in the middle of recording, and it is really busting my stones.
My Setup:
Sonar 6 Producer
2.4Ghz, 2GB RAM, C-Drive is Apps-only. Audio data is on an internal (250GB)drive on a different Bus. I also use a USB-2 External (500GB). All drives 7200 RPM
RME Fireface 800, Focusrite Octopre w/ADAT. I record at 44.1, 24bit.
A few months back, I did a project, and needed to add a little something at the end. Crash after crash. "Disk Warning, Dropout." Up until that point, disk was at (maybe) 20%, CPU at about 40% (plenty of plugins).
Anyway, I worked around it by bouncing tracks, but never solved the problem.
Last week I was up to about 24 tracks, and got the dropout again. Got through it by saving the project, renaming and dumping some tracks (I'm sure I could have archived, but I didn't need the old takes, anyway - I now have track-layering down). Again, substantial plugins used (probably 15 comp and eq, or so - reverb routed to an effects buss).
This week, I had a project with only 14 tracks going on playback. Again, at the end, recording only track one at a time, with very little going on in the way of effects. Zero automation. At that point, I moved the entire project to another drive and I got the same problem. In the same place in the song. I was able to work around it by archiving some tracks.
It seems that the general consensus online is to manage system resources. I am pretty bare bones with that. The system is not online, and Power settings are optimized. Screen savers, hibernation, all shut down. I reloaded the RME driver and flashed the update. My last resort may be to change the FireWire PCI card as I apparently have an inferior one with a VIA chipset. RME all but recommends a TI chipset on their website.
I will probably punt the ASIO drivers for WMD, and ratchet up the latency, as I do no input monitoring, anyway.
I hope someone has a fix for this. Thanks.
My Setup:
Sonar 6 Producer
2.4Ghz, 2GB RAM, C-Drive is Apps-only. Audio data is on an internal (250GB)drive on a different Bus. I also use a USB-2 External (500GB). All drives 7200 RPM
RME Fireface 800, Focusrite Octopre w/ADAT. I record at 44.1, 24bit.
A few months back, I did a project, and needed to add a little something at the end. Crash after crash. "Disk Warning, Dropout." Up until that point, disk was at (maybe) 20%, CPU at about 40% (plenty of plugins).
Anyway, I worked around it by bouncing tracks, but never solved the problem.
Last week I was up to about 24 tracks, and got the dropout again. Got through it by saving the project, renaming and dumping some tracks (I'm sure I could have archived, but I didn't need the old takes, anyway - I now have track-layering down). Again, substantial plugins used (probably 15 comp and eq, or so - reverb routed to an effects buss).
This week, I had a project with only 14 tracks going on playback. Again, at the end, recording only track one at a time, with very little going on in the way of effects. Zero automation. At that point, I moved the entire project to another drive and I got the same problem. In the same place in the song. I was able to work around it by archiving some tracks.
It seems that the general consensus online is to manage system resources. I am pretty bare bones with that. The system is not online, and Power settings are optimized. Screen savers, hibernation, all shut down. I reloaded the RME driver and flashed the update. My last resort may be to change the FireWire PCI card as I apparently have an inferior one with a VIA chipset. RME all but recommends a TI chipset on their website.
I will probably punt the ASIO drivers for WMD, and ratchet up the latency, as I do no input monitoring, anyway.
I hope someone has a fix for this. Thanks.
