Unable to parse FCP XML file

  • Graeme Robinson
  • Graeme Robinson's Avatar
  • Offline
  • User is blocked
  • User is blocked
  • X2Pro Support
More
6 years 1 month ago - 6 years 1 month ago #302 by Graeme Robinson
Graeme Robinson replied the topic: Re: Unable to parse FCP XML file
Marth,

I think the best way for us to look into this is if we could get your project in font of us in our lab here. If I give you FTP details would you be able to upload:
  1. Your FCP X project files
  2. Your exported FCPXML for above project
  3. All accompanying media files used in the above project

It sounds like you might be able to recreate you problem using just a single clip, if so then it should be able to make this set of files quite small.

  • Please read the forum rules before making a new post.
  • Copy and paste the text from any error message. Please don't post screen grabs of X2Pro error messages.
  • Investigations into issues when converting a project will be faster if you attach your fcpxml file
  • If you are having trouble with X2Pro's "Media Locations" or the app sandbox, please read this explanation and guide for help.
  • If you seeing the error message "not a WAV file or too many audio channels", please read this explanation
Last Edit: 6 years 1 month ago by Graeme Robinson.

Please Log in or Create an account to join the conversation.

More
6 years 2 months ago - 6 years 2 months ago #301 by Marth
Marth replied the topic: Re: Unable to parse FCP XML file
I have a unique problem with this very same error Message. I am importing and editing transcoded XDCAM EX video files that are converted to Prores 422 files. No matter what I do, simply add a single clip with stereo audio, mono audio, or no audio at all into the primary storyline, it gives me this same error:

Invalid track number 2 referencing asset 2012-10-06 09:46:42 - a1

This happens if it is a compound clip, a single clip, with it's own imported connected audio, audio removed, or any configuration you can think of. I simply can not use X2Pro Audio convert to send my audio tracks to pro tools at all anymore. This is frustrating as i spent 100 bucks on a program that is now worthless.

Here are screen shots of the clip on the timeline, the error, the audio config for that clip.

Running OSX Lion 10.7.5
FCP X 10.0.6
Attachments:
Last Edit: 6 years 2 months ago by Marth.

Please Log in or Create an account to join the conversation.

  • Graeme Robinson
  • Graeme Robinson's Avatar
  • Offline
  • User is blocked
  • User is blocked
  • X2Pro Support
More
6 years 2 months ago - 6 years 2 months ago #296 by Graeme Robinson
Graeme Robinson replied the topic: Re: Unable to parse FCP XML file
If C300 clips are imported to an FCP X event using Canon's XF tool and FCP X 10.0.5, they will cause a problems when a project is exported as an FCPXML from FCP X 10.0.5 OR 10.0.6

This does not appear to affect C300 clips that were imported to an FCP X event using Canon's XF tool and FCP X 10.0.6.

If some C300 clips were imported using Canon's XF tool and FCP X 10.0.5, a more simple workaround than suggested below is:
  1. Leave the clips in the FCP X event, but move the mov files from the event folder on the hard disk to another folder (e.g. desktop). This should make all the clips in the event go offline.
  2. Relink all the clips in the event to the mov files in their new location
Once those clips are back online, an FCPXML export should work as expected and X2Pro will be able to process it.

  • Please read the forum rules before making a new post.
  • Copy and paste the text from any error message. Please don't post screen grabs of X2Pro error messages.
  • Investigations into issues when converting a project will be faster if you attach your fcpxml file
  • If you are having trouble with X2Pro's "Media Locations" or the app sandbox, please read this explanation and guide for help.
  • If you seeing the error message "not a WAV file or too many audio channels", please read this explanation
Last Edit: 6 years 2 months ago by Graeme Robinson.

Please Log in or Create an account to join the conversation.

  • Chris Steele
  • Chris Steele's Avatar Topic Author
  • Visitor
  • Visitor
6 years 2 months ago - 6 years 2 months ago #261 by Chris Steele
Chris Steele replied the topic: Re: Unable to parse FCP XML file
This message indicates that the fcpxml refers to more tracks in a piece of media than exist in the source file. This is a known issue in FCP X.

You can verify that the fcpxml is the cause of this problem, by loading the fcpxml back into FCP X and looking at the named media on the timeline. You will see that one or more of its channels are black. This indicates that FCP X cannot find that channel.

We have heard of this happening in particular with Canon EOS C300 files, but it may happen with other media files too.

The only solution appears to be:
1. delete the media described by <asset name> from the project,
2. import it again,
3. rebuild that part of your timeline,
4. re-export the fcpxml.

Doing so may then reveal another piece of media which causes the same problem. Unfortunately the only solution is to continue to deal with each one as described above until the fcpxml passes through X2Pro without a problem.
Last Edit: 6 years 2 months ago by Chris Steele.

Please Log in or Create an account to join the conversation.

  • Chris Steele
  • Chris Steele's Avatar Topic Author
  • Visitor
  • Visitor
6 years 2 months ago - 6 years 2 months ago #260 by Chris Steele
Chris Steele created the topic: Unable to parse FCP XML file
X2Pro produces an error message "Unable to parse FCP XML file" like the attached screenshot that ends with:

Details:
Invalid track number <track number> referencing asset <asset name>


Attachment ScreenShot.png.png not found

Attachments:
Last Edit: 6 years 2 months ago by Chris Steele.

Please Log in or Create an account to join the conversation.

Time to create page: 0.064 seconds
Powered by Kunena Forum