[Chris Borjis]

There are certain corrections using lumetri tools that can do that.

try checking or unchecking the HDR box and see if it has any affect.

[Chris Borjis]

I can answer that.

To get around the 2gb limit, you have to choose “external files” instead of “embedded”
in the omf export dialogue.

The problem then, is you have to open it in Audtion then export another .omf

Pro Tools will then be able to find the externally linked files. This has been a bug
in omf export in premiere for a VERY long time (back to CS versions) and just
today I posted a question to adobe about why they don’t fix that.

oh and the latest version of Audition now needs help to find the first file
when opening the omf….thats a new bug in 2017.1.1

[Chris Borjis]

I have very fast pci express direct connected raid storage
to a 2009 mac pro with 32gb of ram and an NVIDIA GTX 670 gpu.

From my experience I can say I’ve never had full res 4k playback smooth unless it was a single track
with no f/x applied.

You’d likely need the massively faster speed of an SSD raid to get reliable smooth full
resolution 4k playback in premiere.

[Chris Borjis]

What about deleting everything except the titles.

Then save as a new project.

Then import that project with only the titles in the other project?

[Chris Borjis]

2017.0.2 is the new release today isn’t it?

I too am a holdout on 2015.0.2, will be watching this thread.

[Chris Borjis]

[Jon Doughtie] “You’ll always want to transcode anything variable frame rate (like anything recorded on iPhones with the native app) to a codec with a fixed frame rate.”

Ran into that recently with a live stream captured webinar.

Oddly media encoder CC 2015.2 will not fix that for a transcode,
but using apple compressor 3.5 to transcode does.

[Chris Borjis]

[Dave LaRonde] “Yeah, I’ve never even heard of a Ryzen CPU. Since you mentioned that this started when started running it, I’ve been wondering about that.

It may be cheap (don’t know), but I don’t think it’s great for Adobe applications.”

It reminded me way back in the days when I was a pc tech, it was either the AMD K5 or K6 cpu
could not run the then current version of photoshop.

Good to know AMD has put that in the past.

[Chris Borjis]

I have to second the thought that you really shouldn’t have to transcode h.264
I haven’t had to transcode anything since going from fcp 7 to premiere cs 5.5
The only footage that ever slows me down is Red4k these days.

I have an early 2009 mac pro with raid storage, 32gb of ram and
an old GTX 670 and CC 2015.2. Thing cuts h.264 like a hot knife through butter.

Have you tried lowering the program window resolution?

Maybe do a google search of premiere cc editing with the new Ryzen cpu?

[Chris Borjis]

wow that is tiny.

I just did a 68 minute DCP and it clocked in at 28gb.

But i don’t use wraptor either.

[Chris Borjis]

Is it set for OpenCL or CUDA acceleration?

I would switch to OpenCL if it is currently CUDA or vice versa (something to try)
I had awful lag with 1080p AVC multicam with CUDA but switching to OpenCL solved it.

There was some buggy cuda stuff going on recently.

If that does nothing try disabling mercury transmit if it is enabled.
That might help too.

Nice system by the way!