It avoids me going back-n-forth configuring Sonar for WDM/WSAPI/ASIO driver settings. Mekashi - I use ASIO4All in Sonar when my Tascam is not connected. It is set to "USB selective suspend setting - disabled" (for both - on battery and Plugged in). Brian - I checked the USB power settings. Hello Brian, Meashi - thanks for your quick response.
Tascam 122 mkii driver drivers#
Korg Kronos 2 (with Korg drivers v1.14r_14) - I don't use this as an audio device.ĪSIO4All - ver2 - But I use Tascam ASIO driver in Sonar. Tascam UK-122mkII (with its ASIO driver - driver v2.05 and firmware 2.03, both are latest) The reason I think it is a Sonar problem is because when I set my laptop to use Tascam device for all its sound, it works great.
I am wondering if anyone else is facing such issues. That again lasts for about 5 min before the sound drops out again. The only way it starts working again is if I disconnect the Tascam device and re-connect it. No audio engine drop out error message either. I open up a vst to tweak some controls (or take a natures break) and when I get back. What's even more frustrating is that it seems to be dependant on "idle time". Recently (for about a week), Sonar has stopped giving me the Audio Engine drop out message. Restarting the audio engine from the toolbar would solve it. Sonar detects my Tascam Device and I am able to work the ASIO drivers that came with it. Initially I used to get intermittent "Audio Engine has unexpectedly dropped out" message. After upgrading to the Cambridge release, I seem to be having a problem with Tascam midi/audio interface. I have been using Sonar right from v5 upto now the Platinum version. Sonar Platinum with Tascam US-122mkII - ASIO Driver
0 kommentar(er)
