Welcome to our community

Be a part of something great, join today!

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 :)

Clipfinder 2.1 final version released

Yes, Clipfinder, Clipfinder, and Clipfinder!!!!

I still dont beleive it... :)

Logical, fast and comprehensive workflow.

It does what you're looking for, and a ton more.

Oh...and the development speed is astonishing.

Antoine
 
Feature request.

I would love for Clipfinder to hack ProRes files so that they contain the flag that tells Final Cut to "Log and Transfer" instead of "Log and Capture" when batch capturing from FCP. I like making my ProRes files in RED Rushes, but I also like conforming to Native QT before sending to Color. Only ProRes files that were created from R3Ds thru FCP's Log and Transfer, allow for this.

STeve
 
Steve MacMillan said:
Feature request.

I would love for Clipfinder to hack ProRes files so that they contain the flag that tells Final Cut to "Log and Transfer" instead of "Log and Capture" when batch capturing from FCP. I like making my ProRes files in RED Rushes, but I also like conforming to Native QT before sending to Color. Only ProRes files that were created from R3Ds thru FCP's Log and Transfer, allow for this.

STeve
Click to expand...

Have a look at Clipfinder 2.2. There is a workflow for getting from ProRes files that were created outside of L+T to Native QT. You can conform your edit this way. Plus Clipfinder 2.2 allows for tweaking metadata right inside the app.
 
Steve Sherrick said:
Have a look at Clipfinder 2.2. There is a workflow for getting from ProRes files that were created outside of L+T to Native QT. You can conform your edit this way. Plus Clipfinder 2.2 allows for tweaking metadata right inside the app.
Click to expand...

Thanks,
Could you point me in the right direction for that feature. I couldn't seem to find it.

STeve
 
Hello Hans!
Firt of all let me tell you THANKS for this great application you´ve made!.
I went to your site and read about ¨basic Avid conform support¨.
Could you explain me better what can be done in an avid scenario with clipfinder?
I know you are developing mainly for FCP, but feel free to ask me whatever you may need to increase the Avid side of clipfinder, I´ll pleased to help you.
Thanks again.
Agustin
 
Augustin,

There is an (admittedly brief) explanation of Avid-related features in the "What's new in Clipfinder 2.2" section of the integrated Help Pages (CMD-?).
In addition to the features discussed there I am working with Jamie Parry on integrating his MXF conversion into Clipfinder.
I'd very much appreciate your help in improving Avid support in Clipfinder.
If you have any comments or suggestions, feel free to mail me. My mail address is listed in the Clipfinder Help Pages.

Cheers,
Hans
 
Chris,

As you know, Jamie is away on holiday until the 8th, so no news until then.
I expect there to be some fairly rapid progress after he comes back.

As for "native" MXF support, that would depend on either REDline offering this as an option, or me writing my own render engine to use instead of REDline. So this could take a while. Besides, I have no intention of eating Jamie's cake.

Cheers,
Hans
 
i didn't think you'd be eating his cake. i was hoping you would be eating cake together (perhaps as a paid version of clipfinder??) for the benefit of all of us, and you and Jamie. This really would make clipfinder a 'magic bullet' of sorts, not that it isn't pretty magic already.
 
I second the request for a version of Clipfinder with its own render engine, and would definitely be happy to pay for it, as well as be an Alpha tester.

Direct MXF export would certainly be a plus, and also not being limited to the codec presets in REDline. Also I would love to be able to export iPhone dailies (using x264 for speed?) in a single pass.
 
I will start work on a for-pay version of Clipfinder as soon as the beta phase for Clipfinder 2.2 is concluded. One of the features I am considering for this version is an alternative render engine.

As for the cake eating, I suggested to Jamie a 'plug-in' model, where we agree on a common interface and then each of us can develop, market and charge independently, but we could still offer users high integration between Jamie's work and mine.

To whet your appetite, this is what it currently looks like:
You order a plug-in from Jamie and install that into an "Extensions" folder. Clipfinder will then present JamFuze settings as part of its render settings
and execute Jamie's code for each rendered file.

View attachment 12981

So much for future plans.
I appreciate your feedback and comments, so please keep them coming.

Cheers,
Hans
 
You must log in or register to reply here.
Back
Top