Using Adobe Audition

[Flaviano Bada]

Forthe past 4 months I've been having processing issues with my Apollo Twin interface. While recording I intermittently have a white noise or static sound running through my files and levels dropping mid recording. I have tried different Thunderbolt cables and outlets, different mic cables, different mics, hard reset on computer and interface, different computers, etc. I've been in contact several times over this time with UA. After recommending all of the above they said it must be Adobe Audition's problem. They went on to say I need to try one of their "supported DAW's".

Ask yourself this; if just about every other interface on the planet works fine with Audition, both on Macs and PCs, why is it even likely to be Audition's fault? More interesting to ask which other ones don't, and why. The prime culprit here is M-audio - their drivers are primarily intended to run with ProTools, and their ASIO driver appears not to be up to scratch at all. What do UA recommend as a suitable DAW?

But the other thing is that it's Thunderbolt, and that's still slightly unknown territory. If you do a search, you'll find that plenty of people have had similar problems with UA interfaces - it's not that rare. Audition is notoriously good at recording exactly what's sent to it, but if, for any reason that gets compromised then we're in different territory. I've heard about one instance where turning off hyper-threading appears to have improved UA performance, but that seems to be a little extreme.

It might be useful though to test the interface with some other software - preferrably ASIO-based just to see what happens. Whilst it's clearly not impossible for this to be Audition's fault, whatever it is still needs to be isolated, and that's going to need some more checking on your part, I'm afraid...

UA suggested several DAW to test, the one I choose to test was Ableton Live 10. I tested both Audition and Ableton with ASIO. Neither are perfect. I set everything as close to the same as possible. Ableton shows a bit less staticky. I wanted it be the other way around. I prefer Audition. I'm also testing a couple of different brands of thunderbolt cables, just to rule that out. Not sure how much patience I have left.

I just got the ua solo thunderbolt heritage edition. i use adobe audition cs6 and its a static distortion when using the ua but when i use my ssl2 interface its crystal clear. ua says i need to use asio but when i do there is not sound recorded into aution. i can see the levels on the solo but no sound in audition. im not really sure of the settings for asio 2.15 beta2 but i have the power for solo input lit and just saw tonight that the highest buffer is recommended by some dude and i tried 96k res but i did a test at 48k and it worked on the asio driver in audition but the static is still there. i dont know what else to do. SteveG I hoping you can G this is for us.

Recently purchased Adobe Audition CC 2019. Currently using both Adobe Audition and Garageband for recording music and vocals. Using Zoom R24 and Focusrite Scarlett 2i2 as my interfaces on both software programs.

Problem: Using both an omnidirectional mic and a condenser mic. When I record a vocal track with either mic through either interface in the Garageband software, the vocals come out sharp, clear and normal sounding, no issues or problems. HOWEVER, when I do the same using Adobe Audition, the resulting vocal tracks sound somewhat distorted, not at all normal sounding. The best way to describe it is they come out sounding almost slightly doubled and as if they were recorded in a closet.

Does this happen with both recording into the Waveform view and the Multitrack view? You don't happen to have tried starting a brand new session in Audition using one of the Template s provided have you? Some of them contain rather coarse application of effects by default unfortunately.

I have not recorded yet into a single wave form view. I record into what I set up to be a voice track in a "new session". The resulting recording has the distortion. I can hear that distortion in both the multitrack and waveform views. I did not use a Template, just set up a "new session" from the basic menu.

One possibility is that somehow, you've got Smart Monitoring enabled when it shouldn't be. You can check this out easily by following the advice in the FAQ about it. I realise that the FAQ appears to relate to the 2018 release where it was accidentally switched on by default, but it still applies whenever it's switched on. Anyway it's easy to check - information here: I'm getting strange feedback and monitoring issues with the Audition 2018 release - can I fix this?

Thanks for the tip. However, when I followed the instructions in the FAQ, I found that the Smart Monitoring was NOT checked to be on, so I'm thinking that was not the cause of the problem. Any other ideas?

