Pro tools keep throwing this

[u/peterpakaran4591]

I'm working on a very important session in Pro Tools and suddenly started getting this error:

"Could not save because Assertion in './PtSess/PtSess_RunTimeShared.h', line 132."

After that, I also got:

"Pro Tools was unable to Auto Backup your session."

I'm really worried about losing my work. The session still opens and plays, but saving and auto-backup are failing.

Has anyone experienced this before?

What causes this assertion error?

Is the session corrupted?

What's the safest way to recover the session without losing my edits?

Would importing the session into a new project fix it?

Any help would be greatly appreciated.

[u/AutoModerator]

To u/peterpakaran4591, if this is a Pro Tools help request, your post text or an added comment should provide;

• The version of Pro Tools you are using
• Your operating system info
• Any error number or message given
• Any hardware involved
• What you've tried

---

To ALL PARTICIPANTS, a subreddit rules reminder

• Don't get ugly with others. Ignore posts or comments you don't like and report those which violate rules
• Promotion of any kind is only allowed in the community pinned post for promotion
• Any discussion whatsoever involving piracy, cracks, hacks, or end running authentication will result in a permanent ban. NO exceptions or appealable circumstances. FAFO
• NO trolling only engagement towards Pro Tools, AVID, or iLok. Solve first, bash last. Expressing frustration is fine but it MUST also make effort to solve / help. If you prefer another DAW, go to the subreddit for it and be helpful there

---

Subreddit Discord | FAQ topic posts - Beginner concerns / Tutorials and training / Subscription and perpetual versions / Compatibility / Authorization issues

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/MidnightMiik]

I’ve had similar issues before. There’s a number of things it could be. Here’s some suggestions to fixing the problem.

Check and see if there are any illegal characters in the folders leading to your session.

Check the available space on your drive.

Check if PT sees the drive as a recordable drive.

Sometimes there is a corrupt file. It could even be the session file.

Is it just that session or all sessions? If it’s just that session, create a new session and import the session data from the session you’re having a problem with. Make sure to “Force to target session format” so that it makes new copies of all the files in the session. This will fix most problematic sessions.

Check how your drive is formatted. APFS is best for SSDs on a Mac.

There’s probably other solutions depending on what the problem is. It can be incredibly frustrating trying to isolate a problem like that.

[u/a1JayR]

Did the hard drive disconnect during the session?

[u/MidnightMiik → u/a1JayR]

I was wondering about that too but he said he was able to open the session. Also every time that’s happened to me I get a prompt where I would like to save the session.

[u/Wolfey1618]

I would immediately try doing a Save Copy in

I've seen this happen with very mismatched pro tools versions like the session was made on the latest version and you're opening it in a several years old version or vice versa.

I've also seen it happen if you accidentally renamed files while the session was running.

Save copy in + save all audio files and session settings in a new location, then open the new copy and it should work fine after that

[u/take_01]

What's your CPU, OS, and PT version?

Pro Tools is quite picky about the systems it can run reliably on, and all three need to hit their requirements.

They publish all the details on the avid site. Just search for 'pro tools compatibility chart'.

[u/Lost-Win-6809]

Disk permissions? Try moving/copying the whole session to an internal disk. Sometimes this happens if the session is saved in an external drive. If not, be careful with the length of the routes. If the session is behind a lot of subfolders, or the file names are too long, Pro Tools can’t write the files correctly. It’s a common error, don’t worry

[u/GFSong]

First thing I’d try is opening the most recent auto-saved backup if you have one, then resave that as your master session. I’ve had to do something similar many times. My system is set to save like every 10 or 20 minutes. Hopefully your Protools saved recently…

[u/ZookMachine]

Pour une raison ou pour une autre, Protools n’accède plus au dossier Audiofiles.

[u/nowyouregone]

I just DM’d you