-
L&T jumpy playhead + conversion mismatch
Hi —
I’m using “Log and transfer” to capture footage copied from CX-305 and MC1P cameras onto a Firewire 800 external drive (copied the whole file structure). I’m using a MBP (pre-unibody 2Gig of RAM) and FCP 7.0.2.
It’s set to convert to ProRes 422, and most clips work fine, except on some, in the L&T control window, the playhead begins jumpy, I can’t really control where it’s set, if I click at a certain point, it can go a couple of minutes later (on a 45mn clip) or the end of the clip, and if I end up being able to set correct in and out points, then, the converted clip doesn’t match the selection.
I tried to find a solution here (or on Google) and couldn’t find a thread on this particular symptom.
Any idea?
May TIA’s.
— IG
-
7 Replies
-
I think I’d transfer the whole clip. Sorry don’t have a better answer, but when I run into things like this, I do whatever it takes to get past it.
Jerry
Apple Certified Trainer, Producer, Writer, Director Editor, Gun for Hire and other things. I ski. My Blog: https://blogs.creativecow.net/Jerry-Hofmann
Current DVD:
https://store.creativecow.net/p/81/jerry_hofmanns_final_cut_system_setup8-Core 3.0 Intel Mac Pro, Dual 2 gig G5, AJA Kona SD, AJA Kona 2, Huge Systems Array UL3D, AJA Io HD, 17″ MBP, Matrox MXO2 with MAX – Cinema Displays I have a 22″ that I paid 4k for still working. G4 with Kona SD card, and SCSI card.
-
Many thanks for your input, and the (radical) workaround.
I’ll do that if I don’t get a lighter solution.
— IG
-
In the log and transfer window, the computer is having to decode the native codecs of the camera your offloading the footage from… It’s a much more processor intensive workload than playing back files such as ProRes, which are optimized for editing in FCP. That is why your playhead is difficult to control and your footage is so stuttery. Your computer is also NOT ideal in the processor and memory department. I would either be do what Jerry said to do and transfer the whole clip, or (if your raw footage is long but the footage you need is short) be very patient with the computer and deal with it. It is not a bug per se, it’s just long GOP codecs…..
don walker
texarkana, texasJohn 3:16
-
what I meant by “dealing with it” is to wait for the computer to catch up with your keystrokes, and mouse inputs. If you are paitent with it you should be able to get the clips you need. Also (if possible) while your shooting, take careful time code notes of the segments you’ll need, and enter the timecode in the L & T window to set your in and out points
don walker
texarkana, texasJohn 3:16
-
Thanks for your input. I got your point.
The thing is that this only happens with (very few) specific clips, AND I just heard from someone else working for me on this on a recent iMac that they’ve been the same issue (namely the exported clip doesn’t match the one in the L&T window).Would this (cpu “shortage”) happen on one particular clip and not others?
Thank you again.
-
Sorry, I hadn’t seen your second post while I was typing my answer.
Actually, it’s not a matter of patience here, since on these clips only, clicking a hundred times to a specific point will get you to a random point (mostly located after the point where you clicked) whatsoever.
Thanks for reading.
-
An update, just in case this would ring a bell to someone.
First, this jumpy playhead symptom, when it appears, seems to mostly affect the second half of 30+mn clips.
Second, sometimes, the offset between the point clicked and where the playhead stops is nearly consistent : 20 seconds and 2 or 3 frames.
Looks weird enough. I converted the whole clip where needed, but I’m still a bit puzzled as to why this happens, on about 1 out fo 4 clips. Again, these are footage from SONY CX-305 and MC1P cameras.
FWIW.
Reply to this Discussion! Login or Sign Up