I'm having a similar issue. Using a USB mic to record in Audition for the 1st time and my voice sounds bad, repeated the same exercise in Camtasia and it was crystal clear. Since I did not change a single setting on my laptop or microphone, I'm certain the issue is with Audition.

Hoping someone has figured this out because splitting the audio from the screen recording in Camtasia is not an ideal work around and I am not too keen on installing more software when I've already paid for the CC suite.

Actually, Audition records very faithfully what it's sent. But that does give us a clue, because there's a pretty good chance that Camtasia doesn't use an ASIO engine, whilst natively Audition does - and that's what sends the audio to be recorded. The obvious thing to try here, because it's free and gives good diagnostics, is ASIO4ALL as a driver, because this is known to work well as an interface that can get around some of these problems. The other option is simply to change the driver model in Edit>Preferences>Audio Hardware - especially if it's set to WASAPI. If it is, then try MME instead. If you install ASIO4ALL that will also show up under ASIO in the driver types list, and that's where you select it. It has its own control panel, which will show you very clearly what's working and what isn't.

Interesting piece though: after installing and rebooting, I selected ASIO from the Audio Hardware Panel, and the Input/Output options were chosen for me. I assumed this was by design, so I went with it. I recorded audio, but the playback didn't come through my headphones which are connected through the USB mic, so I'm not sure if the sample got recorded through the USB mic or the Computer's mic using the ASIO hardware setting. I also couldn't select my Yeti Microphone as the Default Input / Output hardware, so I reverted back to MME.

The interesting part though, is that this time when I recorded a sampling of my voice in Audition, it worked! It didn't sound at all distorted like yesterday. Is it doing something magical in the background?

WASAPI is a very old driver - a legacy product. And it's never worked very well, or really been supported by M$. MME generally works fine, but sometimes if you're using internal hardware in your computer, it gets its underwear in a twist and tries to re-sample the result according to what your computer's sound device was previously set to. If, for instance, it's been playing system sounds, or even something simply at a different sample rate, then the results can sound awful until something resets it. Sometimes just playing the file again is enough to do that.

And, I shouldn't have called ASIO4ALL a 'driver' as such - it's an interface between ASIO-based software and existing PC drivers, provided for when a manufacturer doesn't provide their own ASIO solution. As for everything else, you might like to have a look at another thread concerning Blue Yeti mics: problem with mic and asio drivers.

I just bought a Procaster and a Focusrite Scarlett Solo, and am having this issue also. In OBS softward the microphone is crystal clear but in audition there is a static and it sounds like I'm under water. I just can't figure out what this issue is.

Did you ever figure it out?

What I suggest is that if you are having difficulties, the best thing to do is to start a new thread about your specific problem. On the home page there's a button marked 'Post to community' at the top, under where you sign in - that will start a new thread. The more information you put in your post, the better the chances that we can figure out what's going on. Especially tell us whether this is with a Mac, or a PC - the sound systems are significantly different.

I fixed it by just resetting all the settings. Did this by closing then opening Audition while holding down the "Shift" key. NOTE: This will get rid of any preset data you added, like hotkeys and settings. But it worked for me.

Students: Place an order for Adobe CC via the Software Distribution site. Faculty and staff: Click the link below to submit a request for access to Adobe CC. Note: if you already have been issued a Creative Cloud license and want to install it on a new or second computer, please follow the re-installation instructions.

The Adobe CC software is available to the UNC-Chapel Hill community through an Adobe Enterprise subscription model. To begin the installation process, you need to uninstall all old Adobe products from your computer. To uninstall the Adobe software, visit the adobe.com article: Use the Creative Cloud Cleaner Tool to solve installation problems.

If you need further assistance removing Adobe CC, please contact the ITS Service Desk using one of the contact methods listed below. If you do not have any Adobe CC products, you may skip the uninstall process and continue with a clean installation. All users logging into, Adobe Creative Cloud will need to use Duo for 2-step verification.

3a8082e126