Hi Christopher, |
Time input sucking fps even where patch doesn't have much to do.qtz
Description: application/quartzcomposer
This example I have two JS patches. The first just flip-flops b/w two Arrays of n and n/2 elements. It only takes CPU when changing state. The second patch modifies it's output to match the length of the input Array. First it compares .length of the Arrays, if same do nothing. Although it's actually written if (a<b) {lose elements}; if (a>b) {add elements}, where a is input and b is internal JS array. So maybe some kind of if (a == b) break_statement(?); is required Anyhow without a Time input forcing execution every frame it runs 60fps even on my old box but with execution every frame it crawls to 5fps at n=2000 Best Alastair The machine does not isolate man from the great problems of nature but plunges him more deeply into them. Antoine de Saint-Exupery |
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
