Skip to main content
Participating Frequently
January 31, 2023
Question

Video Previews not helping in render

  • January 31, 2023
  • 8 replies
  • 5525 views

I am using Premiere Pro Version 23.1.0 Build 86. When I do a final render, if I check use previews, this seems to have no effect. 

For example - I rendered a timeline with no pre-renders and it took approx 42 minutes.

Then, I pre-rendered the timeline with previews at Pro-Res 422 HQ and rendered again. Also 42 minutes. Both renders were to H.264.

Then I tried rendering the pre-rendered timeline to the same settings as the previews, Match source, Pro-Res 422 HQ, and it took 38 minutes (The timeline was 13 minutes long).

It would seem the use previews has no effect, or am I doing something wrong?

This topic has been closed for replies.

8 replies

Participant
January 25, 2024

Did anyone find a straightforward solution to this? 

I'm using Premiere Pro 2023 and working with MP4 H.264 4:2:0  4k footage.
My timeline is fully prerendered, 4 minutes on the timeline took around 8 minutes to prerender. 

Now when I try to export the video with "Match Source" and "use previews" and nothing else, it says estimated time is 8 minutes then it starts to climb up until it says 30 minutes estimated time.

I'm no expert whatsoever but it seems such a needless and trivial issue, since my previewed playback is running smoothly in 4k, I just need to get it on my computer and yet it wants to export nothing for 30 minutes. 



steveclarkefilms
Participant
November 15, 2023

I'm not sure if this will cure the problem for everyone but I have just been suffereing this same problem. Without really knowing what I was doing, I thought I'd experiment. I tried turning off the effects button in the export settings and 'Presto!!!' my render, which previously took around an hour, now renders in about 30 seconds!!

Even when there are no effects selected, if the button is on it makes the render super slow almost as if it is trying to apply a 'non effect'. I hope this works for you guys.

Ryan Fritzsche
Inspiring
November 15, 2023

Well if that isn't a bug, i don't know what is.  But good to know as a workaround.  Thanks for the insight, @steveclarkefilms.

steveclarkefilms
Participant
November 15, 2023

Thanks Ryan.

Pretty sure that button is on by default!

By the way,  the 30 seconds export was for a 3 minute 4K Prores sequence.

My machine specs are:

27" Imac 2020

3.8 GHz 8-Core Intel Core i7

AMD Radeon Pro 5700 XT 16 GB

64 GB 2667 MHz DDR4

Participant
August 29, 2023

Same problem here, I had a rendered timeline with Video Previews set to Quicktime Apple ProRess 422 HQ, requiring hours to export despite clicking on Match Sequence Preview Settings and having Use Previews checked.

 

Somehow changing the HDR Graphics White (Nits) export setting from 203 (75% HLG, 58% PQ) to 100 (63% HLG, 51% PQ) made the difference for me (a few minutes to export).

 

MacOs 12.5.1
Premiere Pro 23.5.0 Build 56.
Project Color Management:
- HDR Graphics White (Nits): 203 (75% HLG, 58% PQ)
- 3D LUT Interpolaion: Tetrahedral

R Neil Haugen
Legend
August 29, 2023

Would be good for @Fergus H to see and comment here.

Everyone's mileage always varies ...
Participant
May 1, 2023

I am facing the same issue on several machines (iMac 2020 Intel, I mac 2019 Intel, Premiere 2022 as well as with l´the latest Premiere 2023).

It is sooo frustarting! You finish your projects and have rendered everything for hours before then you hit the export button (use sequence settings with previews) and what happens, it will render again for hours! This is something which can`t be accepeted from a professional software provider. This  leads to real business problems! I want my money back!

Participating Frequently
February 8, 2023

I think the main frustration is that several builds ago, the exports were significantly faster when using previews. Now, and for the last 2 builds (at least) it is much slower. Using the same settings. And according to the official Adobe export best practices, if exporting using previews to the same format as the previews, it should take seconds. But mine takes as long (the exact same time) as if there are no previews.

R Neil Haugen
Legend
February 9, 2023

Yea  ... that's rough. Same rig I suppose also?

 

The variability of behaviors across the user base right now is kinda frustrating. Most are getting decent to good use, but some others are getting crud.

 

And while at times we peers can say ... oh, yea, try this instead ... and get people going ... some of this is just dang puzzling.

 

Neil

Everyone's mileage always varies ...
Participating Frequently
February 9, 2023

I understand it can be hard. So much easier if everone had the same rig with the same specs and we could chalk stuff up to user error (and it may well be, who knows). But yeah, it's the same rig I was using before.
I had a problem with InDesign too. And then all of a sudden, a new build came out and th eproblem disappeared. Never really heard anyone complaining about it, but it got fixed. Maybe this will happen in Premiere too!

Ryan Fritzsche
Inspiring
February 8, 2023

This is an ongoing issue for me, going back for numerous versions now.  I work in ProRes, render in ProRes, and check "uses previews" on export to H.264, meaning I want it to read the rendered ProRes files to encode to H.264, not go back to square one and re-render everything from scatch into H.264.  Yet it's obvious that it's doing exaclty what I don't want. This is an issue direct out of Premiere or via AME.  Seems like a #bug to me, and it's aggravating.  If I export into "same as sequence", then it's very fast, and then similar to what @RyanSchinneller said, encoding that ProRes file into H.264 is also super fast.  

Jeff Bugbee
Community Expert
Community Expert
February 8, 2023

Please take a look here: https://helpx.adobe.com/premiere-pro/using/bestpractices-export.html

 

Specifically, the "Smart Rendering of codecs" and "Accelerating h264/HEVC (H.265) output" sections.

R Neil Haugen
Legend
January 31, 2023

The use of previews requires of course that the Preview format/codec chosen on the Sequence is exactly the same as the export settings format/codec used, in all details. So that's the first thing to check.

 

Second, if any significant section of your timeline are not rendered with previews, those areas of course won't get any faster.

 

And from your post, unfortunately I can't be sure of what applies.

 

Neil

Everyone's mileage always varies ...
Participating Frequently
January 31, 2023

In the Sequence settings for Previews I choose Quicktime for the format, and for the codec ProRess 422 HQ

For the export I choose Quicktime for the format, click on Match Settings, then choose ProRes 422 HQ for the Codec. I also ensure Use Previews is checked. Is there more to look at to make sure they are the same?

Inspiring
January 31, 2023

Make sure that you did Not set/change/checked any other options on export page except Match Settings and Use Previews. Because any other change very likely will force rerender.

Jeff Bugbee
Community Expert
Community Expert
January 31, 2023

If the time it takes to export is the same as the render time, it's possible your bottleneck is elsewhere in your workflow. Where are you exporting? A fast internal SSD/NVME or an external device connected via USB?

Participating Frequently
January 31, 2023

Thank you. I am exporting to a SSD drive that is a different drive than the one the project is on.

I also may be confusing terms rendering and exporting. I have not timed how long it takes to pre-render the timeline. I tend to do that in chunks. But all the exports are timed by the program and recorded in the log, so I can see those.
So essentially what I am saying is exporting with previews or without previews takes the same amount of time.

Now, if I export to a ProRes 422 HQ file, then import that, then export that to H.264 then it takes around 4 minutes, vs. 42 minutes using previews that are supposedly the same (ProRes 422 HQ)

Participating Frequently
January 31, 2023

I forgot - the SSD is a fast internal, and the project is also on an internal SSD - but a different drive.