Track Mixer Effects Bug
Since the update to 12.1.0 there has been a bug related to audio track effects (I've specifically found it using the multiband compressor), but haven't tried to reproduce with other effects.
Basically, when re-opening premiere again after working on a project with a multiband compressor effect on a track, the effect won't be doing anything. In order to get it to work, I'll have to go into the mixer and toggle the preset to something else like "raise vocals" and then toggle it back to what it originally was (for me, "Broadcast"). Obviously, this is really inconvenient, as I have to do it every time I re-open a project. Though, an even much bigger issue is if other editors are opening the project, unaware of the issue, and changing the mix. I'll come in later and the mix will be totally off because it's not taking into account the compressors that were supposed to be on the track.
Luke
shared this idea
30 comments
-
Johan Storm
commented
Same problem! On PC, latest version of premiere as of 2021-03-11
-
Nic Beery
commented
On 13.1.4 (build 2), Premiere CC. Multi-band compressor doesn't work at all when I turn it on. It was working recently, in this same version of Premiere. As of yesterday, it doesn't. Is Adobe monitoring this board, and can they fix this once and for all?
Here's a bit more info, I am on this iMac -
Model Name: iMac
Model Identifier: iMac15,1
Processor Name: Intel Core i7
Processor Speed: 4 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB
Boot ROM Version: 224.0.0.0.0
SMC Version (system): 2.23f11
Serial Number (system): D25NX24DFY14
Hardware UUID: 6609D22D-2053-51F5-8D53-C1C4AAC5D2EA
This OS - MacOS Mojave Version 10.14.4My Mac is a 27" Late 2014 model.
The new issue, an existing timeline that I had already applied the multiband compressor to an audio channel still works. But if I turn off the multiband compressor and then back on, the multiband compressor no longer works. I can only select it and then manually turn up the gain, which is not compressing, just increasing the gain.
Can someone from Apple respond and let me know how to fix this? I use Premiere daily and the multiband compressor is a must.
Thx. -
Elliot Frahs
commented
Same problem here, July 2019, latest release.
-
Matt
commented
I do believe this has been solved with the update. I have not experienced the issue any more. Thanks!
-
Matt Stegner
commented
Hi all, Matt from the Premiere team here. This should have been fixed since version 13.0.2 (we are currently on 13.1.2). Can anybody still reproduce this in the latest version of Premiere?
Ivan Ivanov did not include the version in which he found this unacceptable (below).
-
Ivan Ivanov
commented
Just spent THREE HOURS rendering a movie. Once it was finally finished I start playing it and lo and behold - the audio sounds TERRIBLE!!!! This bug has been happening to me for a while now and I would usually catch it before I start my export but I didn't this time and now I am missing my deadline because I have to re-export again.
UNACCEPTABLE!!!!!!!!!!!!!!!!! HOW DARE YOU, ADOBE?? YOU HAVEN'T EVEN ACKNOWLEDGED THIS OUTRAGEOUS BUG!! FIX THIS IMMEDIATELY!!!!!!!!
-
Ben Israel
commented
This happened to me today, January 24, 2019. Multiband Compressor was not working in the duplicated sequence.
Strange, because I duplicate all the time. I've probably duplicated 100x during the course of this project. This is the first time that this bug appeared. It is very time-consuming to deal with.
I am using cc13.0.
-
Anonymous
commented
Has this problem been fixed? I'm using version 13.0.2 for Mac and haven't run into this problem since I updated from prior CC2019 which was terrible for this bug (as well as CC2017,18).
I'm interested to know if anyone else has found this problem still exists on 13.0.2, so I know if I still need to religiously check every compressor after I duplicate a sequence!
-
Evan Davis
commented
Yep. Me too. Such an insidious little error that I didn't notice at first, client had to point out drops in volume - very frustrating.
-
Anonymous
commented
Same happening with us. Have to delete and readd multiband compressor.
-
Anonymous
commented
I'm experiencing this issue as well. I use the Multiband Compression effect frequently, and find when I duplicate a sequence, not only does it set the gain to 0 for that effect, it turns it off entirely. Please fix this Adobe!
-
Anonymous
commented
I was hoping to see this fixed in the newest 2019 update, but unfortunately it is still an issue. Very frustrating and disappointing to see it has not been fixed for this many months!
-
Hans
commented
Does anyone know if this bug is fixed in the latest update?
-
Chris
commented
Workaround...well...sort of :-) Before duplicating a sequence if I OPEN the sequence in the timeline, then OPEN the Audio Track Mixer, then DOUBLE-CLICK the FX so that the Track Fx Editor window is open, and then go back to the Project folder and DUPLICATE the sequence...it will keep all of the audio FX. If I don't do that...then it wipes all of the parameters for the applied audio Fx. All my tests have been specific to the Tube-modeled Compressor.
-
Chris
commented
Still happening for me too...super frustrating...trying to figure out if there's a different process I'm overlooking and perhaps I should not be using premiere audio track mixer for my audio fx?
-
Nic Beery
commented
Same issue, duplicate a sequence and my multi-band compressor setting is not where it was set. P{lease fix Premiere gods!
-
Anonymous
commented
Horrendous. Such an irritating time-wasting bug.
-
Stephen Doyle
commented
Same issue when duplicating sequences with the Mastering Effect. It shows up but is not activated. I basically have to apply it again each time.
-
Matt
commented
Yet another casualty commenting here, caught by this major flaw. This bug needs to be fixed. It creates huge setbacks and an enormous waste of time having to switch settings just to reactivate the effect. A paid premium subscription should have this corrected by now.
-
Hans
commented
Unfortunately it is still not fixed in the latest update :/