I'm not going to quote the discussion here, but I've been having gobs of
problems with similar issues: Not being able to initialize inputs at launch,
not being able to read related outputs, and some things simply not
propagating values. I should note that I'm a QC neophyte, so who knows?
I'm using a QCCompositionLayer. Some things work in the viewer but not
in my layer. Some things just refuse to work in either.
For example I have an image transform that refuses to take a change in
the ScalingX input. I flip the scale value to a negative to reverse the
image. It works correctly if set initially, but refuses to change while
running. I even added an LFO, connected to something innocuous, just to get
frames out instead of a static image. Still, no go on the switch.
I have another (test) composition that uses a multiplexer (with a bool
switch input) to simply change to another output image after a 5 sec. timer
(PatchTime + conditional) fires. It works perfectly in the viewer, but not
in the Layer.
BTW, all attempts to put an observe on the output of that timer have
failed.
I tried using a splitter to set a (BOOL) constant flag I could read,
just to distinguish between two types of compositions I want to use. Even
that didn't work. I finally took someone's suggestion here and set it as an
attribute. At least that worked.
One final comment (or question). Where the heck do you get decent
specifications on existing patches? The self documentation is next to
worthless. For example, I haven't a clue what that Feedback patch does,
which was the initial subject of this thread.
_______________________________________________
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]
