Sir Les
So what is being said in full front...This software is not fully made, you see more needs to make more money...Moe cash in the cow, or cow in the cash....and you are stating it will be updated, as all things needs be, that are not fully functional or working as should be?...So you make the peoples pay forward?....why not get it completely right out of the box?...and make us pay full price...because things with computers as I know of in some forms....Things change, and so does gear....and to pay for something, get it, and then it is no longer supported by the system it is made for....is ok to pay for...but to say, this software is asking for payment for further upgrades and such, in stating it will do in time adding in new or fixes, makes my mind worry about upgrading if it is not working fully...and needs be fixing!...who pays us to R&D?...and the hair loss if it is buggy?
Every piece of music software in existence today has undergone updates to add new features over multiple revisions, and with
very few exceptions, you pay for major updates. Every piece of music software in existence today has also released bug fixes. So it would be accurate to say that no piece of music software in existence today was
ever released in a totally functional state, unless it works perfectly and is still on version 1.00.
The advantage of Cakewalk's approach is you get new features as soon as they're ready and it's easier to do QA that way. Also, this will allow something similar to the Quick Fixes that were done years ago...a great idea, but it was impractical because people were on all kinds of different versions. If you're a member, whatever software you are running is the latest and greatest version.