Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Dropping frames on cuts?

  • Dropping frames on cuts?

    Posted by Charles Ferran on May 26, 2009 at 1:04 am

    in the master timeline I’m losing frames on the straight transitions, or cuts in my project, its driving me crazy because I can’t watch my timeline without it lagging, also playing in reverse using ‘J’ lags really bad too, any idea what the problem could be? everything is rendered, so its nothing that simple, thanks for all the help everyone.

    Also, just upgraded to new FCP 2 never had this problem before with the old FCP, hope this helps.

    Charles Ferran replied 17 years, 3 months ago 5 Members · 8 Replies
  • 8 Replies
  • Walter Biscardi

    May 26, 2009 at 1:10 am

    [Charles Ferran] “Also, just upgraded to new FCP 2 never had this problem before with the old FCP, hope this helps.”

    Without system details, it’s impossible to help. Most likely your hard drive array is too slow for the format you’re working with.

    Walter Biscardi, Jr.
    Biscardi Creative Media
    HD and SD Production for Broadcast and Independent Productions.

    Read my Blog!

    STOP STARING AND START GRADING WITH APPLE COLOR Apple Color Training DVD available now!

  • Charles Ferran

    May 26, 2009 at 1:31 am

    well, the reason I didn’t give them is I’ve never had this problem before, I’ve been working with FCP on this machine for years with no problems, I did recently upgrade the HD, its the same speed, just bigger, other than that, and upgrading FCP, I haven’t done anything different, also there’s nothing special about the format I’m working with, just standard H.264, I’ll list my specs now though:

    MacBook Pro
    2.33 GHz Intel Core 2 Due

    Mem: 2 GB 667 MHz DDR2 SDRAM

    and here’s my new HD:

    Seagate Momentus 7200.3 ST9320421AS 320GB 7200 RPM 16MB Cache 2.5″ SATA 3.0Gb/s Internal Notebook Hard Drive (Bare drive) – OE

  • Steve Eisen

    May 26, 2009 at 2:03 am

    I hope you understand that H.264 is NOT an editing codec.

    Steve Eisen
    Eisen Video Productions
    Board of Directors
    Chicago Final Cut Pro Users Group

  • Charles Ferran

    May 26, 2009 at 2:05 am

    well then maybe that is my problem, can I get a confirm of that if it is the case? just always worked with H.264 before, what would you suggest?

  • Zane Barker

    May 26, 2009 at 2:08 am

    [Charles Ferran] “can I get a confirm of that if it is the case”

    I confirm h.264 is a delivery codec and it is never recommended to edit in that codec.

    It is best to convert to a proper editing codec before editing.

    There are no “technical solutions” to your “artistic problems”.
    Don’t let technology get in the way of your creativity!

  • Bret Williams

    May 26, 2009 at 4:20 am

    You just updated FCP, so most likely the scratch disk reverted back to your system drive. Have you checked scratch disk settings?

    And no, you should not be editing with h.264. It usually grinds a system to a halt. Oddly, some people seem to be able to use it for a period of time. But usually we hear about it in a post like yours at some point.

  • Walter Biscardi

    May 26, 2009 at 11:08 am

    1 – others have already noted H.264 is not recommended for editing. Never has been.

    2 – you’re working off a single hard drive, not an array. That’s the slowest possible media playback system you could get. 2 to 4 drives striped together are the bare minimum I recommend for a media array.

    Walter Biscardi, Jr.
    Biscardi Creative Media
    HD and SD Production for Broadcast and Independent Productions.

    Read my Blog!

    STOP STARING AND START GRADING WITH APPLE COLOR Apple Color Training DVD available now!

  • Charles Ferran

    May 26, 2009 at 1:30 pm

    well thanks guys, now that I feel like a total ass, changed the sequence settings and seems to be running fine now, thought I was being smart when I changed them from DVCPRO to H.264 to match the source video’s codec, guess not, too far along in the project to re-export everything, may need to though, thanks everyone.

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