EDIT: I apologize to all for talking about notation in this thread, but my comment
is peripherally related to the original poster's question.
Anderton
One notation advocate in this forum (sorry, I forget who) wanted to make a constructive comment that would actually help the Bakers, so he put together a list of the 5 bugs which, if fixed, would make people who use notation with Sonar a whole lot happier. I passed that along to the product manager with a recommendation to implement.
This was the point where I gave up reading the "No Notation Fixes!" thread. It was a sensible, well-considered post. The five points looked to me (not a notation guy) as if they would provide partial notation satisfaction to the majority of those who really wanted improvements, while remaining limited enough to be achievable from a programming standpoint. But the thread rolls on, still with no one happy. The five points were torn apart, added to, and ignored in hundreds of more comments.
My takeaway was that there is no consensus within the group demanding notation fixes, even on something like
the definition of notation fixes, and not much willingness to "settle" for some initial steps in the right direction, which
could lead to a more robust staff view. Add to that the commenters who predict that nothing will ever happen based on what they perceive as 20 years of stonewalling by Cakewalk, and it just looks like a roiling cauldron of bitterness and anger, sort of a support group for people to share the ways in which they already know they are not going to get what they want.
I'm sure there are thoughtful users who could use a better staff view, and I hope they get it, one way or another. But I respectfully suggest they all use their time making music whatever way they can, and send constructive criticism and requests directly to Cakewalk through the channel that is set up for that.
Meantime, if that thread got locked it would be OK with me