| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
I could conceivably request YUV results and write my own parallelized converter, but that would be a pain and it's not obvious how to tell when this is a good idea, given an arbitrary movie (ie if the codec already produces RGB it would be counterproductive, how to tell?).
I also have major zero-fill problems --- when ingesting footage my app is running as a RAM cache so gobbling huge amounts of RAM is a given.
**** Now the show-stopper **** When I try reading a different movie: my code reads all the "interesting times" from the movie; to get a given frame, it does a SetMovieTime with the corresponding interesting time built up into a TimeRecord containing the interesting time, the scale value, and the timebase (as obtained earlier from the movie). So it's all exact integer timing. The interesting times in the movie have some variability, at frame 10 in this particular movie, it is timevalue 201. But, when the VisualContextIMageAvailableCallback is called, I extract the timevalue and it is 200! Since it's waiting for the requested timevalue 201, the reader hangs permanently.
_______________________________________________ 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
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.