Every time, after changing Audio Gain by using Adjust Gain by parameter, a "Calculating Audio Peeks" dialog with progress bar is pop-up.
It is expected, that the peaks will be updated instantly like after setting a value for the Set Gain to parameter. Opinions?
Concise problem statement:Unnecessary "Calculating Audio Peeks" dialog with progress bar pop-up after changing Audio Gain.
Steps to reproduce bug:
1.Place some Long Audio Clip in a Sequence, let it be 1 hour
2.Open Audio Gain Dialog
3.Set Value for "Adjust Gain by" Editbox to 10 and hit OK
Results:Every time a "Calculating Audio Peeks" Dialog with Progress Bar is opened
Expected results:Instantly update peaks, like after setting value for the "Set Gain to" Editbox.
What is the difference between Instant vs Delayed functioning in your opinion?
I'm rest assured that if on my systems there would be a Delay and on yours the same function would be Instant you would say offensively:
Dude, you may want to wipe your system and reinstall everything from Windows on up. You seem to be having a LOT of issues that I can't reproduce on two different systems.
But when there's an obvious Program fault, you're saying inadequately that it's the way it should be, it's by design, it's just work differently, I'm not seeing an issue, etc.etc. Even Adobe Employees are not such an app defenders.
Anyway, thanks for entering discussions, you are probably one of the most active participant on the forum.
FYI, each of my described bugs have it's own workaround(s). But in most cases workarounds are slow. I start Discussions to confirm that I am not alone and the issue is Program-specific, no need to defend the app reputation. Current issue is solved by a macro script which uses it's own methods to alter Audio Gain by manipulating Premiere's Audio Gain Dialog Box.
I guess I don't really understand the problem.
When you say "change the gain from 0 to 5" the application doesn't have to think about it. When you say "adjust it by 5" it has to check the current peak gain on the clip and make a relative adjustment, not an absolute adjustment.
Assuming I understand your bug correctly, I would tend to agree that once the peak gain level has been determined that no more adjustment is made. In that case, no further analysis (calculating) should be required, but the program may just be set to check it every time by default when a relative adjustment is being made.
At any rate, hopefully I've explained why they DO work differently. As to whether or not it SHOULD in many cases, I guess that's a question Adobe developers will have to answer for you.
When you say "adjust it by 5" it has to check the current peak gain on the clip and make a relative adjustment, not an absolute adjustment.
imho, a Calculation of %iCurrentGain% +5 should not invoke the Calculating Audio Peeks progress bar.
I would tend to agree that once the peak gain level has been determined that no more adjustment is made. In that case, no further analysis (calculating) should be required
but the program may just be set to check it every time by default when a relative adjustment is being made.
But why? It's needless. Could you imagine that after using a Clip Speed/Duration and setting a checkbox to Ripple Edit an unnecessary Calculating Ripple Edit, Shifting Trailing Clips progress bar dialog box would appear? Would you say in that case that the program may just be set to check the clips location every time by default when a ripple edit is being made?
Looks like you are defending app's operation behaviour like Jim did.
Adobe developers will have to answer for you.
Hopefully in this Discussion.
But when there's an obvious Program fault, you're saying inadequately that it's the way it should be
No, I'm just saying it appears to be the way it IS. I'm not saying anything about the way it should be. If you think it should be different, go ahead and file a feature request.
I just don't believe this is a bug, that the behavior you're seeing is the way it was designed to work. I say this because I think it's important to file the proper form, in this case, a Feature Request.
This case is definitely cannot be a Feature Request and it is defenitely not a thought-out design of an app operation.
Can you assume that it's simply a mistakenly written code?
A software bug is the common term used to describe an error, flaw, mistake, failure, or fault
a mistake in program code is also considered as a bug
When you will have an opportunity, try changing Audio Gain for a > 1 h long audio clip.
Simply type +1 in Adjust Gain by editbox, and then do the same thing, but use Set Gain to editbox. It's interesting that Set Gain to can be used in the same manner as Adjust Gain by.
Activate Adjust Gain by editbox, then press End and type +1. New Gain will be calculated in the same way as when typing relative values for Set Gain to, but with a difference - the change will be Instant, no Progress Bar.
Thanks for the feedback.
It's great that somebody can benefit from my manifests.
I suspect it's working as designed. But only an Adobe engineer would know for sure.
An Adobe engineer would just confirm a mistake in program code or, if you wish, not deliberately a function("Calculate Audio Peaks") is used in wrong place
Now I understand why this Dialog appears. A progress bar which shows a calculation of audio peaks is correct for multiple selected clips. But even in that case it's not obvious why it pop-ups for simple addition and subtraction math operations. Some code should be added to test whether a Single Audio Clip is selected - because when changing gain the change should be Instant at least for a single clip selection.
I've made the script that controls Audio Gain Dialog publicly available
Works only in CS6.
No installation is required. A System Tray icon will appear after starting the app and an ini file is created near the executable.
No need to invoke Audio Gain dialog.
By default a HotKey Alt+G is defined, but feel free to modify it in the ini file:
^ - Ctrl
! - Alt
+ - Shift
# - Win
for example, ^+g is Ctrl+Shift+G
the Hotkey triggers only in Premiere Pro Window
Relative value cannot be set with Set Gain to for Multiple Clips, as a 0 dB value is shown when changing audio gain for multiple clips.
It’s a good question for the reasons you've mentioned. I suggest you go ahead and submit a bug. The only cases where I'd expect a progress bar is for the Normalize selections, which require an analysis pass on the selected waveform(s). T
Exactly, it's reasonable only for Audio Normalization, not for simply adding/subtracting Audio Gain Value(s).
Each created discussion is automatically sent to
but nobody replies
Steven Pribilinskiy wrote:
Adobe developers will have to answer for you.
Hopefully in this Discussion.
We had AkilW answer you in post #10: http://forums.adobe.com/message/4470380#4470380
He is an audio specialist on the Premiere Pro team.
If a bug was filed, you've done your best.
I'm the Sr. Content and Community Lead. I'm mainly responsible for Help for After Effects, Premiere Pro, Media Encoder, and Prelude. I'm also responsible for the community, both online and in person. I do demos, create tutorials. write blogs, manage author relations, and evaluate statistics. My main job is simply to help people. I'm in a good position to do that as the founder of a prominent user group, an author, a trainer, and editor in San Francisco and Los Angeles.
Akil is a quality engineer for the Premiere Pro team. He has a strong background in audio in Premiere Pro.
Europe, Middle East and Africa