site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=EiaqRX2mgFLn1oxWG8PT5QOnaSr7Fmhhcv2ACT7lk+W8+2NQKqrHeYDO5CH3wmfw; h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP; I'm a complete newbie to FxPlugins. So, please forgive me if I say something too stupid. :-) Is it possible that the temporal API was trying to get a non-existent image somehow? Perhaps a +0.5 (second field)? If the video was interpreted as "interlaced", the image would exist. But, if it were interpreted as "progressive", there'd be no +0.5 image. Perhaps the update turned off field processing? (Or altered a default or preference setting, etc.) Something that might either cause the Video from being interpretted as interlaced vs progressive, or change the render mode from i to p. My attention was just caught by the good G5 trying to process "interlaced", but the bad G5 processing as "progressive". That seems like an important clue. It'd be interesting to see if the bug subsides, if the video icould be marked/interpreted as "interlaced" again. Just a thought. Sorry if it was a dumb one. -- brian -----Original Message-----

From: Micah Sharp <micah@redgiantsoftware.com> Sent: Jan 25, 2008 4:54 PM To: pro-apps-dev@lists.apple.com Subject: question about fcp 5.1.4

Hi, I have a bug in our FxPlug in FCP 5.1.4 only, where calls into the temporal api are causing some kind of exception and execution returns back to FCP, with no more plugin code being executed. The resulting output is just transparent black (not seeing an exception caught in the debugger, but no more breakpoints are hit, stepping through or over the call and execution in the debugger stops and FCP is "live" again).

I was NOT seeing the bug on one G5, but DID see it on another G5. Debugged and the problem is this "crash" in in the temporal call. Darn, how can this be? The "good" G5 has no problems with the exact setup/code/project/media, etc. Also a bit strange was the "bad" machine was trying to process progressive, while the "good" machine was (correctly) processing interlaced. RenderInfo struct was different but the project was the same.

Comparing the two machines, I see no alternative but to run Software Update on my "good" G5 to try matching everything on the "bad". Bad idea, now the "good" machine has the same problem in FCP 5.1.4. Great.

Items installed:

Pro Applications Support (4.0.2) Xserve Raid Driver update Apple QMaster update GarageBand update Java 1.3.1 and 1.4.2 Release Soundtrack Pro update Compressor update Pro Applications update 2007-02 (1.0) Security Update 2007-009 (PowerPC)

If I was smart, I would have done these one at at time and I'd know which caused the problem, though I bet it must be part of the Pro App updates (or maybe Compressor?). For a total stab in the dark, any clues?

Thanks,

Micah Sharp Red Giant Software www.redgiantsoftware.com

Sign up for our newsletter! http://redgiantsoftware.com/newslettersignup.html

_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... This email sent to site_archiver@lists.apple.com