Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Why the XDCAM clips didn’t come “transcoded” to PRORES ?

  • Why the XDCAM clips didn’t come “transcoded” to PRORES ?

    Posted by Fredy Schwerdtner on September 6, 2011 at 1:38 am

    Isn’t it better to work with Prores instead of native XDCAM codec in FCPX ?
    So, I’ve got some XDCAM EX3 material to be edited. I’ve did some logging and transferred to a folder (using Sony Tranfer) in my system disk. After that I opened FCPX, created a new event and import the clips (copying them) to my RAID disk. In Preferences I have checked to Optimize the clips but they didn’t come as Prores. Why ?

    thanks.

    iMac 2.7 GHz Intel 4 Core i5
    16 GB memory

    MacBook Pro 17″
    2.5 GHz Intel Core 2 Duo
    6GB 667 MHz DDR2 SDRAM

    OWC RAID 5 with 3TB
    (2) External HD LaCieMac (400/800 FW and USB)with 500GB -(2) USB External HD Western Digital (in cases) with 750GB
    OS X 10.6.5
    Final Cut Studio “3”

    Steve Connor replied 14 years, 8 months ago 3 Members · 6 Replies
  • 6 Replies
  • Steve Connor

    September 6, 2011 at 6:38 am

    They don’t need to be optimised,

    “My Name is Steve and I’m an FCPX user”

  • Craig Seeman

    September 6, 2011 at 8:22 am

    Basically the EX workflow has remain unchanged between FCP7 and FCPX.

    I believe Sony has promised plugin support (and they do have a plugin that allow import of the EX .mp4 without rewrap as does Calibrated Software for FCP7).

    The questions I’d have would be: will clips be joined using the BPAV metadata (.smi), will the optimize and proxy options work?

    If neither of the above were supported it would, ironically, mean AVCHD and H.264 .mp4 were better supported.

  • Fredy Schwerdtner

    September 6, 2011 at 12:33 pm

    Thanks to Steve and Craig,
    but just a little advice …
    At the end should I export as 422, 422 HQ , 444 ? Do I get any better doing that ? Or should I leave it in native codec wrapped in .mov ?

    iMac 2.7 GHz Intel 4 Core i5
    16 GB memory

    MacBook Pro 17″
    2.5 GHz Intel Core 2 Duo
    6GB 667 MHz DDR2 SDRAM

    OWC RAID 5 with 3TB
    (2) External HD LaCieMac (400/800 FW and USB)with 500GB -(2) USB External HD Western Digital (in cases) with 750GB
    OS X 10.6.5
    Final Cut Studio “3”

  • Craig Seeman

    September 6, 2011 at 12:54 pm

    I’m not sure if there would be a visual difference between 422 and 422HQ. It may well depend on what the rest of your chain is to the targeted destination. I’d think 422 is fine unless you’re looking at another round of heavy compositing or grading or theatrical presentation.

  • Fredy Schwerdtner

    September 6, 2011 at 1:18 pm

    Thanks Craig,
    For my client:
    What I know is that my client will use the final movie in a DVD and in his website (compressed).
    For me:
    I will need to do some composition with Motion. Since we don’t have anymore the “roundtrip” between FCPX & Motion, I’m still trying to figure it out the best workflow to insert some objects (pictures), text and clips (with alpha channel or created with masks).
    In the past we could select the clip in FCP timeline and send it to motion as a background reference for the job and after that decide if we want to let FCP to render or export from Motion and put the clip over in a upper track in FCP.

    greetings ….

    iMac 2.7 GHz Intel 4 Core i5
    16 GB memory

    MacBook Pro 17″
    2.5 GHz Intel Core 2 Duo
    6GB 667 MHz DDR2 SDRAM

    OWC RAID 5 with 3TB
    (2) External HD LaCieMac (400/800 FW and USB)with 500GB -(2) USB External HD Western Digital (in cases) with 750GB
    OS X 10.6.5
    Final Cut Studio “3”

  • Steve Connor

    September 6, 2011 at 1:23 pm

    ProRes is a very robust codec so going down a generation or two by importing the background into Motion won’t have any effect.

    Hopefully true roundtripping will return in a later version

    “My Name is Steve and I’m an FCPX user”

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