Sorry to keep piling more problems onto the list, but I just go with what I get. It would be nice to hear someone reads them...
In addition to the unsolved problem with garbled and out-of-sequence frames on my single-core PPC (perhaps the buffer pools are buggy and the buffers are being reused even though they are still retained and locked?) ---- I have discovered another qt movie in my collection that is problematic on all platforms----
When trying to read this movie, my QTVisualContextImageAvailableCallback is being called with buffers that never have a kCVBufferMovieTimeKey dictionary attached... so there is no usable timing information at all for any frames in the movie (the CVTImeStamp argument is never usable because it is only a host time, not any kind of movie-related time). I've verified that the TimeValueKey is not attached directly to the buffer on these frames either.
So how is this supposed to work? My GetMoviePict reader is slow, but at least it works. I'd like to use the newer stuff, but it has to be ready for prime time. Should I sacrifice roosters or lambs?
Russ
_______________________________________________
Do not post admin requests to the list. They will be ignored.
QuickTime-API mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quicktime-api/email@hidden
This email sent to email@hidden
