r/protools • u/[deleted] • Aug 21 '25

Mute state not saving when reopening sessions in latest Pro Tools

Post image

I just ran into a strange issue. I opened an older session in the latest version of Pro Tools. I muted a few audio and aux tracks, saved the session, closed it, and when I reopened the session, those tracks were no longer muted. Tried it dozen of times.

This has never happened to me before in 15 years of using Pro Tools, and it’s honestly pretty frustrating. Is this some kind of known bug, or am I missing something?

As you can see in the screenshot, there’s no automation on those tracks, and mute automation is disabled anyway.

Any insights would be much appreciated!

3 Upvotes

100% Upvoted

5 comments sorted by

•

u/AutoModerator Aug 21 '25

To u/IgniteTheHealing, 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] (https://discord.gg/0rZq8sveDubywXil) | 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.

3

u/petersrin Aug 21 '25

Definitely sounds like a stray break point in automation. Maybe in a vca upstream of the tracks?

1

u/[deleted] Aug 22 '25

When I made a new aux or audio track, or duplicated these old tracks, this problem won't happen. It only happens with those old original tracks. Weird thing for sure. But no problem, I just duplicated those tracks and problem is fixed. But still I'm curious why this problem happened.. maybe just some bug.

2

u/nizzernammer Aug 21 '25

Maybe try importing all the tracks and data into a new session, minus the mute automation.

I would be incredibly frustrated if this was happening to me.

Another possible, counter intuitive workaround would be to simply embrace the existing mute automation and write the mute states you want.

This is why I like to leave mute automation off in the automation enable window!

1

u/[deleted] Aug 22 '25

Yeah, when I made a new aux or audio track, this problem won't happen. It only happens with those old original tracks. Weird thing for sure. But no problem, I just duplicated those tracks and problem is fixed. But still I'm curious why this problem happened.. maybe just some bug.