George I agree. Speeding up will work only for consumers, the last nodes in the compositions. They still can react to input changes. I think it would be faster as packing ie. 200k particles (600k floats) which then are immutable in the objc container, you need to recreate the arrays on every single execution, it's just expensive. The solution for this would be to just introduce a plain NSData type in QC. Maybe with some basic metadata attached so you can match the format. That could speed up things but it needs to be designed properly as it can create a lot of mess with dozens of new types per developer ;) Here's example of the first case using the plugin: Or as composition: |
Objective-C Consumer Example.qtz
Description: application/quartzcomposer
It would be nice to use Accelerate framework to compare the speed. Mirek On 4 Oct 2010, at 16:28, George Toledo wrote: Mirek, you're totally missing my point, which is integration with the rest of QC. QC doesn't have a C-array structure type native to it, and if it did, it wouldn't necessarily become "blazingly fast" just because of it. I understand where you're coming from, insofar as utilizing plugins in a way that doesn't necessarily have to interact with anything else. |
_______________________________________________ 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]
