Premiere 2017 having to render after every edit

[nmbltgrr]

Why does every single edit I make, even just switching a layer on or off, a single frame trim to a clip, any change at all, require the clip to be rendered before it will play back? This is a new thing since updating to Premiere 2017. The sequence settings match the clip settings and I've never had any problems with the spec of my Mac being able to cope on earlier versions of PP. It's driving me insane!

[R Neil Haugen]

Not normal behavior ... so help us out.

OS/CPU/RAM/GPU/vRAM, the type, number, and connection of any drives used by the computer for PrPro projects/media/cache & etc., the type of media you're cutting, and the types of effects you've typically got applied to a sequence.

Neil

[nmbltgrr]

iMac (Retina 5K, 27-inch, Late 2014) running Yosemite 10.10.1

Processor 4Ghz intel Core i7

Memory 16 GB 1600 MHz DDR3

Graphics AMD Radeon R9 M290X 2048MB

I have two adjustment layers, both lumetri colour, one with just a saturation edit the other with a curves edit. Switching them on/off = render required. Delete the adjustment layers to see if it's them that's the issue = render required.

There is also a single JPG file with a saturation edit. Switch on/off - same thing.

Video clips layer - every single edit requires rendering. So even just trimming a single frame.

Everything was working fine until I accidentally upgraded to Premiere 2017. So what has changed with this version of the software that's causing this? Is it an OS issue? Thanks

[R Neil Haugen]

Is this across all projects, or only in this one project?

If you've only had this one in process, please create a new project, import one of the clips that's at issue, and apply the same Lumetri effects on that, and see if the issue still occurs.

I would note that in general, it works better if one does migrate a project 'forward' to create a new project in the new PrPro version, then using the Media browser, import the older project file ... rather than opening the older project file directly in the new PrPro and getting an auto-conversion. I of course don't know the process you used to bring that project into 2017.0.2 (which I presume is the version you're on now).

Neil

[nmbltgrr · Accepted solution]

So I've been on to tech support and it turns out my graphics card on my not actually that old iMac isn't compatible. So there is no fix. Three weeks of my life I won't get back eh. Thank you for trying to help though.

[R Neil Haugen]

Dang.

Neil