-
Premiere 5.5 Exports contain crazy glitch in highlights
Hi everyone, I’ve been editing a project in Premiere Pro 5.5. The footage was shot on a 60D and then transcoded to DNxHD 145 before editing. I edited the first draft on a Mac and exported it as Prores. Everything was fine. I then brought the project to a PC (because I have an effects package on the PC that isn’t on the Mac) for the final edit and it’s giving me a strange problem. Whenever I export the sequence, the video has wild multi-color glitching in all the highlights. Not even just things that are overblown, everything over about 80 IRE is a mess.
The glitch doesn’t appear in the Output tab when I’m exporting. I have tried exporting straight from Premiere and from Media Encoder. I have so far tried MPEG2, H.264, and DNxHD all at 1920x1080p 29.97 square pixels as it should be with no success whatsoever. I’ve exported dozens of videos from this system with no trouble, but this is the first time I’ve used DNxHD, could that possibly be an issue? Like I said, editing and playback is smooth and fine, it’s just the actual exports. I supplied a picture of what the footage should look like and what I’m getting. I very much appreciate your help, I’ve never seen anything like this.
-
3 Replies
-
Looks like my pictures aren’t working – here are the direct links.
https://imgur.com/6ydz8
https://imgur.com/qzqUdI’m out of time today but tomorrow I’m going to attempt to import the sequence into After Effects and export it from there. Maybe that will fix it?
-
Linking the sequence to After Effects and exporting from there worked fine (and I tried DNxHD, MPEG2, and MP4), but I’m still hoping someone can shed some light on why exports from Premiere are suddenly so wonky.
-
Hi Ryan,
The artifacts you’re seeing relate to a bug in Premiere CS5.5 and the way it deals with the DNxHD codec above 24bit color depth.
The easiest solution for your situation is probably to have Premiere export picture with 24bit depth rather than 48bit, etc. This takes away the benefit of a 10bit per channel codec like DNxHD, but its the quickest fix.
The other solutions are to re-encode your DNxHD source material to something else or upgrade to CS6, which seemingly fixed this issue.
-mike
Reply to this Discussion! Login or Sign Up