Just what I needed. Thanks a bunch.Don On Mon, Aug 17, 2009 at 10:07 PM, vade wrote:
> If you really really really need to do this you can make a series of small > mini compositions that encapsulate each operation you may want to do and > published each with inputs and outputs and connect them programatically via > setting an input key of one QCRenderer with the value of an outputKey of > another. For speed, you can use [someQCRenderer > setValue:[someOtherQCRenderer valueForOutputKey:@"myPublishedOutputImage" > ofType:@"QCImage"] forInputKey:@"myPublishedInputImage"]; > > So you would have someQCRender which has a loaded comp that has a published > image input "myPublishedInputImage" and set it to the published image port > from someOtherQCrenderer with a comp that has an output image named > "myPublishedOutputImage". > > What you end up doing is similar to core image units, but they are more > flexible because you can load the QCRenderer with a QCComposition that > outputs not just images but multiple images, numbers, arrays, etc. > > > > On Aug 17, 2009, at 10:09 PM, Don Atkins wrote: > > >> I'm working on my first mac application which will be a video analysis >> tool. I want to use QC but I need to build compositions on the fly. >> Basically I want to duplicate fun house but with video. I've dug through the >> manuals, this list, and the API. The Composition Loader looked promising but >> I didn't see anyway to make the connections without direct interaction. The >> last resort is to build .qtz file direct but I'm hoping I'm missing >> something. >> >> Thanks, >> Don >> >> >> >> >
_______________________________________________ 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]
