Skip navigation

Choppy Multiclip

4095 Views 33 Replies Latest reply: Aug 6, 2012 2:26 PM by ujayank RSS
  • thrillcat editorial Level 4 Level 4 (3,840 points)
    Currently Being Moderated
    May 25, 2011 6:31 AM (in response to MagnusLekberg)

    You need to be factoring the combined data rate of all four clips, since they're all streaming off your drive at the same time to create the multiclip.

     

    I don't think your video card would cause this.

     

    Do you have thumbnails and waveforms turned on or off in your timeline?

     

    You mentioned that a multiclip created from 3 of your angles played fine. Have you tried creating that 3 angle multiclip with different combinations of your 4 angles? Perhaps one clip is simply corrupted and is choking your multiclip.

     

    Your system should handle this. Confusing.

  • Brian Conner Level 6 Level 6 (16,020 points)
    Currently Being Moderated
    May 25, 2011 6:59 AM (in response to thrillcat editorial)

    Also, make sure you do not have Video Scopes Playback selected in your timeline. If you must see the scopes during playback, leave Video Scopes Playback selected and select Limited Lines (fastest).

     

    The idea is to reduce the load as much as possible.

     

    Again, investigate the possibility that your Fusion DX800 has a drive that has gone paws up. If you're not sure how to do this, call Sonnet Tech Support.

  • Patrick Sheffield Level 7 Level 7 (29,175 points)
    Currently Being Moderated
    May 25, 2011 7:15 AM (in response to MagnusLekberg)

    The problem still sounds like a disk throughput problem...

     

    Remember, your RAID may be able to do that data rate from a single file, but with multiclip, you're reading from 4 separate files. That can involve considerable latency as the drive heads may have to be jumping all over the platters.

     

    Patrick

  • thrillcat editorial Level 4 Level 4 (3,840 points)
    Currently Being Moderated
    May 25, 2011 7:23 AM (in response to Patrick Sheffield)

    Jeez, Patrick, why the negative vibes?

  • BenB Level 5 Level 5 (7,535 points)
    Currently Being Moderated
    May 25, 2011 8:13 AM (in response to thrillcat editorial)

    I'd chop that Multiclip up into smaller sections.  An hour long Multiclip could be too much.

  • thrillcat editorial Level 4 Level 4 (3,840 points)
    Currently Being Moderated
    May 25, 2011 8:28 AM (in response to BenB)

    He mentioned that he has tried an approx 60 second 4 angle multiclip with the same issues. I've done 90 minute 6-7 angle ProRes multiclips without a problem.

     

    Magnus, how big is your project file?

  • Brian Conner Level 6 Level 6 (16,020 points)
    Currently Being Moderated
    May 25, 2011 8:36 AM (in response to Patrick Sheffield)

    Especially if the RAID 5 set is degraded due to a drive that's gone down. The OP still hasn't clarified if he's checked that.

  • Studio X Level 7 Level 7 (26,835 points)
    Currently Being Moderated
    May 25, 2011 2:59 PM (in response to Brian Conner)

    Brian Conner wrote:

     

    Especially if the RAID 5 set is degraded due to a drive that's gone down. The OP still hasn't clarified if he's checked that.

     

    I concur. I'd bet the external raid device is not playing up to spec.

     

    x

  • Patrick Sheffield Level 7 Level 7 (29,175 points)
    Currently Being Moderated
    May 25, 2011 5:13 PM (in response to Studio X)

    AJA Disk test should confirm his throughput...

     

    Patrick

  • Brian Conner Level 6 Level 6 (16,020 points)
    Currently Being Moderated
    May 25, 2011 6:13 PM (in response to Patrick Sheffield)

    Upthread, the OP says Aya Stem Test benches the DX800 at 650 MB/sec. But that array should be giving him something in the 800 MB/sec range. Sunds like 1 drive is down, which could create throughput problems beyond the raw data rate.

  • Brian Conner Level 6 Level 6 (16,020 points)
    Currently Being Moderated
    May 25, 2011 6:34 PM (in response to Brian Conner)

    Stem should be System (Aja System Test)

  • soundman1024 Level 2 Level 2 (205 points)
    Currently Being Moderated
    May 25, 2011 6:54 PM (in response to Patrick Sheffield)

    I agree with the thoughts about it being disc throughput related.

    If it worked with ProRes LT, but not with ProRes or ProRes HQ that seems to suggest that ProRes LT's lower bitrate is solving the multiclip problem.

     

    Perhaps you multiclip with LT, then reconnect to HQ?

  • Brian Conner Level 6 Level 6 (16,020 points)
    Currently Being Moderated
    May 25, 2011 6:59 PM (in response to soundman1024)

    I suggested that upthread, but I think the OP has left the building.

  • cineblue Calculating status...
    Currently Being Moderated
    May 25, 2011 10:44 PM (in response to thrillcat editorial)
    I've done 90 minute 6-7 angle ProRes multiclips without a problem.

    I'm curious, what quality were the ProRes? HQ? Were they 720 50p or superior? What was the data rate of those clips? What was your setup?

    It would be interesting for everyone to know. Because the OP's situation and question is pertaining to his particular setup and material, but in the interest of everyone reading, it would be interesting to know if it's possible to edit a hour long 4 camera show filmed in HD and converted to ProRes HQ on a MacPro like the OPs

    MacPro 5,1, 3,3 GHz 6-Core Xeon with 12 GB of RAM

    Perhaps the OP has left the discussion because he found that using  LT and Proxy he could edit the piece as I suggested upthread and for that he gave me the 5 points that I have since shoved up my bum.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.