Premiere to Audition adds +9dB of volume to clips

[UK TV Professional]

Hello, me again!  Can you believe it, I've found more bugs!  What a suprise.

When I send an Adobe Premiere sequence over to Adobe Audition it is adding +9.0 dB of volume on Audition's yellow volume graph/line on each clip AND a clip effect on each clip, called Channel Volume, which sets each channel to +8.98 dB.  The result is inaudable and burries the needles.

I've used the Remove All Clip Effects and Track Effects options and unticked the Pan and Volume Information.

Before I can start audio mixing in Audition I have to manually click on each and every clip, one at a time, move the yellow volume graph/line back to 0dB, then click in Clip Effects Rack and remove the Channel Volume effect.  EVERY SINGLE CLIP - ONE AT A TIME.

Please don't write bugs, I don't have the time.  And please, please, please hire some QC people.  Lots of them.  Why are we paying you to QC your software?

For an editing application that was released over 30 years ago, there sure does seem to be a lot of bugs.
This bug isn't new, as there are references to it over the years, but this is recent - Premiere 24.1.0 Build 25.

Please don't reply, I'm now much busier than I thought I would be.  Thanks a lot guys.

[UK TV Professional]

Just add, it doesn't add the Channel Volume clip effect to voice over records done in Premiere - only the ingested video files.
It does add the yellow line/graph volume of +9dB.

I'm so glad that line snaps to 0dB when dragged.....

[UK TV Professional]

Okay, this bug gets better.

I've just been through the Audition project and removed all that garbage that the export puts in there, dragged all the volume line/graphs back to 0dB for evey single clip.  Then I hit play...

The audio is all at the same levels that I used in my rudimentary Premiere mix, meaning the exported clips have been rendered or exported at the levels in the mix - And NOT without all effects and levels, as requested in the export dialogue.  Surely it's supposed to send the files at orignal source file level, ready for a propper mix.

😞

[R Neil Haugen]

I've been working in Pr/Ae/Au over a decade, and not only have I never had anything like this ... I've never seen anything remotely like this posted on either the Pr or Au forums.

So what you've got is a rare enough thing I would start with the assumption something's off in your local setup somehow.

And ... the best way to get good help on anything in Audition is to go directly to the Au forum.

Adobe Audition

[UK TV Professional]

Last time this bug reared its ugly head it was posted on the Audition forum and THEY said it was a Premiere bug.

Any way, as a user, it's not my bug - It's Adobe's.  I only came here to help point it out.  And for that, I'm sorry.  I care not if the bug's origins are Premiere or Audition, I subscribe to Adobe Creative Suite.  Adobe can decide.

[UK TV Professional]

R Neil Haugen, let's not get into a argument about who has used this longer.  I've been using Adobe insince the early 90s.

Just because you've never seen the bug, doesn't mean it's not there.  You've not been at all helpful here.  I provided clear instructions of how to replicate the bug - Did you even try?

Same goes for the forum posts - Did you read every post on the Adobe forum?

Try this one:-

https://community.adobe.com/t5/audition-discussions/major-bug-edit-in-audition-from-premiere-adds-am...

[R Neil Haugen]

You make some assumptions about motives ... not a wise thing in forum discussions. My comments about using for a long time but not seeing this are a basis of reference ... and if you check my total posts etc. well ... there's very few people that in the history of this forum both on the old and current platform have more posts.

And as I read far faster than most people, I've also read thousands I haven't responded to. This forum is in large part a learning experience for me. A way to track what's going on in the app and "out there".

I wasn't saying anything about ego. Just forum experience. Lose the emotional/egoistic motive things behind. They are absolutely of no use in troubleshooting.

Troubleshooting starts with gathering data ... establishing a base of all the where/why/how elements, how to replicate if one can.

In that view, the comment from the Audition users that this is a Premiere bug is both useful and intriguing. So it has popped up "over there", and yes, only on things coming from Premiere. That's solid knowledge.

Note, that in the devs, the entire Premiere audio team is actually the Au team. Pr doesn't have a separate audio team.

And no, I can't replicate. Your attitude on that is just a wasted comment, naturally I tried to replicate. It's the most basic part of troubleshooting, as if I could replicate it, that would be useful information. Which is all I am about.

And as to the post in Audition, the OP is Richard Knight, a very solid longtime troubleshooter here, and of course, SteveG, one of the Meisters of Audition ... and quickly got to a the apparent conclusion that the Pan & Volume checkbox was involved.

So ... have you tried the fix listed? 

And as this ... though clearly rare but existent bug is popping up again ... @Matt_Stegner might be able to assist. 

[mstegner]

I've read though this cannot replicate this issue, given the information in the thread.  Please allow me to explain that statement below.

I tried import a single file, creating a sequence and sending it to Audition using the current beta builds.  There is no instance of the Channel Volume effect applied to the clip in Audition and the clip Gain is still set to zero.

A short explanation of what the Premier and Audition interchange is doing:

There is not a 1 to 1 relationship between feature between Audition and Premiere, so some parameters are translated when a Sequence is sent from Audition to Premiere.

Premiere’s Channel Volume parameter is one of those cases.  There is no similar channel volume in Audition, so the engineering team created a custom effect  (that you cannot find in the effects menus by the way) called Channel Volume. 

The Channel Volume effect is applied to a clip in Audition if it is detected in the Premiere sequence.  I’ve tried this again, to see if there was anything broken, and confirmed that it appears to be working correctly.

Your Premiere sequence appears to have the Channel Volume effect set to add 8.98 dB of gain to each channel, when you that sequence to Audition that is added as the Channel Volume effect.  This is just a guess since I haven’t seen your Project.

So, that appears to be working correctly from the information I’ve been able to ascertain from this thread.  That said, there could be something more that I need to investigate from what you are reporting.  I haven’t been able to replicate what you are describing. 

I have a few of questions that I’d need answered to be able to try to move forward and try to help.  Could you answer a few question?

1. Are the Channel Volume parameters for the clips set to zero or are they altered?
2. Could you post an example Premiere Project, with a note about which clip is having this issue so I can see exactly how your sequence is set up?
3. Are you using any type of 3rd party Extension that manipulates the project at all, or an extension that manipulates file on import?  Essentially, is there a plug-in or extension that is changing the internal data of the Premiere Pro Project?

Please understand that I’m unable to replicate this on my end, which is the first steps to determine what is actually happening, and is needed to be able to provide any workaround or potential fix. There must be a variable that I'm missing on my end.  Please help me find that variable.

-Matt

[jelizondoedits]

Same thing happens to me. Definitely a bug. 

[R Neil Haugen]

Please ... give details so anyone can see and try to replicate. In this case, at a minimum ...

What is your media in Premiere?

What audio changes have you made if any in Premiere?

Which option in sending the sequence to Audition did you use?

What exact difference do you see, and how verified?

I'm not questioning at all that something odd may be happening. Just trying to establish the basis for testing the situation out.

[Michael Grenadier]

and fwiw, Neil is one of the most authoritative and dependable contributors here...    He doesn't need me to defend him, but can't think of a time his posts haven't been valuable....   Not trying to rattle the cage, just to give you some perspective on what he's trying to do...