backwoods
:) Just so you know, it would be a hell of a lot quicker to just switch DAW.

No it's not.  All DAWs are different.

backwoods
I'd like to know the percentage of user base. 

 How about the percentage that left for another DAW? You can google that.

BobF
IMO, the anti-SV crowd is concerned that an intense amount of development pouring into SV would necessarily take away from development in other areas.  Of course this isn't necessarily true, depending on how Cake went about staffing* this [to date] fictitious Staff View initiative.

 
I agree the staff view initiative is fictitious. Little progress has been made for as long as I've been about (about a decade). What conclusions would a logical person draw from this? I'm asking the wrong people I think.  BTW I'm a pianist and have read notation since I was about 6 years old, I don't hate it. I just don't think every DAW has to be exactly the same.

Brando

backwoods
Buy something for what it is- not for something you desire it to be in the future. I hope you guys get what you want but maybe it's not that easy or they would have done it already. Or maybe not many people want it!

Nonsense. The whole premise of the membership model was that cake would roll out a mix of new features and fixes on a monthly basis. No one could have predicted that (for example) one of the features would be Drum Replacer. No one knows whether or what (if anything) Cake has in store for Notation. This is only about a user base trying to voice their opinion. 

 Most of them used Sonar since it had notation.  I started with Digital Orchestra which had nice notation in W98. I needed a new app because of XP.  I tried the watered down version of Cubase, didn't like it.  I started on Music Creator, Home Studio and then Sonar 2.  I used Sonar 2 and Gigastudio from then on and needed a score editor to see what I was doing.  Eventually I got use to not using a score editor but for complex stuff sometimes eyes work better than ears.
 I find notation programs far more annoying to work with when I don't need printed parts. It's more time consuming than using notation in a DAW.
 The complainers in this thread are not trolls but long time users who don't want to fork over another $400-500 for something like Cubase and also the time learning the app. I think those who never had to use this feature in Sonar don't know what it is like to walk in the others' shoes.  There two options, one is to deal with it or move on to something else.  I don't think this needs to be repeated. 

backwoods

BobF
IMO, the anti-SV crowd is concerned that an intense amount of development pouring into SV would necessarily take away from development in other areas.  Of course this isn't necessarily true, depending on how Cake went about staffing* this [to date] fictitious Staff View initiative.

 
I agree the staff view initiative is fictitious. Little progress has been made for as long as I've been about (about a decade). What conclusions would a logical person draw from this? I'm asking the wrong people I think.  BTW I'm a pianist and have read notation since I was about 6 years old, I don't hate it. I just don't think every DAW has to be exactly the same.

You're overlooking something critical. SONAR has Staff View NOW. Nobody is advocating adding something that isn't there. Most users are simply asking for all aspects of the tool to work correctly. To use Anni's windshield wiper analogy, the car came with them - they should work.
You seem to be advocating for (the equivalent of) the wipers being pulled off the car - if cake had no intention of ever letting its users use staff view, completely removing it from future versions would at least be a clear communication of their intention. As a user who paid for it I would be ticked off but at least I would understand cakewalk is "differentiating itself" from other daws that do have professional, usable staff/notation views.
Instead of advocating that users should switch daws, how about just avoiding discussions that advocate notation improvements in our daw of choice?

Brando

backwoods

BobF
IMO, the anti-SV crowd is concerned that an intense amount of development pouring into SV would necessarily take away from development in other areas.  Of course this isn't necessarily true, depending on how Cake went about staffing* this [to date] fictitious Staff View initiative.

 
I agree the staff view initiative is fictitious. Little progress has been made for as long as I've been about (about a decade). What conclusions would a logical person draw from this? I'm asking the wrong people I think.  BTW I'm a pianist and have read notation since I was about 6 years old, I don't hate it. I just don't think every DAW has to be exactly the same.

