MacOS can't eject a drive with Pro Tools running

[simonchase]

When I try to eject a drive I get the error message:

The disk "Simon's Disk" couldn't be ejected because "Pro Tools" is using it.
Quit that application and try to eject the disk again.

But I have no session open. I'm sure Pro Tools fixed that some versions back. But it seems to have been back for a while. For me at least. Anyone else?

[Darryl Ramm]

Pro Tools version? macOS version? Filesystem type? Signature correct?... if so I'm close with running 2022.7 and other recent releases on 11.6 and 12.x on a similar era Intel MBP and have ~dozen APFS and exFat filesystems mounted and never have noticed this.

What is on this drive? Your home directory? (Yes you can't be unmounting your home directory but I'm wondering if there is anyhow that Pro Tools could be confused where your home directory is... and there are likely ways). If so… that may be working as designed, Pro Tools keeps a lot of state information in ~/Library/Avid.

Are samples used by VIs on that drive?

Otherwise I have not seen Pro Tools grabbing drives. If not a home directory how did Pro Tools interact with the drive? You opened or saved a session there? Did the session save really finish cleanly, etc. …

[JFreak]

Is it assigned something else than Transfer mode?

[Frank Kruse]

I get this from time to time regardless of PT version. Sometimes it's because PT is indexing the drive but more often it's not and even with no session open it won't release the drive and the only option is to quit PT, shrug and move on

[its2loud]

Same,

Been this way for me through multiple versions of PT and OS. There used to be a way to eject it from the workspace but that’s been gone for a while.

[simonchase]

Originally Posted by Darryl Ramm

Pro Tools version? macOS version? Filesystem type? Signature correct?

Yes signature correct.

Originally Posted by Darryl Ramm

What is on this drive? Your home directory? Are samples used by VIs on that drive? how did Pro Tools interact with the drive? You opened or saved a session there?

Video files is all that I reference there, not home directory or VIs or session files.

[simonchase]

Originally Posted by JFreak

Is it assigned something else than Transfer mode?

It's a record volume

[Farhoof]

This happens when a video file was at some point linked to the drive. You have to quit PT to unmount the drive, not just close the session.

This was indeed fixed for sessions and audio files, but not for video files.
I run video files on a dedicated (internal) drive because of this and never have this issue anymore.

[simonchase]

Originally Posted by Farhoof

This happens when a video file was at some point linked to the drive. You have to quit PT to unmount the drive, not just close the session.

This was indeed fixed for sessions and audio files, but not for video files.
I run video files on a dedicated (internal) drive because of this and never have this issue anymore.

That would explain it...

[Cryos]

Been having that too. Very odd. Happens with 2022.5 for sure .. Can't remember if it was happening with earlier iterations of 2022.xxx