Visual export problem

[Back Edit Again]

Hello, I am exporting a finished edit.

Original file format: 1920 x 1080 55.13 fps MP4

Exported format: 1920 x 1080 60 fps H.264

I have also attempted exporting at various different frame rates and formats, I've also run it through Media Encoder to no avail. This is a frame from the export, the issue continues throughout the entire film.

Any ideas?

[R Neil Haugen · Accepted solution]

That sort of result is normally a GPU problem, most commonly a driver needing update.

What's your GPU? And if Nvidia, have you tried going to their support page and downloading and installing the latest Studio driver? PrPro tends not to get along too well with the "game-ready" drivers.

Also, looking at your first comment ... 55.13fps is not a normal camera frame-rate. So this is probably a phone or device capture, undoutedly "VFR" or variable frame rate. The camera records a constantly changing number of video frames per second as it sees a need (due to motion or other factors) against a constant audio rate. PrPro sometimes struggles with VFR media.

So at times, conveting the media to constant frame rate via either HandBrake or 

ShutterEncoder (both free utility apps) before importing into PrPro can fix issues due to VFR.

Neil

[Back Edit Again]

Thank you for the speedy response Neil, my GPU is a Nvidia GeForce GTX 1080 Ti. It did not have the latest studio drivers so I installed those, I also ran the latest update for PrPro which I accidently missed. Unfortunately the export result did not change. 

I will try and convert the media to a constant framerate and get back to you asap.

[Back Edit Again]

I conformed the original media to 60fps and another copy to 50fps using Shutter Encoder. Unfortunately when exported out of PrPro both versions had the same visual problems as my original attempts. Their audio was out of sync after the original conform but I'm not sure if that is relevant. 

The footage is of a live stream with not a very stable internet connection so it does seem like you are correct in thinking this footage has a variable frame rate. 

I exported a completely unrelated project from PrPro just to make sure it was definitely an issue with this specific project and that export didn't have any issues. 

I'm not sure what I should try now

[Back Edit Again]

This was in fact the solution in the end, it just took quite a lot of fiddling with the settings to get it to work. I used Handbrake and then a bunch of cave man work arounds to keep the cuts from the original edit. Thanks guys! 

[Sumeet Kumar Choubey]

Hi there,

Sorry to hear about this. Have you tried switching the Renderer to Mercury Playback Engine Software Only & checked if it's exporting properly?

Thanks,

Sumeet

[Back Edit Again]

Hi Sumeet, sorry for the delayed response, it was a good idea and I tried switching the renderer but unfortunately the export still has the visual problem. 

Something of note is that the visual error even appears in the export settings window before I've actually exported the footage.  

[nishu_kush]

Hi there,

Is there an onboard GPU? If so, try updating its driver. Here's a community discussion around similar issue: https://community.adobe.com/t5/premiere-pro-discussions/random-bars-appear-green-gray-black-in-previ...

Let us know if it helps.

Thanks,

Nishu

[Back Edit Again]

Hi Nihsu, Yes there is an onboard GPU, I've updated the drivers again but unfortunately the problem still persists. 

[Back Edit Again]

Update: I still have this issue, here are a few other things I've noticed that might maybe give us a clue as to what's happening. 

- When I set rendering to Software Only the un-rendered timeline looks normal but any rendered parts show the visual errors. 
- The problem occurs regardless of which renderer I use.
- Updating my studio and other drivers hasn't changed the export. 
- Changing the original file to a constant framerate hasn't changed the export

- I'm not sure which renderer I was using at the time of these errors but I have attached two images of problems I've run into trying to solve this.