"Unable to Parse" or "Error Opening asset"

  • Jeremy Norwood
  • Jeremy Norwood's Avatar
  • Visitor
  • Visitor
9 years 2 months ago #2507 by Jeremy Norwood
Jeremy Norwood replied the topic: "Unable to Parse" or "Error Opening asset"
We apologize for the troubles you are having, but fundamentally we cannot resolve an issue where the XML created by your FCPX can give an asset description which makes no mention of having audio but later audio items refer to this asset or the audio item is missing the ref attribute which links the audio to an asset.

The root cause of the problem would appear to be clearly an issue in the creation of the XML in FCP. We have reported this to Apple and they have requested that users report this issue directly to them, so that they can investigate and resolve.

It is unfortunate that you have experienced this issue and we can understand why you would want a refund. The application itself is sold through the App store and as such you will have to go back to them to request a refund and they will oblige.

Once again we do hope you can raise this issue with Apple and we will continue to provide as much support as we can if you want to continue to use the product.

Please Log in to join the conversation.

  • mcbrat
  • mcbrat's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
More
9 years 2 months ago #2506 by mcbrat
mcbrat replied the topic: "Unable to Parse" or "Error Opening asset"
Hi Jeremy
X2Pro is clearly not working as intended. Please let me know how I can obtain a refund.
Thank you
S

Please Log in to join the conversation.

  • Jeremy Norwood
  • Jeremy Norwood's Avatar
  • Visitor
  • Visitor
9 years 2 months ago #2462 by Jeremy Norwood
Jeremy Norwood replied the topic: "Unable to Parse" or "Error Opening asset"
My apologies for not doing this from the beginning, but i searched your entire XML for assets that were listed as not having audio, but then had audio references later in the timeline part of the XML and was able to find 6 clips including the "r498" file that your error message returned.

If you can check these clips and removing them and re-edit it back into the timeline and that should fix the audio referencing at least.
ZOOM0019_Tr1
A015_C029_01223T
A021_C002_1008FP- which I believe is used multiple times in the timeline.
A001_C012_0930XY- which I believe is used multiple times in the timeline.
A001_C020_093096- which I believe is used multiple times in the timeline.
A011_C009_1005X8

Let me know how everything turns out.

Please Log in to join the conversation.

  • mcbrat
  • mcbrat's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
More
9 years 2 months ago #2459 by mcbrat
mcbrat replied the topic: "Unable to Parse" or "Error Opening asset"
Hi Jeremy

Thanks for that. The problematic clips you mentioned were the first and second in the timeline, respectively. I've now completely removed all of the video, but I am still getting an error message. Here is the latest:

Unable to parse FCP XML file to obtain project information

Details:
Getting asset with Id r498
Unable to find asset with Id r498
Suggestions:
- Ensure that the file is not locked by another application and is readable;
- Ensure that this is a valid FCP XML file from a released version of FCP X;
- Ensure that this is the export of a Project, not of a Library or Event;
- Ensure that this is not an empty project (or that all audio is disabled);

The new XML has been attached.

Cheers
Stu
Attachments:

Please Log in to join the conversation.

  • Jeremy Norwood
  • Jeremy Norwood's Avatar
  • Visitor
  • Visitor
9 years 2 months ago #2452 by Jeremy Norwood
Jeremy Norwood replied the topic: "Unable to Parse" or "Error Opening asset"
Seems to be the same problem as the last with the clip named "A050_C001_0201DP".
If you try removing that clip and re-editing it back into the timeline and see if that resolves the matter.

Please Log in to join the conversation.

  • mcbrat
  • mcbrat's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
More
9 years 2 months ago #2449 by mcbrat
mcbrat replied the topic: "Unable to Parse" or "Error Opening asset"
Hi Jeremy

Thanks for your reply. I replaced the problematic clip with filler, but it is still refusing to parse. I have attached the new XML, and have posted the error message below:

Unable to parse FCP XML file to obtain project information

Details:
Getting asset with Id r12
Unable to find asset with Id r12
Suggestions:
- Ensure that the file is not locked by another application and is readable;
- Ensure that this is a valid FCP XML file from a released version of FCP X;
- Ensure that this is the export of a Project, not of a Library or Event;
- Ensure that this is not an empty project (or that all audio is disabled);

If you are able to create a usable AAF file, please feel free to attach it.

Thank you!
Attachments:

Please Log in to join the conversation.

  • Jeremy Norwood
  • Jeremy Norwood's Avatar
  • Visitor
  • Visitor
9 years 2 months ago #2448 by Jeremy Norwood
Jeremy Norwood replied the topic: "Unable to Parse" or "Error Opening asset"
In your FCPXML from the 10.2.1 version of FCP, the problem with your XML is fairly simple.
In the Asset information for the file "A048_C015_02016X" is does not list that it contains any audio channels or components. However, when it comes to referencing the files in the timeline part of the XML, it references audio components or channels that it has never mentioned before.

If you could remove the "A048_C015_02016X" clip from your timeline, then re-edit it back in and re-export your project and see if that resolves your issue.

If it does not, please let me know and we can try to hand edit the XML to include the reference to the audio that the video clip must have.

Please let me know how you get along.

Please Log in to join the conversation.

  • mcbrat
  • mcbrat's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
More
9 years 3 months ago - 9 years 3 months ago #2444 by mcbrat
mcbrat created the topic: "Unable to Parse" or "Error Opening asset"

File Attachment:

File Name: POP-UP-X2P...l.fcpxml
File Size:5,892 KB

Hi there

Having exported the fcpxml from FCP 10.2.1, I receive the following error message when attempting to convert with X2Pro:

"Unable to parse FCP XML file to obtain project information

Details:
Getting asset with Id r9
Unable to find asset with Id r9
Suggestions:
- Ensure that the file is not locked by another application and is readable;
- Ensure that this is a valid FCP XML file from a released version of FCP X;
- Ensure that this is the export of a Project, not of a Library or Event;
- Ensure that this is not an empty project (or that all audio is disabled);"

I have attached the file: "POP-UP - X2PRO (current xml).fcpxml".

Suspecting that my recent upgrade to FCP 10.2.1 might be causing the problem, I have attempted a conversion using an archived XML which was created with a previous version of FCP. In this case, X2Pro at least started to parse, but it keeps aborting, citing errors in individual media files. This occurs despite my selection of the "Embed the media, optionally trimming" option in Media Handling.

One of many similar error messages is listed below. "SOUNDEDIT.fcpxml" attached.

"Writing AAF file
Adding assets to AAF file
Adding essence for asset [ZOOM0016_LR] to AAF file
Opening audio extractor for portion 0 of asset [ZOOM0016_LR]
Failed to open audio extractor
Error Opening asset (/Volumes/G-RAID with Thunderbolt/POP-UP___LIBRARY.fcpbundle/FULL EDIT/Original Media/ZOOM0016_LR.wav) with QuickTime (The operation couldn’t be completed. (OSStatus error -208.)) [-208] [was not type AIFF or was of bad format,corrupt]

Suggestion: Please ensure that:
- the media file has not been moved or deleted;
- you have added its location to the Media Locations in preferences;
- the media file can be played using QuickTime player.

No AAF file has been generated."

I have noticed that many troubleshooting suggestions on this forum involve manipulation of media within the FCP timeline itself. So if possible, I would like to use the file generated using 10.2.1.

If using the older xml is easiest, I would like to skip problematic media files, rather than have the conversion stop altogether.

Thank you!
Attachments:
Last Edit: 9 years 3 months ago by mcbrat.

Please Log in to join the conversation.

Time to create page: 0.058 seconds
Powered by Kunena Forum