In Logic Pro X, "The document "(file name)" could not be saved"

Question

Level 1

8 points

In Logic Pro X, "The document "(file name)" could not be saved"

Today I am getting a new error when trying to save an existing project. I get a "document could not be saved" error message. Using Save As works, as long as I change the file name or save to a new location, but obviously I do not want to keep doing this. This is happening with any Logic project I open. Cannot save, only save as. I tried a "fix" I read about where I uncheck the Core Audio enabled check box, to no avail.

The only thing new to my workstation is that I am now storing and saving projects on a new external SSD. Is there some special way I need to format that SSD? Again, Logic will let me save to the SSD, but only by using save as and giving the file a new name or location on the drive.

Thanks in advance.

MacBook Pro 15", macOS 10.15

Posted on Apr 5, 2020 12:31 PM

Reply

Answer 1

Top-ranking reply

Wilddrums

Level 5

4,274 points

Apr 5, 2020 12:55 PM in response to dsaunier

Right-Click on the External Drive and select Show Info. This display the Format of the Drive. It should read MacOS Extended (Journaled) or APFS. Anything else may not works well.

What is exactly the location you're saving at? The complete path I mean.

WD

Reply

Answer 2

Apr 20, 2020 10:39 PM in response to dsaunier

Yes, I just started experienced this problem for the first time. I didn't think to try "save as," though that seems to be a last ditch workaround. I remounted the external HD and restarted logic and is seems to be working now, though it's still unsettling.

My external hard drive was not formatted to that—will do that now and hope the problem does not show up again.

Reply

Answer 3

Wilddrums

Level 5

4,274 points

Apr 20, 2020 11:27 PM in response to Markdavin

The issue is different disk formats do not have exactly the same requirements for fully qualified paths and file names. Usually an issue with some "invalid" characters in the name. This is a frequent problem in global setups dealing with many languages.

"Save" and "Save as" are very different commands. To keep things simple:

With "Save" the application tries to save with "Path/Filename" directly on the file system without that much validation. If something is wrong, the application just displays an error message.

With "Save as", the application calls an OS level interactive dialog and this makes it more difficult to select a wrong "Path/Filename" for the target file system.

Hope that shed some light on the issue.

WD

Reply