Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Can’t play down sequence

  • Can’t play down sequence

    Posted by Beth Segal on May 10, 2008 at 8:07 pm

    I am having problems editing – I cannot play down my sequence without getting the following error message:

    One or more frames were dropped during playback.
    If this occurs frequently, try:
    Turning off Unlimited RT
    Lowering compression data rat
    closing Open seqs
    Lowering the pref for real time audio tracks
    Increasing speed of system.

    Here are some pertinent facts for trouble shooting:

    1. I am using FCP 6.0.3. and QT 7.4.5;
    2. My seqs are short and simple – no video fx, just some audio dissolves. 1-2 tracks of video, 8 tracks audio;
    3. System specs: 1.9 GHz Power PC G5, 1.5 GF DDR2 SDRAM
    4. All media on a Maxtor – 233 GB capacity only 164 GB on disk. Using 400 Firewire cable as I don’t have 800 capability on my G5.
    5. Media is a mix of P2 and SXS which is converted to XDCAM. I have NOT yet mixed the media (i.e. each format is it’s own seq with corresponding seq settings – mixing media may become an issue unto itself but is not yet the issue as formats are separated).
    6. I only get the message on the XD Cam EX seqs, not on the P2 seqs.

    Things I have done to try and remedy problem:

    1. Turned of Unlimited RT
    2. Limited # audio tracks to 8 for real time audio tracks
    3. Work with only 1 seq open
    4. Run disk utility on my system HD – all was fine.
    5. Got rid of tons of apps that I wasn’t using to clear up space for FCP
    6. Did not install entire FCP package (i.e. did not install FCP’s version of Protools).
    7. I took my media hard drive and project to a friend’s house to see if it worked on his system. He has the exact same set up as I do except he has 2.5 Ram on his system HD.

    I am really having a lot of problems editing as the error message comes up every 15 seconds or so. It seems clear that it is neither the project nor the media that is the problem but my system. But I cannot figure out what to do. I was wondering if the XDCam format is too hard for my processor to process. If this is so, I am hoping to avoid buying more ram as the feature I am working on is all deferred payment… you know the story.

    Any thoughts?

    Thank you and love your site,
    beth

    Rob Alexander replied 18 years ago 3 Members · 4 Replies
  • 4 Replies
  • Don Greening

    May 10, 2008 at 11:42 pm

    [Beth Segal] “7. I took my media hard drive and project to a friend’s house to see if it worked on his system. He has the exact same set up as I do except he has 2.5 Ram on his system HD. “

    How did that work out?

    [Beth Segal] “Using 400 Firewire cable as I don’t have 800 capability on my G5. “

    This might be part of your problem but keep in mind that the highest EX picture quality is 35Mbits per second, which is only 10Mbits more than MiniDV, so I don’t know if using just FW400 is all that important if you’re only trying to play back one stream of video. Playing back 2 streams might, though. What might be more of an issue is if you’re editing in the EX native codec which is pretty processor intensive because it’s MPEG2 long GOP. If your EX footage is also a full 1920×1080 then your graphics card may also play a part in the dropped frames issue (that’s just a guess).

    If you’re using DVCProHD for the P2 stuff then you can convert the EX files to that for editing, as that codec doesn’t use as much processing power as the EX long GOP stuff does. But then DVCProHD runs at 100Mbits per second as opposed to the EX at 35Mbits, so now you’re back to trying to play 2 streams of 100Mbit video from a FW400 hard drive. Not as processor intensive but FW400 transfer rate intensive.

    As far as getting the most performance from your existing G5 try using a tune up application like Cocktail on a weekly basis to keep your cache and log files cleaned out. Bloated log and cache files have a direct influence on programs like Final Cut and will slow performance of the program, especially when you’re trying to make do with your existing setup. 1.5G of RAM is just barely enough these days, what with the Leopard OS probably taking up almost half of that. I can’t remember what the minimum RAM requirements of today’s FCP is but I’ll bet you’re riding right on the edge.

    Can’t think of anything else at the moment.

    – Don

  • Beth Segal

    May 11, 2008 at 2:40 am

    Hi,

    A few answers to your questions:

    1. When I took my media and project to a friend’s house, the project worked fine which is why I ruled out any problems with project/media. Just an assumption which could be wrong? He had a whole gig more of Ram than me, otherwise it was the same system. He also had more apps on his OS than I did….

    2. The P2 footage specs are:
    960 x 720 23.98 fps DVCPRO HD 720p60

    The SXS footage specs are:
    1280 x 720 23.98 fps XDCAM EX 720 p24

    The SXS footage is already converted to XDCAM EX as I could not figure out how to import the original natively. And finally reminder that I have not yet mixed these different formats in the same seq and am still having problems but only with the XDCAM. Might need some guidance on importing the SXS as DVCPRO HD as I had to drag the footage into my browser as all the options for Log and Transfer for the SXS were grayed out (i.e. not available).

    3. I will try Cocktail as I have never cleared out my cache or even thought to do this and get back to you. But maybe the rest of the info will shed some light?

    thanks,
    beth

  • Don Greening

    May 11, 2008 at 3:25 am

    [Beth Segal] “Might need some guidance on importing the SXS as DVCPRO HD as I had to drag the footage into my browser as all the options for Log and Transfer for the SXS were grayed out (i.e. not available). “

    You don’t need to re-import the footage to change the EX files to DVCProHD. Just drop the EX stuff into a DVCProHD 720p sequence. If you create a new sequence with this codec FCP will ask if you want to change the sequence settings to match what you’re dropping into it. Just say no.

    Or you can drop the EX footage into the same sequence with your existing DVCProHD footage. FCP will play both back in the same timeline, although the EX footage will have a green render bar because it hasn’t actually been changed to DVCProHD yet. But once you render everything out it will be changed/transcoded into DVCProHD.

    – Don

  • Rob Alexander

    May 11, 2008 at 3:14 pm

    Beth,

    from what you describe you ARE editing the SxS natively – the SxS is the card, XDCAM EX is the format.

    You don’t mention whether you’re using any video cards (blackmagic/AJA etc). If you are I’d suggest uninstalling the drivers then reinstalling. Also trying to play your sequences with external video off to see if it makes a difference. You should try trashing your FCP preferences too.

    The suggestion to drop your EX footage into a DVCPRO HD sequence will work as long as you render all the clips, if you’re still editing then you’re going to be rendering every time you make a change and will end up with a huge amount of render files. Leaving the clips unrendered will likely INCREASE the load on your processor. However to convert your EX clips to DVCPRO HD you should select them and then use media manager to transcode to DVCPRO HD, then work in DVCPRO HD sequences. As stated before, the demands on your FW400 connection will be higher but seeing as you’re using DVCPRO HD from your P2 cards without issue should be OK.

    RAM does look like the probable cause of this though.

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