My next "guess" as to what you could do is to use a smoothing patch for each iterator instance outside the iterator. Use the first iterator as an array itself, and a 2nd iterator for display. The first iterator would not have a consumer patch in it for this trick to work. But, say you had ten items you wanted to smooth. Iterator would be plugged into a multiplexer with ten outputs, and it would export the iterator variable for the index of whichinstance and variables it was effecting -- say something like X and Yposition over time. The multiplexer would output to ten separate smooth patches -- thus keeping a record of the data and better efficiency than a Javascript patch for determining a standard deviation (if I'm looking at what a smoother really does). The smooth patches could then go into someother patch that would allow the data to fill a structure. The second iterators only job now is to take this structured data, and apply thecalculations based upon iterator variable to match the index up with the"smoothed" data, and then display this on the screen.
Iterators are always red (in Tiger and Leopard), so they can't have outputs to plug into a multiplexer, even if they have no consumer patches inside. Maybe I'm misunderstanding your setup though.
standard deviation is a bit hard-core for what the smoother does: simple interpolation (linear, cubic, and sinusoidal I believe). It only has half a dozen or so variables of state, so it can't do significant std.dev. for any of its interpolation settings.
-- [ christopher wright ] [EMAIL PROTECTED] http://kineme.net/
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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]
