Premiere won't import the XML
When Premiere refuses the XML or the timeline comes in wrong — re-export first, then work down the list.
A Premiere export from Eddie should import with File > Import in a few seconds. If Premiere refuses the file or the timeline comes in wrong, work through this list.
The import fails outright
- Re-export from Eddie first. Premiere's XML import aborts entirely if anything in the file trips it. Older Eddie exports could be derailed by special characters like & in file names or paths, by an audio-only recorder (a dual-system WAV as a multicam angle) landing on a video track — that one showed an empty "File Import Failure" dialog — or could trigger a "Translation Report" dialog about audio crossfades on every import. Current exports handle all of these; a fresh export fixes files generated before the fixes.
- Check your file names. If your source media names contain unusual characters and a fresh export still fails, renaming the offending source file (and re-relinking) is a reliable workaround.
- Import into a new, empty project to rule out project-level corruption.
The timeline looks wrong
- Multicam appears as stacked tracks — that's by design. Premiere's XML format has no native multicam switching, so Eddie stacks the angles: your chosen angle on the top track, alternates below with muted audio. Delete or disable the spares, or use them to swap angles. See Multicam.
- Only one audio track came in. Premiere's XML import brings the primary audio track; Final Cut preserves all source tracks. See Export to your editor.
- Media offline? Relink: right-click the clips, Link Media, and point Premiere at the folder with your original files. Exports reference media by file name and path.
If none of that lands, email the XML file to hey@heyeddie.ai and we'll dig in.
Was this helpful?Two seconds, and it tells us what to rewrite.
Still stuck?Email hey@heyeddie.ai. A human reads every message. Cutting with a team or at studio volume? Talk to sales.