Hi,
Our new application is a virtual mixer focusing on realtime interaction.
We have a main thread that takes care of the user interface and a
secondary thread that does all the graphic processing in real time.
In order to keep fluidity, we would like to have all QuickTime
processing done outside from the main thread.
Currently our problem is that the "RunApplicationEventLoop" is
indirectly idling our movies from the main thread and this gives us
problems (locks) with components that are not thread safe, such as the
MPEG codec or some Sequence Grabber devices... We do know that the way
our processing is done, even not thread safe component would run fine
(we're just reading there) except that having MovieTasks called 'behind
our back' makes problem arise. This is even more frustrating that the
windows version of QuickTime allows this just fine.
What is the best practice to be able to do our processing in a secondary
thread exclusively? We've gone through the Threading Quicktime document
that states that handling non thread safe component should be done in
the main thread but that seems to be such an overkill, especially for
real-time operation like we do.
-----------------------------------------------------------
Marco Hinic (email@hidden)
ArKaos engine architect & CEO
http://www.arkaos.net
In cyberspace nobody knows you're a cat
-----------------------------------------------------------
_______________________________________________
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
