site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hi Paul, steve On Jun 20, 2008, at 9:10 AM, Paul Schneider wrote: Hi Steve, - Paul On May 23, 2008, at 5:12 PM, Steve Christensen wrote: I also included a couple of test lines: testStart = [timingAPI startTimeForEffect:self]; testDuration = [timingAPI durationForEffect:self]; renderInfo.frame = 6 effectTime = 6 effectDuration = 300 testStart = 240 testDuration = 300 renderInfo.frame = 1806 effectTime = 1806 effectDuration = 3901 testStart = 0 testDuration = 3091 Any ideas if I'm doing something wrong, if it's a FC bug or what? _______________________________________________ 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... The first set of numbers (duration=300) comes from rendering to the canvas window. The second set (duration=3901) comes from rendering to the viewer window. From what I can tell, the in and out are set to a much smaller range centered within the 3901 frames, which I guess explains why the current frame number is so large. It sounds like the TimingAPI is giving you wrong values when your clip is loaded into the viewer? (The viewer is the per-item display window usually in the upper-middle of your monitor; the canvas is the sequence display usually in the upper-right of your monitor). If so, that sounds like a bug in Final Cut; I'll check it out. Kristian, is it possible that you're seeing the same thing, or is there more going on in your case? I'm seeing something weird in both FCP and FCE. I am working on a filter plugin that changes over time, so I'm getting the clip- relative frame number and the clip duration in order to calculate the fraction "done": timingAPI = [_apiManager apiForProtocol:@protocol(FxTimingAPI)]; effectTime = [timingAPI inputTimeForFilter:self fromTimelineTime:renderInfo.frame]; effectDuration = [timingAPI durationOfInputToFilter:self]; Everything behaves correctly in most cases, but I've run into one case where I get very unexpected numbers. Here's what I'm doing: 1. Launch FCE/FCP with a new project. 2. Drag a clip onto the timeline so it starts at about the 01:00:00;08 second mark. 3. Move the playhead so it's a few frames into the clip. 4. Click once on the clip so it's selected. 5. Locate my plugin in the list and drag it onto the clip. I have a breakpoint set in -renderOutput:withInput:withInfo: which gets hit at this time. I see: This is what I expect. I continue execution then switch back to FC. If I double-click on the clip, my plugin breakpoint gets hit once again, this time with the following values: steve This email sent to site_archiver@lists.apple.com