Hi there. I posted this in 2018 and now it's 2020 and this still remains a massive headache for us folks who do audio post within Premiere. PLEASE please please add undo functionality to audio track mixer fx changes!!
232 votesUnder Review · 12 comments · Premiere Pro » User experience/interface · Flag idea as inappropriate… · Admin →
Really into this one. Been missing it since I left Final Cut Pro 7...
We’ve marked this Under Review, see comment.
Still waitin 2020 14.0.1 still opacity keyframes set to ON. Please save me this click. I've been clicking this for over 2 years now...
Yeah I do all my offline in Premiere, all my online in Resolve. Can't trust lumetri outputs at all...
Hey Giles / if you’re on a Mac, go to Documents->Adobe and rename the PremierePro folder in there to PremierePro.old and then start Premiere again. Should unfreeze your broken project hopefully! You’ll lose your keyboard layout but that can be copied from the .old folder -> 13 or 14 -> profile-yourusername-> Mac.
This was and is my workflow in PP2019 for every time there’s a crash (every.time.) so I’m just guessing they didn’t fix that particular bug in 2020. I’m just hanging back on 2019 bc at least I think I know most of the bugs that exist there!
@EddyChiang if you’re on osx, in the Finder, go to Documents/Adobe/ and rename the PremierePro folder to PremierePro.old and restart Premiere. It will then create a new PremierePro folder, and you will lose your keyboard settings (which can be copied from the “old” folder), any custom bins and custom layouts but PP should restart.
I have been suffering from crashing and then not-restarting since 13.0 and this is still an unfixed issue in 13.1.5 on OSX.
Yo yo yo I'm back with another comment with how rubbish CC2019 is! Have updated to 13.1.5 hoping for that "guaranteed" fix for the colour shift on export in OSX. Update: it's not fixed.
Annnnd the terrible bug that's occurring on every crash since 13.0: I have to rebuild my Premiere Pro folder every time it crashes, because if I don't, PP simply does not open. So after every crash, my Premiere Pro folder in Documents->Adobe gets renamed to "PremierePro.old" and all my custom bins disappear and I get to reconstruct them. But I suppose the software reopens, so that's pretty cool.
Hope you're enjoying my $69AUD a month Adobe, it must be great knowing you're getting my cash regardless of the state of your software amirite? 12.1.2 for life I guess.
Stay on 12.1.2! No fancy new features but so much more, so very much more, demonstrably more stable than 13 (aka PP2019). I’ve told my whole firm to start all new projects on 2018 (12.1.2) because until Adobe sorts out whatever’s going on w 2019, we won’t use it. They already have our money I suppose, so no loss to them ultimately. Wow, I wasn’t this cynical until this year... I thought it was the US president, but maybe it was CC2019 all along! Huh.
CC2019 is The Worst. I don't know how the higher-ups at Adobe sleep at night knowing their subpar, buggy AF software is out in the public domain. They should be paying me $69AUD a month for the testing I'm doing.
Seriously, do you want my bank details? I'll take direct deposit.
Just waiting for another render. I hit undo and then redo, but my render disappeared. Hilarious. Oh wait, it's crashed. Ah no it didn't crash. Just taking 11 minutes to render 33 frames.... There's not even any noise reduction plugins. Oh I'd love to denoise this frame, but how long would that take?? I've only got 22 minutes to meet my deadline... Hilarious amirite? I didn't used to be cynical... Actually, I used to be quite positive. Now I take every opportunity to tell people not to use your software. Seriously Adobe, you're directly responsible for a drop in my mental health. What is that worth? I can't actually do my job.
Still happening in 13.1.5 // I have Multiband Compressors applied to three audio fx slots. And on playback it's digital pop nightmare. Even after I "Render Audio" the problem remains. There are also digital pops when a clip ends and then pops again when a new clip begins. I've also added a 2frame audio fade transition to all my audio clips, but the digital popping remains. I basically have to do a ProRes runout to listen to my mix...
iMac (Retina 5K, 27-inch, 2019)
3.6 GHz Intel Core i9
64 GB 2667 MHz DDR4
Radeon Pro Vega 48 8 GB
Probably shouldn't be happening with this grunty a machine...
What you’re suggesting would lead to a full on revision of the feature – therefore I’d like to ask a couple of additional questions:
what kind of footage do you usually try to stabilize with the Warp Stabilizer? And how much tweaking of the settings do you do on average?
Also please fix this new bug introduced in v13, which has nullified one of my favourite workflows from v12 and earlier:
I have a clip where I apply a mask to omit certain tracking points for Warp Stabilizer.
I nest the clip.
I apply the Warp Stabilizer effect.
PP freezes/crashes/spinning ball of doom.
This workflow worked fine in CC2018 and earlier, but not at all in v13, including the latest 13.1.5
Still not fixed in 13.1.5 ///
Yep just updated to 13.0.2 to try it out for the first time and no warps on Nests. Workaround is to go into nest, change sequence size, then warp. But after being told for years that you must nest to Warp Stabilize, this is a particularly ironic backwards step......
Colour shift on export in 13.1.5 is indeed 100% unfixed on an iMac Pro running Mojave. Try again adoob. And enjoy my money in the meantime, isn’t it great?
We encounter this daily as well. Seems to be an OSX / Premiere problem. For example, when viewing the exported clip in Quicktime or on Vimeo in Chrome, Safari, and Opera, the colors are way off. When viewing the clip on VLC or the Vimeo app on a phone, the colors are fine. Don't know if this is Premiere talking to OSX or what exactly. Watching clips rendered from Resolve doesn't seem to have this issue.
We've dealt with the problem by adding an adjustment layer with a Lumetri fx and adding +7 to contrast and +12 to saturation. Then it's close-ish to what it looks like in Premiere, but watching in VLC or Vimeo app makes the over-saturation fix very apparent.
Basically adding tons of guesswork to the last stage of post :/
Thanks for all the feedback. It’s pretty clear that we’ve got to look into the workflow using this format more closely, there are enough reports about gaps at this point to reopen this item. I’ll post more info about next steps shortly. In the meantime, a couple of questions are easy to answer:
- The plugin is designed for Premiere Pro. It currently doesn’t provide support for After Effects.
- It does work with AME, so if you want to use it for batch processing, that’s very doable
- If you’ve started a project with Autokroma, there’s no easy way to transfer it to be running with the new plugin.
Yeah kinda not working Adobe, thanks for letting us be your testers! I've got a lot of spare time, so it's no problem.
Pretty much just rubbish playback in general in CCPP // Davinci demolishes PP in the playback dept.
All h264 encoded files play back choppy forwards and not at all in reverse in PP. Switch over to Resolve, the same files, the same computer, playback is 24fps smooth forwards and backwards.
Catch up adobe.
Yeah everything running much better for me now that I've reverted to 12.1.2 👌Likely won't go back to 2019 ever. I'll wait til their yearly release of 2020 to see if maybe they improve things (but they won't amirite)
Literally the worst. I've just advised my whole firm to roll back to 2018. 13.1.4 is such the worst. The worst update in the History of Software Updates. Worse than iTunes 11. And that's saying something. Does anyone at adobe even read these? Come at me
I’ve kept an old OS X mountain lion partition in order to keep using Encore / still have workflows that require DVD and Bluray....
And yes, it seems as though the metadata is the only label. In PP, when Show Audio Names is enabled, you can see the filename followed by A1, A2, A3 etc, whereas in Resolve, you can see the metadata name MixL, MixR, Boom1, Boom2 etc etc, which is much clearer. Another feature for some decades-in-the-future version of PP that already exists in other software;)
After Merge clips in PP, all the audio channels read as A1, which is the first indicator that something is amiss. Then when you look closely, you can see the waveforms are also all identical for each channel. Such a terrible bug that will seemingly never be addressed by Adobe... In fact, to test my exports to sound, I now export an XML from PP and import it into Resolve to check the labelling of my audio tracks.
Hi again Antoine // my exports to the sound department are XML, OMF and AAF, and even with copy entire audio files enabled, the metadata for the audio is gone.
Instead of the Merged clip feature, I just use timelines now and have all my sync'd takes in a row, rather than using bins with clips in the source window, which is a weird way to edit, but it saves hours and hours of pain down the line.
No one at Adobe seems to care about this crucial aspect of a "professional" workflow. Seriously going to jump to Resolve now with v16, but have to keep subscribing to Adobe for all my post-house's work. So I guess they have my money already, what do they care? ;)
Hi Antoine // when using Merge Clips in Premiere Pro (including the "latest and greatest" CC2019), the resulting outputs to the Sound Dept. are free from all sound-recorder metadata.
This makes Merge Clips a worse-than-useless functionality, as all sound departments require the metadata included from the field audio recorder to sort out their mixes. Oftentimes, wavs from the sound-recorder are supplied with multiple channels, for example, a wav with 8channels labelled MixL, MixR, Lapel1, Lapel2, Lapel3, Lapel4, Boom1, Boom2 (which one can see in Davinci Resolve, but not PP). After Merge Clips, all 8 channels read as MixL, and indeed, contain only the audio from MixL, making the outputs to the sound department unusable.
I solved this problem by reconnecting all the sound clips, for a feature film, by hand; match-framing from the cut to the source window and replacing the Merge Clip audio in the timeline. This process took days, for which I was not paid as it was "my fault" for using Merge Clips in the first place.
Merge Clips is a function I can never use, as my workflow usually includes handover to Sound departments and indeed, I tell all editors to never use it.
Nothing here about metadata loss. Would have been good to know 11 months ago....