Audition CC 2018 Doesn't Recognize My Recording Interface

[jrduer]

Good evening. I just upgraded to Audition CC 2018, and updated my ASIO4ALL driver. When I went to Preferences -> Audio Hardware, the information showed the ASIO driver, the Tascam US-144MKII device, the buffer size (256), and the sample rate (44100). There are no choices for default input or output, etc., like there are when I check the MME, instead of the ASIO driver. When I click the setting button to the right of the device name, a box pops up that says TASCAM, the name of the device, the device driver (2.05, the most recent), and then, where it says "device," it says, "none found." I've tried everything I can think of, to no avail. I can't assign track inputs or outputs to the Tascam device; I can't assign outputs; and when I tried recording with the MME driver, instead of ASIO, the latency was about a day-and-a-half. Has anyone else had this happen, and if so, have you fixed the problem? Thanks.

[ryclark]

If you have a Tascam audio interface then you shouldn't be needing to use ASIO4All since Tascam provide their own ASIO drivers. Make sure that you have these downloaded from the Tascam site and installed.

[jrduer]

Thanks. I have the latest V2.05 drivers for the Tascam US-144MKII. Before the change to Audition CC 2018, it was working just fine. The ASIO4ALL was my attempt to get it to work again, but this attempt seems to have failed.

[ryclark · Accepted solution]

Try reinstalling the drivers and then double check in Audition's Audio Hardware Preferences that ASIO id selected as Device Class and the Tascam US-144 as Device.

[jrduer]

Thanks, ryclark! It turns out "operator error" was the culprit all along... When I clicked to uninstall the Tascam drivers, I got a box asking if I wanted to install the driver, uninstall previous drivers, or cancel the operation. I thought to myself, "Hmmm. I thought those drivers were installed already." So I clicked to install the drivers, and - lo and behold - they weren't installed. Apparently, I missed a step when I updated the drivers. Everything works fine now! I feel stupid, but not contagious...