I'm migrating over to a new secondary machine (brand new MBP, 16", 6 core, 4 GB Video engine). Catalina out of the box. I'm having all sorts of problems running plugins. Mainly - instant crashing upon instantiation and/or out of the ordinary sluggish performance. E.g. - (A) any attempt to instantiate plugins by Nugen Audio immediately crash (the most current version of) Audition. (B)Displaying the UI by SuprEsser by Sonnox severly inhibits the fluidity of the playhead. (C)Elixir by Flux and Loudness Radar (native) by TC Electronic appear as small sort of tiles in the lower left of the Audition plugin wrapper. (D)Youlean Loudness Meter immediately crashes Audition when attempting to customize the plugin's embedded scaling options. There are other issues as well. In essence, and based on my reliance for certain plugins - Audition is unusable. Let me mention that all plugins by FabFilter work as expected. So - what's the cause? Are developers lagging with their support for Catalina? Or is there some sort of wide-spread compatibility issue in Audition? I forgot to mention my issues are not isolated to a particular version (AU, VST/3) of a plugin. Problems persist regardless of the instantiated version. Any insight? This machine replaced a 2013 MacBook Pro running Mojave. No issues on that machine. And I'm also using a legacy MacPro running High Sierra. No issues on that machine either.

I’ll just post a (slightly modified for context) message that I sent to Jason Levine as an open letter since there is literally no information or outreach about this out there.

TL;DR, I’m very close to switching DAWs (likely Pro Tools) even though I don’t want to. Between this and a lack of a real strip silence feature that’s also usable in the nondestructive environment, and which doesn’t force me to ripple my track and/or export to hundreds of useless markers, it’s becoming less and less viable to continue editing in Audition.

Hi Jason,

Please forgive me for contacting you directly. I’ve exhausted all other search options to the extent my capabilities allow, including emailing Adobe support to no avail.

I’ve got a 2019 16” MacBook Pro with 8GB 5500M and a 2018 Mac mini connected to a 16GB Vega 64 eGPU. The former is the 8-core i9 with 32GB RAM. The latter is a 6-Core i7 with 32GB RAM.

I’m running simple multitrack podcast recording and editing sessions in the latest version of Audition. The MBP is used primarily for editing, the mini is what we normally use for recording. We’re recording at 48/32 in mono. I typically apply plugins from iZotope and Waves. My effects chain is usually 7-8 items long per track. Usually 2-4 tracks. One track per individual on the podcast. They’re recording at same rates (at worst, 44.1/16, but assume it’s usually 48/32).

After doing my initial edit I usually do a mixdown to a single WAV at the same rates. This way I can deal with a single track for fine-tuning my pacing, using markers to denote chapters, and mastering to yet another WAV. This is my final, which I later encode (including artwork, links, chapters) to MP3 (160Kbps, mono) in a phenomenal little app by Marco Arment called Forecast (which uses all 8 or 6 cores just beautifully).

My biggest issue is the first mixdown on either device. I’ve noticed on iStat Menus that on either computer only a single CPU core will fire up. On the 16” MBP, it doesn’t even look at the discrete GPU. It stays on the Intel the whole time (even with energy settings that force the discreet GPU on adapter power). On the Mac mini, the eGPU (which I’ve set in macOS to specifically use with Audition, Premiere, Lightroom, etc.) fires up to full bore, but still doesn’t seem fully leveraged. On the MBP a typical 70-80 minute show with two tracks will take over an hour to mix down. On the mini, even with Audition clearly leveraging the eGPU (to what extent or why, I do not know as I thought a mixdown of audio only would be mostly processor intensive), it still takes about 50-60 minutes. In fact, I suspect the difference is more about slightly better thermal performance than the eGPU.

Why isn’t Audition leveraging more of the processor cores? It seems like Creative Cloud applications for 2020 made fairly good leaps in leveraging discrete GPUs in certain apps, even if non-workstation class, but multicore processors are seriously underused across the entire creative suite. Is it just me? Am I missing a setting? It just seems like this stuff should be so much faster. As I take on more client editing work this becomes a real issue. I can use my Mac mini as a passive little render farm so I can free up my MBP, but it’s still taking that hour.

Do you have any insight on this?

I genuinely appreciate your time and once again apologize for reaching out via this forum.

Best,

Gilbert Tang

Audiotin seems to be the most useless program I have ever used since I got my first mac in year 1992. The one and only time I try to use it is in Premiere CC when I try to use the command "Edit Clip in Audition".

And it NEVER works, even if I have the newest version updated; the Audition opens, but the clip does not appear in it.

I have tried to remove the programs, update the programs, use the old&new version mixed - and nothing helps. It has been around TWO years since I was last time able to edit clip in Audition with the command "Edit Clip in Audition"..

Could You kindly tell me and the others, is there a way to get the Audition work? Or if You cannot do that, could You add the basic audio tools to Premiere then?

Only having a rudimentary knowledge that .PKF files are metadata used for display caching purposes (opening and displaying WAV files more quickly), I was wondering why multichannel WAV files can't have this? I have a multi-track recorder that saves the data as single, multi-channel WAV files. I have noticed that, when opened, no PKF file is generated, and when opening a session, it takes ages to open and display, as the large files have to be re-scanned every time the session is loaded. I have wondered this in regards to loading other file formats as well. Why can't metadata be created to describe the files as well, and not just WAV files?

Kindly note: I'm not looking for hypotheses here. I only desire facts from staffers/engineers or simply to request the feature, if possible.

Thanks!!

I have problems with time zoom (holding control with mouse wheel).
When I made the cuts and than try to zoom out or in, the interface freezes. Ok It does not freeze complete since I can grab the timeline and move forward/backward but the ctrl+mouse wheel does not work all the time.
It's very frustrating as it prevents me from making smooth workflow. It constantly stoping work at random moments and start working again after few seconds. It feels like computer is doing something in background and prevents from zooming in. But only with Ctr+mouse. I can still force it to zoom with time line.

While it is so? It is not a problem of my keyboard or mouse. I switched between 2 sets and I even have the same effect on totally different computer!!!
This is Audition interface BUG!