Premiere XML with working Motion

A new tool for bringing Premiere XML into Flame.

  1. Put
    z_xml2action_panel_EN.py
    z_xml2action_core_EN.py
    into /opt/Autodesk/shared/python
    Restart Flame, or rescan the Python hooks.

  2. In the MediaHub, right-click the XML
    → z Tools → “XML2Action: Prep XML (1-frame cut drift)”
    This writes _prepped.xml next to it
    (it fixes the one-frame cut drift on speed-changed clips).

  3. Import _prepped.xml (not the original), conform it and link the media.

  4. Select all the segments in the timeline, right-click
    → z Tools → “XML2Action: Apply Premiere Motion to Selected Segments”

  5. Point it at the same _prepped.xml and press Run.
    Tick “Dry run” the first time to write the .action files out and inspect them.

About offline/online resolution differences: the tool compares the proxy size written in the XML against the size of the image that actually reaches the Action (the Layer resolution), and puts the difference on a dedicated Axis called scale_fix.
Premiere’s own numbers stay on the original Axis, so you can still read them.

That should hold for any combination of resolutions. If the image comes in at the wrong size, switch “Scale reference” between native and frame by hand — it is auto-detected, and the detection is a heuristic that can occasionally be wrong.

z_XML2Action_EN.zip (50.4 KB)