-
Video Glitches in Blu Ray Projects – Premiere and Encore
Hello,
I have been using adobe Premiere for a couple of years now. I have had some off and on issues, but nothing I couldn’t usually figure out by reading forums. I have had one fairly consistent issue that has plagued me for the past year or so. I have issues with glitches in video, usually when I am burning longer projects in either SD or HD blu ray. What I mean by glitches is that the video seems to go back a couple of frames and then repeat which results in a sort of stutter motion. I do not have any subsequent issue with sound.
At times I am able to correct it simply by re-importing and re-transcoding my projects, but as you can imagine this gets time consuming and irritating. I thought the issue was due to the fact that I was using Encore to transcode my video. (I have read in a lot of forums that people suggest using Encore for as little as possible due to issues with the software). On my latest project (a 2 hour and some change blu ray) I decided to export from premiere to Adobe Media Encoder to take care of my encoding for me. After creating blu ray m4v and wav files, I imported into encore, set up static menus and chapter markers and built a blu ray image. I burned the blu ray image to disc using imgburn and once again I have glitches. I only found 2 or 3, but any is unacceptable.
I do not think that hardware is a problem, but here are my specs:
Intel Core I7 Extreme 980x 3.33ghz 6 core 12 thread processor Asus p6x58d premium x58 mobo 6gb OCZ triple channel memory Radeon HD 5750 video card.I shoot and edit in avchd in Adobe Premiere Pro CS4.
Any help/ideas anyone can provide on how to track down and resolve my problem would be greatly appreciated.
-
1 Reply
-
Sorry to necropost, but I’ve been encountering this exact same issue with Adobe Encore CS6.
There was one frame in our film where Encore seemed to have inserted one from an earlier point in the picture. I re-rendered three times and the problem came back each time. The ProRes422 we were using was flawless, so I chalked it up as an Encore glitch, but I wanted to know precisely where so I took some time to try to trace the problem.
Surprisingly, the problem wasn’t with Encore’s (or AME’s) h264 transcoding, but rather its M2TS muxing. I checked the cache directory and tested the H264 M4V Encore made, and it did NOT have the glitch. The glitch would only show up when Encore muxed the video and audio material into an M2TS file.
Ultimately, what I ended up doing was dropping our material into an Adobe Premiere timeline, dynamic-linking it into Encore, and then render. That thankfully finally worked. Unfortunately it sucks that I can’t have faith in Encore.
Reply to this Discussion! Login or Sign Up