Anderton
lfm
forkol
Problem that I have here is that it seems so far that the features and requests forums hasn't really seem to drive any of the most recent feature development. In an idea 'membership' model, what I'd like to see is that top-voted features get some amount of priority development time. Actually, Cakewalk development seems to go in the completely opposite direction - IIRC, I don't remember many people requesting drum replacer or Vocal Sync. I'm not saying they were not wanted by somebody, they just don't seem like features that people were clamoring for.
You've got a point there.
First thing I saw this year that is of any interest to me, is start page improvements to get organized.
But there's a big difference between saying new features aren't of personal interest to you, compared to saying that Cakewalk development goes in the opposite direction of what people want. This post delineates new features that were requested. Those features must have been important to some people, or the features wouldn't have been requested.
Thanks for commenting.
I did write that he had "a point" not that I entirely agreed.
If going forward is scanning and implementing feature requests - you could say that implementing and improving stuff you never saw mentioned even, is going sideways.
So not going backwards or opposite - is not what I meant.
More important is that CWBRN's backlog are treated and fixed - nothing comes before that.
If you look at the list of bug fixes that occurred between X3 and SONAR 2015, as well as the list of fixes in each release, I think you'll see that making fixes has indeed been a priority. So that's another instance of Cakewalk making changes based on the desires of many segments of the community (i.e., those who place more importance on stability than features).
Incredible list of fixes and improvements we saw so far this year - thousands of manhours saved in not having to deal with those bugs anymore.
And I don't consider listening to feedback of bugs the same thing as implementing feature requests.
And I don't consider fixing something just broken as implementing feature requests either.
But you've got a point that stability fixes aren't always obvious - since things working are just as they should be.
I have a CWBRN from january, of things that were an issue in X3e. That moved to "awaiting reply" whatever that means. I put fresh update now that this still not working in Artist Everett and will see what happends. Some plugins loaded inside Metaplugin does not initialize to host sample rate in Sonar. It works in Cubase, StudioOne, Reaper, Mixcraft.
Another CWBRN that also is ignored since X3 early makes console view take up an extra inch in height of screen - the EQ plot does not entirely go away if I uncheck it, you get some blob covering other things in CV.
I tried to gain some extra screen space - but this is ignored in favour of things nobody asked for(in all honestly like forkol said, somebody sure did, but how many).
This is - just me - having to deal with these for me annoying issues.
CWBRN are incemented by a thousand each month - userbase trying to communicate back to Cakewalk things that they are bothered by, and maybe even stops the show for them.
This means that all these Cakewalk customers have each spent hours to troubleshoot these issues and report this - and too many are ignored. Think about it - one thousand users each month report stuff - maybe an hour each to troubleshoot enough to make a report. Many of these are surely double reports of different users having another approach to the same issue. I know the drill, ran my own software business for 16 years. But looking at them all as a whole usually point you towards where the problem is. A lot of wasted manhours in userbase this - so think about that when making priorities.
There were other threads about what forum members felt Cakewalk should focus on. One guy made a list of 5-6 topics, and this was the most quoted topic in that thread, having stability and fixes as top of list.
So again, just emphasizing this about fixes...I can understand the urge for devs to list new implemented features, but why not pick those asked/voted for first, rather than make up features?
I see good things about startup page, as I said, to get organized - but where do news list come from?
How many of us are really online with running Sonar?
I connect purely to check for updates with CCC and do installs - nothing else - for convenience.
I don't want any software like Adobe Flash, Acrobat or Windows updates check things over network while audio is running(some plugins with built in store also do network accesses as started). Attacks from outside to firewall that also may use cpu from time to time.
After updates/installs I reboot computer with router turned off - no network activity that can jeapardize audio.
That part about news on start page seems to me more be of Cakewalk interest spreading info about this and that.I may be out on a lim here - but just an assumption that many do like I do.
Maybe put news part in CCC instead - then surely your are online.
Just feedback from one user running sneak Artist version - but thinking of going to Pro if Cakewalk is going the way I go - forward not sideways.