On Nov 19, 2010, at 4:22 PM, Christopher Wright wrote: >> Alas, adding a runloop and sleeps don't help. It seems the problem is >> internal to the -renderAtTime: method. It doesn't check if the comp uses the >> Video Input Patch, and so doesn't wait for the camera to come on. If the >> video patch had a synchronous flag, that might fix it. Guess I'll try to >> find another route... > > What if you do a -renderAtTime:, then sleep a few seconds, then another > -renderAtTime:?
I tried that, and a lot of other crazy things, but it seems that the qtz composition isn't open/running until -renderAtTime: hits it, and when it's got the image, it closes/stops the comp, no matter how many times or how fast you ask it to render. It does some fancy legwork to simulate "offsetting" itself so many seconds into the composition, but even setting the 'start time' to 10000 seconds or so, -renderAtTime: doesn't let the camera come on, it just takes quick snapshots and returns blank images. I also tried very closely spaced hits, like .001, but no go. Very frustrating! _______________________________________________ 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]
