Muted tracks - annoyance - new in 1.1 ??

I cant remember this being the case with 1.00b but I may be mistaken.

- Take a program that has some pads with a mute group set
- Program a pattern on a track
- Mute that track
- The track correctly doesnt play the pattern anymore.

However:

- Using the same pads, program a pattern on a new track
- The events in the new pattern on the new track that youve just programmed are muted by the events running on the first, muted track.

This behaviour makes no sense whatsoever to me.



Also, if you mute a track, I think you should still be able to hit the pads whilst on that track. You often might want to record a pattern on a track, quickly mute that track and try playing an alternative pattern. You cant do thi. Currently you have to go to an unmuted track to hear the pads.

This is a TRACK MUTE function.
It should mute all recorded events on the track.

That means it should also mute any 'mute' messages being sent out by pads recorded on the track.
It means it should NOT mute the pads themselves.

Forgive me if Im missing something here, Id be happy to find out I am....

47 views, and no replies?
I cant be the only one who uses mute groups on pads?

has nobody else seen this ?

seems to be a bug, but only if
mute/stop of oneshotsample is turned to immediate.(--> other --> misc )
if you turn it to "through" the mutes are muted correctly when muting the track.

thanks bro, ill try changing that option.

bloody annoying though.....