On Sep 6, 2006, at 3:04 PM, Derrick Bass wrote:
I've written a data handler component. As I would expect, during playback calls to my ScheduleData64 function are asynchronous. On the other hand, if I save a movie self-contained, the calls to ScheduleData64 are synchronous. However, when I export a movie, the calls are asynchronous, and this is fouling up the export because sometimes I can't return the data in time.
I wrote a delegate-only component that lets me spy on Apple's Data Handlers. Interestingly, I found the opposite behavior for the http data handler and the alias data handker: calls to ScheduleData were synchronous during an export, but asynchronous during a save self-contained.
I can't figure out what's determining how the data handlers behave. For mine, since it gets information over the network, I want synchronous behavior both for flattening and for exports. How to I make that happen?
Have you tried returning "notEnoughDataErr" when you can not return the data in time? This error tells QuickTime that the data it requested was no available within the timeout period, so it should ask again later.
eric
