jsg
.....
 I have no idea why CW refuses to prioritize the staff view for a while.  I cannot believe it is only an economic decision, I suspect some underlying ideology about notation must also play a part in the neglect.  Maybe the next update will change this, but it's hard not to give up hope given the amount of time these bugs have been around and ignored.
 
Jerry
www.jerrygerber.com
 

I believe the originator of that code left with the rights to that code a long time ago and that is the problem. What else could it be. Even if the code was undocumented someone could have documented it by now and polished it up. It worked better in pro audio 9.

Short of a God's-gift-to-programming, Linus Torvalds type celebrity figure, I can't imagine any programmer retaining exclusive rights to a work product done for a company, under contract or otherwise.  I think the problem is more one of dollars and cents; once the staff view was originally completed and worked well enough, the focus (and the userbase) shifted toward audio production and that's where the programming focus has stayed for years. And years.  
 
And years.
 
At least until the PRV got some love the past couple months.  Hats off to Cake for giving it some attention, for sure.  But my guess is that as the staff view code has aged, it has become a bigger and bigger project to overhaul it, and with staff view diehards such as myself making up such a small percentage of the userbase (and thus income), priorities go where the money is.  I don't fault Cakewalk for that, necessarily, as it makes good business sense and has obviously kept them afloat so far.
 
Doesn't make me want staff view fixes any less, though. :)

There is newsprint on the separation floating around the web.

jfcomposer
Short of a God's-gift-to-programming, Linus Torvalds type celebrity figure, I can't imagine any programmer retaining exclusive rights to a work product done for a company, under contract or otherwise.  I think the problem is more one of dollars and cents; once the staff view was originally completed and worked well enough, the focus (and the userbase) shifted toward audio production and that's where the programming focus has stayed for years. And years.  
 
And years.
 
At least until the PRV got some love the past couple months.  Hats off to Cake for giving it some attention, for sure.  But my guess is that as the staff view code has aged, it has become a bigger and bigger project to overhaul it, and with staff view diehards such as myself making up such a small percentage of the userbase (and thus income), priorities go where the money is.  I don't fault Cakewalk for that, necessarily, as it makes good business sense and has obviously kept them afloat so far.
 
Doesn't make me want staff view fixes any less, though. :)

If Sonar's staff view were on par with the rest of the program, I'd bet that Sonar would make inroads into the educational market, thereby increasing sales and revenue.   All colleges and conservatories that have music technology courses are going to be interested in a DAW that has an adequate notation editor.   
 
Jerry
www.jerrygerber.com
 

jsgAll colleges and conservatories that have music technology courses are going to be interested in a DAW that has an adequate notation editor.   
 
Jerry
www.jerrygerber.com

This.

Wasn't staff view sold off?  isn't it Overture now produced by Sonicscore??  https://sonicscores.com/
 
I was lucky recently to purchase Overture 5 in a fantastic deal... and wouldn't mind at all if  cakewalk collaborated with this company (if possible!!!)
 
 
 

Yes, Sonar's staff view was spun off into Overture and its little brother Scorewriter, which I have. Up through version 4, the core code was still the same. Even the dialog boxes for setting up midi devices and instruments were nearly identical to Sonar's. However, my understanding is that version 5 of Overture and Scorewriter are complete rewrites. I don't know whether this would have a positive or negative impact on the feasibility of a collaboration with Cakewalk and how the integration would be approached.

IMHO, Cakewalk should purchase StaffPad Ltd (2 employees as far as I know), both for their awesome app http://staffpad.net  and as an 'acquihire' to get them to work on Sonar's notation, Sonar's touch interface and more.
 

just out of interest this vid shows what overture 5 is now capable of....
 
 
https://www.youtube.com/watch?v=5_zy3xuwdYY

What's really odd and disappointing is that I've been in touch with several Cakewalk people and they all tell me that the staff view is going to get some attention and that there's energy at the company to do something about it. In late December 2016, I was told that things are moving forward and that finally, the notation editor is going to get an upgrade within a few updates. 
 
January, February, March, April and May have passed.  No upgrade, no fixing of the notation bugs, nothing, in fact the snap function is getting more dysfunctional.
 
For contrast,  I bought VSL's MIR convolution reverb last December and found a bug and reported it.  Within 2 days the bug was confirmed and another few days later they sent me a fix.   There's a company that cares about the quality of the software they produce and when they know about a bug, they fix it. 
 
Jerry
www.jerrygerber.com/mp3/Raga.mp3