link to h movie in clipfinder problems

[Tony Wise]

Doing some test with clipfinder on a feature I'm cutting. Never worked with clipfinder before. Cutting with prores ref. movies. I didn't do the transcode, but file structure and naming seems fine. Exported xml from a short test sequence. Used clipfinder's "Run conform on xml" function. Set the clip directory to the root folder that contains all the r3d's and corresponding proxie movies. Selected box to link to _h movies. No luck. Import xml back into fcp and clips are still linking to prores ref movies. Is it file structure issue? Metadata issue with transcode? Thanks in advance.

 

[David Battistella]

Try opening your XML in a NEW FCP project.

David


ALSO

Please explain your system set up including which version of software you are running, etc.

 

[Tony Wise]

Ya, I already tried that. No luck. I'm running FCP 7.0.1 on Mac Pro 8-core. Clip finder is version 2.1.16 Both the r3d files and the pro-res ref. movies are on the same graid connected via esata.

Could it be a file structure issue with the originals? I didn't do any of the transcoding myself. Here's the file path - r3d master - day 1-8 - day 1 - reel 1 - the rdm folder - scene3 take1 - r3d file and corresponding proxie movies.

thanks.

 

[Tim Sutherland]

I ran into this yesterday.

Try checking the box for ' Match first 8 characters only' in the Run Conform dialogue box. If they transcoding was done with redcine or possibly redrushes, it will have an extra _001 at the end of the name. Checking that box in Clipfinder works around that.

 

[Tony Wise]

The r3d file does have the extra _001. Checked the box "match only first 16 characters". Still no luck. I'm pointing the clip directory to the root folder. Should I being pointing it elsewhere?

 

[Ben Brainerd]

Some people have had issues with Clipfinder not finding files if you point it at the root. Maybe try putting in each folder individually? (Yeah, I know it sucks. I've never had any problems using the root, myself.)

As a test, try importing the XML and doing a "Replace MOV with R3D". Might help figure out where the problem is.

 

[Tim Sutherland]

You have to do the Replace MOV with R3D, then render out your files, then run the conform on the FCP XML. Did you try that in that order?