Error after bouncing project, .aad file?

I'm simply getting a very strange error when I want to bounce a project saying:
 
"The audio file "/Users/jelle/Library/Caches/Cleanup At Startup/minder en minder _v7.aad" cannot be read.
 
[This file does not appear to be a valid Audio Dump file.]"
 
('minder en minder _v7' being the name of the Live set.)
 
Had to realtime bounce it because of hardware processing but now I also tried to bounce it offline. Both methods completed the bounce 100% but gave the same error afterwards and no .wav file ended up on my harddrive. I can apparently render smaller parts of my project but when I just wanna bounce the whole (close to 5 minutes) song it gives the error above.
I am losing a lot of time on this project. Now normally I have enough technical knowledge to solve stuff but I just can't figure out why it doesn't want me to bounce this thing.
No problems bouncing other projects, never have before. Same fx, hardware, etc. on this track too.
 
Google told me nothing so trying it here. Has anyone encountered this error before?

15 followers

AcridAvid 1 year ago | 0 comments

12 answers

  • Willdo
    contribution
    1 answer
    2 votes received
    2 votes

    Hey, I had this same issue it was killing me! 

    Simple solution I found was to re-save the entire project in a new project folder with a new name. Then do a collect all and save. Quit, then reopen the new project and it should export fine. At least it did for me. 

    1 year ago | 0 comments
  • ubertone
    contribution
    1 answer
    2 votes received
    2 votes
    Hey elektrovolt (Jimi right? if so hit me up if you have any questions or need anything.;)
     
    So far I seem to be finally fee of this annoyance but have tried many things a.o.:
     
    Deselect generate analysis file on export.
    Wildo's suggestion to re-save the entire project in a new project folder with a new name. Then do a collect all and save. Quit, then reopen the new project. Worked for me, but only for a while, it seems it has to do with proper permissions (some folders would be marked as no access) thats why re-saving in a new project would fix it) so if working on OS X try verify/repair disk permissions / errors. 
     
    I finally used this app to fix permissions: http://www.lagentesoft.com/batchmod/ 
    on project folders + library and external sample libraries etc.. That also seemed to help but I never really have put my finger on what exactly was causing it, but it was always either folder permissions were messed up or Disk Utility detected disk errors that needed repair, which could also cause files not properly saving.  I also did a reset of Ableton: Delete the files "Preferences.cfg", "Template.als" and "Undo.cfg" just to be thorough.. can't say if that helped but it might help you find what's causing it.
     
    Be sure to backup your default template as a new project too before doing so...
     
    And this might not be related, but a reset could give insight. Do you have any M4L devices from the user base you use frequently or an outdated version of Kontakt? That certainly caused me crashes.. After removing some of these and after updating to 9.5 and Using DiskWarrior to scan for file errors and rebuild my HD which was frequently having errors, I havent had any issues so far. 
    11 months ago | 0 comments
  • weblogik
    contribution
    1 answer
    2 votes received
    2 votes

    I am also having this issue  :(

     

    8 months ago | 0 comments
  • [daw] Ableton staff
    contribution
    208 answers
    255 votes received
    1 vote

    Hi there, 

    This is a bug and currently under investigation. Please get in touch with our support staff, and make sure to include a status report from Live ( help -> get support ). 

    https://www.ableton.com/en/help/contact-support/

    Best, 

    David

    1 year ago | 0 comments
  • Quez
    contribution
    2 answers
    2 votes received
    1 vote

    I've also stumbled upon a similar error. It says that some .aad file (same name as project) in a "clean at startup" cache folder cannot be found, and exporting is not possible. However if I keep trying to export it ends up working..

    1 year ago | 0 comments
  • Heho3000
    contribution
    1 answer
    1 vote received
    1 vote

    I am receiving the same error message over and over. Export isn't possible. Thanks for any advice!

    1 year ago | 0 comments
  • elektrovolt
    contribution
    2 answers
    2 votes received
    1 vote

    same problem, was exporting stems one by one, and suddenly this error appeared. tried saving and collect all and save, but that did not help.

    11 months ago | 0 comments
  • ersatz007
    contribution
    1 answer
    1 vote received
    1 vote

    Has this issue been addressed by Ableton??   I just started having this error.  For me copying the project, collecting and saving, seemed to work.  But seems like a pretty weird bug.  I've tried repairing permissions, repairing disk, restarting, etc...clearing the cache from Live Preferences 'files' pane.  None of this works.  This is really frustrating and time consuming. 

    8 months ago | 0 comments
  • aprilfools
    contribution
    1 answer
    1 vote received
    1 vote

    Hey guys!

    I had same issue.

    Still have when i use Ableton's "external instrument" on the channel were i'm running micro brute and if i try to bounce - gives me this particular error...

    So i just disable it and it works.. :)

     

    6 months ago | 0 comments
  • mangiedog
    contribution
    1 answer
    1 vote received
    1 vote

    None of this has worked for me, Ableton said it was a bug and being looked at a year ago... well done with that...

    27 days ago | 0 comments
  • dj-nh
    contribution
    1 answer
    1 vote received
    1 vote

    Cozway. This didnt work for me.

    Gui crashes when i try to play track after been saved before any error accured - I made sure everything worked before save.

    Now when i try to play track it crashes have removed after a vst scan to see wich vst did this turns out db blue glitch did it.

    removed this but still wont work - Dont know what to do here... 

    24 days ago | 0 comments
  • Cozway
    contribution
    1 answer
    0 votes received
    0 votes

    SOLVED!

    RESCAN ALL YOUR VSTS, if one makes the program crash while scanning, delete it from your VST folder and odds are you'll be good again!

    5 months ago | 0 comments

You need to be logged in, have a Live license, and have a username set in your account to be able to answer questions.

Answers is a new product and we'd like to hear your wishes, problems or ideas.