Cannot write file - disk may be full (but it isn't)

[profwacko]

I am getting this error message trying to save a small project I have been working on attempting to learn more about Audio Snap.

The first time I saved the project file after enabling AudioSnap on probably too many clips, the file size went from 1.1k MBs to 27k MBs.

After deleting the unused clips and moving on editing, deleting, and moving audio transient markers, the saved size ballooned to 87k MBs.

Now, after using the Audio Snap Palette to use transient markers to create splits in my project length (about 90 seconds) audio clips, I'm getting the Cannot save file - disk may be full error message after a 10-minute wait while app seemed to be busy trying to figure something out.

So, I have left the project open in my studio in hopes of being able to save the progress I have made, but am unable to save.

I did a search on the Cannot save... error text, but got no hits.

Anybody ever seen anything like this?

ADVthanksANCE

-Jack (needs saving in central Texas)

 

[profwacko]

Quick update: 

Just did a Google search on the Cannot write... text, and got hits from the CbB forum.

I'll go clear my picture cache and see what happens.

[profwacko]

No change after removing over half of the picture cache files.

Also, I've tried saving this file to 3 different drives, including my C-drive, and they all fail with the same message.

Hardware drive error not likely.

[Kurre]

Sometimes very long filenames together with long paths to the folder can be problematic.

[reginaldStjohn]

As can saving to a compressed folder or directory where you don't have full permissions.

[John Vere]

Did you try Save As? 

[profwacko]

Kurre: I tried reducing the length of the name of the project to no avail.

RSJ: I have been working on this project in the same folder in the same drive for several days now with no issues, until I started editing and manipulating audio transient markers. 

JV: I've tried them all - Save,  Save As, Save A Copy, etc.

Thanks for the suggestions, y'all, but I've decided to cut my losses and go back to a previous saved version  that had no Audio Snap data. That has worked so far...

But now I have a new problem that I'm starting a new thread for.

When I get a chance, I'm going to open the un-savable project and pursue that a little, in the hopes of helping someone else with the same issue.

-Jack (still working on it in Central Texas) 

 

[msmcleod]

Have you made sure that your project directories are excluded from any anti-virus and/or cloud-sync (e.g. OneDrive) software?

If other software is trying to scan the files as Sonar/CbB is trying to save them, this could cause this issue.

[profwacko]

MM: Wouldn't that sort of interference be fairly periodic, rather than continuous?

I banged on this file for quite sometime and found only that a failed saving attempt on a USB3 drive took 15 minutes, where similar action on my internal C drive only took 5 minutes.

When I get in to the studio today, I'm going to see if their are any minidumps to be found.

Really good question that I had not considered, however. Thanks for that.

 

[msmcleod]

2 hours ago, profwacko said:

MM: Wouldn't that sort of interference be fairly periodic, rather than continuous?

It really depends on the AV / Cloudsync app.  AV's in particular can jump in as every time a file is accessed.

You should have all of your project and any VST content (e.g. sample library) directories excluded.  Not doing this is definitely liable to slow down, but could also cause crashes.  Personally I've also excluded the VST plugin directories and Cakewalk application directories too, as I'm confident as to where the exe's/DLL's have come from.

For cloudsync, I use Mega rather than OneDrive and I have a batch file that copies my project files to a directory on another disk which is set to sync to the cloud.  The batch file does an incremental copy - i.e. it only copies newer / newly modified files.  This means that it only syncs when I want it to, and I've also effectively got another backup.  The downside of course is that I need twice the space for my projects.