Track can't be unmuted

Randomly I have one track that is muted, no automation written in any sequence for it. I press to unmute it and it just stays muted unless I hit solo.... if I hit solo another track is muted in it's place. Any one come across this issue before?

Lampdog wrote:There are a few different menus that mute/unmute, they all don’t equal 1 global mute. You’ll have to find the menu that was muted in the first place. Check all mixers, submixes, track mutes, pad mutes, returns, list edit, even looking at bottom screen on some of them there’s a mute tab.

Flip side of that is something somewhere in the menus mentioned above in SOLO!?

I looked every where my guy! only thing worked was to solo every thing in the track mixer. which is odd. I found a few more things that got messed up in my project as well though, so in between pushing buttons I probably did something stupid without realizing it.

I'm not at home but if you locate and expand the velocity menu you will see the graph raise delete on lower and it will fix it. Sorry I'm on the road so I know what I am saying is confusing lol..

Certified Beatz wrote:I'm not at home but if you locate and expand the velocity menu you will see the graph raise delete on lower and it will fix it. Sorry I'm on the road so I know what I am saying is confusing lol..

I managed to fix my issue as mentioned above. I did look at the velocity section, there wasn't any mute tracks added to any of those in any sequence. I'm not sure what caused that weird issue. And again, it was such a strange thing because when one track was unmuted, another track became muted. So that's odd af.

I feel like this is one of those bugs that has persisted since the beginning. I fix it by going into the list editor and fixing it there. It's one of the first automation events on the first beat.
You'd think just deleting any mute automation would clear it but it doesn't always.
Some times it is a matter of the many mute states but I swear that is a real bug.
I'm.on OS 2.7

I think I hit this a few weeks back. I suspect it has something to do with solo/mute behavior. Like you, I had to solo/unsolo all my tracks to fix it. Until I did this, all the mute buttons were locked, but nothing was clearly flagged as solo.

It may be muted in another Screen. Like the Channel Mixing Screen. Is the whole Program muted? Or just the Track?

NearTao wrote:I think I hit this a few weeks back. I suspect it has something to do with solo/mute behavior. Like you, I had to solo/unsolo all my tracks to fix it. Until I did this, all the mute buttons were locked, but nothing was clearly flagged as solo.

I found the same problem. The solo being the issue a lot of times. It doesn't function like a normal solo should.

Definitely finding some weird bugs, but I'm also having a lot of fun. The more time I spend on the MPC one the more I appreciate certain features Reason has. I'll probably start splitting my time between the two.

I ran into this problem the first day I got my X. I ended up going in preferences and turning mute/solo events off.

Just by way of an update - I'm getting this on 2.10.1

Fix for this was to go into track mutes and simply mute and unmute the misbehaving track, then it came back to life.

Usually when I run into this nonsense, I have put a track on solo in some sequence, and then moved to another sequence and something glitches out I suppose.. Because it shows certain tracks as to be muted, but nothing says it is on solo.. And then it may or may not work if I go through all tracks and un/mute, un/solo..

And I know it's not an automation issue, those are much easier found out.

At worst I have to reload the project..