Hey, QCRenderer is not thread safe, but this not means it won't work well in a multithreaded scenario. You just need to use the QCRenderer on the same thread on the thread you created it. If you miss this step, your application will leaks memory. The movie player patch should work an a secondary thread too with the major codecs.
You can use an NSThread to drive the rendering loop without problems, not just the CVDisplayLink. Cheers, Tamas On Sep 28, 2011, at 9:16 AM, Nisar Ahmed wrote: > Dear List, > > I need to know the difference between CV's Displaylink thread and a usual > thread that we use in our cocoa application for rendering with QCRenderer > object. All i know about QCRenderer and threads is that QCRenderer does not > render compositions on thread properly, specially the ones with video. > > The reason for using my own thread is that I need to render compositions on a > different frame rate and displaylink is always tied to display refresh rate > that cannot be changed easily. > > Thanks > Nisar > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Quartzcomposer-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/quartzcomposer-dev/tamas.lov.nagy%40gmail.com > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
