- Posts: 244
- Thank you received: 12
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
XML and footage provided. XML works but can't connect media.
- Doug Suiter
-
Topic Author
- Offline
- Elite Member
-
2 problems:
1) FCPX won't search for media recursively. I was under the impression fro Alex4D's post that there is now... "Much better relinking of missing files. Select the parent volume or folder and Final Cut will now search all sub-folders until it finds the correct files". Searching a folder just comes up with nothing even thought there is definitely the correct file(s) within the folder structure.
2) when I go into the file structure and manually select the correct footage it throws up an "Incompatible Media: Error: The original file and new file have no shared media range. Relinked files must have the same media type and similar audio channels as the original files, and must be long enough to cover all the clips that reference the files.
The footage is definitely correct. Any thoughts on either issue?
Please Log in to join the conversation.
- Andreas Kiel
-
- Offline
- Platinum Member
-
- Posts: 1077
- Thank you received: 189
- Andreas
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
- Ronny
Please Log in to join the conversation.
- Andreas Kiel
-
- Offline
- Platinum Member
-
- Posts: 1077
- Thank you received: 189
I think that's the "solution".
- Andreas
P.S.
Doug you can send me the XML and can try to make "metadata clean up"
Please Log in to join the conversation.
Please Log in to join the conversation.
- Doug Suiter
-
Topic Author
- Offline
- Elite Member
-
- Posts: 244
- Thank you received: 12
Instead now I have black clips. I can relink these in FCPX and they do not throw the incorrect media error, but the clips simply remain black.
It looks like this:
If I drag the same R3D file in from the finder, no trouble at all:
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Please Log in to join the conversation.
- Doug Suiter
-
Topic Author
- Offline
- Elite Member
-
- Posts: 244
- Thank you received: 12
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
FCP X 10.1.2 looks for compatible media anywhere on any connected drive. If it finds compatible media it will point to the correct folder no matter how deep this folder is inside other folders.
When it does not see any compatible media on any drive (as in this case) it is quite logical that it will not point you to any folders and it will ask you to manually select compatible media.
Tom is correct that recreating an new XML with the media that has been corrupted by Pr will not solve the problem. You might take up Andreas' offer and send him the original XML so he can see if he can fix this. Only an XML wizard can sort this out. Adobe's XMP is :evil:
- Ronny
Please Log in to join the conversation.
- Doug Suiter
-
Topic Author
- Offline
- Elite Member
-
- Posts: 244
- Thank you received: 12
Please Log in to join the conversation.
- Andreas Kiel
-
- Offline
- Platinum Member
-
- Posts: 1077
- Thank you received: 189
Just out of curiosity, could you try the below little app and let us know what happens.
I will simply remove all metadata from the PPro XML and save a new one at "/modXML.fcpxml"
In case it works that could be a simple solution for other people who run into the problem as well.
- Andreas
dl.dropboxusercontent.com/u/63959366/mdRemove.dmg
Please Log in to join the conversation.
- Doug Suiter
-
Topic Author
- Offline
- Elite Member
-
- Posts: 244
- Thank you received: 12
Please Log in to join the conversation.
- Andreas Kiel
-
- Offline
- Platinum Member
-
- Posts: 1077
- Thank you received: 189
I was assuming you used 7toX to get the xml into FCP X. So you should have an fcpxml file somewhere.
Make a copy of it and open that one with the app. In an blink of an eye all metadata inside the file are removed and the fcpxml is saved. Then import this XML into FCP X.
- Andreas
Please Log in to join the conversation.
- Doug Suiter
-
Topic Author
- Offline
- Elite Member
-
- Posts: 244
- Thank you received: 12
Please Log in to join the conversation.
- Andreas Kiel
-
- Offline
- Platinum Member
-
- Posts: 1077
- Thank you received: 189
When I said you should have a fcpxml I implied that you create one from the 7toX. Sorry my bad.
Otherwise it's the procedure I described. Make a copy and run the little app.
- Andreas
Please Log in to join the conversation.
- Doug Suiter
-
Topic Author
- Offline
- Elite Member
-
- Posts: 244
- Thank you received: 12
Please Log in to join the conversation.
- Andreas Kiel
-
- Offline
- Platinum Member
-
- Posts: 1077
- Thank you received: 189
means that it is a file named "modXML.fcpxml" on the root level of your boot volume.
- Andreas
Please Log in to join the conversation.
- Doug Suiter
-
Topic Author
- Offline
- Elite Member
-
- Posts: 244
- Thank you received: 12
"41 name matches were found, but 41 files are not compatible.
Relinked files must have the same media type and similar audio channels as the original files, and must be long enough to cover all the clips that reference the files.
Select a single item at a time to get information about why it is not compatible."
Please Log in to join the conversation.
- Beeldcomponist
-
- Offline
- Junior Member
-
- Posts: 33
- Thank you received: 8
".. name matches were found, but .. files are not compatible.
Relinked files must have the same media type and similar audio channels as the original files, and must be long enough to cover all the clips that reference the files.
Select a single item at a time to get information about why it is not compatible."
This was our workflow: about 80 XDCAM disk were imported on 2 hard disks, both disks have the same material.
The director worked in FCP 7 and sent me the project.
I relinked it in FCP 7 to check everything and exported the XML.
I copied my hard disk to a Pegasus2 R4 and here comes the strange thing:
Importing the XML (7toX) on an other Macpro with the Pegasus hard disk I got that same error massage as above.
When I connected the original hard disk, were I created the XML from, all files could be relinked!
Copying the Library to the Pegasus and relinking was also possible.
On both machines Premiere Pro is not installed.
On both machines FCPX 10.1.2 is installed and the latest version 7 to X.
I think it has to do with the new xml version in 10.1.2.
-Hans
Please Log in to join the conversation.
- Andreas Kiel
-
- Offline
- Platinum Member
-
- Posts: 1077
- Thank you received: 189
First one the XML not working, second one with a clip from the "bad one" dragged to a timelime (which works on re-import).
- Andreas
kiel(at)spherico(dot)com
Please Log in to join the conversation.

