Skip to main content
T
Thorsten D
New Participant
October 22, 2022
Question

Multicam sequences are not supported in FCP XML export !?

  • October 22, 2022
  • 2 replies
  • 1290 views

Hi! I'm trying to export a project into the FCP XML format. In the error-log the following is mentioned. Any idea/suggestion how to resolve this issue? Thanks in advance! Regards Thorsten

 

Spurenelement <103018 nex6.MTSMultikamera> wurde übersprungen, da Multikamera-Sequenzen im FCP XML-Export nicht unterstützt werden.

 

let me translate

 

Trace element <103018 nex6.MTSMulticamera> was skipped because multicam sequences are not supported in FCP XML export.

    This topic has been closed for replies.

    2 replies

    J
    Jason34398722vjsk
    New Participant
    January 31, 2024

    Argh... I ran into this same problem.  Multicam export to FCP seems VERY USEFUL.  And like an obvious feature.  I'm sure there is a way to get it to work in XML with a smart engineer determined to make it work.  (Where there is a will, there is a way.)

    R Neil Haugen
    R Neil Haugen
    Brainiac
    January 31, 2024

    XMLs and EDLs are rather 'ancient' text based forms for transferring "timeline" data. And yes, they have MAJOR, frustrating limitations.

     

    I work for/with/teach pro colorists, so "conforming" a job from Premiere or Avid into Resolve is a major Thing to learn. And The Rules are that no complex timeline work can make it successfully through an XML or EDL. 

     

    The Long Form/Episodic document that Jarle Leirpoll produced for Adobe a year or two back covers this pretty well.  "Complex" data that cannot survive transfer includes nearly all audio changes, video effects, multicam (sent "intact"), and color/tonal changes. Some sizing and speed changes might make it through.

     

    And so that's not a limitation of Premiere or Adobe's devs ... it's a limitation of the transfer systems themselves.

     

    Multicams must be flattened. Color corrections ... fuhgedaboudit. Audio sweetening? Don't kid yourself. Speedramps? Um ... just ... no.

     

    Which is why most colorists require a low-res H.264 output file of the sequence as part of the conform package of media and instructions. They put the H.264 reference on V2, run the XML or EDL on V1, and go down the sequence checking everything. Cuts, size changes, the right section of the clip ... all of that.

     

    Here's the most excellent long-form/episodic document ... 

     

    Adobe Long-form and Episodic Best Practices Guide 


    Jarle’s blog expansion of the pdf Multicam section: Premiere Pro Multicam

    Everyone's mileage always varies ...
    R Neil Haugen
    R Neil Haugen
    Brainiac
    October 22, 2022

    I'm a contributing author at MixingLight, a pro colorist's subscription teaching website. So XML/EDL operations to get from FCPx, Premiere, or Avid into Resolve are a constant item for discussion.

     

    And multicams are always listed as a no-no. The advice is to go back to the original app the program was in, dupe the sequence, flatten the duped sequence, then make the XML/EDL. No matter the app that the editing was in.

     

    Neil

    Everyone's mileage always varies ...
    T
    Thorsten DAuthor
    New Participant
    October 30, 2022

    Thanks for this statement ... so it seems to be a known limitation of Adobe Premiere Pro.

    R Neil Haugen
    R Neil Haugen
    Brainiac
    October 31, 2022

    It's actually a limitation for all NLEs ... multicams don't fit into the rather ancient XML or EDL formats.

     

    Neil

    Everyone's mileage always varies ...
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices