Liz Parham
Forum Replies Created
-
Thanks, Paul.
I did adjust the dslr sequence setting to match HQ codec, but it seems I didn’t for the output settings.
Plural eyes still exports a sequence that isn’t the right setting, but I can copy the sequence and paste into one that is correct.
-
PS I also used PluralEyes, which exports its own xml into Premiere. I assumed those sequences would match the sequence settings set in Premiere, but maybe not? Oye, my problems usually start at PluralEyes.
-
True, but I also transcoded everything to HQ via mpeg streamclip ahead of time in order to edit with Premiere/FCP. I know you can edit h264 in PPro, but we found it easier to just have the HQ files already so we would’t have to deal with an offline/online workflow.
-
Sry, editing in Premiere Pro CS6 using the DSLR sequence preset.
-
Did you ever figure this out? I’m stuck in a similar situation + nobody seems to be responding.
-
Thanks for clarifying!
-
DId a test sequence and most of the clips matched up with the same timecode except for one…kind of strange. We have about 1,000 clips in the timeline oye! Thanks for the help. Nick’s response seemed useful to try except that it alters the original clips..I’m usually worried about anything that’s destructive.
-
I figured SanDisk would be the best but maybe I should switch to Lexar? No guarantee really with any if these cards despite stellar reviews. My camera does tend to overheat more than usual but it didn’t during the speech. Starting the new year with the mark III so hopefully I’ll have better luck.
-
Only uncorrupted video files play back when card is reinserted. One of the TH^ shows 1.2 gigs sooo there was something on that. No battery problems, I didn’t record for over 12 minutes but it was definitely around 7-8 and the longest I continuously shot because it was the most important speech out of all the ones that were captured correctly. oye! I’m in the process of working with Treasured who have recovered the file miraculously. Just wondering if it’s my camera/card..or If I should look into it further to avoid it happening again. The firmware wasn’t updated soo that could be it.
-
Thanks, Todd! Your videos were really helpful.