The Dreaded "Audio Disk May Be Full" error and USB?

Author
kevinwhitect
Max Output Level: -83 dBFS
  • Total Posts : 376
  • Joined: 2005/01/15 11:21:04
  • Status: offline
2017/05/12 13:36:07 (permalink)

The Dreaded "Audio Disk May Be Full" error and USB?

I shouldn't be getting it, but I am.

I redirected the audio folder, and picture cache folder to a 1T (empty) SSD ... connected via USB (2.0). All projects have the audio stored in the project file, and are also located in a separate folder on the SSD.

I bought a new Soundcraft UI24r. It also connects through USB via hub (2.0).

I'm forced to use hubs, as my high powered laptop (i7 quad and 8G ram) has only 2 USB 3.0 inputs ... and I've multiple devices needing to connect. 

Everything is reading right in Sonar ... I can see the signal come through the Soundcraft device fine. The trouble is when I roll the tape ... even on a single track. It rolls, but two - three seconds in? Up pops the error.

Does that error pop if there's bottlenecking occurring in the USB? Should that have any impact? Any other ideas why I might be seeing a problem when I roll the tape? Any suggestions that might help?

I've seen suggestion about deleting the picture cache and the audio.ini file ... but Sonar is pointing at literally empty folders.

I'm stumped. Any assistance is warmly appreciated.
 
 

All my music is free for download at:  

KevinWhiteMusic.com

The Rig:
i7 950 Processor
Gigabyte GA-X58A-UD3R V.2 Mobo
12G Corsair DDR3 RAM
OS Drive: Samsung 500G SSD
Program/Storage Drives: Samsung 500G SSD (x3)
Windows 10 Pro (Anniversary) x64
Layla 24/96 on ASIO Drivers
Sonar Platinum 

#1

3 Replies Related Threads

    JonD
    Max Output Level: -39 dBFS
    • Total Posts : 3617
    • Joined: 2003/12/09 11:09:10
    • Location: East of Santa Monica
    • Status: offline
    Re: The Dreaded "Audio Disk May Be Full" error and USB? 2017/05/12 16:37:22 (permalink)
    kevinwhitect

    I've seen suggestion about deleting the picture cache and the audio.ini file ... but Sonar is pointing at literally empty folders.

     
    First, just a general tip.  Make sure your USB hub is powered.
     
    Not sure what you're saying about empty folders.  Did you try the suggestions?
     
    This error is one of those gremlins that's been around forever, and often has nothing to do with disk space.  All you can do is try one of the suggested fixes until you find one that works.
     
    http://www.editthis.info/sonar/Sonar_Errors_and_Workarounds

    SonarPlat/CWbBL, Win 10 Pro, i7 2600K, Asus P8Z68 Deluxe, 16GB DDR3, Radeon HD5450, TC Electronic Impact Twin, Kawai MP11 Piano, Event ALP Monitors, Beyerdynamic DT770 Pro, Too Many Plugins, My lucky hat.
    #2
    kevinwhitect
    Max Output Level: -83 dBFS
    • Total Posts : 376
    • Joined: 2005/01/15 11:21:04
    • Status: offline
    Re: The Dreaded "Audio Disk May Be Full" error and USB? 2017/05/12 17:05:35 (permalink)
    Thanks Jon!

    Both hubs are powered, but one is a 2.0 and one is a 3.0 hub. What I'm going to try and do is swap some low demand inputs from the keyboards into the 2.0 unit and free up space for the higher demand SSD and UI24r into the 3.0 hub.

    I changed the folder settings in Sonar to point to the empty SSD in brand new (current empty) folder entitled (creatively) R://Cakewalk Projects/Audio and R;//Cakewalk Projects/Picture Cache. I've got Projects themselves being saved under R://Cakewalk Projects/Project Files.
     
    So when Sonar looks at the disk where EVERYTHING is being saved, it should see brand spanking new, empty folders. It shouldn't matter to delete the picture cache or the aud.ini file. There's nothing in the picture cache, and the .ini file is pointing the audio to an empty folder for storage.

    I did not up the cache size though ... which I will do.

    I did see that high CPU usage might be an issue, and I was running a live rig w/ Cantibile 3.0 running and powering several plug ins. I don't know if that's an issue or not because I didn't have time to experiment with things during last night's rehearsal ... which I'd hoped to record w/ the new Soundcraft piece using Sonar.

    I was so hopeful. I get the whole band miked up, routed through the mixer and registering in Sonar ... press the record button ... and ............ fail.

    I'll work on it in a bit ... but I was terribly disappointed when the error popped and I couldn't record.

    All my music is free for download at:  

    KevinWhiteMusic.com

    The Rig:
    i7 950 Processor
    Gigabyte GA-X58A-UD3R V.2 Mobo
    12G Corsair DDR3 RAM
    OS Drive: Samsung 500G SSD
    Program/Storage Drives: Samsung 500G SSD (x3)
    Windows 10 Pro (Anniversary) x64
    Layla 24/96 on ASIO Drivers
    Sonar Platinum 

    #3
    emwhy
    Max Output Level: -62 dBFS
    • Total Posts : 1402
    • Joined: 2006/01/03 15:09:02
    • Status: offline
    Re: The Dreaded "Audio Disk May Be Full" error and USB? 2017/05/13 13:17:52 (permalink)
    Kevin, out of frustration a few months back with a USB device I tried using a powered hub that was being shared with other devices rather than using a single USB port. It was like tying a boat anchor to my machine. I didn't get the error you're getting but rather a lot of clicks and pops and overall sluggish performance from audio apps that were using the device. It's really in your best interests to make sure your soundcard is not sharing USB bandwith with any other devices. I know that's not going to be easy given your system specs from above. Can you try just the soundcard on the USB 3.0 hub and put the SSD over on the 2.0 hub? It defeats the purpose but may give some insight on whether or not you just don't have the bandwith for those two devices on one hub. Most cases with laptops and certain desktops the USB processing is being handled on the chipset and not a physical USB hub which can really hog resources. Have you changed your PCs powerplan and disabled things like USB suspend settings? None of that may help but it's also worth looking into.
     
     
     
    post edited by emwhy - 2017/05/13 14:29:27
    #4
    Jump to:
    © 2024 APG vNext Commercial Version 5.1