problem with Clipfinder

[Gregory Bennett]

SO...I've followed all the steps as outlined in Clipfinder instructions but program won't link to R3D files.

RED footage was output using RED Alert into 1080p ProRes422 files for editing.

Each original camera reel is in it's own 'mag' folder.

Output Proxies are in one big folder called 'Proxies'

 

[N_Villers]

Hard to say exactly because it has worked consistently for me. Can you list the steps you have taken in detail - perhaps that will help us identify what is going wrong.

-noel

 

[Gregory Bennett]

There are 9 directories with REd footage named Mag 1 - Mag 9

files are named thus:

A004_C001_0829FK_001.R3D etc.

Proxies which were created in Red Alert are named thus:

A004_C001_0829FK.mov etc.

I've tried everything. Outputting XML/EDL from FCP

Using Clipfinder

When I open XML in Color it isn't linking to R3D footage at all.

 

[David Battistella]

Try to make sure your R3D data and the .mov data is in SEPARATE folders.

ALSO

Make sure that there are proxies with the r3D IN THE SAME FOLDER as the r3d file. If there are not then create new proxies with clipfinder.

This is really simple stuff, it should be pretty straightforward.

David

 

[Gregory Bennett]

Thanks David,

Should be, but there seems to be a snag somewhere in the process.

The R3D data is in separate folders

i.e.: in directory named Mag 1 there is the following structure:

A001_0829VR.RDM at the top

within that there is:

A001_C001_08297G.RDC

A001_C002_08298E.RDC

A001_C003_0829FF.RDC

etc. etc.

in each of those directories is:

.R3D file
_F.mov
_H.mov
_M.mov
_p.mov

and so on for Mags 1-9

and in the same top directory called REWIRE there is a folder full of the proxies that were rendered from Red Alert.

I didn't make those proxies. They were rendered out into ProRes422 files which were used for editing.

 

[David Battistella]

hmmm.

I think can you post a snapshot of how it looks or PM me your number and i'll call you to try to help you out.

David

 

[Gregory Bennett]

just PM'd you my phone #

 

[Uli Plank]

Make sure that you add all the R3D directories directly into the list for the sources in Clipfinder, not just one higher folder in the hierarchy. Plus, there shouldn't be any funny characters in their paths.

 

[_mike_]

.... folder full of the proxies that were rendered from Red Alert.

I didn't make those proxies. .....

There could be the problem - check the naming and properties of these proxies. Usually if You want to edit prores proxies and conform using clipfinder then you should also render those prores proxies using clipfinder so that it will name proxies correctly and embed all the necessary metadata inside the quicktime file. If you open clipfinder generated prores quicktime file using quicktime 7 (not the ugly new quicktime X) and click movie properties at the window menu you will find there what fields of data was written - video track, audio track, timecode track, timecode start and the source name field. And compare to the redalert generated quicktimes.

 

[Ben Brainerd]

There could be the problem - check the naming and properties of these proxies. Usually if You want to edit prores proxies and conform using clipfinder then you should also render those prores proxies using clipfinder so that it will name proxies correctly and embed all the necessary metadata inside the quicktime file. If you open clipfinder generated prores quicktime file using quicktime 7 (not the ugly new quicktime X) and click movie properties at the window menu you will find there what fields of data was written - video track, audio track, timecode track, timecode start and the source name field. And compare to the redalert generated quicktimes.

I've used RedAlert proxies with the clipfinder workflow and never had a problem.

Gregory:
Are you trying to open the clipflinder XML in Color? Because that's not how it works. In general, you want to:
1. Edit Proxies
2. Output XML from FCP
3. Run Conform using Clipfinder (Tools -> "Run Conform on FCP XML")
4. Import the new XML back into FCP
5. Send the project to Color using the built in "send to color" command

Make sure you've got "replace clips with X proxy" checked (Where X is the proxy size you want to use. I use M proxies and reset the geometry in Color). FCP can't actually use the R3D files, but if you conform the proxies, Color will reference back to the R3D for the RAW data.

I assume your phone call with David will probably solve the issue. But if it doesn't, can you post a detailed, step-by-step description of your workflow and where you start having problems?

 

[David Battistella]

Hey Guys,

I'm not sure Greg is checking this thread but we had a talk on the phone yesterday and worked it all out.

He is probably Color Correcting as we speak.

David

 

[Ben Brainerd]

Good to hear. For posterity's sake (And to help out others) what ended up being the problem?

 

[Gregory Bennett]

Thanks to David for getting me back on track. I was doing all the right things except re-importing XML back into FCP and THEN sending to Color. I was trying to open the XML created by Clipfinder directly in Color without doing that extra step. Works great and now I'm color-correcting!