Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Clipfinder 2.1 final version released

Dale,

I'd like to complete the feature set for working with FCP first.
There is still a lot to do.
I'm afraid that supporting multiple platforms (FCP, Premiere, Avid) will be difficult for me (and having to buy licenses for all platforms does not make it any more attractive).

Cheers,
Hans


I hear you Hans and do appreciate that fact, though now that you are implementing the "Replace MOV with R3D" could you not theoretically achieve the goal of importing R3D's/FCP XML into Premier Pro once the plug-in arrives. In other words, cut proxies on FCP, Export XML, open XML in Clipfinder, replace MOV with R3D, save, then import that xml to premier pro through this upcoming process:
http://www.studiodaily.com/main/training/10122.html
 
Hans
I have a quick question. I tried importing some redcode files from an NFS mounted directory and it wouldn't open them. Do you have anything in the code that might cause that? I pulled the same directory in and it worked fine.

regards,
mr. whip
 
I hear you Hans and do appreciate that fact, though now that you are implementing the "Replace MOV with R3D" could you not theoretically achieve the goal of importing R3D's/FCP XML into Premier Pro once the plug-in arrives. In other words, cut proxies on FCP, Export XML, open XML in Clipfinder, replace MOV with R3D, save, then import that xml to premier pro through this upcoming process:
http://www.studiodaily.com/main/training/10122.html

I've been thinking about this on and off during the day and started over 3 or 4 times on my reply.
I'm afraid that this will not be quite as simple as it seems. While native R3D playback and FCP XML import may each work by itself, they may not work too well (or at all) when combined with each other.
With R3Ds, several parameters that are "baked" into QT proxies or transcoded files (desired width / height, cropping, debayer resolution, OLPF compensation, color space, gamma space, etc.) are still open. There will need to be a way in PP4 to set these parameters (globally, per sequence, per clip ?). I do not see a way to set these parameters via the FCP XML, because the FCP XML does not define any tags for these parameters.
I'm thinking we'd better wait until the RED plugin for PP4 is available and we can see exactly how it works.

Cheers,
Hans
 
Hans
I have a quick question. I tried importing some redcode files from an NFS mounted directory and it wouldn't open them. Do you have anything in the code that might cause that? I pulled the same directory in and it worked fine.

regards,
mr. whip

Interesting... may be a problem with symbolic links. I'll need to do some research. I will report back.

Cheers,
Hans
 
Hey there!

Hey there!

I'm a newbie to reduser.net, though I've been lurking awhile.

First, awesome software, I'd like to contribute, so let us know how or when we can.

Second, I'm developing a new workflow. We edit in FCP with clips created in Red Rushes at either 1080p or 720p ProRes depending on length of production and-or what system an editor is using. What I'm wondering is this, (please forgive me if I'm just missing it...) After editorial, I can import an XML into Clipfinder, but, can I create a "pull" list that essentially creates a folder and either copies, moves or creates aliases of only the shots needed for final finishing. Am I making sense? Basically a folder-place of only the .r3d files used in the edit.

Thanks in advance.
 
I'm a newbie to reduser.net, though I've been lurking awhile.

First, awesome software, I'd like to contribute, so let us know how or when we can.

Second, I'm developing a new workflow. We edit in FCP with clips created in Red Rushes at either 1080p or 720p ProRes depending on length of production and-or what system an editor is using. What I'm wondering is this, (please forgive me if I'm just missing it...) After editorial, I can import an XML into Clipfinder, but, can I create a "pull" list that essentially creates a folder and either copies, moves or creates aliases of only the shots needed for final finishing. Am I making sense? Basically a folder-place of only the .r3d files used in the edit.

Thanks in advance.

With version 2.1.3, you can match the transcoded files you loaded from the XML to R3D files (actually, RDC folders). Select "Replace MOV with R3D" from the File menu to do this. To copy the RDC folders to another directory, select all clips, press CMD-C, then press CMD-V to paste into the new directory.

What's the reason you want only the .R3D files ?
Wouldn't you want at least the .RSX files as well ?

Let me know if you need more info.

Cheers,
Hans
 
no need for RSX

no need for RSX

As I prep for grading, I don't feel I'll need RSX....

I'd like to Show up for a grading session with the RDC-folder/R3D shots rather than all media that was shot
 
If you want to copy just the R3D files, I have an alternative suggestion:

- create an Automator Action as shown in the attached screenshot and save it to a file. You'll need to do this only once.

When you need to copy clips
- import clips from XML file
- re-connect to R3Ds ("Replace MOV with R3D")
- select all (CMD-A)
- select "Run workflow with selection" from the Edit menu
- in the File Dialog that appears, select the Automator Action you saved
- if you wish, you can change the copy destination in the "Configure Task" window.
- press "Start" in the "Configure Task" window

Clipfinder passes the R3D files to the Automator Action, the Automator Action copies them to whichever folder you specify.

It's not terribly pretty and there is no progress indicator, but it should work.

I hope this helps.
Cheers,

Hans
 
No. Just the green icon. See here http://www.daun.ch/software/ClipfinderHelp/renderingclips.html
(also available by pressing CMD-? in Clipfinder)

Cheers,
Hans

Hans -

Thanks for your response. I just didn't understand what "other Quicktime-supported formats" mean. Say I have rendered a R3D to 720 into a separate
folder. Do I expect to have the Quicktime icon in the info column? That's kind of what I was thinking, but when I open a saved Clipfinder again after a render I don't get neither Quicktime icon nor the green "rendered" icon.
 
Aha! Now I understand what's going on with the Quicktime icon. When I open a clip that's been rendered, say "A001_C001_x.R3D", I will have two files of "A001_C001_x" in the name column. But I will see one with R3D icon, and the other one with MOV icon in the info column.

Whew, that took me a little while to figure out.

Sorry for the confusion, Hans!
 
Thanks, copy and paste works for what I think I'll need.
 
I have just released Clipfinder 2.1.3.
As usual, it is available from http://www.daun.ch/software/

This version adds the ability to load a list of transcoded (.MOV) files, either from a directory or (more likely) from an FCP XML file, and to find the R3D files with matching names.

YOU SIR, ROCK THE FUCKING CASBAH!!!

Thanks for turning this around so quickly!

Aloha,
mel
 
When double click on the clips, i got error saying that AttachScript Error

Error -25211 occured the OpeninREDAlert/Volume/-----------------------------
call: Access for assistive devices is disabled
 
you need to go into system preferences, click on the universal access icon and check enable access for assistive devices and it will work.

good luck
scott
 
Just to let people know, I've just experienced Clipfinder skipping a R3D with no proxies during rendering all clips process. The camera failed to generate QT proxies for some reason, and I guess Clipfinder works based on those QT reference files. So it would make sense this happened. For the fix, I just generated the proxies from RA, and all was well.
 
you need to go into system preferences, click on the universal access icon and check enable access for assistive devices and it will work.

good luck
scott

Thanks Scott :) It works
 
Hans,

Thanks for this great little app- very useful and helpful. It is greatly appreciated.

The only thing I would request is the ability to download the manual in PDF form, as I am not always around an internet connection, and it would be handy to have when on location. (I checked the web site, and if it is there I couldn't find it.)
 
Back
Top