ALERT! Possible driver conflict between Windows 7 and X2?

Alright! I have been using X2 in the studio the last two days and I have found this possible bug.
My windows driver for my computer is set to 48khz but I have been using 24 bit 44.1Khz settings in X2. If I just use save in X2 everything is fine. BUT, if I use save as, after the save is done X2 re-sets the audio driver to 48Khz! Is anyone else experiencing this? You can see my computer and card setup in my signature below. If I close the X2 down and re-open, it sets the driver back to the 44.1 setting. Anyone having this issue or suggestions?

Do you have the windows sounds set to "no sounds"?
If not, maybe windows was changing the sample rate every time it played a system sound. 

My computer gives the option to play at cd or dvd quality. I have the onboard card disabled because ASIO won't allow more than 1 card. The MOTU is a PCI card. It is the only card running. I found that for whatever reason with X2 You have to set X2 driver properties to directly match the interface settings. This was not a problem in any of the other versions of Sonar. My interface has 24 ins and 24 outs. I just set one pair for outputting the computer sounds. It's not that big of a deal. I just don't think that setting everything for 48K is really going to make much of a difference quality wise. If I were going to use 96 or 128K maybe the qaulity would be noticeable. I usually set everything at 48K. I just wanted to run X2 thru the ringer and when it came to mismatching the sample rates this problem came up. The fix is just to make sure that the interface settings and X2 settings are exactly the same. Otherwise, the Save As problem pops up. It maybe a MOTU driver problem, but just the same, X2 is a really fine upgrade.

bigboi


Sid...I have 2 motu 2408's, and 2 24i/o's.  I would love to hear if Win 8 improved your buffer settings or latency.  I have heard that it is a big improvement.

According to this post on the Motunation forums, the MOTU drivers in particular are not very efficient in Windows 8.  Also, a number of us have found that the current MOTU drivers often blue-screen at start up in Windows 8.
 
I did try Windows 8 for a few weeks and felt that I could get lower latency overall, but also found that some USB devices caused deferred proceedure calls in Windows 8 that were fine in Windows 7.  I rolled back to Windows 7 eventually, because I couldn't live with the MOTU driver problems in Windows 8.

Hi,guys. First, the latency is unbelievable on my machine. 8.5 and X1 both would usually be set at about 256 or 512 with loads of vstis and audio plugs. I don't use any outboard gear and haven't for a while. X2 is allowing me to get down in to the 64 and 128 range very easily. Even with the CEs on all channels. Some of the new plugs are very CPU hungry but I have had no crashes this far. Secondly, I may have mis-spoken when I said Windows driver. There is just the bug when you mis-match the output of the computer sound to play Cds or Dvds on the computers drive and the settings in X2. As I said, it only happens when you use Save As as opposed to Save. As soon as the save process is over the X2 sample rates jump to the settings for the output of the overall computer sounds. Not really a big deal, just something I happened to find. The fix is to make sure I set the computers audio out to 44.1 if I'm using 44.1 in X2. Or vice-versa, make sure the overall computer audio output is set to 48khz if I'm using 48K in X2. I just never had an issue before outputting my computer audio 48K while using 44.1 in older versions of Sonar. I don't use 44.1 anyway. I always use 48 once I got enough space to handle the extra size files. Some projects come to me in 44.1. That's why I was checking this setting out. I just have to remember not to use Save As when I'm working in 44.1 with the interface set to 48K. I hope that clarified the situation. I just wondered if anyone else had found that issue. Thanks for the interest in this.