Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Mark Out is offset by one frame

  • Ken Pugh

    October 19, 2008 at 10:06 pm

    Actually, here’s another….

    Mark in, use make edit command, move forward 4 frames, use make edit command, delete the cut section you have made, how many frames have gone…. 4!

    So how can it be logical to the simple mind of an editor (especially one that came from film) that when you move forward four frames from an in point, the technique from my previous email (mark in and out) deletes 5 frames while this technique deletes 4?

    I know the argument goes that the make edit command is cutting on an in point in both cases, but what are the rules that says that the cursor cuts on a different frame depending on whether it thinks it’s an in point or an out point? Certainly my film splicer did not make such presumptions under my firm and unwielding grip, try as it might….

    And come to think of it I’m sure my old and trusty Media 100 system did not work this way, maybe not all NLE’s have this ‘quirk’.

    Anyway, rant mode off. I’m on assignment sitting in a hotel in Dakar with not much else to do – posting when I should be listening to Mbalax at some groovy nightclub. Sad but true. But I do enjoy this fine forum.

    Best,

    Ken.

  • Sven Bogard

    April 2, 2009 at 6:50 pm

    it is funny how people response to serious questions. You are all WRONG! My FCP is having the same issues since TODAY! I was writing on the wrong keyboard and must have triggered something in FCP 6. Suddenly, the out-point is NOT where the playhead sits atm (which indeed is and should be normal behaviour) but one frame to the right. For all of you who are to ignorant to understand:

    ….|O…
    ….|….
    ….|….

    Legend:
    | = playhead
    O = outpoint

    Before I hit some stupid shortcut, it was like this:
    ….O…..
    ….|…..
    ….|…..

    See, how the outpoint is created just where the playhead resides? So please, if someone would tell an experienced, three years user of FCP, how I could undo this stupid shortcut …

    sb

  • Kevin Smack

    April 29, 2009 at 8:08 pm

    Sven,

    Did you ever resolve this issue? I am having the same problem with marking my out point. I encountered this problem once before and then it mysteriously went away. However, now it’s back and I need to get this resolved.

  • Kevin Smack

    April 29, 2009 at 9:08 pm

    Sorry for the mess of replies, but I think I understand the issue more fully now. As it was explained to me, the FCP playhead sees the beginning of a frame, but when you set an out point the marker is placed at the end of the frame. Therefore, you won’t see the out point marker on the same spot as the playhead but you will see it on the in point marker. I hope this clears up any future confusion, as I found myself scratching my head at some of the previous responses.

  • Erika Wagner

    July 23, 2010 at 6:10 pm

    Ok I am having the same problem, it seems like I turned a setting on… Either that or I need further explanation cause it makes no sense to me that I can’t cut at a desired point.

    Look at this screen cap… The darker area ahead of the timeline marker needs to be turned off. HELLLLLP lol

    [IMG]https://i1037.photobucket.com/albums/a459/t3gproductions/Picture1.png%5B/IMG%5D

  • Tim Seley

    December 9, 2010 at 4:38 pm

    Same problem here.

    – – – –
    I like to make music and give it away at newmusicmonday.com

  • Adam Sonnenfeld

    December 9, 2010 at 6:53 pm

    So after a couple of years since making this post originally, and developing more as an editor, I’ve realized that it’s not a problem, it’s how it should be, and I’d have it no other way. It’s frame inclusive, how else could you mark an in and an out at the playhead, and have 1 and not 0?

    Just remember to back off a frame and mark your out. Make it reflex. You’d have so many more problems if it was an exclusive out point.

Page 2 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy