QT stuff can't run on any thread other than the main thread (without a lot of hand-holding that the QC Movie Loader patch doesn't do anymore -- that's a QC bug). QuartzBuilder is "properly" designed to handle UI and event stuff on the main thread, and do rendering on a secondary thread (so that user interaction doesn't slow the rendering down like it does in the editor). QuickTime notices this, notices that it wasn't hand-held, and dies.
There aren't any workarounds right now (other than making QB single-threaded, which defeats the purpose) -- eventually we may make a thread-safe movie player patch, but that's a way out (as QT still sucks as a dev platform/API).
the same things happens here, looks like a threading issue.
It's a quicktime bug thinly veiled as a QB bug --
QT stuff can't run on any thread other than the main thread (without a lot of hand-holding that the QC Movie Loader patch doesn't do anymore -- that's a QC bug). QuartzBuilder is "properly" designed to handle UI and event stuff on the main thread, and do rendering on a secondary thread (so that user interaction doesn't slow the rendering down like it does in the editor). QuickTime notices this, notices that it wasn't hand-held, and dies.
There aren't any workarounds right now (other than making QB single-threaded, which defeats the purpose) -- eventually we may make a thread-safe movie player patch, but that's a way out (as QT still sucks as a dev platform/API).
as i know, the latest vade's movie player build working in multi-threaded situations, but i don't know how far is the release.