bapu


I want more hours in the day.

And to pass Beagle in post count.

OK Seriously.... If X2 has working drum maps, true across the board color customization and folders in folders (and throw in a gapless engine) I'll take it over more modules/synths/jewlery.

+1

For me - its really simple..  I have gone the hardware route for video and audio gear for 30 years.  Not only does hardware change and outdate other hardware that it interfaced to,  obsolescence is the defacto reality of the millennia.  After 30 years, I'm good with it and have a pile of gear I haven't used in years and probably won't ever use, however its fun to look at and remember.  My 30 year old son just chuckles at me when I describe what a unit was, what it did, what it cost, and then how realtively short the time was between it being in the music room and it being in the basement...

I moved to software, knowing full well obsolescence is still the defacto reality, but with the hope that it is pretty simple to leave an old specification such as DX, VST etc,  in the code.  So far, Cakewalk has met this with each version. At times, given hardware changes (16 bit to 32 bit to 64 bit as an example), and developer tools have changed (you programmers very well know the difference between MS first C compiler distributed on floppy disks) - but we still have these old and useful audio software tools working to some degree in our current workstations because they thought through the miriad of issues old specs and new specs uncovered. 

Now my point - I go back from time to time to use some of the OLD audio software tools I bought back in the late 80's and early 90's.  In most cases, those old 8 and 16 bit tools are relative garbage to what has replaced them.   Even when I thought it would be cool to protect my older investments, my heart and my ears just can't stand to use them...  Thats me.   My hats off to all those who designed change, not for change sake, but because it gave us some seriously way cool tools we use today.

Best Regards,

L