Copy link to clipboard
Copied
I've searched far and wide trying to find the right search term for this problem, so hopefully, someone can help! As I'm editing and making adjustments to videos. Randomly, one or two frames out of a clip have some contrast and exposure adjustments are done to them (no keyframes or anything like that). Sometimes I can fix it by deleting all render files and then re-render from in to out or the whole sequence.
So far I've been able to somehow get around it, but it's a crazy frustrating issue to continually stumble into. And YES, it does export this way, so I constantly have to make sure the entire timeline is acting normally before I'm able to export any project.
2017 iMac Pro
3.2 GHz Intel Xeon W
32 GB 2666 MHz DDR4
Radeon Pro Vega 56 8176 MB
Premiere Pro CC Version 12.1.2 (Build 69)
Any input would be greatly appreciated!
Here is an example of crazy added contrast. There are no keyframes in play...first part is the original footage/look, the second half happens out of my control.
Curious question ... are the preview/cache/media cache database files also on the RAID or internally?
You could test as to whether that RAID makes a difference ... make two exact same small projects, one with the project on the RAID as currently done, the other with project files and cache files all internal (but leave the media on the RAID).
See if it happens both ways.
Neil
Copy link to clipboard
Copied
What's the original media?
Neil
Copy link to clipboard
Copied
This happens on footage from both my 5D Mk IV as well as the 1DX Mk ii.
So Canon DSLR H.264 MOV files. Shot in FHD ALL-I
Copy link to clipboard
Copied
All-I, so they're intraframe media. Huh.
If you go into Project settings and set Mercury Acceleration to Software Only, does it still happen?
Neil
Copy link to clipboard
Copied
I can give that a try. Looks like it slowed down rendering by quite a lot. Not sure which is worse.
Copy link to clipboard
Copied
Yea, I know. But ... if going to software only fixes the issue, there's a GPU/driver issue then. At least, we'd have identified where to go further.
Neil
Copy link to clipboard
Copied
First render through with that setting changed seemed to work. I realized something...I believe any projects this has happened on have been stored on a RAID device (linked below). Could that be affecting it?
Copy link to clipboard
Copied
Curious question ... are the preview/cache/media cache database files also on the RAID or internally?
You could test as to whether that RAID makes a difference ... make two exact same small projects, one with the project on the RAID as currently done, the other with project files and cache files all internal (but leave the media on the RAID).
See if it happens both ways.
Neil
Copy link to clipboard
Copied
I tried this on a project on a different Lacie drive that stores all the footage and then project files -- with my Premiere Pro handling the Media Cache Files and Database locally in my User/Library/Application Support folder locations.
Noticed the render still doing the same thing at random times. Same as before, I can delete the render cache and re-render within premiere and it seems to clear it up...for now. Then it will randomly re-surface.
Copy link to clipboard
Copied
Dang.
That's just a killer for delivering work. Something is screwing up there. The next release was previewed a week ago, so we're in a window of I'd guess one to six weeks until it is 'dropped'. Maybe that will finally cure this for you.
Wish I had a better solution!
Neil
Find more inspiration, events, and resources on the new Adobe Community
Explore Now