site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com 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? steve _______________________________________________ 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... 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: This email sent to site_archiver@lists.apple.com