oops ignore this - i should have read the previous posts first :(
James Sheridan wrote:
So lets make sure im right on this right - when an object is inside an
iterator there is only one instance of it. The iterator then just
reuses this object each iteration causing the resulting behavior.
The reason I tried the smooth patch was because I'm writing my own
plugin that averages data over a period of time and was having the same
issue with it. How can I enable this plugin to know its inside an
iterator and to not spaz out.
Christopher Wright wrote:
Could someone please explain to me why the smooth patches inside the
iterator (in attached patch) act differently from those outside?
The smooth patch is "stateful" -- meaning, it stores data inside from
the previous frame. When it's inside an iterator, it doesn't know,
and stores data from the previous iteration instead. Don't use smooth
patches inside iterators, they'll produce incorrect output.
See Also:
http://lists.apple.com/archives/Quartzcomposer-dev/2008/Mar/msg00139.html
--
[ christopher wright ]
[EMAIL PROTECTED]
http://kineme.net/
_______________________________________________
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/james.sheridan%40anu.edu.au
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]
