Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro xml issue Premiere to FCP7

  • xml issue Premiere to FCP7

    Posted by Lewis Stiefel on April 24, 2013 at 4:56 pm

    Hello I just cut 2 different sequences in premiere then exported xml to fcp7…straight cuts
    no effects. One of the sequences translated ok but the other had all my shots with different
    in and out points. What happened to my other sequence? Thanks.

    Tim Kolb replied 13 years ago 3 Members · 14 Replies
  • 14 Replies
  • Tim Kolb

    April 24, 2013 at 5:17 pm

    Did you check to see if you have a text file that has any conversion errors? Did you compare the sequence settings?

    What type of media do you have? (format/frame rate/TC type)

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Ilya Osovets

    April 24, 2013 at 5:18 pm

    What version of XML did you export from FCP7?

  • Lewis Stiefel

    April 24, 2013 at 6:57 pm

    apple interchange format version 4. Thanks

  • Lewis Stiefel

    April 24, 2013 at 7:00 pm

    this is the error message i get

    Wed, Apr 24, 2013, 2:57 PM – Errors Found Importing SHINE WEDDING 2.xml
    project:children:bin:children:sequence:media:video:track:transitionitem – : Unknown element encountered.( line 28105 )
    project:children:bin:children:sequence:media:audio:track:transitionitem – : Unknown element encountered.( line 28239 )
    project:children:bin:children:sequence:media:audio:track:transitionitem – : Unknown element encountered.( line 28355 )
    project:children:bin:children:sequence:media:video:track:transitionitem – : Unknown element encountered.( line 54618 )
    project:children:bin:children:sequence:media:video:track:transitionitem – : Unknown element encountered.( line 55168 )
    project:children:bin:children:sequence:media:audio:track:transitionitem – : Unknown element encountered.( line 55503 )
    project:children:bin:children:sequence:media:audio:track:transitionitem – : Unknown element encountered.( line 55597 )
    project:children:bin:children:sequence:media:audio:track:transitionitem – : Unknown element encountered.( line 55712 )
    project:children:bin:children:sequence:media:audio:track:transitionitem – : Unknown element encountered.( line 55806 )

  • Lewis Stiefel

    April 24, 2013 at 7:04 pm

    All the footage is coming from same source HDV…what I don’t understand is why would one sequence
    translate perfectly from pp to fcp and the other sequence ( same settings ) would be so screwed up?

  • Tim Kolb

    April 24, 2013 at 7:09 pm

    I don’t see anything in the error doc that would cause timing inaccuracies…just transitions that didn’t translate.

    There is a difference someplace here…either between the two PPro sequences, or in how FCP is importing them.

    How did you create each sequence in Premiere Pro?

    Was the HDV material captured in PPro, or FCP? Is the material 29.97 or 25 fps (or JVC 720p59.94/50)?

    If it was captured in Premiere pro, did FCP then re-wrap the media to load it?

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Lewis Stiefel

    April 24, 2013 at 11:02 pm

    Hi Tim

    it does not make sense….import from 1 drive into PP….seq 29.97
    have 4 sequences same settings but one does not work??? I also
    tried putting everything on 1 track no effects no moves still this 1
    sequence has wrong in and out points. What do u mean by fcp re-wrap?

  • Tim Kolb

    April 24, 2013 at 11:17 pm

    [Lewis Stiefel] “What do u mean by fcp re-wrap?”

    FCP can’t use HDV native…it has to convert the file to a .mov

    So…I’m wondering if somehow Premiere Pro brought in the media native…but then FCP is having problems with/or converting the native files when you load the material into FCP?

    …though if all the sequences contain the same type of media, that is probably not the issue.

    Are you certain that the one sequence doesn’t have non-drop TC as opposed to drop-frame, or some other variation? There must be something…

    …if you copy one of the working sequences, and use that as a test and copy/paste the media from the problem sequence into it and attempt another XML export, does that fix it?

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Lewis Stiefel

    April 25, 2013 at 12:43 am

    Nice idea Tim….copied edit onto sequence that translated fine but still all footage ins and outs
    r wrong. All sequences have same settings

  • Tim Kolb

    April 25, 2013 at 4:09 am

    Damn…I was hoping that would fix it.

    Well, at this point it points to some factor in how the media is interpreted.

    Are all four sequences constructed from the same kind of footage? Are the same clips that are coming through with odd in/out points in the one sequence also included on one of the other sequences?

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

Page 1 of 2

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