Skip to main content
davescm
Community Expert
Community Expert
July 7, 2017
Question

Premiere CC2017 unloading video card LUTs

  • July 7, 2017
  • 1 reply
  • 416 views

Hi
I have a strange issue with the latest Premiere CC2017 and Windows 10. I am not sure whether it started with the recent Windows creator update or the recent PPro update as both happened in the same week.

I have an AMD7970 3GB card with three monitors. Each is calibrated and profiled with i1Pro and windows loads the calibration data to the video card LUTs on start up. All is well in Photoshop and the set up used to work well in PPro.

However I now find that if I enable playback on a second monitor (in Preferences > Playback > Video device) , on pressing the spacebar to play a sequence the video calibration LUTs are unloaded resulting in an immediate colour change on every monitor. Reloading the LUTs in Windows holds until next time playback is attempted.

Disabling playback on the second monitor and playing back only in the Program monitor works fine. However it is convenient to see a full screen playback, so I would like to get this working.

Any insight would be appreciated.

Dave

    This topic has been closed for replies.

    1 reply

    davescm
    Community Expert
    davescmCommunity ExpertAuthor
    Community Expert
    July 22, 2017

    No-one else had this issue, or can offer any insight?

    Dave

    Legend
    July 23, 2017

    About the only thing I can think to suggest is to use a proper I/O device for external monitoring rather than the GPU.  Something like the Intensity from Blackmagic or the T-Tap from AJA.

    davescm
    Community Expert
    davescmCommunity ExpertAuthor
    Community Expert
    July 23, 2017

    Hi Jim

    Thanks for responding. I realise that using the second/third GPU monitors in Premiere Pro was not the intended way . My primary use is Photoshop and Illustrator, hence that set up.

    It used to work in the older version of Windows 10 and with the last version of PPro. I hoped I was missing something in the settings, it looks like I was just lucky with those versions and I'll have to try a separate I/O device.

    Dave