Welcome to our community

Be a part of something great, join today!

Register Log in
  • 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 :)

New: public beta of Clipfinder 2.1 - the render features you requested

I'd like to think about this some more, so I can find a solution that is as flexible as possible but not so fuzzy as to match to the wrong clips.
If you need something urgently, let me know within the next hour and I will try to help you.

Cheers,
Hans
 
Hans-Georg Daun said:
I'd like to think about this some more, so I can find a solution that is as flexible as possible but not so fuzzy as to match to the wrong clips.
If you need something urgently, let me know within the next hour and I will try to help you.

Cheers,
Hans
Click to expand...

I'm fine for now, so please think about the needs and come out with something great as you already provided in other features. Clipfinder and your support are just awesome.
 
I tried out clipfinder and I must say it's really easy to use.

whats the difference between this and crimson? are there things crimson can do that clipfinder can't?

also, is there a page or more info somewhere on the difference render settings ideal for various outputs?
 
Kaku Ito said:
I'm fine for now, so please think about the needs and come out with something great as you already provided in other features. Clipfinder and your support are just awesome.
Click to expand...


Cineform just came out with the update to solve the naming issue.
 
gary chan said:
I tried out clipfinder and I must say it's really easy to use.

whats the difference between this and crimson? are there things crimson can do that clipfinder can't?

also, is there a page or more info somewhere on the difference render settings ideal for various outputs?
Click to expand...

Like Nook Kim said in the other thread where you asked this question, Clipfinder's main disadvantage vis-a-vis Crimson is that it does not currently support a conform with in/out points and handles, i.e. a conform where the (compute intensive) high quality render is only done for the part(s) of a clip that is actually used in your timeline. Clipfinder requires you to render the entire clip.
Clipfinder also has no support for REDCine but instead relies on REDAlert for one-lighting.
You'll be able to get more info from Clipfinder's Help Pages (CMD-?) and the website forCrimson (www.crimsonworkflow.com).
Regarding render settings, the info is unfortunately spread all over REDuser.
Nigel Stanford (author of Monkey Extract) has been kind enough to collect some info here
http://reduser.net/forum/showthread.php?t=23094
If you have any specific questions, send me an E-mail (my address is listed in Clipfinder's Help Pages) and I'll try to answer as best I can.

Cheers,
Hans
 
thanks

thanks

thanks Hans for making it clearer.

i think i'd rather use clipfinder even though it renders the whole clip b/c of the ease of use.

great program.
 
Hans,

Can you explain why Clipfinder's picture and REDAlart!'s picture look different? After doing one light color correction, select "make QuickTimes" then Clipfinder picture gets updated but looks significantly brighter. Which one we should depend on?
 
Kaku Ito said:
Hans,

Can you explain why Clipfinder's picture and REDAlart!'s picture look different? After doing one light color correction, select "make QuickTimes" then Clipfinder picture gets updated but looks significantly brighter. Which one we should depend on?
Click to expand...

Clipfinder 2.1 uses the QuickTime reference files for movie display and for extracting thumbnails.
There is a known issue with the QuickTime Reference files in that they do not reflect the color space, gamma space and curve settings made in REDAlert.
This is not particular to Clipfinder and is the same with all QuickTime based tools (e.g. QuickTime Player).
Differences between what you see in REDAlert and what you see in QuickTime may be compounded by the dreaded QuickTime gamma issues.

For now, any color correction decisions should be based on what the image looks like in REDAlert.

There is hope, though.
Clipfinder 2.2 will use RED's SDK for thumbnail extraction and Loupe display and playback. Clips rendered via the SDK look the same as in REDAlert (except for the DRX parameter).
 
Ah, now I see the gamma and colorspace don't get applied.

I'm looking forward to your update!
 
Hans is there a way to replace the footage edited with clipfinder with the native files from the new Red log and transfer plugin?
 
shashbugu said:
Hans is there a way to replace the footage edited with clipfinder with the native files from the new Red log and transfer plugin?
Click to expand...

There is this

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

Also, with the latest version, you can conform from transcoded files to references files (proxies). Unless you have multiple R3D files for a single clip, I understand this is just as good as wrapped R3Ds.

Cheers,
Hans
 
Hans,

Thank you so much for all your work, and what you have done for the community.

Do you happen to have a PayPal address - I would like to send at least a few thank-you dollars/Euros/Franken in your direction.

Or maybe a postcard from all users?

Let us know what you'd appreciate.
 
We will all like to send you some money.
 
Hans,

This is a great application. I love it. Thank you so much.

I recently started trying out some of the more advanced conform options, and I can't seem to get it to work. I have imported an FCP XML into clipfinder, but nothing changed. Everything just stays the same - same clips loaded, everything. What am I doing wrong?

Ryan
 
Nevermind. I realized that I had to start a new project and open the XML from there. This would be helpful to note that in the documentation.

I'm sure you have thought of this, but is there any way to add a function that will allow only clips in the timeline to be rendered - and after that, only the areas used plus an x-frame handle? This would be very useful.

Thanks!

Ryan
 
Ryan,

If you export only the timeline from FCP, Clipfinder will load only the clips used by the timeline and you can then render only those.

Conforming with handles has been on my list for a while, but seems less urgent now because of the new workflow options offered by the latest changes in FCP/Color.

Check out Crimson for full-featured conform functionality.

Cheers,
Hans
 
Hans,

Merry Xmas and thank you for ClipFinder ... great app !

One small question (and clearly not a ClipFinder problem) ... once the QTs are regenerated by RedAlert (via the 'File=>Make QuickTimes' option) proxies are darker than the RA preview ... ?

I'm finding that the preview shown in RA is lighter (as is any rendered output) than the QT proxy (and as you are referencing the proxies, they also appear darker in the CF previews).

Thus :

  • CF and QT player (of the proxies) = darker
  • RA preview and QT player (of the rendered ouput; codec = none) = lighter

Note 1 : I'm using 'none' as a codec as I hate the gamma shift of ProRes HQ when working in Shake/FCP.
Note 2 : I have the QT player preference 'Enable Final Cut Stdio color compatability' NOT enabled (if you use 'none' for QT codec it makes no differnence).

On another thread (simplest Apple workflow type thread) there is mention of 'set REC709 in the RED CAMERA Quick time proxy setting' ... where on earth is this setting ? I had assumed that the coded was just plain old RED Codec ?

Any suggestions of how to get the gammas all lined up !?!?

Cheers (AND A VERY FESTIVE SEASON TO ALL RED USERS OUT THERE)

EDIT : happy to do some screen grabs if necessary :biggrin:
 
You must log in or register to reply here.
Back
Top