[Durin Gleaves]

Loving “bashing” from supportive users is great – there’s no sense in us working on a program if our users don’t enjoy the application. Constructive criticism is part of the job, and as a member of the Quality Assurance team, it’s basically my job description.

There’s several potential causes of lockups during recording, though it’s not a common occurrence. What sound device are you recording with, and which driver are you using? (If it is an ASIO-capable device, is Audition configured to use the ASIO driver, or is it using the default ASIO wrapper we install in order to support older, DirectSound and WDM devices?) What is the latency set to? And how many channels are you recording to simultaneously? Are your session files recording to a local hard drive, or is it a USB or similar external drive?

I know that during testing, we ran some pretty rigorous load tests on the application in order to backup some of our marketing claims. I believe we had up to 64 inputs recording simultaneously, with several lower-powered effects, before we could really make it glitch, but even then, we weren’t getting freezes or crashes – it was more dropouts related to disk speed. (This was done a year and a half ago, so don’t expect this to be accurate if I’m subpoenaed 🙂

Can you explain the problem you’re having on the 64-bit system? I know that one of our testers, Charles, did a lot of work with Windows XP 64-bit and Audition 2.0, and got most of the compatibility problems fixed. It doesn’t take advantage of the 64-bit architecture, but it certainly should function just fine.

[Durin Gleaves]

Hi Rojan_Man,

The section that describes the EDL and AAF import functionality is labeled as part of the Premiere Pro functionality. Premiere Pro can import EDL and AAF files for use in video projects, but these aren’t features currently supported in Audition.

You could open these in Premiere Pro, then use the “Edit in Audition” command to work on the specific audio data, however.

[Durin Gleaves]

I’ve spent some time this morning reading through the forum posts and it looks like a lot of the issues that have been brought up are ones we’re pretty familiar with and intend to resolve with Audition 3.0. Performance of the real-time mix engine is not as optimal as we’d like, and without a truckload of ram and CPU, it doesn’t take a lot of audio tracks and real-time effects to start getting a performance hit during playback and record. We’re not happy with the support for many third-party VST’s, and are going to look at improving that as well.

We’re already addressing these things for the next version. We’d also like to address usability or workflow issues, since the UI changed so dramatically in Audition 2.0. For the most part the response to the new UI and mixer have been extremely positive, but even minor changes can break some people’s standard procedures.

Maybe I’ll start a thread on it next week when I have more time to post, but I’d like to collect specific issues from folks. The more comprehensive and detailed reports I can get, the better the chance I have of getting them addressed.

And we do have an Audition beta testing program, although it’s inactive right now until full development begins again. As we get closer to getting that back up and running, I’ll see about getting you involved.

Thanks, Willie.

[Durin Gleaves]

Hi Doug,

You can try adjusting the latency of the onboard sound device a few ways. First, under Edit->Audio Hardware Setup, open the Control Panel and double click in the “Buffer Size” fields for your selected output and input ports. The driver defaults to 2048 samples, but your device may be able to go much lower – especially if you’re not listening to several other tracks or using real-time effects during recording. Double click those fields and change it to 512 for a start. If you experience dropouts, you may need to raise it to 1024. If there’s no dropouts, you can even go lower: 256 or 128. Test it out until you get dropouts, then reel it back a bit.

You may also want to check out a free application called ASIO4ALL (google it.) It’s an ASIO-wrapper for non-ASIO devices like the Audition Windows Sound driver is, however the developer has done an amazing job at reducing apparent latency in slower audio devices. Once installed, Audition sees it as an ASIO driver and it’s control panel lets you configure ports and latency settings pretty in-depth.

The M-Audio device was using it’s native ASIO drivers, which are MUCH faster than almost any on-board sound device will be. True ASIO drivers allow applications direct access to the hardware without needing to go through Windows’ slow WDM and MME drivers.

[Durin Gleaves]

Hi Willie,

I’m on the development team for Audition and Soundbooth, and was hoping you’d be willing to share your issues and concerns with Audition 2.0. At the very least I can make sure they’re adequately prioritized in our database for when we begin working on Audition 3.0, and at best, maybe we can determine solutions or workarounds in 2.0.

Also, I want to reassure you that Soundbooth is not intended to be a watered-down replacement for Audition. While it IS replacing Audition in the video production suite, Audition will remain a stand-alone application for Audio professionals. We found that most users who purchased the Production Studio suite, did so for the video editing tools and that the primary users of Audition purchased it separately. Video and Flash designers felt intimidated by Audition, and either relegated audio to an afterthought in their projects, or sent it out to third parties. Soundbooth’s goal is to help these folks perform the majority of their audio needs, cleaning noise and artifacts, basic EQ and effects, minor edits, in a format that they’re comfortable with.

Audition will continue to be a hub for audio professionals who don’t break a sweat at panning laws and phase correction. There are already a lot of new features completed for Audition 3.0 and several more in the design phase. But new features don’t matter if there’s fundamental usage problems you’re facing.

I hope to hear from you and discuss this further,
Durin Gleaves
QE Adobe Audition, Adobe Soundbooth

[Durin Gleaves]

Hi ausrod,

You can merge those clips to a new track by selecting them and bouncing them to a new track. you can then replace the old clips with the new bounced version. Select the main clip and your punch-in clips, right click and choose “Bounce to New Track” -> “Selected Audio Clips” A new track will be created immediately under the current one with your merged audio.

Hope this helps!