This was driving me mad until I finally found the problem, once again I believe it's related to Take Lanes.
I was recording a new midi track & could not hear it on playback. I then expanded the take lane & it was somehow muted. Shouldn't be, it's a new & previously unrecorded track.

It wouldn't un-mute using the mute button, only the solo button would do it. I then deleted that take/ lane & then all would work normally. 


I have no idea what's causing this.
Is this a known bug/ anyone else having this happen?


thanks

Did it only happen the one time? I had kind of the opposite thing happen. Previous takes I had muted would all of a sudden unmute themselves once I started recording using the R key on keyboard. If I muted the actual clips it wouldn't do it or if I used my mouse to click the record button in the transport module.

Just quirkiness. It only happened a couple times. 

Thanks Beepster,

It's happened several times since X2a was released but I can't pinpoint the problem.  All tracks & projects are derived from the same template using the same
vst/i's.

It does sound like your problems are similar to mine.
If it's a bug fine but I'd like to know what the cause is so I can steer clear of it in the future.



-c

Well I find that just trying different ways of executing things end up solving my issues or making use of features that aren't necessarily meant for the specific task I'm trying to perform keeps me moving. Like using mute clip instead of the mute buttons or using the transport module to start recording in my example above. That's one of the nice things about Sonar is there are so many different ways to do things if I run into a bug or broken feature I can usually find another path to accomplish what I want.

Good luck.

Sounds like a bug to me but I haven't done too much midi recording with x2a so I haven't experienced that issue.  I did experience the forced "overwrite" mode when recording audio on an existing take lane even though record mode is set to "blend". I thought that was a bug too but found that its a "feature".  Your issue sounds like a true bug.