Tak put a lot of effort into bug reporting during the X3 days, and all were done to this caliber of detail. It is disconcerting to me to see the longevity of reported/confirmed bugs and feature requests in comparison to what the monthly updates bring. I can only commiserate with the folks that have put forth the time and effort into these.

mettelus
I can only commiserate with the folks that have put forth the time and effort into these.

And we use to have an up-to-date list of most current bugs and their status.
It was a lot of work and we've unfortunately lost he who maintained it.
 

What would be most helpful is if a Cakewalk rep would acknowledge these things and give us some indication if their priority.
 
Normally I work alone with Sonar, so I may not be too put off by glitches.  Yesterday I had a vocal quartet and a composer in my studio.  Overall it went well, but there were 3 or 4 times when I got stuck on things that sure seemed like bugs.  I was under pressure to keep the project moving so I really didn't take the time to figure out the situation and record the pathology.  I just backed out and went at it from a different angle. 
 
Overall, reliability if excellent for me, but there are a lot of little nagging things that just aren't right.  Some that I remember:
 

1. I added 4 audio tracks and the input assignment was just not right at all.  I lost a good take because of that.  I ended up deleting all those tracks and creating each audio track by hand.  This might be too specific to a particular audio interface, but if the add multiple tracks cannot add anything useful, then it shouldn't be there.
2. I continue to have lots of cases where multiple clips are selected yet when I try to adjust the beginning or ending point of that group of clips (or apply a fade-in/out), only one clip responds.  I have to deselect all of them and select them again, then it works.
3. Aux tracks aren't automatically selected if I am right-click selecting a whole range of clips for exporting a mix.  If I don't manually Ctrl-click those aux tracks, they are left out of the mixdown.  I suppose that isn't technically a "bug" as the aux tracks don't have a "clip" that I touched when selecting the whole group, but it seems that if a person is right-button sweeping through a range of tracks, all tracks in that range should be selected, even if there are no clips.

There were 3 or 4 more, but they escape me now.  There are work-arounds for all of these, but I certainly agree with the sentiment of prioritizing these things that are so central to the use of the system.

cparmerlee
I continue to have lots of cases where multiple clips are selected yet when I try to adjust the beginning or ending point of that group of clips (or apply a fade-in/out), only one clip responds.  I have to deselect all of them and select them again, then it works.

I get this a lot too. Seems to be something that appeared with/during Platinum somewhere, because I don't recall having any such problems with X3.

When you encounter what seems to be a bug, it's important to find steps to reproduce it. I know it often takes time and efforts, but unless we can reproduce it, it's very unlikely to be fixed. Not all bugs are reproducible, of course. I have a few unreproducible ones myself, which I gave up and decided to forget (e.g. one of the views in MultiDock shrinks to the upper left corner of the pane after changing screensets, the width of the track pane at the right of PRV becomes much narrower to completely hide the track name fields at a certain point even though I made it wider, locked the screenset and saved the project).
 
The ones I posted in the OP are all reproducible and have been confirmed. I have more, but they are not as bad, so I didn't post them (e.g. Screenset doesn't remember the status X-ray, the "Fit MIDI Content" command doesn't work in Take lanes).

icontakt
... Screenset doesn't remember the status X-ray,...

That surely can only be because the dev left that parameter out by accident.