Skip to main content
Brit.b
Brit.b
Inspiring
July 4, 2017
Answered

Exporting 25fps to 24 FPS is choppy (and intermittent GPU export error)

  • July 4, 2017
  • 1 reply
  • 2772 views

When I export my video (compiled of clips 30 fps and animations rendered at 25 fps) at 24 fps it comes out much more choppy than if rendered at 25 fps. I need to submit it soon at 24 fps. (Though if its screened digitally with others of a different frame rates should it make a difference?) .

This is a  2 part question. This particular video rendered without a problem until I installed the latest version of Premiere last week. Now I get the following error:

However I did do one render that completed without this error... though I have tried again for several hours, with different variables to try to stop the choppiness, and it only worked once. Additionally if I render the section in question alone (the last section of about 30 seconds at 05:48:02 -05:48:20 on a clip that is using the Lumetri filter) it renders without a problem, as it does when I render the section before this. I updated the video card drive for a GTX 750 Ti and the problem continued - except for that one exception that I mentioned above. Any suggestions?

This topic has been closed for replies.
Correct answer Brit.b

Thanks for the tip!

I created a new 24 fps sequence, nested the original one, and change the timeline to "Optical Flow". I then went through and cut all transitions, and then changed these bits to "frame sampling" . It is now much smoother...but this process is time consuming.  Is such a script that disables Optical Flow just at transition points available for Premiere? That would save lots of time!

Also what to I do for the final render in the encoder? Do I pick "use previews", since the time interpolation has been frequently changed in the new sliced and diced timeline?  And what do I do for the time interpolation in the encoder - leave it at Frame Bending?

Turning off the GPU for rendering really slows things down - especially since it is now difficult to multitask as the rendering uses 100% of the CPU now. I hope Adobe fixes it soon.


I deleted a Lumetri color effect (that I had turned off and was no longer using) in a clip and the GPU error in AME disappeared. I'm still confused about how to output a sequence with multiple time interpolations ("render previews" ...and  then which time interpolation to chose in AME?) , so I started another thread on this subject.

1 reply

Vidya Sagar
Adobe Employee
Vidya Sagar
Adobe Employee
July 4, 2017

Hi Brit.b,

Please try the steps recommended in this article & let us know the status. How to fix issues that cause errors when rendering or exporting

Thanks,

Vidya.

Brit.b
Brit.bAuthor
Inspiring
July 4, 2017

Thanks. I turned the Cuda rendering off in the project settings, re-saved the file, and it successfully rendered. Of course I would not like to do that with all my files. This error only appeared last week with the update. I had rendered that file before several times (at 25 fps) without problems so it is clearly a new bug. I'm sure Adobe will fix it soon.

Regarding my first problem (the choppy playback when converting 25 fps to 24 fps), I just noticed today the drop-down menu in the media encoder for Time Interpolation. "Frame blending" worked OK, losing a little sharpness as would be expected, but it is acceptable. (However "optical flow" made the transitions just weird).

chrisw44157881
chrisw44157881
Inspiring
July 4, 2017

i made a optical flow scene detection script in after effects that disables optical flow just at transition points. I don't know why adobe doesn't make this a standard procedure. you may have to manual change it around edit points.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices