Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Why is rendering XDCAM 422 as slow as Molasses in a SD timeline.

  • Rafael Amador

    April 8, 2010 at 6:46 pm

    [Andrew Kimery] “I’d change your sequence’s compressor settings from ProRes HQ to regular ProRes as that should decrease the render times”
    Why should be faster?
    More compression, more time to accomplish (with quality).

    [Andrew Kimery] ” of the formats you listed would take advantage of the higher bitrate HQ needs. “
    Sorry but that is not like that.
    Every single format/size will take advantage.
    Is just a matter of maths.
    Read the Prores White Papers.

    [Arnie Schlissel] “Rafa, isn’t the 220Mbps from the Nano all I-frame? “
    Yes.
    Up from 160 mbps is only I-frame.
    I’m waiting to get a MP mostly because the GPU of my MBP is to short for working 1920 and rendering in 10b, but not issue due to being the footage LGOP.

    Cheers
    rafa (wish to be Nadal)

    http://www.nagavideo.com

  • Peter Corbett

    April 8, 2010 at 8:14 pm

    Yes Andrew that helped a bit. Still slow but faster then HQ.

    Peter Corbett
    Powerhouse Productions
    http://www.php.com.au

  • Andrew Kimery

    April 8, 2010 at 8:17 pm

    I did a quick test and 1 min of XDCAM EX 1080p30 footage rendered in a ProRes 422 sequence took about 10% less than time than the same clip in a ProRes 422 HQ sequence. Not exhaustive testing by any means, but there it is.

    I have read the ProRes white papers and I’ve also read numerous posts referencing Gary Adcock’s test results about when ProRes HQ makes a difference and when it does not.

    -Andrew

    3.2GHz 8-core, FCP 6.0.4, 10.5.5
    Blackmagic Multibridge Eclipse (6.8.1)

  • Peter Corbett

    April 8, 2010 at 8:23 pm

    [Steve Connor] “Is it just me that doesn’t have any problems with it then? I edit with XDCamHD 422 material every day and I have no issues, I always use ProRes timelines and I find rendering out isn’t any worse than when we used to use DVCPro100.”

    That would work fine with me as well Steve, but in this case I’m editing a mixed SD timline of XDCAM 422, DVCPRO50 abd HDV. The answer is as many suggested, to downconvert non-tape media through Compressor to SD first. But I have found Compressor crashes if you load more than 25 or 30 clips, so that is a workable but PITA solution. I’m in the middle of the job now, so I’ll stumble through to the end now. I have a “new” Varicam H arriving next week, so even though I’ll be on tape, I know it will integrate well in mixed timelines edits. Thanks to all who chimed in on this issue.

    Peter Corbett
    Powerhouse Productions
    http://www.php.com.au

  • Rafael Amador

    April 9, 2010 at 2:30 am

    [Andrew Kimery] “I did a quick test and 1 min of XDCAM EX 1080p30 footage rendered in a ProRes 422 sequence took about 10% less than time than the same clip in a ProRes 422 HQ sequence. Not exhaustive testing by any means, but there it is.

    I have read the ProRes white papers and I’ve also read numerous posts referencing Gary Adcock’s test results about when ProRes HQ makes a difference and when it does not.

    Which tests are you talking about?
    Quick tests and sporadic observations means nothing.
    If you want to know how a codec should be tested, see the work of Marco Solorio.
    Your work may be very creative, but your tools are pure science.
    rafael

    http://www.nagavideo.com

  • Andrew Kimery

    April 9, 2010 at 5:26 am

    [Rafael Amador] “Which tests are you talking about?
    Quick tests and sporadic observations means nothing.
    If you want to know how a codec should be tested, see the work of Marco Solorio.
    Your work may be very creative, but your tools are pure science.
    rafael “

    I was referring to the write up about ProRes that Gary Adcock did.
    ProRes: A Closer Look (it’s the first hit). If you have problems w/the methodology talk to Gary not me.

    In Gary’s tests ProRes ran smoother than ProRes HQ, in my admittedly casual test ProRes rendered faster than ProRes HQ and the OP said that ProRes rendered faster than ProRes HQ. I don’t need to use the scientific method in order to look outside my window and say whether or not it’s raining.

    -Andrew

    3.2GHz 8-core, FCP 6.0.4, 10.5.5
    Blackmagic Multibridge Eclipse (6.8.1)

  • David Roth weiss

    April 9, 2010 at 5:43 am

    [Andrew Kimery] “I was referring to the write up about ProRes that Gary Adcock did. ProRes: A Closer Look (it’s the first hit). If you have problems w/the methodology talk to Gary not me. “

    They’ve actually had several talks on this subject, but Rafael continues to tout Pro Res HQ come Hell or high water despite Gary’s attempts to dissuade him. Rafael is very stubborn on this one particular issue for some reason.

    David Roth Weiss
    Director/Editor/Colorist
    David Weiss Productions, Inc.
    Los Angeles

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    EPK Colorist – UP IN THE AIR – nominated for six academy awards

    A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, Indie Film & Documentary, and Film History & Appreciations forums.

  • Rafael Amador

    April 9, 2010 at 6:56 am

    [Andrew Kimery] ” I don’t need to use the scientific method in order to look outside my window and say whether or not it’s raining. “
    Right.
    That way you can know if its rains in your place, but the world is bigger than that.
    rafael

    http://www.nagavideo.com

  • Andrew Kimery

    April 9, 2010 at 8:50 am

    [David Roth Weiss] “They’ve actually had several talks on this subject, but Rafael continues to tout Pro Res HQ come Hell or high water despite Gary’s attempts to dissuade him. Rafael is very stubborn on this one particular issue for some reason.”

    I’ve noticed.

    -Andrew

    3.2GHz 8-core, FCP 6.0.4, 10.5.5
    Blackmagic Multibridge Eclipse (6.8.1)

Page 3 of 3

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