Another interesting tidbit from the Cubase forum. There, as on this forum there is a debate raging between new features and bug fixes. Someone even started a poll. As of earlier this AM, I think the bug fixers were winning like 20:1.
http://www.steinberg.net/forums/viewtopic.php?f=226&t=88945
Here it seems like closer to 50/50 with the new feature contingent possibly slightly in the lead.
I really don't think that monthly vs. quarterly updates is the issue here. Both regimes could be made to work and release less buggy code. 
I think Craig hit the nail on the head. Releasing increasingly buggy products is the new corporate paradigm. Companies cannot afford the diligence required to release near perfect code.

I run nVidia exclusively and have never had an issue.  The "secret sauce" that Mr. Anderton mentioned is a very real thing though.  Make sure when you install your nVidia driver, you do the following three things at the minimum. 
 
1) Only do a custom install.  NEVER select Express.  
2) Make sure "do a clean driver install" is selected.  (It's on the bottom of the newest installer...this removes ALL traces of the old driver in the registry and in Windows.  THIS WILL REQUIRE a reboot when complete. (Even if it forgets to prompt you)
3) During that custom install, UNCHECK HD Audio drivers (while you are at it, uncheck the 3d Vision driver as well, unless you have the 3d Gaming Glasses...this driver is useless without those glasses and puts extra resources on the machine that aren't needed).

microapp
 
I think Craig hit the nail on the head. Releasing increasingly buggy products is the new corporate paradigm. Companies cannot afford the diligence required to release near perfect code.

I don't think that is what he was saying. I think you have misquoted him. 

KPerry
And I'll ask again: what defines a "stability release"?  Unless *all* bugs are eliminated in it, it'll still generate heat.

1) Enhancement and new feature freeze.
2) Regression bugs tackled (that's with new functionality only, ie platinum features).
3) If time fix trivial legacy bugs that are unlikely to threaten the stability of the release.

Pretty standard practice stuff.

And it's iterative as well, meaning if the release brings up new bugs, they get fixed straight away until the release is deemed stable.

Further info about Regression testing...
https://en.m.wikipedia.org/wiki/Regression_testing

John

microapp
 
I think Craig hit the nail on the head. Releasing increasingly buggy products is the new corporate paradigm. Companies cannot afford the diligence required to release near perfect code.

I don't think that is what he was saying. I think you have misquoted him. 

I don't think so. I just put it in a very terse way.
The whole attitude here is that some bugs are unavoidable. This is true. The number of bugs is inversely proportional to time spent testing to find those bugs. Cakewalk (and other companies) cannot rely on existing users for necessary revenue and must rely on new users to buy product. TIme spent on new features detracts from time spent on debugging. As time goes on, the market becomes more saturated, it gets harder to attract new users. As the product develops, it becomes more difficult to add new features. This takes more time away from testing. Over time the number of bugs increases.
Originally, the non-subscription subscription model was touted as a way to produce more features with less bugs. Is this true ? I  am not sure. Hard to quantify bu it seems about the same really. But what has happened is that I increasingly read 'It is easy to roll back, the bug that killed your  workflow will be fixed in a later release'. This to me, means that complacency in regards to quality is on the rise. I think we as users and Cake as a company must be careful about this attitude.
Whether Cake does a formal monthly release model or not is irrelevant to me. They could just as well release updates in an ad hoc manner. Any method that works for Cake, works for me as long as things are fixed and Cake survives.
This is not an indictment, it is simply recognizing the result of the complexities of the modern market evolution. Do I like it, not especially. Can I do anything about it? No.
 

I have been updating every two or three months.  No problems so far.  None.
 

Someone seems to forget that EVERYONE with a MS OS has different hardwar,e software,and maybe even OS versions. Not to mention many configurations and settings on the way. There is NO WAY for ANY company to test every possible combination. To say it's the fault of the company is just asinine...or juvenile. You can pick...
 
Better yet, please list all bug free programs you know of.....

charlyg
Someone seems to forget that EVERYONE with a MS OS has different hardwar,e software,and maybe even OS versions. Not to mention many configurations and settings on the way. There is NO WAY for ANY company to test every possible combination. To say it's the fault of the company is just asinine...or juvenile. You can pick...
 
Better yet, please list all bug free programs you know of.....

If you are referring to my post, you missed the jist of what I said.
There will always be bugs, their frequency will likely increase. It is the result of market forces. Just because bugs are inevitable do not become complacent. Deal with bugs in whatever way you see fit as long as you deal with them.

 Mine is an economical decision.  Something that has impressed me more is the communication between developers and the end user that use to be almost nonexistent.

I do not think anyone can argue that the monthly payment option does not allow more people to use Sonar. If the monthly payment option normalizes their cash flow that is good too.