[Chris Wright]

I think it was pretty much the same one; old architecture with low clock speed.

Ok, I’m going to suggest a few “tweaks” to premiere pro so NO promises; this stuff is floating around adobe and it helps some people. So as after a boiler plate disclaimer(because this could possibly break adobe software), here I go:

some more ways to “hopefully” get premiere from “lagging”:
19. Changed Audio Hardware from MME to ASIO.(lower level audio driver for lower latency)
20. Limited Premiere’s RAM allocation to 32Gb if you have 64GB
21. In task manager, set affinity to utilize only 16 cores for PP (unfortunately, this setting does not hold on

re-launch)
22. Turned Hyperthreading off in BIOS.
23. in bios, disable Intel Speedstep.
24. disable C1E – in the bios, power settings,change to performance.

25.
– go to CTRL+F12 inside premiere and find these settings:
– DisableSpeculativePrefetching – set this from false to true
– ImporterMXF.ReadBlockSizeinKB: default is 1024. Experiment with this.. I’m trying 2048 with good results
– CodeProfiler – set to true
– GPU.EnableGOPFormats: set from false to true
– Player.MainMaxOutstandingAheadofPlayback=3
– Player.MainMaxQueuedFrames=10

The above two can make a difference. Higher values if you’re working 60P rates.

if you’re interested in an editing system, I’m going to tell you a little secret,
the intel 4790k (overclocking) processor is the same speed as a brand new skylake 6700k for premiere pro.
https://www.pugetsystems.com/labs/articles/Haswell-vs-Skylake-S-i7-4790K-vs-i7-6700K-641/

with a 4x pci3 M2 slot mobo, you can run a samsung 950pro and get over 1500 MB/sec transfer speed

that’s why we needed to know the video codecs you’re using, because I’m talking 4k full debayer systems for $1,000
which means HD systems would be a fraction of that.

[Chris Wright]

aw the old junky Nehalem series. edit in SD 🙂 it might actually be slower than what you have now, lol.

2008 Nehalem (you’re here)
2008 Bonnell
2011 Sandy Bridge
2013 Haswell 14
2015 Skylake 14

[Chris Wright]

and some more:
– limit Premiere to use only 7,9Gb of ram
– go to CTRL+F12 and find these settings:
– DisableSpeculativePrefetching – set this from false to true
– ImporterMXF.ReadBlockSizeinKB: default is 1024. Experiment with this.. I’m trying 2048 with good results
– CodeProfiler – set to true
– GPU.EnableGOPFormats: set from false to true
Try tweaking some of these settings, I hope the performance increases.

Player.MainMaxOutstandingAheadofPlayback=3
Player.MainMaxQueuedFrames=10

The above two can make a difference. Higher values if you’re working 60P rates.
https://forums.adobe.com/thread/1583049

[Chris Wright]

alt click stopwatch to edit and paste expression into timeremapping area.

https://helpx.adobe.com/after-effects/using/time-stretching-time-remapping.html

[Chris Wright]

enable timeremapping to output each to its own comp with this formula. use n=1 or n=2 for each comp.

-modified from Dan Ebbert’s code:

n = 2; // skip every nth frame
frameToSkip = 0; // 0,1,2 …n-1
currFrame = Math.round(time/thisComp.frameDuration);
currFrame += Math.floor((currFrame – frameToSkip)/(n-1)) + 1;
framesToTime(currFrame);

[Chris Wright]

After effects is not that bad at color management. I’d say it gets a bad rap because its so complicated. and a lot of times, its the codecs and video players that place the blame back on adobe. You COULD do a bunch of technical color mumbo jumbo, but if you just want a passthrough with preserved RGB unchanged, its easy, just don’t turn on color management in the first place!

Besides, if you don’t have 64 cube luts, or large enough profiles etc., you’ll actually get artifacts from lower quality color transforms. With color management off, AE acts as a passive device for your display’s profile which is usually sRGB or Rec. 709.

here’s a more technical reason why colors clip.
https://ninedegreesbelow.com/photography/icc-profile-conversion-clipped-colors-examples.html

[Chris Wright]

x.264 and h.264 both in there at the same time… can you pre-render them with DnxHD and see if the problem still exists?

[Chris Wright]

if its only a few frames, you could use this

https://aescripts.com/pt_framerestorer/

you’d be surprised how well you can hide stuff with optical motion.

[Chris Wright]

if you have premiere cs 6.0.1 or later, you can use smart rendering which will stream copy the codec without re-compressing.

https://blogs.adobe.com/kevinmonahan/2012/10/11/smart-rendering-in-premiere-pro-cs6-6-0-1-and-later/

[Chris Wright]

it might be the flickering adjustment layer bug. can you apply effects to an adjustment layer or to layers directly?
are you using leave color effect?
it looks like the transition effect is causing it. can you apply it to adjustment layer or directly to clip?

-try pre-rendering a small section with media encoder to prores or DnxHD before importing into premiere.(just to be codec safe)

-try turning sequence settings on to maximum bit depth and maximum render quality
-composite in linear color
-export media, video tab – render at maximum bit depth renderer(CPU) to DnxHD with a small test

you might need to contact adobe tech team and have them remote in to fix it. This is an adobe bug I think.
https://helpx.adobe.com/tech-comm-suite/customer-support.html

there is also a content forum team here that is user to user based, but adobe ocassionly pops in.
https://forums.adobe.com/community/premiere/content