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..
 

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.

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...

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. 

mudgel
Thanks for that Noel.

someone should contact the author http://www.audiorecording.me/about-me

Steve it could be that. I think people just repeat what they have heard and not question it. It seems the "smart" answer. But it isn't. Its a lazy answer.  If you look at how the various drivers actually work the native windows KS drivers are better theoretically than ASIO. 

I have been attempting to get my Audio Interface back into a situation whereby WDM KS Drivers will work.  Meanwhile I have been using the ASIO drivers and my Tascam US 122 in either a 16 (occasionally it goes to a  24) Bit mode.  I've experienced crashes when the number of tracks , for example are large.  However  my PC now exhibits the BSOD almost immediately upon launching Sonar X3e.  It will also frequently go to the BSOD  when shutting sown Sonar.  From what I have read on this forum, I suspect that the issue centers around the US 122 WDM Interface Driver.  I have no idea  as to why that is the case but offer it up as a possibility as I have been working with trying to return my system to operating the way  it did  before I posted what may be a related issue.
 
Perhaps someone can help shed light on how to fix the issue.

The current Drivers either do not support the audio format or are etc etc

Two issues have shown their heads almost simultaneously. 

  My US-122 Audio Interface in not recognized when I try using it in the WDM mode.  The following error message is presented:   

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

I am able to use the ASIO setting. 

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? 

not all manufacturers include WDM drivers with their audio interfaces any more, especially the lower end ones.  it would not surprise me if your US122 does not have WDM drivers for your Win7.  nor would it really surprise me if Tascam's WDM drivers were not 100% right.  I know in the past I have helped a lot of people try to get them to work correctly and they were always "hit and miss" as far as Tascam's drivers for the older US122 models.
 
 
NOTE:  this is the same subject as your "driver does not support..." thread, so I merged them.  there's no need for 2 separate discussions on the same problem for the same person.

It must be that time of year when miracles are somewhat  more of a common occurrence.  After a SONAR X3 re-install my US122 WDM KS interface is working again  ... just as it did a day or so ago!

Beagle
well that's great!  I never would have suggested reinstalling sonar for a problem like this!  glad you sussed it!

Thanks for the follow up note!  That was very kind of you!