Strange audio glitch on output – is this a bug?

[Jessica Cox]

– System specs:

MacOS Sierra version 10.12.6
Model Name: Mac Pro
Model Identifier: MacPro6,1
Processor Name: 6-Core Intel Xeon E5
Processor Speed: 3.5 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Memory: 32 GB

– What exactly are you hearing?
11776_audioglitch2017.mov.zip

– Does this happen in the timeline or only in the rendered/exported file?
Does not happen during playback in timeline, only in exports.

– Sequence settings
Timebase: 29.97, 1920 x 1080, square pixels, upper field first, drop frame, timecode, 48000 Hz,

– Export settings
1920 x 1080 (1.0) 29.97 fps, Upper, Quality 90, Apple Pro Res 422 (LT)
AAC, 48000 Hz, Stereo

[Jerry Bignotti]

I believe this is still a bug. I experienced it with Adobe Premiere Pro CC 2018 today.

I have a mulitcam sequence (2 cameras) with several tight audio edits. While listening to the sequence, things sounded fine. After exporting via the Queue in Adobe Media Encoder, there were blips and other noises (sounding like they came from the unused audio track from camera 2).

Thanks to others on this thread, I was able to work around it by exporting the sequence directly out of Premiere.
( File/Export. Then, when the AME interface pops up, select Export, rather than Queue.)

Thanks to those posting the workaround as you saved me a lot of time and angst. And you made me a member of Creative Cow!

BTW, I am using:
Adobe Premiere Pro V 12.0.0 (Build 224)

OSX El Capitan 10.11.6 (15G17023)
Mac Pro (Late 2013)
3.5 GHz 6-Core Intel Xeon E5
64 Gig Memory
AMD FirePro D500 3072 MB Graphics Card

[Felix Von nida]

I have been having the same issue as JB above and have traced it back to the fact I was using the obsolete multi band compressor (the current version didn’t work on certain tracks).

I’ve had to remove all compression, export audio separately, then reimport as new audio track and add compression to the whole thing. A very broad stroke and not totally ideal but at least it’s been solved for now after many hours of playing with manual crossfades.

Has anyone else found this as the cause or are there possibly others as well?