| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
But now, I took my code and ran it on a PowerPC iMac running 10.4 and the latest Quicktime, and I see nasty frame mis-ordering problems and some mangled frames where one image has clearly overwritten part of the other. The PPC machine is uni-core; my other machines are Intel multi-core (2 or 8) running 10.5. So the problem may be specific to being on only 1 core, to being a PPC, or to being on 10.4.
Either way, it seems to be a thread-safety issue, which leads to the obvious question: exactly what degree of thread-safety do the Core Video and QTVisualContext calls have? As they are advertised as "modern" I have treated them as thread-safe ...
It's very odd since it works nicely on multicore machines where the sequencing can be fairly random and would tend to expose simultaneous-access problems. It seems like maybe 10.4 is buggy, almost like something is saying "we've only got one core so why bother with this mutex stuff" ?!
_______________________________________________ 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.