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.2 beta 6 released

Hans-Georg Daun

Well-known member
Joined
Apr 30, 2007
Messages
573
Reaction score
0
Points
0
Age
71
Website
www.hamingja.ch
I have just released Clipfinder 2.2 beta 6.
The new version can be downloaded from my website.

Below are the release notes (also included in the integrated help pages (CMD-?))

New in Clipfinder 2.2 beta 6

Added "Disable Safe Mode" setting in the Preferences. Safe Mode is enabled by default and protects you from potentially dangerous functions. You will need to disable Safe Mode to use the "empty" buttons in the Render window (not a good idea to use those if you have set your render target directory to the Desktop directory) or to use the "Prepare Clip Directories..." and "Restore Clip Directories..." functions (see below).

Renamed "Move Clip Directories to..." and "Move Clip Directories back from..." functions to clarify their intended purpose. Functions are now called "Prepare Clip Directories for L&T..." and "Restore Clip Directories after L&T...".

The reason for these functions' existence is that the Log & Transfer function in FCP will not work with multi-level directory structures (e.g. myProject / Day1 / Magazine1 / Clip1).

The "Prepare..." function makes it possible to ingest all needed clips in one go by collecting all .RDC directories for the clips currently loaded in the main window into a single-level hierarchy in the destination folder you specify. In order to save time and space, it does this by moving (not copying) the directories.The destination folder must be on the same drive as the R3Ds.

The "Restore..." function moves all .RDC directories back to their original place in the folder hierarchy.

Both functions will display an error message if you try to move to a directory that is not on the same drive as the R3Ds or if there are multiple .RDC directories with the same name (very unlikely for clips recorded with newer builds).

Use as follows
- load clips (e.g. from FCP XML, use "Replace MOV with R3D", if necessary)
- create a directory (e.g. "Selects") on the same drive as the original R3Ds for your clips
- select "Prepare Clip Directories for L&T..." and select the directory you just created
- save the Clipfinder document
- in FCP, select Log & Transfer and navigate to the directory you prepared with Clipfinder
- when FCP has finished ingesting he clips, open Clipfinder , load the saved document, select "Restore Clip Directories..."
- to conform to the newly created wrapped QuickTimes, use the conform function in Clipfinder and set "Clip Directories" to FCPs capture scratch directory for your project.

Added 3 movable readouts to histogram. The left readout displays the percentage sum of brightness values for each channel from the bottom of the histogram to the marker position. The right readout does the same from the top. The middle readout displays relative channel brightness (color balance) at the marker position.

Improved "Import subclips from FCP XML" and added option to not merge overlapping clips into one subclip.
It is probably worth repeating at this point, that, while this function allows you to extract partial clips (with in/out-points and handles) from an edit, and also allows you to render partial clips, Clipfinder does not support conforming with partial clips.

Added new preference "keep render session alive" and changed render behaviour such that render mode will now be exited after all clips are rendered, unless a watchfolder is active or "keep render session alive" is enabled.

Added code to pop up an alert when there is a problem loading a reference (proxy) file. Since the most common reason for this to happen is that the .RDC directory was moved to another directory or volume (which seems to break the link from the reference file to the R3D), the alert also suggests that you rebuild the reference files.

Added code to ensure that HDV material is shown at the proper aspect ratio.
Fixed problem with annotations being wiped out by lift & stamp.
Fixed problem with loading and displaying look settings for clips where no RSX exists.
Made documentation feature more resistant to "bad" clips.

Please report any problems to me so I can fix them in time for the conclusion of the beta phase.

Cheers,
Hans
 
