8 results found

1. Utilize CPUs better when mixing down to file

   I have a podcast template with 6 voice tracks, a dialog bus, SFX / music tracks and a final mix/check bus before master. I have 1-2 VST effects on each of these. Mixing down a 2 hour podcast episode will easily take an hour on a pretty decent machine - with 15% CPU utilization.

   I realize this is complex, but couldn't the mixdown process be modularized to take advantage of multiple CPUs in the system, and thus probably reduce the mixdown time greatly?

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Performance  ·  Delete…  ·  Admin →

2. Use of VST Instruments.

   Allow Audition to be able to use VST instruments and midi.

   9 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Performance  ·  Delete…  ·  Admin →

3. Multicore performance (or lack thereof) in Audition

   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

   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… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Performance  ·  Delete…  ·  Admin →

4. Smooth Transitions for New Punch n Roll (non-destructive or destructive) Feature!

   The new Punch & Roll feature is great. However, there is one tweak that needs to happen, soon. You shouldn't have to "fade-in" a clip in multitrack to make the "punch-in" transition smooth. The automatic crossfade should work like it did before in multitrack. You also shouldn't have to go back and smooth over punch & roll sections in the waveform editor. For long form narration, this adds editing time which PnR was designed to reduce.

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Performance  ·  Delete…  ·  Admin →

5. Multi-Core usage in Audition Please!

   hi guys .. my name is dani, i have a beast of a PC with 28 cores to work with and Audition only knows to use one of them, two at best .. my suggestion is to work on multicore usage .. thank you ( btw i have a 150k subscribers youtube channel :D, i have somwhat of a voice) :D thank you ..

   •  

   9 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Performance  ·  Delete…  ·  Admin →

6. General Performance Bugs (moving audition window, play-head framy, levels monitor slow.

   i haven't seen this reported anywhere elsewhere so it seams like I'm an edge case, but essentially Audition for me is acting like programs do when your CPU is taxed 100%. The whole program is just extremely laggy, the whole window takes ages to move then I try to drag it around, it takes a long time to open effect windows, the playhead is laggy, ect... It's worth stating that my PC is pretty overpowered for Audition so there shouldn't be any issues like this and there weren't any before. It's just acting like my PC is working too hard but it's not, i have no idea why this would happen besides some weird bug.

   i haven't seen this reported anywhere elsewhere so it seams like I'm an edge case, but essentially Audition for me is acting like programs do when your CPU is taxed 100%. The whole program is just extremely laggy, the whole window takes ages to move then I try to drag it around, it takes a long time to open effect windows, the playhead is laggy, ect... It's worth stating that my PC is pretty overpowered for Audition so there shouldn't be any issues like this and there weren't any before. It's just acting like my PC is working too hard… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   4 comments  ·  Performance  ·  Delete…  ·  Admin →

7. mp3 export from audition is bad (compared)

   I just discovered that when saving a file as MP3, the quality is very poor, even at 320kbps CBR.

   I simply noticed with my ears that it sounded muddy. When I checked the waveform it was confirmed.

   So see if this is the best MP3 has to offer, I did a similar export (320Kbps CBR) using Izotope RX6.

   And the export from RX6 sounded much better and punchier, with a similar file size. This too can be confirmed in the attached screenshot.

   Please improve.. So many MP3's, unnecessarily sounding bad... :-(

   I won't be using it anymore, but many people rely on audition.

   Win10, CC2018 11.1.1.3

   I just discovered that when saving a file as MP3, the quality is very poor, even at 320kbps CBR.

   I simply noticed with my ears that it sounded muddy. When I checked the waveform it was confirmed.

   So see if this is the best MP3 has to offer, I did a similar export (320Kbps CBR) using Izotope RX6.

   And the export from RX6 sounded much better and punchier, with a similar file size. This too can be confirmed in the attached screenshot.

   Please improve.. So many MP3's, unnecessarily sounding bad... :-(

   I won't be using it anymore, but many people… more

   •  

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Performance  ·  Delete…  ·  Admin →

8. Since the last premiere update, dynamic link sends audio from premiere pro to audion in one single waveform instead of a multitack
   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Performance  ·  Delete…  ·  Admin →