Bug PrPro 2020: Export "Using Previews" not working
I have a timeline with several AE comps that I have rendered to the green status in GoPro 10bit
When I try to export an h.264 with the 'Use Previews' option the previews are ignored and AE is run in the background slowing down the export to a crawl, even thought I spent a lot of time rendering previews already. This is a straight export out of Premiere, not an AME export. This is a very typical workflow for a lot of projects and it's very frustrating that it's broken again.
- Create project with several Dynamic links in a timeline
- Render Previews for entire timeline in GoPro 10 bit(entire timeline is now green)
- h.264 Render
- Check use previews
- Export using Premiere....its going way going slower than it should
- Confirm in Task Manager that After Effects is using a significant %of CPU to render frames again instead of using the preview files.
Premiere Pro 2020
Intel i7 4770k (yeah I know I'm due for an upgrade)
RAM 32GB Ram
EVGA Nvidia GeForce GTX 1080 8GB
Preview files kept on scratch SSD
Project files on C:
Hopefully this can be addressed quickly its a real bummer.
Paul O'Brien commented
echoing the sentiment here. par for Adobe's course, what could be useful as part of a workflow requires a whole separate, additional workflow. That and it contributes to the ugly issue in my case that what I see is NOT what I get. My previews look good. My output looks ugly. I'm not doing anything special here, using vanilla h.264 files with dynamic link AE files, and the final outputs look horrible unless I output the after effect comps first, swap them in for the dynamic links, then output. So yeah. Sure some time is saved using dynamic links, right up until I need the project to be done and then it is NOT.
Richard Malmberg commented
exactly matched preview settings. Doesn't work. a timeline that renders in premiere with "render entire work area" takes 15 minutes or so. Same timeline takes 5 hours.
Korin Unka commented
The file format used in the preview needs to exactly match the export file otherwise it won't use the preview file.
fastest way if you have pre rendered out a project with the wrong file format is to use the export function using "match sequence settings" tickbox at the top of the export screen. this will take a minute to export. Open up media encoder, add the newly created clip to the queue and export it in the desired format. Basically it's a manual way of what probably premiere pro "use preview files" should have been built as. I'm suggesting to adobe that this is how the function should be used
This is still happening to me nearly three years later.
We've found a workaround: render your timeline, then change your project settings to Mercury Playback Engine Software Only. You can then export using previews to H.264 and other codecs as you would normally and get fast exports.
Then change your project settings back to Mercury Playback Engine GPU Acceleration to continue editing.
It's frustrating. Adobe please fix!
Richard Malmberg commented
Classic adobe. Break things in new versions that used to work. And by the way, it is not difficult for the computer to transcode into a new codec. If the render is already done by rendering previews then as long as the codec is of high quality such as ProRes then rendering to an H264 should not take that long. It's already done the processing of AE dynamic link and heavy effects, all it needs to do is convert to another codec. Still the best editing software we have available. Resolve for me is unreliable and doesn't play or render audio reliably. Unparallelled for color correction but not for a complete workflow.
Carlos Robles commented
I have the same issue, for at least 3 versions now. It used to work great. If I export at the same setting as my previews it works but if its any other format it re-renders everything.
Still having this problem nearly two years later. Would be nice if the checkboxes in this program worked reliably.
Joel Ferland commented
I have the same problem here (Premiere 14.9 on macOS).
When the timeline codec matches the export codec, it's fast using "Use previews", but when the export codec isn't the same, then Premieres doesn't use previews (which is more slow than just converting the source codec to the export codec, because it re-renders all effects too).
This problem is NOT present with Media Encoder, only in Premiere, so using it is a workaround for more speed.
Here are my results.
In Premiere 14.9 :
22 min. ProRes rendered timeline ==> ProRes file (using previews) : 2 minutes
22 min. ProRes rendered timeline ==> MXF file (using previews) : 40 minutes
In Media Encoder 14.9 :
22 min. ProRes rendered timeline ==> MXF file (using previews) : 15 minutes
Please fix this annoying issue.
Erik Parys commented
Ronald Hill commented
Yeah have run into this same issue. I've been rendering to ProRes and exporting using previews to avoid GPU render issues.
On export from Premiere, with "Use Previews" checked and the export settings matching my render settings and the entire timeline rendered - I still get a render error. if I send the sequence to Media Encoder with the same export settings it completes successfully.
It seems like at least occasionally Premiere is not using previews.
Peter Delahunty commented
My understanding is that you can only 'Use Previews' when the export codec is the same as the timeline rendering codec - so it doesn't have to re-render. You can't magically convert GoPro 10-bit to h.264 8-bit without rendering again.
Strangely enough, AME does do it correctly, but PrPro does not. So I guess that is the workaround for now.
This is a crucial workflow for things like quick turn-around sport. It's something I use a lot. Couldn't do F1 coverage without it.