Anderton

Doktor Avalanche
In fact with recent new functionality over the last 4 months I haven't seen anybody ask for what is being delivered.

There were requests in this forum for a Drum Replacer, Plug-In Upsampling, MIDI engine improvements, and Windows 10 compatibility. These all happened in the last four months. The Virtual Keyboard was five months ago, but people asked for that too. Also, several of the enhancements to Mix Recall, Drum Replacer, and VocalSync were in response to requests.

I didn't see a request for a drum replacer, was it huge with lots of votes? The plugin upsampler?... Well I saw your threads. Nobody asked for win10 certification, previous versions are probably win10 compatible, I do agree it win10 was a bloody good thing to do. I don't think any of these were in the top 10 or top 100. And none of these go anywhere near functionality that was present in X3E which is desperately in need. Forums are pretty silent about the other functionality (dare I say it again) probably because most of us have given up.

Now don't get me wrong, the enhancements were good and impressive. I'm not slagging it off. I'm just talking about main priorities, issues that seemed to have lasted forever. Day to day workflow. I remember when the survey came out several months ago there was a few long discussion threads as a by product, and it seemed pretty clear what people needed.

I think Platinum got off to a good start but I feel that long outstanding issues have been sidelined a little recently. Still this audio routing stuff is something to look forward to. At least CCC got sorted as well.

The new start screen described in the video looks useful to me.  I was wondering how it will handle the fact that I turn off internet access when using Sonar to avoid pops and clicks.  How will it know there are updates?  Also, I hope there won't be an annoying delay while it looks for the internet connection. 
Based on recent history with CW programming these issues are probably "handled with aplomb".
 
Cheers

RD9
The new start screen described in the video looks useful to me.  I was wondering how it will handle the fact that I turn off internet access when using Sonar to avoid pops and clicks.  How will it know there are updates?  Also, I hope there won't be an annoying delay while it looks for the internet connection. 
Based on recent history with CW programming these issues are probably "handled with aplomb".
 
Cheers

Yeah I thought that, one hopes it will be tested offline. Of course the news feed won't know anything unless you are on the internet. Hope they sorted it so it's a seperate background process much like the plugin scanner and that it terminates quickly.

Doktor Avalanche
I'm just talking about main priorities, issues that seemed to have lasted forever. Day to day workflow. I remember when the survey came out several months ago there was a few long discussion threads as a by product, and it seemed pretty clear what people needed.

 
Exactly. If you seriously try to utilize features like Take lanes, clip automation, PRV controller pane etc. you'll know how unreliable they are. Staff view also seems to have a number of issues, judging from the recent threads (I don't use SV except for TAB, so I'm not sure).  

Doktor Avalanche
Actually as a developer myself I don't see these enhancements being terribly difficult at all. Drum maps esp. Actually a new drum maps UI would be perfect for newbie developer.

I mean not only drum maps UI form, but a massive improvement for all Drum Map chain: track view, map editor, midi routing, drum pane, drawing tools, etc.

Agree. At least drum maps signal flow works now, and saving them in project isn't an issue (thx Cakewalk), but for me making the UI a pleasure setting up drums would be a start (rather than a nightmare). The drum map UI just stinks. I see that as relatively simple to give it it's own docking tab, redesign it and take it out of preferences.

I am hoping these new audio enhancements coming soon isn't going to kill drum map signal path again either... We shall see.. I think it's inevitable there will be problems when it is released, and Cakewalk will patch it up a few weeks later (fine by me as I won't install it until most are satisfied here).

Can't believe they've worked on this instead of implementing "John T Mode". They ought to be boiled in oil.

If John T Mode involves gin I agree..

Doktor Avalanche
I didn't see a request for a drum replacer

 
As soon as it was announced that a drum replacer was forthcoming, the forum was filled with people who inquired about when it would be available because they wanted it. AFAIC that qualifies as requests. For many production styles Drum Replacers are a very big deal.
 

The plugin upsampler?... Well I saw your threads.

 
People won't ask for something if they don't know it exists. As soon as I mentioned the improvements at 96 kHz, someone suggested upsampling during render. Others confirmed that upsampling made a difference, and what Noel did was WAY better than the workarounds I proposed. I can't imagine someone putting in a nebulous feature request for "improved audio quality" but once given an indication of how that could be done, they wanted it. (Frankly, I was skeptical that is was worth the development time because not everything benefits from upsampling. However, after doing final renders on all the songs for my next album, I have to say the cumulative difference is significant and I'm glad the feature has been included.)
 

Nobody asked for win10 certification, previous versions are probably win10 compatible, I do agree it win10 was a bloody good thing to do. I don't think any of these were in the top 10 or top 100.

 
Several threads were started as soon as the preview version was announced, and people wondered about Windows 10 compatibility. I'm pretty sure both Windows 10 compatibility and the Drum Replacer would place in the Top 10, or at least the Top 20, of desirable enhancements.
 

I'm just talking about main priorities, issues that seemed to have lasted forever. Day to day workflow. I remember when the survey came out several months ago there was a few long discussion threads as a by product, and it seemed pretty clear what people needed.

 
Don't think I consider issues like ACT's problems, remaining comping issues, etc. unimportant. It's vital that these be addressed. It's great that some of the deal-breaker Staff View issues were fixed but of course, it won't make any difference to anyone who doesn't use Staff View, and anyone who doesn't use Drum Maps will wonder why you mention it constantly. Obviously Drum Maps are important to you and other people, but is it more important that Staff View? Fixing ACT? Take Lane clean-up (granted, there have already been improvements to that but more could be done)?
 
There are some people who don't want new features - just fixes. I understand that. There are other people who no matter how many bug fixes you do, want new features and I understand that as well. Look at the threads about how Cubase has some whizbang MIDI chord feature...I bet the people posting those threads would rather have SONAR incorporate a whizbang MIDI chord feature than a new Drum Map UI. OTOH I doubt you care about having a whizbang MIDI chord feature.
 
Personally, I want to see a "drum machine mode" in the Piano Roll View where previous notes are still visible and accessible for editing while doing overdubs. We all have certain things we want, but the one thing I can guarantee you is that there will always be tradeoffs between what the community wants, what they think they want, what they don't know they want, and the available company resources. How well Cakewalk navigates multiple conflicting priorities to satisfy the greatest number of users will determine the company's success.
 

Indeed. I'm pretty sure that the last thing I want is development solely guided by forum requests.