Hey, thanks for the insight, if this is your job and something your passonate about then I'll agree, I guess I'm just not as worried about if anything should change because it all seems good to me the way it is. Or at least as good as it's ever going to be. They will make a more powerful computer, then Mirco soft will find a way to bring it to it's knees again. 
Looking like it's going to snow,,, better get outside and put my patio furniture away :) 

Karyn I'd be surprised if the dev team starts doing any serious work with Win10 until at least the first release candidate when things start to get a little more set in stone.  Up until that point anything can change at the drop of a hat.

Hi, Karyn.  That surely is the case with current technology cycles.  However, I am certain that the Bakers are working with Win10 as I type this post...wait, what time is it in Boston.  After all, Cakewalk (TT) has always been cutting edge.  If you recall, or maybe it was before your time, SONAR was the first 64bit processing DAW software available.  At that time, 64bit processing in Windows was just released.  So, obviously the Bakers were at the cutting boards with rollers in hand long before 64bit Windows was approaching gold, [much less on the shells or in webcarts - ancillary remark].  (Please don't confuse programs like Windows Server and such already having 64bit capability which was not intended for consumer consumption.)  Since Windows 10 is slated for release sometime in 2015, that's just over a month away (not that is going to be available on January 1, the Bakers are not going to be sitting on there loins until Win10 is in its final stages.  The Win10 foundation is already complete, it's all about building and tweaking from there.  I'm confident to say the Bakers are on it.
 
Kind regards,
 
Living Room Rocker

As release is likely to be 10 months away (Sept 2015) and there is only a preview build I suspect developers have far more pressing issues (like X4), and by the time is gets released X5 might be just around the corner...

Or they are going to release X4 in Sept 2015 when the new OS comes out ;)

I didn't get around to installing Win 10 yesterday.  Too much going on and may not get around to it for some time.  But, when I do I'll report back.

Karyn
I'd be surprised if the dev team starts doing any serious work with Win10 until at least the first release candidate when things start to get a little more set in stone.  Up until that point anything can change at the drop of a hat.

That's exactly right...
Once Win10 hits RTM status, that's when it makes sense to address outstanding issues.
Prior to that, it's chasing a moving target...
 
FWIW, I see Win10 somewhat as Microsoft's answer to the ever "evolving" OSX.
It's not a huge change from one version to the next... but rather incremental evolution (improvement/enhancement).
In some ways, I think that makes good sense.  It allows innovation... but things can more easily be reined-in and coarse-corrected (if not well received).  The OS is more easily "adapted" to circumstances...

Given that the CW managers have a history of working with the MS dudes, I think the CW offices have multiple machines running every version of windows CW products are/will-be supported on.
 
I doubt the CW guys want to wait until RTM to learn something is way wrong with Windows. And the same for MS.
 
Any Windows GUI changes will influence how CW products are designed. Best to be working on these bits instead of just anticipating all will be OK.
 
Fur Shur any intelligent hardware group should already be testing drivers on the every new build of W 10.

I'm positive the Cakewalk staff do checkout Beta OS releases.
 
Cakewalk isn't a giant company.
They have to be mindful of how they "spend" resources.
It doesn't make sense to focus on fixing issues (bugs) with an early Beta OS release... when those fixes might break other things... and with the next Beta OS release... those fixes may (again) be broken.
It's chasing your tail...
 
 
 
 

Jim RoseberryFWIW, I see Win10 somewhat as Microsoft's answer to the ever "evolving" OSX.

Hi, Jim.  Actually that was what Win8 was supposed to be with the Metro interface, correct?

Jim Roseberry
It's not a huge change from one version to the next... but rather incremental evolution (improvement/enhancement).
In some ways, I think that makes good sense.  It allows innovation... but things can more easily be reined-in and coarse-corrected (if not well received).  The OS is more easily "adapted" to circumstances...

Exactly, so Win10 has that foundation.  The functionality isn't going to change dramatically for the majority of end users, just some feature enhancements.  And if there are any audio enhancements, I am sure it would be minimal if at all.  Further, if and when Cakewalk releases the next version of SONAR I wouldn't expect it to be Win10 ready.  Neither do I expect the Win10 version (of SONAR) ported to run on a WinPhone (taking advantage of the "universal" OS platform).  No one is expecting SONAR to be controlled by voice via Cortana.  As it is, Win10 seems to be targeted for business applications.  So it is likely that the Bakers already have plans in the works for the Win10 compatible version of SONAR (if not an update to the next version release).  It has been obvious that the Bakers are working on a number of fronts as we've seen in the X3 release.  Quickly after the initial release, the Bakers already had two updates the first of which was included in the X3 download and the second readily available at the time of release (or rapidly soon after).  Since Cakewalk, like any other software company, is always looking for ways to improve and/or enhance their products, it's understandable that there are features planned for the next release and other features that are set aside for the release following thereafter.  So it is quite possible there is an overlap of R&D going on while production is moving.  Isn't that the likely scenario?
 
Kind regards,
 
Living Room Rocker

Living Room Rocker

Jim RoseberryFWIW, I see Win10 somewhat as Microsoft's answer to the ever "evolving" OSX.

Hi, Jim.  Actually that was what Win8 was supposed to be with the Metro interface, correct?

Jim Roseberry
  So it is quite possible there is an overlap of R&D going on while production is moving.  Isn't that the likely scenario?

Win8 was a step in that direction.  
Win10 is a pretty quick follow-up.
Less "comprehensive" (change wise) than previous new versions of Windows.
 
Agreed about Cakewalk development being tested on numerous fronts (including Beta OS).
I think you're also correct in that official Win10 compatibility would likely be added via a follow-up patch.
It just makes good business sense.  Once Win10 is solidified, then you know what you're dealing with... and bugs can be squashed.  Prior to that, it's a guessing game.  Fixes may be broken with new Beta releases... and new bugs created (from the release and previous "fixes").  It's a slippery slope... where lots of time/resources could be potentially wasted.
 
johnnyV has a pretty common-sense point above.
If you need to be productive, why rush to throw a "monkey-wrench" (Beta OS) into the equation?
All is currently working pretty well with X3e and Win7/Win8.
 
It's cool to checkout new technology... but life on the "Bleeding Edge" can be a PITA.  
 

YouDontHasToCallMeJohnson
Given that the CW managers have a history of working with the MS dudes, I think the CW offices have multiple machines running every version of windows CW products are/will-be supported on.
 
I doubt the CW guys want to wait until RTM to learn something is way wrong with Windows. And the same for MS.
 
Any Windows GUI changes will influence how CW products are designed. Best to be working on these bits instead of just anticipating all will be OK.
 
Fur Shur any intelligent hardware group should already be testing drivers on the every new build of W 10.

I know quite a few MS developers in Redmond who are not on the OS . One of them has just bought a Mac in fact to develop iphone apps. As somebody said earlier, targetting a moving target is a waste of effort esp with companies with limited resources.

I think some people don't really realise that it is a mamouth enough task just to develop and test multiple builds on one OS, there is just too much work to do.