Skip to main content
F
fiinale
Participant
March 26, 2018
Answered

Premiere Pro CC 2018 Import Green Glitch/Render Error

  • March 26, 2018
  • 2 replies
  • 3256 views

This only started recently. Whether I preview or drag a clip into Premiere, the video comes out extremely glitched and tinted green, and the issue occurs when I hover over the video preview too:

I use MP4 files, but changing to MPG hasn't worked. Changing the resolution and other factors don't work either. Trying to render also results in this error:

The clip run perfectly fine when viewing them separately, only glitching in Premiere. I've opened up projects I've made before which had exported normally and they're glitched out now too.

Yesterday I uninstalled my graphics driver and reinstalled an updated version, but the two are exactly exactly the same and I got the new version off the official website. I feel like this might be linked to the issue, but it doesn't really make sense because the two drivers are essentially the same.

I really need help - I run a channel and I largely depend on Premiere to edit my videos. Does anyone have a solution?

    This topic has been closed for replies.
    Correct answer fiinale

    Found the solution: Turns out it was the driver. Rolling back to the previous one restored it.

    2 replies

    P
    pointblank223
    Participant
    March 28, 2018

    So what drivers are you speaking of the drivers for the program or your video card drivers? Because I am having the same problem and it's just started recently so what do I need to do what drivers do I need to update?

    F
    fiinaleAuthor
    Participant
    March 29, 2018

    Video/Graphics card driver - I think I might've updated to an incompatible version. If you recently updated the driver trying rolling it back.

    L
    LinnightL
    Participating Frequently
    May 11, 2018

    Same issue after Intel graphics driver update in March - I rolled back to earlier version. April Windows update pushed the new Intel driver out again and problem came back - once again I rolled back to 2017 driver to fix the issue.

    F
    fiinaleAuthorCorrect answer
    Participant
    March 26, 2018

    Found the solution: Turns out it was the driver. Rolling back to the previous one restored it.

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