Not Enough Storage Available to Complete This Command

Author
Post
Essentials Only Full Version
gbowling
Max Output Level: -84 dBFS
  • Total Posts : 315
  • Joined: 2009/02/25 20:36:32
  • Status: offline
2016/05/16 09:31:50 (permalink)

Not Enough Storage Available to Complete This Command

 
So I'm trying to freeze a track, guitar track with multiple FX on it, and I get this error. 
 
"An internal error occured while processing the mixdown. The operation was unsuccessful. Not enough storage is available to complete this operation."
 
This started when I turned on upsampling for the track.
 
I have 173G of free space on the drive sonar is installed on, and 152G of free space on my project drive. I also have 32G of RAM with  about 27G free. 
 
Is there some setting some where I need to tweak to give more mem to something? Or is this error message not entirely what's going on?
 
gabo
 
EDIT: In doing some testing this seems to be related to Izotope's Alloy 2 plugin. When I turn off upsampling for Alloy 2 I don't get this any more. Still interested why upsampling on Alloy 2 is a problem. 
 
EDIT 2: I seem to have fixed this by changing the setting "BounceBufSizeMsec" from the default of "0" to "100." I'm not sure what the optimum value for this is, but at least it's resolved my immediate problem.
post edited by gbowling - 2016/05/16 13:09:33

___________________________________
The Moderns
https://www.facebook.com/TheModerns.US
https://themoderns1.bandcamp.com/
#1

2 Replies Related Threads
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: Not Enough Storage Available to Complete This Command 2016/05/16 11:18:54 (permalink)
    100's probably fine, but maybe overkill. I've had mine at 20 for a long time just to eliminate issues with plugins that don't like fast bouncing at very low on-line buffer sizes like 1-2ms. 20ms is high enough to avoid that, but not so high that you encounter problems at the opposite end of the spectrum because the offline buffer is so much higher than any typical real-time setting the plugin was tested with.
     
    Incidentally, if you ever use 32-bit synths with Bitbridge, be aware that the rendered clip will have an extra buffer of silent audio added to the front end, making the clip play back audibly out of sync when bouncebufsizemsec is high. This is a Bitbridge issue; it doesn't happen with the third-party JBridge.

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #2
    gbowling
    Max Output Level: -84 dBFS
    • Total Posts : 315
    • Joined: 2009/02/25 20:36:32
    • Status: offline
    Re: Not Enough Storage Available to Complete This Command 2016/05/16 12:51:58 (permalink)
    Ah, thanks for that. I don't use bitbridge but it's something to keep in the back of my brain. I may actually set that back to "0" for now after finding out  how Alloy responds to upsampling. Not a plugin that upsamples well at all, created all sorts of weird artifacts.
     
    So I got curious and also tested Ozone 7 and Nectar as I also own both of those Izotope products. Turns out none of them respond well to upsampling!
     
    So, I'll keep upsampling off for any of the Izotope plugs that I have. 
     
    At one point someone suggested a list of things to use with upsampling, but I've not seen one. If anyone is keeping a list, scratch off Ozone 7, Alloy 2, and Nectar 2.
     
    gabo 

    ___________________________________
    The Moderns
    https://www.facebook.com/TheModerns.US
    https://themoderns1.bandcamp.com/
    #3
    Jump to:
    © 2025 APG vNext Commercial Version 5.1