AA3 can't see my Santa Cruz.

Hey everybody...

I'm currently using a Turtle Beach Santa Cruz, and it works fine with CEP 2.1, but when starting up AA3 I get this -> "Adobe Audition could not find a supported audio device.

Please check your device settings."  Real snooty like that.

It then abruptly closes. Not even a glimpse of anything.

Any thoughts ? Anyone ?

Does it have an ASIO driver? If it doesn't, then your best bet is to download the (free) ASIO4ALL driver and try it again using that. This converts AA3.0's ASIO-only engine I/O to WMD, which I would have thought that even an old Santa Cruz would be able to cope with.

This appears to be a system problem, not one from AA3.

I have run AA2 and AA3 with a Santa Cruz up through the Spring of '08.  It's messy, visual timing is off, and the occasional glitch can be annoying.  I can't even say it recorded reliably, but then I used AA1.5 for that when needed.  (This wasn't my primary recording computer.)

My experiences showed that ASIO4ALL is not necessary.  You might find it advantageous depending on what you're doing, but the problem here is very much from something else.

AA3 should be able to see the Turtle Beach when Edit>Audio Hardware Setup>[any of the three tabs]>Audio Driver is set to "Audition 3 Windows Sound."  From there the port assignments below should reflect the presence of a Turtle Beach card.  If they don't, then you might check your Windows Control Panel settings for sound, and see if the Turtle Beach shows up there correctly.  Even if it does, there may be a problem with the driver.  Make sure you're using the final TB driver (4193).  Please confirm this, and let us know if the TB works with other programs and players.  Also, is this in Windows XP?  If you're in Vista, or 64-bit, you're begging for trouble using a card that old.

A TB card served me well for years, even for pro work, so stick with us.  There's another computer far from where I am at the moment still running a TB card with AA3, so if need be, I can poke around that machine if need be for more clues. 

My experiences showed that ASIO4ALL is not necessary.  You might find it advantageous depending on what you're doing, but the problem here is very much from something else.

Fair enough - but one of the things William is doing is troubleshooting the installation, and the one thing that ASIO4ALL does infinitely better than the Audition Windows Driver is to give you a clue as to what's going on!

So I reckon it's worth it, just for that reason alone.

Ok, it's working. Thank you both.

This is the first "Off the Shelf" computer I've ever owned. It's a Pavillion a6419fh. Catchy, huh ? It came with Vista pre-installed, and I gave it an honest shot.....about 45 minutes, before throwing XP on it. But not having a Vista disc, I didn't want to burn any bridges, so I'm dual-booting, and that's fine.

The reason I mention it is that my Santa Cruz drivers were actually the 4161s release, not the final 4193. And now I remember why.

Vista violently objected to the Santa Cruz's presence, or at least, driver version 4193. It actually prefers the older 4161. They work fine together. So that's the version that I
must have had on hand when setting up XP, I had forgotten they were older.

Anyway, Steve made a comment in another thread around here something to the effect of..'if the card works with Windows at all, it should work with Audition'. So the first
thing I did was try to update the drivers. And I got very strange error messages flying around both when trying to uninstall the old driver, and when trying to install the new
one. Also, since updating "Windows Installer" recently I've had to manually start the service every time something needed it. (Nice) Plus, my AV (TrendMicro) was perpetually
updating.......never quite succeeding....

So, to make a long story longer, I ran Windows Setup, then uninstalled the old Santa Cruz driver, then installed the new one, and Audition works fine. What I didn't do was try the older driver version after running setup, so I can't say for sure what the issue was, but my sense is that it was something deeper than the driver release.

I remember, ages ago, debating the merits of running Windows Setup, essentially, installing Windows over the top of a current installation, and I guess this a pretty good example of why it's not always a bad idea.

This appears to be a system problem, not one from AA3.

...AA3 should be able to see the Turtle Beach when Edit>Audio Hardware Setup>[any of the three tabs]>Audio Driver is set to "Audition 3 Windows Sound."  From there the port assignments below should reflect the presence of a Turtle Beach card.  If they don't, then you might check your Windows Control Panel settings for sound, and see if the Turtle Beach shows up there correctly.  Even if it does, there may be a problem with the driver.  Make sure you're using the final TB driver (4193).  Please confirm this, and let us know if the TB works with other programs and players.  Also, is this in Windows XP?  If you're in Vista, or 64-bit, you're begging for trouble using a card that old.

Trouble was, I couldn't get Audition to start, so I couldn't even begin fiddling with it. And it (the card) had been working fine with every other application. But, your first observation was, I suspect, absolutely correct.

Cool!  And the main advantage of the 4193 driver, other than potential stability, is the ability to play discrete 5.1 via the WDM driver and the combined 3 stereo-pair outputs on the card.  This used to work great with AA1.5's surround panner, or PowerDVD for AC-3 or DTS playback.  WDM 6-channel playback isn't very compatible with AA3, unless ASIO4ALL adds some configuration features.

Speaking of which, now that all this is behind us, grab ASIO4ALL and try it out. It's definitely a YMMV situation, but Steve's advice to get it is well-warranted.