[fxTimingApi startTimeForEffect:self];
In FCP of previous versions (not sure, but not TOO long ago), used to always return 0. And we relied on that, so we could use the same code for FCP and Motion. Now FCP (10.2.2, possible other versions) now returns –5? Or sometimes in my tests, -6? Perhaps it's dependent on something I don't quite understand.
What? Confused. I'm presuming this is a bug? If not, Darrin, can you explain what deal is here?
[fxTimingApi durationForEffect:self];
durationForEffect seems to also have 6 or 5 extra frames added to it, so the calculated end frame of (start+duration-1) is correct.
Help? What's going on here?
Pete