Looks like the disabled billboard is not killing that execution
branch, as it ought to because the value of Enabled is dependent on
the patches it is rendering. In debug mode, you can see both patches
get executed when they shouldn't.
Sort of -- Enable needs to re-evaluate the branch to see if the
condition has changed (and thus, the consumer's enabled status). If a
disabled patch never re-evaluated its enable input branch, it would
end up staying disabled forever. The behaviour I documented is
actually "Correct" as far as graph evaluation is concerned, just
"incorrect" as far as generated output (since audio isn't generated at
the consumer). I can't recall for sure, but I believe the inverse
was the case in Tiger: a disabled patch wouldn't re-evaluate its
enable input, so once it was disabled it was toast unless the enable
input was used elsewhere to keep that branch of the graph running. I
might be mistaken on that point though.
Should this get a bug as well? I don't know that there's a reasonable
way to fix this from within QC...
(Looks like Adrian beat me to the Loop Duration Hang bug :( sad..... )
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden
This email sent to email@hidden
