Hi
 
I have a Pod Studio UX2 interface and I recently took notice that in addition to working with Sonar when the DAW is running on my new Lenovo desktop PC, it also works as the PCs soundcard when the DAW software is not running.  IOW, it plays all MP3s, WAVs and internet content just as the PCs internal sound card would when not running Sonar.  My question is, is this supposed to work this way?  I never took notice to this when I was using my old music PC, but then again, I never tried to monitor anything else but the DAW software on my previous PC, so it might have worked that way on the old one but I never tried it.  I like it this way better and am also wondering if, as the UX2 doesn't have an On/Off button, would it cause any harm to just keep the UX2 hooked up to the PC and let it turn on/off with the PC, or would that cause trouble if I don't unplug the interface before shutting the PC down?
 
Thanks!
 
John B.

I play everything through my interface. No problem that i know of

Many music interfaces will attempt to play soundcard and do all those associated sounds, from 8-bit MS warnings to strange video formats.  Many times it is fine, other times the multitude of formats will confuse your interface.  It is made for maximum throughput of high quality sound in one format, while your internal soundcard is designed to handle all kinds of audio at relatively low bandwidth.
 
If it works for you, fine - it does for most people I think.  If not, it is relatively easy to switch back and use your soundcard for windows etc. sounds.
 
@

The major problem is ASIO.
 
its recommended that you use your devices ASIO driver but Windows can't use ASIO drivers. So it changes to use MME or WDM. the problem occurs if Windows decides to hang onto the audio device and you can't use the one that Sonar's setup to use, which should be ASIO.
The other problem that often trips people up is that Windows only uses 16 bit audio @ 44.1 kHz and if set to play Window's sounds then the bitrate and sample rate may be even lower.
When you start up Sonar, it may not only get the driver from Windows it may get the bit depth and sample rate changed to other than 24 bit @ 44.1 (this is the recommended bit depth) and all sorts of inconsistencies start to occur, like a message that says that the sample rate is wrong.
 
Their are 2 schools of thought:
1. says to only use one device for everything, though this can mean the occasional problem with settings.
2. says to you use your quality audio device (in your case the UX2) for Sonar and use your on-board sound card/device for Windows and other sounds. Kind of like a decoy.
My experiences is that the second choice is preferable.

I've never had a problem using the same device for the DAW and as a general Windows sound card in the last 25 years. Though I always switch off everything in the Windows 'sound scheme' because a computer that goes "ping, whee, pand, da-da" all the time I'm typing or doing pretty much anything irritates me a great deal.

So the sound output is either DAW, music/video playback or maybe games.

I also switch off the motherboard sound-chip in BIOS because I've found having multiple audio devices present confuses Windows (and Sonar) far more than acting as sole audio device confuses a decent interface.

I really like it because everything can come through my JBL monitors which are plugged into the outputs of the UX2.  The PC speaker output is only a single mini plug.  If it ever does start acting up I'll just go back to my old method of DAW only through the interface.  But just to play it safe, I disabled the internal sound card.  Maybe I should try tlw's suggestion of turning it off at the BIOS too.  If nothing else, it should free up more (much needed) CPU cycles.
 
Thanks all for your input!
 
JB

I use onboard sound for Windows, all DAW goes to audio interface.  I learned that is the best way to do that years ago.  My EWX2496, AP 2496 would crash when I used it for gaming.