Activity › Forums › Apple Final Cut Pro › Match frame not working in list view
-
Match frame not working in list view
Posted by Tom Brooks on July 1, 2011 at 1:12 amShift-F works as I want it to when Event Library is in Filmstrip view. I get a nice range selection on the clip in the Event Library. But when ELib is in List View, I get no range selection when I hit Shift-F. What am I missing?
Craig Seeman replied 14 years, 10 months ago 7 Members · 16 Replies -
16 Replies
-
Geoff Dills
July 1, 2011 at 1:34 amI thought was to do match frame. Your playhead in the event library will be parked on the match frame.
Best,
Geoff -
Tom Brooks
July 1, 2011 at 1:45 amYes, it does the match frame, but my Ripple tutorial says it should also select the same range in the clip. It’s not selecting a range. Unless I switch the Event Browser to Filmstrip view. Then Shift-F does the match frame and also selects the same range from in to out.
-
Jeffrey Carter
July 1, 2011 at 3:26 amWhen I click on a clip, hit shift-F, I get the range in the event browser clip and a line parked at a frame which should be the match frame but it’s off by a second.
So the range is there (in/out of the clip), a line is parked on a frame, but it’s arbitrary.
So I guess no match frame capabilities?
FCP 7 is so much easier…
-
Craig Seeman
July 1, 2011 at 3:34 amI’m finding this with some clips and not other.
I’m seeing a non matching frame with H.264 source but ProRes and DV sources works. I’m wondering if the issue is related to GOP codecs. What is the codec of the clip(s) you’re having this problem with -
John Spirou
July 1, 2011 at 9:57 amI dont have this problem, and i am working now with native canon – sony hdslr footage (h.264).
-
Geoff Dills
July 1, 2011 at 10:48 amReading the manual it says shift f locates the clip in the event browser….no mention of match framing.
Best,
Geoff -
Craig Seeman
July 1, 2011 at 11:39 am[john spirou] “working now with native canon – sony hdslr footage (h.264)”
Did you have it set to optimize in the background?
Just making sure that it might not have become ProRes while you weren’t’ looking.I vaguely remember something abode DSLR H.264 being different. It may be only I and P frame and no B frames. HDSLR H.264 has a higher data rate due to more inefficient encoding compared to AHCHD video coming from a video camera. I have a Canon HDSLR I should test this theory with. I’m currently mixing Vixia, EX, DV, ProRes, H.264 from Wirecast video in a timeline.
Reply to this Discussion! Login or Sign Up