24
Spent 6 hours trying to fix a render glitch in Premiere that turned out to be a single corrupted frame from my Sony A7IV
I was checking every setting and cache folder under the sun before I finally used the project manager to open the sequence frame by frame and there it was at 00:04:23 just a black pixel line that took me longer to find than the actual edit itself, has anyone else wasted an afternoon on something this dumb?
3 comments
Log in to join the discussion
Log In3 Comments
emery1999d ago
A single dead pixel"? That is honestly INSANE. I would have bet everything I owned on it being something way more complicated, like a video driver glitch or a corrupted project file. The fact that it was just one tiny little black line in one frame is so wild it almost makes me mad. How are we supposed to troubleshoot something that specific? It's like finding a needle in a haystack where the haystack is made of needles.
7
lee.drew9d ago
You ever just stare at your timeline and feel personally attacked by a single frame? Because that's exactly where I was last month. I seriously considered enrolling in a wilderness survival course just so I could live off the grid and never have to troubleshoot Premiere again. But then I remembered I can't start a fire, so I just sat there and cried over a black pixel line instead. At least you found it in 6 hours, it took me two days and a full reinstall of Windows before I realized it was one frame of pink noise from a dodgy HDMI cable. I think my camera is just gaslighting me at this point.
2
Three hours in I was convinced it was a codec issue till I found a single dead pixel.
1