FCPXML Import not linking to PNG files on import

[tpayton]

When exporting a scene for Final Cut Pro X, the resulting FCPXML file does not properly open in FCPX.

Repeatability: Always

STeps to repeat:

1. Create a scene with several shots.
2. From the file menu choose "Export Scene for Final Cut Pro and Premier"
3. Reveal resulting FCPXML in the finder and drag onto FCPX.
   Results:
   Error message is shown.

Expected Results:
It works!

Analysis:
It appears that you are following the FCPXML specs exactly, according to this page (below) and yet it still doens't work. Frustrating. I'll do some futher research to see if I can discover what the issue is.

https://developer.apple.com/library/content/documentation/FinalCutProX/Reference/FinalCutProXXMLFormat/Resources/Resources.html

[audionerd]

I noticed there are spaces in the filename "storyboarder test 1". If you make a new Storyboarder test without spaces in the filename, would it work?

[tpayton]

That is indeed it! Works like a charm now. So looks like it just needs some encoding on the URLs. BTW. Tremendous job on this app. Thank you! - T.

…

On Sep 13, 2017, at 11:17 AM, Eric Skogen ***@***.***> wrote: I noticed there are spaces in the filename "storyboarder test 1". If you make a new Storyboarder test without spaces in the filename, would it work? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#659 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAWDLI0WM-vGVaZHXoeZGilWtTXdcCA-ks5siA4ngaJpZM4PWbul>.

[audionerd]

Fixed the bug. FCPX/Premiere export will now percentage-encode the urls representing the relative paths to the exported images.

Should be part of the Beta 12 release.

[audionerd]

I don't have FCPX so I'm not able to verify that this works. Could you try editing the "storyboarder test 1" .fcpxml file (the one with spaces) and editing the "src=" filenames to replace spaces with %20, then try importing? That would verify that this is indeed the fix we need...

Alternately, if you want to test this again when Beta 12 is released and report back that would be great 👍

[tpayton]

Unfortunately encoding the urls with %20 still produces the import error in FCPX. Puzzling because exporting a XML does encode it with %20 (see attached). For the time being perhaps replacing spaces with an underscore in the filenames would be the most efficient way to give a quick fix. - T.

…

On Sep 13, 2017, at 12:01 PM, Eric Skogen ***@***.***> wrote: I don't have FCPX so I'm not able to verify that this works. Could you try editing the "storyboarder test 1" .fcpxml file (the one with spaces) and editing the "src=" filenames to replace spaces with %20, then try importing? That would verify that this is indeed the fix we need... Alternately, if you want to test this again when Beta 12 is released and report back that would be great 👍 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#659 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAWDLIFZ73V7ZeMLijSvxncUY_I1tFLxks5siBhkgaJpZM4PWbul>.

[audionerd]

Could you attach your example XML directly to this GitHub issue?

#659

(GitHub apparently omits attachments sent via email)

[tpayton]

Unfortunately encoding the urls with %20 still produces the import error in FCPX.

Puzzling because exporting a XML does encode it with %20 (see attached).

For the time being perhaps replacing spaces with an underscore in the filenames would be the most efficient way to give a quick fix.

[audionerd]

In your example export from FCPX, how does the "src" line start? With a file://?

[tpayton]

I tried a few combinations. No workie. In fact I was able to get FCPX to crash! I sent off a bug report to Apple on that one. I also asked the FCP team for any insight on the relative paths with encoded spaces. (I worked there for a short time, they should get back to me soon.)

[tpayton]

BTW. Changing to underscores does work just fine in my tests. It might be the best solution for both Premiere and Final Cut.

[audionerd]

Added an issue to track replacing spaces with dashes in exported filenames: #730

[audionerd]

We'll convert spaces to dashes in the upcoming release, which should fix this issue.