AAE -9013 Memory Low error when mounting or ejecting drives

[faraway]

I'm running to AAE -9013 errors that prevent playback of sessions that seem to be triggered by mounting or dismounting drives on my system. I'm running PT 2024.3.1 on Ventura 13.6.6 on an Intel Mac with 96GB of ram and these sessions are nowhere near that ram limit. I have noticed this issue since 2023.12 on previous versions of Ventura also.



Only fix to get playback working again is to close and reopen the session which is a bit annoying.



Anybody else run into this issue?

[Darryl Ramm]

Mmm interesting. Never seen that behavior and I sure have connect USB thumb drives to sessions where the transport is stopped.

What type of drives are they and what is on these drives? Are they transfer or recording volumes etc. How soon does the error happen after mounting the drive.

Can you try with macOS Activity Monitor running and see what the reported free memory and other memory stats are. Is there a spike in any of these when you mount these drives? Does this happens with the transport stopped? How large is the disk cache (and roughly how full... from the cache meter).

[faraway]

Originally Posted by Darryl Ramm

Mmm interesting. Never seen that behavior and I sure have connect USB thumb drives to sessions where the transport is stopped.

What type of drives are they and what is on these drives? Are they transfer or recording volumes etc. How soon does the error happen after mounting the drive.

Can you try with macOS Activity Monitor running and see what the reported free memory and other memory stats are. Is there a spike in any of these when you mount these drives? Does this happens with the transport stopped? How large is the disk cache (and roughly how full... from the cache meter).

The drive is a NVME drive in an USB4 enclosure which is a clone of my internal work drive. It's set as a record drive in the workspace. Error happens when I stop play back and try to play again. Even if I un-mount the drive, I cannot play the session without having to close it and reopen it.



I think this is plugin related to the sessions I'm running because I cannot reproduce this problem with a blank session FWIW.


Here's a screenshot of PT with activity monitor open. There is no change in the RAM usage when the drive is plugged in.

[Darryl Ramm]

It was a good idea to test with an empty session. But maybe it's failing because of content not plugins, or maybe your session is corrupt. You could try running the session that does fail with Plugins disabled (hold down shift when opening the session in Pro Tools) or remove .aaxplugin files from the plugin folder. Or try Save Session Copy In and see if that helps if it was session corruption.

I've tried this running my own sessions, and running the Low Roar demo. I have 6 external Samsung PCIe/NVMe drives in two Thunderbolt 3 chassis, all marked as record volumes (although normally these drives are really not used for audio content or samples). They are all APFS volumes. I can mount and unmount them at will while sessions are playing back and stop and start the transport (all playback here for my test, but do you have to be recording for this problem?) and never see a problem. Pro Tools 2024.3 on macOS Sonoma 14.4.1 on an Intel MBP with 32GB.

And so, like you I suspect it's something specific to your setup/session etc. And yes, always suspect plugins.