jackballed Posted October 2, 2010 Share Posted October 2, 2010 I often get this message in the middle of working. I do not understand how and why it pops up, but it is extremely frustrating because I lose all the work I did since my last save and can do nothing about it. If anyone has a workaround to when this happens, or even a way to stop this, I'd appreciate it very much. Thanks. Quote Link to comment Share on other sites More sharing options...
paboblaustein Posted October 2, 2010 Share Posted October 2, 2010 Check your activity monitor...I get that error when Logic creeps towards it's 4GB limit in Virtual Memory. Even at 3.5 I start getting errors. Quote Link to comment Share on other sites More sharing options...
jackballed Posted October 2, 2010 Author Share Posted October 2, 2010 Check your activity monitor...I get that error when Logic creeps towards it's 4GB limit in Virtual Memory. Even at 3.5 I start getting errors. I've checked it a few times. My current project is at 1.93GB of virtual mem. If Logic did this constantly, I would definitely think I'm overloading the memory, but it's randomly every once in a while. Thanks. Quote Link to comment Share on other sites More sharing options...
slamthecrank Posted October 3, 2010 Share Posted October 3, 2010 Hmm. While I don't have an idea why this specifically happens to your machine - if you're looking for a "workaround", I would suggest that you get in the the good habit of hitting "save" every few minutes no matter what. It has saved my butt so many times I can't adequately explain... ps ... cmnd-s ... do it now! Quote Link to comment Share on other sites More sharing options...
ozinga Posted October 3, 2010 Share Posted October 3, 2010 Trashing undo history sometimes helps Oz Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted October 3, 2010 Share Posted October 3, 2010 Also check out this recent thread on the same topic: Can't save session [sOLVED] Quote Link to comment Share on other sites More sharing options...
untitled1100 Posted October 4, 2010 Share Posted October 4, 2010 i've been getting this with big projects too. disabling and reactivating the audio engine has also worked for me in the past. it's such a pain when that error happens.... but also i agree 100% with what slamthecrunk says, pressing cmd+s randomly every so often has also saved my arse on numerous occasions! Quote Link to comment Share on other sites More sharing options...
grooveroom Posted October 4, 2010 Share Posted October 4, 2010 Options > Song Information > "Reorganize Memory" ...works for me every time. Quote Link to comment Share on other sites More sharing options...
jackballed Posted October 6, 2010 Author Share Posted October 6, 2010 Hmm. While I don't have an idea why this specifically happens to your machine - if you're looking for a "workaround", I would suggest that you get in the the good habit of hitting "save" every few minutes no matter what. It has saved my butt so many times I can't adequately explain... ps ... cmnd-s ... do it now! I do "command-S" often and more. I usually do a ton of "Save As"es (plural?) hence the "v1.82" in my screen grab. This way I have something to go back to in case of a corrupt file, etc. Quote Link to comment Share on other sites More sharing options...
jackballed Posted October 6, 2010 Author Share Posted October 6, 2010 BTW, thanks to everyone for the workarounds. Quote Link to comment Share on other sites More sharing options...
kibu Posted June 6, 2012 Share Posted June 6, 2012 Options > Song Information > "Reorganize Memory" ...works for me every time. thanks grooveroom.... you are my angel ... ... Quote Link to comment Share on other sites More sharing options...
Zassimo Posted September 10, 2013 Share Posted September 10, 2013 Just happened to me on Logic Pro X! Tried to reorganize memory, delete undo history, save as a new file and it still happens. Pretty much buggered. Quote Link to comment Share on other sites More sharing options...
mikey10101 Posted June 9, 2020 Share Posted June 9, 2020 Hello there, Returning after a long sabbatical and setting up Logic X on a 2015 MBP. My last time through I was on Logic 5 through 8 for many years so I can navigate fairly well still. I followed this post, as well as a couple of others, to refresh myself. I've taken these steps: 1. Created an "alias" folder on the external T7 drive. 2. Brought the alias into the logic folder on my Mac after backing up then deleting the current folder. 3. I tested it. No issues so far there - I can open up and save things and the external drive and logic seem to be communicating just fine. 4. When I am actually in a project however, if I command S I get the dialog "The document (project name) could not be saved." 5. I tried two fixes suggested here - turn off the core audio and turn back on, and also the "consolidate" function. Neither have worked yet. 6. I also tried another suggestion to open the project, do a "save as" in the new folder and then reopen this and try there. I come up with the same issue. Thanks in advance for any help. I've used your forums from the search side of things many times and it's always a huge help. First time posting here since restarting though. Sincerely, Mike Quote Link to comment Share on other sites More sharing options...
Coolie Bwoy Posted July 20, 2021 Share Posted July 20, 2021 Ok so I started having this problem when I switched computers but carried files over from my external hard drive. Long story short... I copied files from my External Hard Drive to desktop then Unplugged my external hard drive where the source of the file originated from and now it saves fine, I did notice however, that when I plugged my hard drive back in it wouldn't save, started going on about permissions again. Hope this helps... Coolie Bwoy Quote Link to comment Share on other sites More sharing options...
ralof Posted October 17, 2021 Share Posted October 17, 2021 For me, the "Cannot Save" seem to happen each time Logic crash and I click the "Reopen" option. When I do that, a terminal window is opened and Logic is started (automatically) from there. It seems as Logic then set the files into read-only mode. Doing a "Save As..." under a new name and then do "Quit Logic" followed by a normal launch enable me to save again. Quote Link to comment Share on other sites More sharing options...
richyrich Posted April 12, 2022 Share Posted April 12, 2022 Does 'reorganise memory' still exist? Where is it? Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted April 12, 2022 Share Posted April 12, 2022 Does 'reorganise memory' still exist? No. I remember being told that "reorganize memory" was no longer necessary, and thus retired. Quote Link to comment Share on other sites More sharing options...
Dynamic_Notes Posted April 15, 2022 Share Posted April 15, 2022 Its still there, albeit buried. You have to assign a key command to "Project Information" Screenshot is of Logic Pro10.7.2 but I checked in 10.7.3 and its still there. Quote Link to comment Share on other sites More sharing options...
des99 Posted April 15, 2022 Share Posted April 15, 2022 This is true! Apparently, we both have memory for 34+ billion MIDI events..! (My free space numbers are exactly the same as your screenshot, which leads me to think this number is not particularly accurate or relevant any more). Quote Link to comment Share on other sites More sharing options...
Dynamic_Notes Posted April 15, 2022 Share Posted April 15, 2022 Hi des99, Did you use a new project to compare with mine? As you can see my shot was taken of a barebones new project. I'll compare the numbers with an existing project once Ive been in it a while. Whatever the case it begs the question - If its not needed anymore then why have they left it in? Quote Link to comment Share on other sites More sharing options...
NAVASA Posted February 10, 2023 Share Posted February 10, 2023 FOUND A FIX!! Go to File: Save A Copy As... Then save with an unique title (i.e Song Title-1) in the same folder as your original session. To make sure you're good, open the new file and your session should be intact with the latest version saved. You can then delete the corrupted file, and rename your copy file with the original name. DONE! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.