Hopefully more than a just a tease, Jonesey. If Sonar does improve staff view significantly, I would have to consider returning. If I can get used to Sonar that is not 8.5. Maybe the artist version would be slimmed down enough for my needs. 

I have looked at every DAW and will repeat the truth that all have strengths and weaknesses.  because of work reasons, i find myself using Studio One and Logic more, but even at work, i let everyone know i think Sonar is just as good and even better in some areas. I don't use Sonar as much at home, but plan to because i honestly mix more efficiently in it. 

Are there any stats as to how all these DAWs stack up per user base? Which one is the most widely used to the least used by world populace?
 
Limited area polls don't count because any one of them simply won't have enough respondents to be acurate.

I've never seen any such stats. But I'd could venture a guess that it's probably close to 50% Protools, 10%-15% Digital Performer, 10%-15% Logic, 10%-15% Cubase and everyone else fighting over whatever percent is left over.

Anderton
 
Well then, I guess all the conversations Cakewalk and I have had over the past few months with a developer who specializes in notation didn't occur. I have no idea when/if anything will come to fruition, but Cakewalk continues to seek a solution for the minority of SONAR users to whom notation is important.
 
The issue of improving notation is far from "dead in the water." However I do not think Cakewalk wants to apply band-aids to the existing notation, but find a solid, from-the-ground-up solution. 
 

I want to remember this quote the next time you say "Aww shucks, I'm just a regular user, just like the rest of you fellers". 

I met the developer at a trade show, and made introductions to Cakewalk. No different from what I've done with many companies over the years...and many companies remain open with me about their plans for the future.
 
I do ping them about notation, but so do regular users. And I've had about as much success in effecting change . I guess the only real difference is that Cakewalk told me about the antediluvian nature of the code so I understand why they think applying band-aids is fraught with peril, but IIRC they've said this in the forums as well.

I often define a range and then insert a series of controllers or pitch bend events.  This can seriously bog down the CPU because Sonar inserts too many events (e.g., 8-12 pitch events per tick at 120ppqn).  One 1/8 note bend can have 720 events, and if I am doing 3-4 tracks of steel guitar, that is 2,880 pitch events on one 1/8 note. I have to use the Thin Controller or Thin Wheel CAL command.
 
For me, a simple way to change the default number of events inserted per tick or per quarter would solve the problem.  If this were in Preferences or in an INI file, that would be great.

So each tick can have more than 1 event? I thought this was why we could adjust the number of ticks per quarter in the preferences. I think I have mine set to 240 instead of the usual 960.

ampfixer
So each tick can have more than 1 event? I thought this was why we could adjust the number of ticks per quarter in the preferences. I think I have mine set to 240 instead of the usual 960.

But wouldn't that reduce the midi 'resolution' of everything that you play in rather than just control data John?

konradh
I often define a range and then insert a series of controllers or pitch bend events.  This can seriously bog down the CPU because Sonar inserts too many events (e.g., 8-12 pitch events per tick at 120ppqn).  One 1/8 note bend can have 720 events, and if I am doing 3-4 tracks of steel guitar, that is 2,880 pitch events on one 1/8 note. I have to use the Thin Controller or Thin Wheel CAL command.
 
For me, a simple way to change the default number of events inserted per tick or per quarter would solve the problem.  If this were in Preferences or in an INI file, that would be great.

May be I do not understand something... but why you are not using Snap for that? When enabled and in PRV set let say to 1/64, CC/Wheel operations are using that quantization.