To adopt a "No new features - just fixes please" strategy begs the question, what would the devs be doing for the other 9 months of the year?
 
A balanced mix please, of fixes, enhancements & new features, just like it's always been.

I personally would prefer a "no more 'content', only bug fixes and new features (in that order)" approach. I don't need 7000 useless guitar loops - I need 'pre-roll recording'. Virtually every other DAW has had it for years and it's a great time-saver and workflow (that's why all major DAWS chose to implement it).

I like new features and what-not.  You never know what can inspire a new song or idea.  Just my 2 cents.

I'd like to see new features, bug fixes, PLUS focused enhancements where every major feature, menu and dialog box is examined for usability, consistency in design and function, plus any inevitable fixes that might come from process of asking "is this working as intended".
 
Sonar's MIDI handling is pretty darn good, though I agree that Cubase has probably jumped ahead in that department a bit, but then you'd have to use Cubase . With the latest enhancements, like patch points, Sonar's audio is as good as any other DAW.
 
Regards,
Dan

I would hope that ACT and MIDI are on the list for improvement.  IMO, the bakers are doing a fantastic job.

irvin
I personally would prefer a "no more 'content', only bug fixes and new features (in that order)" approach. I don't need 7000 useless guitar loops - I need 'pre-roll recording'. Virtually every other DAW has had it for years and it's a great time-saver and workflow (that's why all major DAWS chose to implement it).

Content is done by third parties or people at Cakewalk who aren't involved in engineering, so it has zero impact on development.

Anderton

irvin
I personally would prefer a "no more 'content', only bug fixes and new features (in that order)" approach. I don't need 7000 useless guitar loops - I need 'pre-roll recording'. Virtually every other DAW has had it for years and it's a great time-saver and workflow (that's why all major DAWS chose to implement it).

Content is done by third parties or people at Cakewalk who aren't involved in engineering, so it has zero impact on development.

It does - because whatever resources are allocated to obtaining and providing this "content" (in the form of employee salary, outright purchase from third parties, etc.) could be allocated to engineering. Bug fixes and mainstream features ('mainstream' meaning features common to other major DAWs, like pre-roll recording) are far more useful than 'content' of dubious value.
 
Unless, of course, the "content" is so generic and useless, Cakewalk is paying pennies for it. 

irvin

Anderton

irvin
I personally would prefer a "no more 'content', only bug fixes and new features (in that order)" approach. I don't need 7000 useless guitar loops - I need 'pre-roll recording'. Virtually every other DAW has had it for years and it's a great time-saver and workflow (that's why all major DAWS chose to implement it).

Content is done by third parties or people at Cakewalk who aren't involved in engineering, so it has zero impact on development.

It does - because whatever resources are allocated to obtaining and providing this "content" (in the form of employee salary, outright purchase from third parties, etc.) could be allocated to engineering. Bug fixes and mainstream features ('mainstream' meaning features common to other major DAWs, like pre-roll recording) are far more useful than 'content' of dubious value.

In your opinion.
 
Others may disagree.

Bristol_Jonesey

irvin

Anderton

irvin
I personally would prefer a "no more 'content', only bug fixes and new features (in that order)" approach. I don't need 7000 useless guitar loops - I need 'pre-roll recording'. Virtually every other DAW has had it for years and it's a great time-saver and workflow (that's why all major DAWS chose to implement it).

Content is done by third parties or people at Cakewalk who aren't involved in engineering, so it has zero impact on development.

It does - because whatever resources are allocated to obtaining and providing this "content" (in the form of employee salary, outright purchase from third parties, etc.) could be allocated to engineering. Bug fixes and mainstream features ('mainstream' meaning features common to other major DAWs, like pre-roll recording) are far more useful than 'content' of dubious value.

In your opinion.
 
Others may disagree.

 
Of course! Different people have different priorities....lol... 

irvin

Anderton

irvin
I personally would prefer a "no more 'content', only bug fixes and new features (in that order)" approach. I don't need 7000 useless guitar loops - I need 'pre-roll recording'. Virtually every other DAW has had it for years and it's a great time-saver and workflow (that's why all major DAWS chose to implement it).

Content is done by third parties or people at Cakewalk who aren't involved in engineering, so it has zero impact on development.

It does - because whatever resources are allocated to obtaining and providing this "content" (in the form of employee salary, outright purchase from third parties, etc.) could be allocated to engineering. 

 
No, as I said before it has zero impact on development (well technically, it needs to be included in the installer so people can download it, but that's trivial).
 
Here's why. I create almost all of the content, and it's for projects that I do. As a result this content is created on my own time (weekends and evenings) for projects that have nothing to do with Cakewalk. I make them available to the community because of the positive comments in this forum from people who've tried content like the Hardgroove Steinberger virtual instrument, percussion loops, Monitorizer, VoxTools, Amp Sims, etc. Some people really like them, so why be selfish and keep them solely for myself?
 
Cakewalk does not pay me for the content I create. Third party content is obtained for free not because it's worthless, but because being included provides more visibility for the company. For example, the Boz ProChannel plug-ins brought his company attention that resulted in people checking out their other products. You can think of it as trading content for advertising; both the content and advertising have value.
 
Some of the non-SONAR-specific content I create, like the Gibson Bass Collection, is not included with the membership program but is sold through the Cakewalk store. I do not receive any money for that either, so Cakewalk keeps what they make, and those resources ARE available for engineering.
 
So now that I think about it, I stand corrected...my content creation can have a positive impact on engineering by allowing engineering to have more resources. Cakewalk recently hired two more engineers so it must be working