You're overlooking something critical. SONAR has Staff View NOW. Nobody is advocating adding something that isn't there. Most users are simply asking for all aspects of the tool to work correctly. To use Anni's windshield wiper analogy, the car came with them - they should work.
You seem to be advocating for (the equivalent of) the wipers being pulled off the car - if cake had no intention of ever letting its users use staff view, completely removing it from future versions would at least be a clear communication of their intention. As a user who paid for it I would be ticked off but at least I would understand cakewalk is "differentiating itself" from other daws that do have professional, usable staff/notation views.
Instead of advocating that users should switch daws, how about just avoiding discussions that advocate notation improvements in our daw of choice?

Actually, there are occasional requests for a full-blown notation system inside Sonar that is comparable to Sibelius or Notion.  This is the kind of "feature" I wouldn't want to see Cakewalk head toward.  Check out the Notion forum.  Imagine adding that load to what's already here for Sonar.
 
I do wish the SV bugs would get fixed ASAP though for the benefit of the SV users.  Maybe there's something bigger in the works that makes addressing onesy-twosy bugs not make sense ... who knows?
 
 

BobF

Brando

backwoods

BobF
IMO, the anti-SV crowd is concerned that an intense amount of development pouring into SV would necessarily take away from development in other areas.  Of course this isn't necessarily true, depending on how Cake went about staffing* this [to date] fictitious Staff View initiative.

I agree the staff view initiative is fictitious. Little progress has been made for as long as I've been about (about a decade). What conclusions would a logical person draw from this? I'm asking the wrong people I think.  BTW I'm a pianist and have read notation since I was about 6 years old, I don't hate it. I just don't think every DAW has to be exactly the same.

You're overlooking something critical. SONAR has Staff View NOW. Nobody is advocating adding something that isn't there. Most users are simply asking for all aspects of the tool to work correctly. To use Anni's windshield wiper analogy, the car came with them - they should work.
You seem to be advocating for (the equivalent of) the wipers being pulled off the car - if cake had no intention of ever letting its users use staff view, completely removing it from future versions would at least be a clear communication of their intention. As a user who paid for it I would be ticked off but at least I would understand cakewalk is "differentiating itself" from other daws that do have professional, usable staff/notation views.
Instead of advocating that users should switch daws, how about just avoiding discussions that advocate notation improvements in our daw of choice?

Actually, there are occasional requests for a full-blown notation system inside Sonar that is comparable to Sibelius or Notion.  This is the kind of "feature" I wouldn't want to see Cakewalk head toward.  Check out the Notion forum.  Imagine adding that load to what's already here for Sonar.
 
I do wish the SV bugs would get fixed ASAP though for the benefit of the SV users.  Maybe there's something bigger in the works that makes addressing onesy-twosy bugs not make sense ... who knows?
 
 

I own Notion. I personally like the direction Cubase and Digital Performer have taken for daw based notation.
However most users (me included) just want to see existing functionality work the way it was intended (or once did). Incidentally, with respect to "bloat" - I can load Notion as a rewire instrument and Sonar doesn't even breathe hard.

Fixes have been made to staff view since SONAR 2015 was introduced; there were few (if any) fixes for years before that. When SONAR 2015 was introduced some people projected the past into the future and concluded that no more fixes would ever be made to staff view and it was a dead issue.
 
If you now project the present into the future, it's reasonable to expect more fixes will be made. The main variable is the rate at which fixes will occur. 

 
 
Speaking in general terms as far as the Elitist type of attitudes go . 
This is just a casual observation and not an attack directed at any of you fine gents or ladies ….
After laying out some big pocket change for the hardware , the software , the sample libraries, plugs and what ever other kitchen sinks we need to throw in just to do our music in todays digital world .
Is it really an Elitist attitude for a person to say ,
" Hey , I know I don't have chops on every flipping instrument I have access to in SONAR . It would sure be nice to enlist a much better player (on some of these instruments ) and give them an accurate chart in staff view to see what they can come up with " 
folks, is that asking too much ? 
 
Kenny

Ok... finally got Duckbar to work with my Sonar X3... Thanks to Panu for his efforts - I finally have not icons to click on.... 
 
My question for notation view users is ......   
 
What are the bestchoice of keyboard shortcuts for SV....   I think would make sense for the Step record function to correspond so I assume I need number lock to be on?