Unable to parse
- Graeme Robinson
- Visitor
9 years 9 months ago #1915
by Graeme Robinson
Graeme Robinson replied the topic: Unable to parse
The clip is there when I convert your fcpxml (see attached pic).
What is in that place on the timeline when you convert it and open it in Pro Tools? Is it just a gap?
What is in that place on the timeline when you convert it and open it in Pro Tools? Is it just a gap?
Please Log in to join the conversation.
- Dominique
- Topic Author
- Offline
- Fresh Boarder
Less
More
- Posts: 13
- Thank you received: 0
- Graeme Robinson
- Visitor
- Dominique
- Topic Author
- Offline
- Fresh Boarder
Less
More
- Posts: 13
- Thank you received: 0
- Graeme Robinson
- Visitor
9 years 9 months ago #1909
by Graeme Robinson
Graeme Robinson replied the topic: Unable to parse
Is the clip disabled in your FCP project?
Are the audio tracks for the clip disabled in your FCP project?
Do the clips have audio tracks (not video only)?
Perhaps you could attach your new fcpxml and tell me the name and time code of a clip that is not in the AAF?
Are the audio tracks for the clip disabled in your FCP project?
Do the clips have audio tracks (not video only)?
Perhaps you could attach your new fcpxml and tell me the name and time code of a clip that is not in the AAF?
Please Log in to join the conversation.
- Dominique
- Topic Author
- Offline
- Fresh Boarder
Less
More
- Posts: 13
- Thank you received: 0
- Dominique
- Topic Author
- Offline
- Fresh Boarder
Less
More
- Posts: 13
- Thank you received: 0
- Graeme Robinson
- Visitor
9 years 9 months ago #1895
by Graeme Robinson
Graeme Robinson replied the topic: Unable to parse
The fcpxml seems to have some invalid information in it. There are a few clips that are described as having 1 track with 4 channels but in the project section it says that you have used channel 1 from tracks 3 and 4.
We have come across this before, but we're not sure how it happened. I think perhaps they were imported using Cannon's XF plugin...
The only way we know of fixing this is to make the clips offline in FCP X by moving them and then re-linking to them in their new location. Make sure you backup your project and media before doing this. After the re-link you can exporting a new fcpxml and see if X2Pro will process that.
We have come across this before, but we're not sure how it happened. I think perhaps they were imported using Cannon's XF plugin...
The only way we know of fixing this is to make the clips offline in FCP X by moving them and then re-linking to them in their new location. Make sure you backup your project and media before doing this. After the re-link you can exporting a new fcpxml and see if X2Pro will process that.
Please Log in to join the conversation.
- Dominique
- Topic Author
- Offline
- Fresh Boarder
Less
More
- Posts: 13
- Thank you received: 0
- Dominique
- Topic Author
- Offline
- Fresh Boarder
Less
More
- Posts: 13
- Thank you received: 0
- Graeme Robinson
- Visitor
- Dominique
- Topic Author
- Offline
- Fresh Boarder
Less
More
- Posts: 13
- Thank you received: 0
- Graeme Robinson
- Visitor
- Dominique
- Topic Author
- Offline
- Fresh Boarder
Less
More
- Posts: 13
- Thank you received: 0
9 years 9 months ago #1887
by Dominique
Dominique created the topic: Unable to parse
Hi i have this pb for my export and i don't understand what is it could you please help me my project have to be online for monday and the mixing is waiting for me
Unable to parse FCP XML file to obtain project information
Details:
Invalid track number 3 referencing asset Auto-detected stereo
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);
Unable to parse FCP XML file to obtain project information
Details:
Invalid track number 3 referencing asset Auto-detected stereo
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);
Please Log in to join the conversation.
Time to create page: 0.064 seconds