It isn't the movie player plugin as it works fine in quartz composer and gets the proper messages. I switched to the v002 because the current movie player patch had some strange behavior issues which I assume are quicktime related. The main issue is that there needs to be a way of telling a composition to stop like qcview does when it stops or unloads. I think this happens beyond simply releasing the composition.
On Mar 1, 2010, at 11:29 AM, Tamas Nagy wrote: > As far i know, the v002 movie player doesn't work properly on a background > thread, maybe this is the issue. Did you tried with the built-in movie player > patch? > > > On Mar 1, 2010, at 5:10 PM, Joshua Strickon wrote: > >> Autoreleased or not, it seems that the composition movie rendering is not >> stopping. This could be some quicktime blunder. I did some more digging >> and it looks like QCView has all the functions for starting, stopping and >> unloading compositions. I get all the messages properly in Quartz Composer. >> I abandoned using qcview because it renders on the main thread which had >> undesirable results. I wonder if there are hidden private apis that could >> deal with unloading, stopping and cleanup. >> >> >> On Mar 1, 2010, at 9:14 AM, Tamas Nagy wrote: >> >>> Hi, >>> >>> as i remember, the QCComposition object is autoreleased, for be sure, check >>> the QCComposition's documentation. It's not the answer for your question i >>> know, but FYI :) >>> >>> >>> >>> 2010/3/1 Joshua Strickon <[email protected]> >>> I have an nsview for which I programmatically swap out quartz compositions. >>> I do this by recreating a new QCRenderer. I have using the V002 movie >>> player plugin as I had terrible results with the current Apple quartz movie >>> player patch, it could be related to this problem. After a bunch of >>> switches, I have noticed that the thread count going up in sync, to the >>> point of instability. Upon further investigation it appears that the >>> plugin disableExecution or stopExecution functions are not getting called. >>> When should these get called? Shouldn't these get called when I recreated >>> the QCRenderer with a new composition? >>> >>> I currently have an array of compositions that I keep from querying the >>> repository. I then reference the array by a number that is passed to the >>> code that swaps the compositions. I simply create the new renderer and >>> pass in the composition and the relative view pieces. Seems like the >>> composition is not getting cleaned up when it is no longer being rendered. >>> Is it possible because my array is retaining the composition? How do I >>> tell the composition to that is is no longer being used? >>> >>> Any ideas? >>> >>> Here are the swap functions. >>> >>> >>> Thanks >>> >>> Josh >>> [_renderer release]; >>> _renderer = [[QCRenderer alloc] >>> initWithCGLContext:(CGLContextObj)[[qcView openGLContext] CGLContextObj] >>> >>> pixelFormat:(CGLPixelFormatObj)[[qcView pixelFormat] CGLPixelFormatObj] >>> >>> colorSpace:CGDisplayCopyColorSpace(kCGDirectMainDisplay) >>> >>> composition:[compositions objectAtIndex:comp]]; >>> >>> _______________________________________________ >>> 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]
