Does that make it more important than everything else?... Drum maps has been fixed but the UI still sucks balls... Take lanes still has bugs and UI functionality isn't optimal. Problems with midi are getting resolved but there are still a few outstanding issues. Controller functionity has some really annoyong bugs. There are various workflow and UI issues. It looks like Cakewalk is finally tackling all this and taking it seriously.

If you read the pdf's there is a lot of work being done monthly. On Roland's watch the response was pathetic. Sonar X3 was a big improvement but then died on X3E. Platinum is taking all the awards as we see progress monthly.

Notation will have it's day. We are just getting started.

Also with notation at least there are third party alternatives to plug the hole. The above would be very difficult (well impossible) to plug with third party apps unless you hook in another DAW.

vintagevibe
Some long time users have left because Cakewalk ignored their requests.

And some never bought it in the first place because, for example, Ableton Live or Logic suited their needs better. So what? The reason why there are many different DAWs is because they have different priorities and serve different audiences. If Cakewalk wants to stay in business, and I believe they do, then they should prioritize providing what the greatest percentage of their core audience wants. That is exactly what they are doing, with decisions based on surveys of their users (whose statistical validity is far greater than anecdotal evidence on a forum that represents a single-digit percentage of the active user base).
 
To say that Cakewalk ignores the requests of notation fans is inaccurate. To say that they haven't implemented the requests of notation fans would be accurate.
 

vintagevibe
You don't know the history.  People have been asking for 20 years.  It's not on any Cakewalk to do list.

 
As to history, this isn't the same company that it was 20 years ago, let alone prior to September 2013...although since you seem confident about stating what's not on Cakewalk's to do list, maybe you know something I don't know. I haven't seen any list myself. The only list i see is the fixes being implemented, so I can include them in the eZine.

Anderton

vintagevibe
Some long time users have left because Cakewalk ignored their requests.

And some never bought it in the first place because, for example, Ableton Live or Logic suited their needs better. So what? The reason why there are many different DAWs is because they have different priorities and serve different audiences. If Cakewalk wants to stay in business, and I believe they do, then they should prioritize providing what the greatest percentage of their core audience wants. That is exactly what they are doing, with decisions based on surveys of their users (whose statistical validity is far greater than anecdotal evidence on a forum that represents a single-digit percentage of the active user base).
 
To say that Cakewalk ignores the requests of notation fans is inaccurate. To say that they haven't implemented the requests of notation fans would be accurate.
 

vintagevibe
You don't know the history.  People have been asking for 20 years.  It's not on any Cakewalk to do list.

 
 
As to history, this isn't the same company that it was 20 years ago, let alone prior to September 2013...although since you seem confident about stating what's not on Cakewalk's to do list, maybe you know something I don't know. I haven't seen any list myself. The only list i see is the fixes being implemented, so I can include them in the eZine.

You and Cakewalk employees have said it is not a priority.  Add that to the fact that it's never been addressed in all these years and I'm pretty confident with my statement.   

vintagevibe
 
You and Cakewalk employees have said it is not a priority.  Add that to the fact that it's never been addressed in all these years and I'm pretty confident with my statement.  

There were two staff view fixes in Dorchester, but they probably just fixed themselves. 

Anderton

vintagevibe
 
You and Cakewalk employees have said it is not a priority.  Add that to the fact that it's never been addressed in all these years and I'm pretty confident with my statement.  

There were two staff view fixes in Dorchester, but they probably just fixed themselves. 

They probably did fix them selves.  They were so tired of waiting.

vintagevibe
Some long time users have left because Cakewalk ignored their requests.

I can relate to that - I stayed on Sonar 4 for five years since my reports were ignored.
Then I got a new daw and needed x64 version and updated 8.5.
That's a lot of money Cakewalk has been loosing out on over the years having that approach - multiplying with every user with similar problems.
 
Something changed with X3 - and a boost in confidence and determination from Cakewalk.
So X3 update - but let it rest again for 15 months due to showstopper problems.
 
But now even more determination and my former showstopper gone - it's a joyride.
In Dorchester at least one from X3 days bug were fixed in Artist - another got even worse than before, but not showstopper, just annoying blobs covering gui(also from X3 days, new report filed CWBRN-32826 after Dorchester).
 
But this new approach monthly having quite a list of things attended to - every release.
Cakewalk are on it and improving how they attend to things reported.
After all, I saw that report number increase by a thousand each month or so - summing these up, see what is possibly same cause, sorting and evaluating it quite a task - then file on todo list.
 
And notation improvements are pretty high on my request list too.
Will experiment and see if music xml export works with different time signatures and how much fiddling before getting it right in external notation.

Actually I believe Cakewalk lost a number of users from not responding to Notation requests. Only really Jerry recently, but when it was imoplied that it was the same people asking and not a great range in on post a while back, I went through a stack of threads and listed all those that had been requested. The list is posted in one of the feature request with a link to the thread. I didn't just take those that posted, as some weren't posting to say it was important to them. I took just those who said they cared, many said it was important enough that they would move on. So many of the names from that list had stopped posting, so I'd say many havn't just stop posting, but moved on.
 
Then theres all those that read the threads and never posted but sat at their PCs nodding, so I think Cakewalk has lost business through not dealing with Notation or combined with that and other issues.
 
The question is, are they listening now regard this issue, and can they demonstrate it. As they have said it was something they took seriously many times and did nothing, I'll beleive it when I see it.
 
 

Hey can we get back on topic? There's another huge thread for notation we don't need another :)

There are prolly a number of requests that seem like they are being ignored, when in reality they are being set aside because the longer term plan we don't see indicates that they will be obsoleted.  IOW, effort expended now will be thrown out in the future.
 
The best example I have are the GUI bugs and inconsistencies that drove me nutz all the way thru 8.5.  I had been reporting them heavily in S7 and continued to do so in S8.  I was pretty miffed at the gall to ignore these glaring errors.  Guess what?  One more release and they all went away ...
 
I learned a long time ago that when something somebody else does seems beyond reason, it's prolly NOT because they are unreasonable.  It's more likely there are things included in their line of reasoning that I'm not aware of.  In these cases it's best to ask questions rather than criticize.  That's NOT to say you'll necessarily get answers