disk not full - Recording terminated

[fork-media]

Ran into this a few weeks ago, of course the night of the playout. ( 90 ish min tele feature )

ended up consolidating on that one. a couple of days later there were notes/ QC fixes and I was able to punch in the corrections.. ( settins all the same?! )

last week was fine on another 90 min show, but have a delivery tomorrow on on this film I'm getting the same message

I'm going to have to do the consolidate again on tonights playout... but its a pain in the posterior - I like my drives tidy hahha

there's at least 120 gig on the drive. destrcutive punch has 90 mins ( not relevant tho? )

I trashed prefs and got an extra 2 mins of recording time..


recording 5.1 mix dx mu sfx M+E and stereo folds of the same

destructive record gets the job done no messing!

last time files were 740 MB when it resisted, today 540 MB go figure!

any thoughts?

[Darryl Ramm]

What make/model drive are you recording to?
What filesystem is on the drive?
What is the largest size of the audio files that result from the recording? -- you sure it was 740/540 MB etc.? Can you remeasure that using the UNIX/command line du utility. i.e.

$ du -m filename

Some disagreement in size there can happen.

Anything interesting in the Pro Tools log files ~/Library/Logs/Avid/Pro_Tools* showing up around the time the recording stops?

So destructive record does not stop like this? Or what?

[fork-media]

recording to the internal mac disk documents folder - session is on external USB so allocated to the SSD system drive..

tried your command - just got 'no such file or directory' admit I'm no Unix warrior tho..

its an APFS partition - its the Apple internal SSD

[fork-media]

trashed prefs again, cleared a bit more space ( now 190 gig form 130 gig ) did a restart and its working ...

( spoke too soon 5 mins later and........... )

[Darryl Ramm]

Originally Posted by fork-media

recording to the internal mac disk documents folder - session is on external USB so allocated to the SSD system drive..

This makes no coherent sense. If you are recording to the internal SSD (great) why is there a "session on an external USB". Huh?... and what is the exact drive make and model and filesystem for every attached USB drive? what happens when you disconnect all external drives, including any USB thumb drives, SD Cards, etc.

In terminal...

$ mount
$ cd [directory containing session audio files]
$ ls -l *
$ du -m *

($ is the shell prompt, you don't type it, replace [...] with the actual path)
copy and paste all the output of that terminal session here.

how *exactly* are you determining the size of these audio files so far?

[JFreak]

Documents folder is mirrored to iCloud so if you have that activated your internet upload speed eventually kills the recording.

[Darryl Ramm]

Originally Posted by JFreak

Documents folder is mirrored to iCloud so if you have that activated your internet upload speed eventually kills the recording.

Hopefully icloud crap is turned off... but is it???

[fork-media]

Originally Posted by Darryl Ramm

This makes no coherent sense. If you are recording to the internal SSD (great) why is there a "session on an external USB".

I run the sessions on some external seagates, I use the disk allocatiion to record my output set to a different drive.. ( the internal SSD )

I can see the file size in finderx

Documents folder not going to icloud,

[Darryl Ramm]

Are you absolutely sure no media file is going to those other drives?

What filesystems are they?

Can you move the session fully to the internal drive, physically remove the external drives and test.

I suspect your problem is tied up in all the complexity of multiple drives.

Disk space reported by du may help, vs. what the finder guesses file sizes are, they are reporting different things.

[fork-media]

testing will have to wait as I have to deliver updates to VFX today, there maybe an other ouput tomorrow if VFX are late again.

I've already hit the inconvenience, ie truncated files which need to be consolidated for delivery....

For the record, all recordigns are going to the allocated folder, I do at least one movie a month sometimes 3 so solely using my puny internal 500GB isnt going to be an efficient workflow.... but its convenient to put the outputs into a different location to the audio file folder...

I'm wondering if its a permissions problem.. but then I get worried when I see computer may be unresponsive for several hours if I try fix the disk.....

Should also mention, this exact same session successfully output the full duration of the movie 2 or 3 days ago....