Muted track unmutes when I hit play with no automation written?

[jjboogie]

I imported a track for reference into a session and after muting it turns on by itself when I hit play! There is no automation written at all.

Weird! Anyone know what that might be?

[juhanni]

I have encountered this too. It happens when i have an instance of Kontakt 3 running with multiple midi-channels, but same audio output.

[jjboogie]

Bump

[albee1952]

Make it inactive. That only takes a second longer than hitting the mute button(and it won't over-ride you).

[jjboogie]

Originally Posted by albee1952

Make it inactive. That only takes a second longer than hitting the mute button(and it won't over-ride you).

That's what I have been doing in the mean time. Just wondering if there was a setting or something that I accidently engaged that makes the muted tracks unmute on there own when I hit play.

Thanks

[nigel smith]

I'm having the same problem on 8.0.4 LE with a DIG002.
If you hit play first, then click mute, it works.
Otherwise it's as you describe.
I am working with a session from v6.4.1 and 3 of the 7 tracks have this problem. Other tracks mute with no problem.
is it a bug, or is there a setting I'm missing?

[albee1952]

Usually, its because of "accidental" automation. If you view MUTE automation on the track, you can see what the setting is and change it, or select the automation mode as OFF. I have seen it here and there, but its never been anything persistent on my system.

[Darryl Ramm]

Are you running on a legacy old 003 or similar? with Pro Tools 8LE? And now you are posting on a 13 year old thread.

Good you are looking at past threads, but can you follow the DUC rules and stop spamming posts onto multiple threads. Post once per problem and focus on describing the most basic stuff about your setup.

In this case you likely should just delete your posts and create a new thread and describe your setup. Esp. what exact version of Pro Tools you are running so other users here might want to spend time trying to see if they can see this behavior on their setup. If this is really just caused by display set to MIDI or clips... that has to be a bug or maybe corrupt session. Does this happen in multiple sessions? Have you trashed Prefs? tried to see if this happens when you start with a totally empty session?

[Darryl Ramm]

Duplicate of https://duc.avid.com/showthread.php?t=157508&page=2