Two issues have shown their heads almost simultaneously/
 
1.   My US-122 Audio Interface in not recognized when I try using it in the WDM mode.  The following error message is presented:   
 
but
 
2.  I am getting feedback with latency through my headphones.  
 
The issues mysteriously showed themselves with  nothing that I recall doing in the settings to create them.   Prior operations were faultless.  
 
Any ideas as to what's happening? 

Would recommend stay with Asio drivers.
Don't know about the feedback/latency, if you have this on all projects or just 1..
Under Preferences,Audio,Driver Settings you can see your latency below in the screen.
If you have a Total Roundtrip of + 20ms or so, then increase sample rate maybe and lower buffer size.
Feedback/Latency might also be in the 'input echo' function (button) not set correctly, or tack inputs/outputs.
 
anyway, good luck..
 

Stick with ASIO driver, make sure they are up to date and you have the latest audio interface firmware.
 
In the case of feedback with latency, do you mean perhaps phasing or echoing?

Are you monitoring via the audio software that might come with the interface, and then have echo buttons turned on in Sonar? If so turn one of them off.
 
Cheers...

cpkoch
 

The current Drivers either do not support the audio format or are in use by another application

 

This could be due to the internal sound chip not supporting the project settings. To use WDM, make sure the TASCAM is the only interface selected in Preferences > Audio > Devices.

Why do members prefer ASIO drivers? I hear this on almost every audio device thread yet I know not why.
 
Each case is different. Not all drivers are written with tender care but the notion that WDM drivers are to be avoided is something one needs to explain at least to me. 

John
Why do members prefer ASIO drivers? I hear this on almost every audio device thread yet I know not why.
 
Each case is different. Not all drivers are written with tender care but the notion that WDM drivers are to be avoided is something one needs to explain at least to me. 

I think this is a pretty good article:
http://www.audiorecording...rn-home-recording.html

Cheers...

CakeAlexSAre you monitoring via the audio software that might come with the interface, and then have echo buttons turned on in Sonar? If so turn one of them off.
Cheers...

I have determined that the audio feedback has nothing to do with  Sonar's performance.  It exists even when Sonar is off.  The US 122 has a direct monitoring function that bypasses all system delays that contribute to latency.  Subject to additional troubleshooting, it appears the function has failed.  

That Alex is pure nonsense. Sorry man but there is no such thing as a professional audio driver model. There are only driver models. Windows supports many different ones. Check this out http://www.highend-audiopc.com/PDF/audiophile_optimizer_setup_guide.pdf I don't endorse it or agree with it necessarily but notice they clearly dispute the assertion about ASIO in the article you reference.  
 
My view is use the best driver for your gear. This could well be ASIO. If however as in my case it makes no difference one will be fine with a WDM version or type if for no other reason than convenience. 
 
My point is if written well either type will do exactly the same thing. 

I wasn't really referring to the authors profiling rather to the explanation given.

Assuming all drivers are well written, anything that bypasses the windows kernel has to be a good thing when it comes to performance IMHO, that the biggest factor. That has nothing to do with the driver model..

Cheers..

CakeAlexS
I wasn't really referring to the authors profiling rather to the explanation given.
Assuming all drivers are well written, anything that bypasses the windows kernel has to be a good thing when it comes to performance IMHO, that the biggest factor. That has nothing to do with the driver model..
Cheers..

Its a terrible article :) That link has more misinformation than fact. It is also way out of date. WDM drivers do not impose SRC, kernel streaming completely bypasses that part of the Windows stack that is involved with mixing and sample rate conversion.
Also ASIO drivers do NOT bypass the kernel. A driver in Windows has to have a kernel component, the miniport driver.