lfm
History so far has shown very little, if anything at all, of what is top voted on Features & Ideas forum is ever implemented.
So why have lifetime updates of something that is never going to implement things that you want down the line.
Please remember the multitude of forum requests along the lines of "I don't want new features, I want stability, I want faster operation, and I want fixes." Regardless, while Cakewalk has been taking care of those requests from people, they've also delivered many requested features:
- Softube Console 1 support - requested
- Upsampling - requested
- New themes - requested
- Theme editor - requested
- All of the future enhancements like plug-in load balancing, ripple editing, and comping enhancements - requested
- Update to TH3 - requested
- More track color choices - requested
- Melodyne tempo detection - not requested specifically, but the functionality was
- Smart Solo - requested functionality
- Speed improvements and optimizations - requested
- Patch points - requested
- Synth recording - requested
- Relative video path - requested
- Drum Replacer - requested
- Better mastering tools - requested
- Use same solo and muting on drum maps as instrument tracks - requested
- MIDI engine changes to avoid stuck notes - requested
- Customizable control bar - requested
- The many, many fixes that were based on user requests - requested
...as well as features like Mix Recall which may not have specifically been requested, but have ended up being very popular. So I think history has shown that Cakewalk listens to its users. However, I think it also shows that users give less credit when Cakewalk implements what is asked for by a majority of users in multiple places if it doesn't align with their personal priorities. That's just human nature.
Also, please remember that there was a backlog of fixes that needed to be made. IIRC the Features and Ideas forum is less than two years old. As just one example, it took over a year to do the Drum Replacer. I don't think Cakewalk introduced Features and Ideas as a way for people to benchmark "See?!? It's been several months and Cakewalk hasn't implemented what I asked for!!" but to collect and then prioritize ideas for future roadmaps, which are becoming more relevant now as backlogs of long-standing fixes and enhancements are being targeted and in the process of being dispatched.
People still harp on things like "Well
EVERYONE wants better notation!
Therefore Cakewalk isn't listening!" First, not
everyone (by a long shot) wants better notation, and the user surveys - which are statistically far more valid than cursory analysis of forum posts - bear that out. But second, and much more importantly, Cakewalk is
always open to solutions for better notation capabilities. Just because they haven't found something suitable
yet doesn't mean that they've stopped looking. Remember, it was said unequivocally in these forums that there would never be any fixes to staff view and that it was a dead issue to Cakewalk. Obviously the first was not true and I can tell you that the second one is not true either. But the company is going to wait until any staff view improvements can be done right, not cause the price to balloon, and cause minimal disruption to the rest of the program and its stability...which is not trivial. Maybe it's doable, maybe not. We'll see. Just because Cakewalk
wants to do something doesn't mean they're comfortable with promising, or even hinting, that they will or can.
If it's any consolation I'm pushing for improved notation handling so SONAR can earn its rightful place as the DAW of choice in educational institutions. But I don't say they're not listening to me. They're listening. They just haven't found the right solution. I understand.
So since I'm not signed up for life - my wallet is closed - screaming a statement of discontent.
If Cakewalk's priorities are not in alignment with yours, there are many other options. I say that not in the spirit of "if you don't like it, leave." The only reason I'm using SONAR was because the programs I'd used prior to it were not in alignment with my priorities. I didn't scream a "statement of discontent" in their forums, I switched to SONAR because it was the tool that matched my priorities most closely, and then got on with making music. There are still plenty of people using the programs I used, which is fine with me...and I'm sure with them
Finding the tool that matches my priorities most closely is MY responsibility. It is not Cakewalk's responsibility to create a tool that matches MY priorities. It is
their responsibility to strike a balance that will satisfy, and hopefully delight, the majority of SONAR users.
The day SONAR doesn't match my priorities more closely than something else, I'll switch
from SONAR as easily as I switched
to SONAR.
Life is too short not to do whatever it takes for you to be creative, so that you can exercise that creativity.