> Playing QT content on a background thread is error prone, complex and poorly > supported.
Thanks, I was afraid it would sum up to that. I'll settle with the way things are for the moment, pretty decent. F. On Fri, Dec 18, 2009 at 5:23 PM, Jean-Daniel Dupas <devli...@shadowlab.org> wrote: > > Le 18 déc. 2009 à 17:10, slasktrattena...@gmail.com a écrit : > >> Hi all, >> >> QTKit docs say that Quicktime playback is designed to work without >> interruption on the main thread. This works fairly well, most of the >> time, but I notice occasional glitches in the playback when the >> computer is busy, especially when loading web content or reading files >> (regardless of what app is currently busy, not necessarily mine). So >> I'm considering doing the playback on a secondary thread. Is this a >> safe thing to do? Will it improve performance and if so, what's the >> recommended design pattern? >> >> Thanks. >> Fabian > > Playing QT content on a background thread is error prone, complex and poorly > supported. > > But if you really want to go this way, you will have to read this: > > http://developer.apple.com/mac/library/technotes/tn/tn2125.html > > > Note that creating thread is not a magic way to improve global OS > performances, it's just a way to perform two tasks simultaneously in a single > application. > If what cause glitches in your app is not related to something you do in your > application on the main thread, so this is pretty much useless. But the only > way to know is to profile your application. > > > -- Jean-Daniel > > > > > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
