SONAR X3 Producer Installed In WINDOWS 10 Preveiw.

I have a copy of the Win 10 Beta, that I haven't installed yet, but intend to.  If I get a chance today, I'll install it and then install X3 and see what happens. 
 
But as this is relatively early in the Win 10 Beta timeline and not everything is included in the Beta version (and not everything is going to work or work properly and Win 10 will evolve/change), if it doesn't work I don't think developers, such as Cakewalk, would issue any Win 10 specific patches for a "working" program.

Hello again.
 
Fireberd:
Sounds really interesting, please keep me posted about the progress. 
 
A tip: make a copy of the file "avrt.dll" beforeyou reinstall the computer.
Its located in c:\windows\system32 folder.
It can save you from some "headache"... if you should receive the same problertm as i did
then its only to take the avrt.dll file, from the old installation, and replace the "new" one in Win 10.
 

 
//Stefan
 

Hello there...
 
cclary: Sorry to hear. But in your case im almost certain that it has to do with issue regarding the driver to your soundcard, or something. I did not experience anything like that. :(
But if you try to experiment with it, please feel free to post it hear.
Should be nice to se if you come to an solution.
 
For couriosity: Did you experience problems with the "avrt.dll" file as well? If so...did you make a copy of it before installing/upgrading to win 10, and replaced it? ( as i described earlier )
 
//Stefan

I put the Windows 10 beta on a stock laptop (no music production) simply because it was acting flaky with Windows 8.1.  It was either a reinstall of 8.1, or try the new OS. 
 
I really like Windows 10 beta so far.  Everything works fine on it, though that's just the typical stuff like browsers, Word, and a printer.  It felt like I was working with Windows 7 in friendliness and Windows 8 in performance, but again, nothing stressed the system like SONAR might.
 
All this is to say I am impressed with Windows 10 and look forward to the final release.

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

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.

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.

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

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.

(I posted yesterday and again it is not present)
 
I am not suggesting the CW dudes change any CW products. Testing CW products on every w10 build will result in feedback to MS about issues and concerns.
 
Is this not what beta testing is all about; Providing feedback about functionality, compatibility, and annoyances?
 
Waiting for the RTM version could be a disaster for CW, though I doubt MS will release something that does not properly support MIDI, etc.
 
updating to windows 8.1, from 8, can not be done if the OS is installed using a multiple license. And then the need to re-activate!  Both of these stupidities caused a few of my clients and me much wasted time. 
 
I learned some programs would not work with 8.1. One was QuickBooks 2007. Worked fine on w8. Not happening on 8.1. Yea, it was an "old" program, but it worked for the client. Same for some kids' games. Unhappy children.
 
 (Having trouble with the forum software while typing this. Will not scroll the box.)

CakeAlexS
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 ;)

Maybe they will skip X4 like Microsoft skipped 9, and go straight to X5

I finally got around to installing the Win 10 Beta.  Win 10 installed OK.  I installed Sonar X3 Producer 64 bit this morning.  It starts up OK, no errors.  I tried one of the sample projects and it loaded and ran without problems.

phineas malebati
hi guys I am using windows 7 + sonar X3 studio; my question is will it work with Windows 10 since one has to keep up with the times. please help.   

Maybe. You have 12 months to work this out I wouldn't rush, drivers are maybe the issue:
http://www.makeuseof.com/tag/computer-compatible-windows-10-can-upgrade/
 
Some people here reporting X3 works...
 

nitejamr@att.net
If Microsoft's pitch for Windows 10 they said that it was not Beta.  But from what I'm reading on here it seems that that was a lie.  I think I may wait for a while and see what kind of experiences people end up having with it as it relates to Sonar x3 and if the developers get the problems resolved. 

I can't see how it's a lie it's out of beta. If you are arguing it's unstable or not working where is the evidence on this thread?
There is no doubt third party driver and software may have problems but it's hardly Microsoft's fault.
I do agree it's best to wait, it's always the same with windows releases they do come with issues, after about 6 months it tends to stabilise.