If the Dynamics plugin is enabled on an audio track, an audible "echo" or glitch can be heard between audio clips if there is track silence between them, right at the beginning when the next clip plays. It's unusable. I have to disable "Dynamics" and use the single compressor and hard limiter effects instead. Please fix ASAP!

Previousely, the "reset parameter" button in the effect controls panel used to set audio levels to 0db. Recently, that has been changed to +9db which is useless in the majority of cases.

I understand that this change may have been made to address the typical digital recording level of -10 to -12db, but most recordings I receive are well above that (-6db), and music tracks are always normalised to 0db, so the current reset parameter value will always result in clipping.

I suggest adding a user defined "reset parameter" value to the audio preferences.

Audio tracks 4,5,6 will not accept audio...audio tracks 1,2,3 and 7 work fine. Why??

You should be able to change every setting as you please. If you create a mono sequence you can't change the master track to stereo. You should be able to change a tracks output channel amount after the sequence is created

Live preview of keyframe edit occurs when playback is paused but doesn't occur when in playback

The feature Avid Media Composer has and it's called auto-sequence.
In the editing software you select all your sound clip and video clip and, when you hit auto-sequence, it automatically creates sequences in which audio and video are merged and synced

When I add FFT filter to a sound clip it will cause the clip to get stuttery or just cut a small part of the clip upon render or export. Sounds good on playback in premiere, but when i export or do a render and replace, the clip will get affected.
PR Version 14.0.0 (build 572)
Mac Pro late 2013, high sierra (10.13.6)

We use a Sony camera to record long-form content, and it breaks long clips into 2GB chunks. On import, Premiere is able to to recognize that these are all part of the same clip, and pulls them all into timelines together. However, it seems that Premiere is generating a peak file for the entire clip, for every single file, which takes hours on a well specced machine.

Just discovered a new bug in CC2020:
- I have one Prores LT 4K file to synchronize with an H264 4K file (coming out from a GH5 4:2:0 8bit shot). When trying a right click/Synchronize/Audio), the Prores file is moved at the middle on the other file and is of course, out of sync...
- When trying to synchronize the same shots but not in Prores LT (both H264 from GH5), it's working as usual without any trouble.
Thanks to fix that.

Since update to CC19 (currently on Version 13.1.4, Build 2), Premiere will not playback any audio anymore. Audiolevels show visually on screen while playing and/or scrubbing, but I hear nothing. I have triple checked the Audio Hardware settings (See Screenshot), I have tried with/without headphones plugged in, I have tried uninstalling and reinstalling premiere, nothing helped. Every other adobe program works perfectly fine.

I'm running on a 2014 15" Macbook Pro and OSX Mojave (See specs screenshot)

Any help / ideas?

Please fix the switch from macbook speakers to headphones in Premiere!! Takes a really long time to switch

I want to sidechain 3. party plugins

Add exclusive solo mode for audio tracks like there is in Audition.
Audition has a preference setting for always exclusive audio solo.
And it has a short cut of Command Click solo for exclusive solo.
Premiere Pro has the modifier of Shift Click that toggles the state of all solos but sadly Command-Click does nothing.

A one click option to restore ALL camera audio to all clips and then create a new track and place that sync audio there.

Revert the visual design of the rubber band in the audio track, so that 0.00db sits vertically in the centre, as it used to be before 2020 update.

The attached screenshot shows the left clip at 0.00db and the right clip at -6.00db, however, the design language would suggest the left clip to have amplified audio. I'm not sure if this is due to new features, or a bug.

Rather than having to do this a batch at a time on the timeline, it would be great if we could set this up as a background job on import.