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

Clipfinder Render Problems

Z

Zsolt Såndor

New member
Joined
Jul 8, 2009
Messages
3
Reaction score
0
Points
0
I'm using Clipfinder 2.2.5 (although have same issue with 2.1.16) on a Macbook Pro 2.33ghz with the latest Quicktime, REDCODE, Red Alert installed.

When I try to render a clip in clipbrowser, it starts to render and seems to work fine, the new file appears in finder, however, when finished, the rendered file disappears and is nowhere to be found.

According to the system log it has something to do with Quicktime AviImporter.... Any ideas what this means and how to fix it?

Log files are as follows:

08/07/09 1:26:19 AM Clipfinder[3794] REDline reported the following error while trying to render '/Volumes/Nightswimming 3/DAY 4/DAY 4 ROLL 15 D1/A018_07041P/A018_07041P.RDM/A018_C009_07048G.RDC': (
"2009-07-08 01:26:19.220 REDline[3859:10b] Error loading /Library/QuickTime/AviImporter-r7 (ppc).component/Contents/MacOS/AviImporter: dlopen(/Library/QuickTime/AviImporter-r7 (ppc).component/Contents/MacOS/AviImporter, 262): no suitable image found. Did find:",
"\t/Library/QuickTime/AviImporter-r7 (ppc).component/Contents/MacOS/AviImporter: mach-o, but wrong architecture",
""
)

...and it keeps repeating this over and over and over....

HELP!!!

I love Clipfinder and would love to use it for rendering - especially since i've been getting bizarre results using Red Rushes.

Any ideas would be greatly appreciated.

Thanks!
 
Are you using a intel computer? The error is talking about a wrong architecture, which means I believe you are on a PPC mac. All the red rendering material only works on intel.

If you are on an intel, is your system up to date? Use software update to make sure.

It would explain your weird Red Rushes results also.
 
Yes, on Intel (macbook pro's only come with intel chips), it's a Core 2 Duo 2.33Ghz, completely up-to-date, latest version of all system and video related software (and most everything else)

I also found it odd that the problem refers to the PPC component of AviImporter.
At a bit of a loss here...

Any other thoughts?
 
Sorry - Missed the MBP part of your post. I know from support of my own software that whenever I see ppc in the error message, the user is using the wrong arch. Perhaps try encoding to a different codec? How about removing the aviimporter plugin?

... Ill go back to supporting my own product now...
 
Try avoiding spaces and any other non-standard characters in your directory names.
 
Actually i had the same same issues from before, even earlier builds. I just checked the "make sub directories" and that was my workaround.
 
Thanks for all the advice everyone.

Hans, I didn't get a chance to try Nick's advice as I simply removed the PPC element of Quicktime AviImporter - which fixed the problem.

However, rendering is INSANELY slow. It takes about 1-2 hours to render a 1 minute clip! And there is over 2 hours of raw footage to transcode to ProResHQ for editing. I simply gave up. Is there a way to speed this up?

When full res proxy to ProRes HQ in my FCP timeline, it only takes about 5 mins per 1 minute clip. Why is Clipfinder so much more sluggish?
 
Clipfinder is working much faster for me than L&T. Did you accidentially use a full debayer? That would be very slow.

FCP is always using half! And check if you are using standard or high quality in FCP to compare. I'd recommend half high for finishing.
 
You must log in or register to reply here.
Back
Top