This was posted elsewhere, but I got no reply. I installed the Clipfinder 2.2 beta 5 (I haven't tried beta 6 yet) and tried to send to REDAlert and if I remember correctly, i was asked which application it should open and I accidentally selected something other than REDAlert (damn wacom stylus!). Now whenever I try to send a clip to REDAlert, Clipfinder just hangs. I tried uninstalling (using AppZapper) but to no avail...
Any suggestions?

Jean
 
Hans,

Thanks for the update!

I noticed, however, that the link for downloading seems to still point to version 2.2 beta 5, instead of beta 6.

I was able to copy and past the link into my browser and change the 5 to a 6 in the file name and it downloaded fine.

Just thought you should know.
 
Jean,

When you press CMD-R, Clipfinder just runs an AppleScript that launches REDAlert and persuades it to open the selected clip.
I'll have to do some research to replicate problem you are having.
In the meantime, most of the corrections you can perform in REDAlert you can also perform in Clipfinder directly (press CMD-E).

Cheers,
Hans
 
It took me a while to figure this out, but I have a solution now:
Go to "/Users/<account-name>/Library/Preferences/com.apple.applescript.prefs" and either delete the file or edit it manually.
This file stores the association between the name "REDalert" and the application you selected when AppleScript presented the dialog you mention.
By the way, have you renamed your "REDalert" application ?
The AppleScript Clipfinder uses to open REDAlert requests an application called "REDalert". Only if this application does not exist should the dialog box ever pop up.

I hope this helps.
Let me know how it goes.

Cheers,
Hans

This was posted elsewhere, but I got no reply. I installed the Clipfinder 2.2 beta 5 (I haven't tried beta 6 yet) and tried to send to REDAlert and if I remember correctly, i was asked which application it should open and I accidentally selected something other than REDAlert (damn wacom stylus!). Now whenever I try to send a clip to REDAlert, Clipfinder just hangs. I tried uninstalling (using AppZapper) but to no avail...
Any suggestions?

Jean
 
Servus Hans-Georg,
thanks for the suggestion, I'll do what you suggest as soon as i find time.

I often rename RED applications because of having to juggle back and forth between this beta version and that one (I was a beta tester recently for their new versions). Is there anyway of having a preference in clipfinder where we can set the "application" we want, or should we go change the applescript itself?

Danke schön

Jean

PS: BTW your application is greatly appreciated...thanks for your contribution to the RED community!
 
Oooops...

Oooops...

Im sorry to say that beta 6 introduced a problem where rendering to DPX or TIFF would pop up an Alert for every clip that had finished rendering.

I have corrected this. The new version is available from my web site.

I apologize if this has caused problems for anybody.

Regards,
Hans
 
I have a question to Clipfinder users: if I want to make a dvd with footage, most of all meant to listen to it and type down the interviews that are in it. So It's not necessary a great amount of video quality. The file name burn in and timecode would indeed be useful.
So... what would you say can be the best render configuration?

I made once some exports from Adobe Premiere (which meant to insert each file at hand one by one) and exporting to a prores at 1k was like 3 minutes of render per minute of footage. But here the test I made was a lot longer, at the same quality.

HansGeorge, once again, thank you very very much for this amazing program!


Regards!
 
Hans, when I double click clips, nothing happens. And when I hit CMD-R, although RED ALERT opens, I'm asked to "go to folder" with an empty field.

Any idea what I'm doing wrong?
 
Martin: I have sent you an E-Mail
Brandon:
The 2.2 version only supports CMD-R for opening REDAlert.
The process for opening REDAlert is basically a "hack", because REDAlert does not support file associations. So I need to use an AppleScript that simulates user input.
Sometimes, especially on slower machines, the timing doesn't work. I'll look at the script again and see if anything can be improved.
Are you aware that, with Version 2.2, Clipfinder has a "Look Settings" panel (CMD-E) that offers pretty much the same set of controls that REDAlert offers ?

Cheers
Hans
 
Thanks ...

Thanks ...

Hans-Georg,

It was a real pleasure meeting you on Monday .... glad you were able to pop in and see us.

Really enjoyed our discussion and look forward to working with you in the future on making Clipfinder an even more impressive tool for RED users.

For those of you that haven't met Hans-Georg - he's a real smart cookie and a total gentleman ... great software comes from great minds.

Safe journey back to Switzerland.

Neil
 
open in REDAlert [in Version 2.2 beta 6b (228)]

open in REDAlert [in Version 2.2 beta 6b (228)]

Get an error 'AttachAScript Error Error -43' ending in : File REDAvert wasn’t found ?

Where does RedAvert come from ?!

PS : prior verion worked ok and Sys Prefs done ["System Preferences" and turn on "Enable Access for Assistive Devices" in the "Universal Access"]
 
Sorry, David

The "REDAvert" bit is a bug that crept in while I was diagnosing a problem for another user.
I have just released version 2.2 beta 6h, which fixes this issue.
The new version is available from my website.

Cheers,
Hans
 
Hello,

I fully understand the Clipfinder workflow process, but have one FCP compression question.

I have a 1080p, 29.97, Apple Pro Res 422 (HQ) timeline filled with a bunch of HVX, HPX, and 5D2 footage all with the same compressor, Apple Pro Res 422 (HQ). I like this because all my HD footage has the green line above it so I can edit without rendering.

Here is my problem, when I send my un-colored Red clips from Clipfinder to FCP, they all come in and need to be be render, has red line.

I think I understand why, the Red clips have the REDCODE compressor and doesn't like the Pro Res 422 (HQ) compressor.

Is there a way to get my Red clips to show up Green in these timeline settings?

Thanks,
Matt
 
Neil,

The pleasure was all mine.
Thanks again for agreeing to meet us on such short notice.
We were very impressed with the magic you worked on those RED shots, especially those with the difficult lighting. I wouldn't have thought it was possible to get such a great, clean image from those.
I'll keep you updated on my progress with the new version.

Thanks again,
Hans


Hans-Georg,

It was a real pleasure meeting you on Monday .... glad you were able to pop in and see us.

Really enjoyed our discussion and look forward to working with you in the future on making Clipfinder an even more impressive tool for RED users.

For those of you that haven't met Hans-Georg - he's a real smart cookie and a total gentleman ... great software comes from great minds.

Safe journey back to Switzerland.

Neil
 
Matt,

I assume you are sending reference files (proxies) to FCP. These require quite a bit of processing power.
You could try the following
- use smaller reference files (e.g. _M instead of _H)
- enable unlimited RT in FCP
if that does not help it is probably best to transcode clips to ProRes and work with the transcodes.

Cheers,
Hans

Hello,

I fully understand the Clipfinder workflow process, but have one FCP compression question.

I have a 1080p, 29.97, Apple Pro Res 422 (HQ) timeline filled with a bunch of HVX, HPX, and 5D2 footage all with the same compressor, Apple Pro Res 422 (HQ). I like this because all my HD footage has the green line above it so I can edit without rendering.

Here is my problem, when I send my un-colored Red clips from Clipfinder to FCP, they all come in and need to be be render, has red line.

I think I understand why, the Red clips have the REDCODE compressor and doesn't like the Pro Res 422 (HQ) compressor.

Is there a way to get my Red clips to show up Green in these timeline settings?

Thanks,
Matt
 
Hi Hans,
me and Giulia still have a bad sore throat since our sushi dinner on the roof top here at Venice beach, it was too windy but very nice company. I've tried the new fcp and color with clipfinder and the new prores "Quattro", I think it's a very powerful workflow. I have to test it more but it seems now color works much better with fcp and I didn't have any looping bug in color importing two clips longer then 2gb. It seems the proxie workflow works really well and I hope apple has improved the debayer capability.
Will you include the new prores codec in the next version of clipfinder?
Thanks.
Ciao.
 
Back
Top