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.0: Free Workflow Tool for OS X / FCP

Hi, thanks so much for your generosity in releasing this app.

When I open the FCP XML in Clipfinder, it displays the .mov file names with no data attached, they wont open in the viewer or REDAlert!
 
sander kamp said:
No, I wasn't using HQ Loupe. Actually I think it happens even when browsing through clips and opening the Loupe a couple of times. Such a shame because it means the application will keep crashing if I use the Loupe.
Click to expand...

The next time Clipfinder crashes, select "Report..." from the Dialog that appears after the crash and have a look at the crash details. If the details are not very similar to the highlighted section in the attached screenshot, please press CMD-A on the crash details, copy the details into a PM and send it to me.

FWIW, I am planning on reducing the dependency on the RED QuickTime codec but I cannot say how long this will take.

Many thanks for your feedback.
Cheers

Hans
 
Bro Anansi said:
Hi, thanks so much for your generosity in releasing this app.

When I open the FCP XML in Clipfinder, it displays the .mov file names with no data attached, they wont open in the viewer or REDAlert!
Click to expand...

That sounds like Clipfinder cannot find the files at the path given in the XML file. Are the files on a local disk or on a server ?

Cheers
Hans
 
They are on an internal RAID.
 
Thanks Hans, yes the path below seems to be valid.

<pathurl>file://localhost/Volumes/Anansi%20RAID/CARIBANA%2008/A004_C008_08028T.RDC/A004_C008_08028T_M.mov</pathurl>
 
I can't get it to open any RED reference files. R3Ds and self contained .mov files open no problem though.
 
hgdaun said:
The next time Clipfinder crashes, select "Report..." from the Dialog that appears after the crash and have a look at the crash details. If the details are not very similar to the highlighted section in the attached screenshot, please press CMD-A on the crash details, copy the details into a PM and send it to me.
Click to expand...

The report looks exactly like that so I guess I'll just have to be patient.
 
Thanks Hans, I will send it right away.

Ian
 
Hans,

I'm having same problem with importing XML.
If I click to open or CMD_R, the clip list window will close down and nothing happens.

Great work!

Dave
 
Thanks Hans, the new version (Clipfinder 2.0.1) you sent me works perfectly, imports the XML, references the R3Ds and with REDAlert! V3.5.0 to boot!

Ian
 
Clipfinder 2.0.1 solves XML import problem

Clipfinder 2.0.1 solves XML import problem

Bro Anansi said:
Thanks Hans, the new version (Clipfinder 2.0.1) you sent me works perfectly, imports the XML, references the R3Ds and with REDAlert! V3.5.0 to boot!

Ian
Click to expand...

Well, there you heard it from Bro Anansi.
Clipfinder 2.0.1 is out and solves a problem with the XML import for files that have spaces in their pathnames.

The download is at http://www.daun.ch/software/Clipfinder2.0.zip

If, for some reason, you must have version 2.0, you can now find it at
http://www.daun.ch/software/Clipfinder.2.0.0.zip

Cheers
Hans
 
ibloom said:
Very cool Hans! Can we have a Tiger version ;)
Click to expand...

You want a birger with that ?

Now, seriously: just for the fun of it I tried to compile for OS X 10.4. I got 16 errors and 185 warnings. It would take a while to wade through this. I definitely would have to get rid of NSCollectionView, but I was half planning on doing that anyway for all the grief it has given me.

Who believes it is more important to work on Tiger compatibility than to work on extending the feature set ?
 
You must log in or register to reply here.
Back
Top