Clipfinder to FCP workflow. HELP PLEASE!

[Curtis Jensen]

I'm currently editing a short film with Red One footage (a first for me). I have a picture lock of the film and now I'm having trouble figuring out a way to get Final Cut Pro to see the changes I made in Clipfinder 2.2.

My workflow thus far has consisted of the following:
- Logged and transferred through Final Cut Pro.
- edited film in a ProRes 422 timeline. Now have picture lock.
- noticed some shots were underexposed or had the wrong white balance. I corrected those shots in Clipfinder.

So now I'm wondering how I can get Final Cut Pro to see the changes I've made to the shots in Clipfinder, keeping the 4k R3D files as a reference for export to Color. Any thoughts?

- Curtis

 

[David Battistella]

try this.

it works for me..

http://reduser.net/forum/showthread.php?t=35308

david

 

[Sebastian Gross]

as i might add:

in case you´re using a multicore machine
and want to save time forget about the log&transfer tool in FCP,
because FCP is not capable of multithreading .
you can nicely check this by enabeling the activity window in mac os x.

clipfinder on the other hand is very well capable of that and takes full advantage of all your cores.
furthermore you can distribute the amount of tasks to the amount of cores you have, also during
the actual render process.

if you find the time have a look.

cheers.

 

[Ravi Kiran]

How do I enable multithreading for Clipfinder? I'd like to use Clipfinder if it can make my transcodes go faster than RedRushes. I'd be using two 2.8GHz Mac Pro Quad Core machines.

 

[Uli Plank]

Clipfinder as a setting in the render window where you can choose the number of tasks and cores in use. Very easy!

It even offers distributed rendering.

 

[Ben Brainerd]

...keeping the 4k R3D files as a reference for export to Color. Any thoughts?

If you're going to Color for Grading/Rendering, why bother getting new versions out of Clipfinder? Nothing you do in Clipfinder (Which handles metadata changes with an RSX file) will carry over to Color, unless you're rendering your entire project out to ProRes/DPX/Etc

 

[Ryan Patrick Flanery]

as i might add:

in case you´re using a multicore machine
and want to save time forget about the log&transfer tool in FCP,
because FCP is not capable of multithreading .
you can nicely check this by enabeling the activity window in mac os x.

clipfinder on the other hand is very well capable of that and takes full advantage of all your cores.
furthermore you can distribute the amount of tasks to the amount of cores you have, also during
the actual render process.

if you find the time have a look.

cheers.

Thank you so much for reminding us about FCP's inability to multithread. This makes ClipFinder much more appealing, especially for projects with lots of takes (like features and music videos).

 

[Uli Plank]

While this is a good reason, there are a few more for ClipFinder, like full support of new color science(s).

 

[Hans-Georg Daun]

That's not entirely correct.
Clipfinder 2.5 has a function for copying RSX settings to the RED tab in Color. It is limited to the parameters in the RED tab (i.e. no FLUT, no Shadow), but still...

Cheers,
Hans

If you're going to Color for Grading/Rendering, why bother getting new versions out of Clipfinder? Nothing you do in Clipfinder (Which handles metadata changes with an RSX file) will carry over to Color, unless you're rendering your entire project out to ProRes/DPX/Etc