Thank you for your answers.
I have to be more precise.
The Iterator patch is not creating a new instance of each object for
each iteration, but using the same instance and changing parameters (you
can test it with an NSLog(@"%p", self), its the same memory address).
But, when I have a patch that need to feedback on its own calculated
values over time, it's not working anymore, even with a time parameter
exposed (custom or not).
So, I can't cache any value internally in my plug-in and it's losing its
interest.
But, Smooth patch (which is certainly feedbacking on its own values to
calculate the smooth curve) is working in Iterator since 10.6 and I
would like to know if someone knows how it's done... or how it could be
done :-)
Ben.
George Toledo <mailto:[email protected]>
24 août 2014 20:09
I don't think that this is supported in the qcplugin API, and I think
there are some peculiarities that make it difficult to impossible even
in the private API to interface with the built in iterator and
iterator variables. Do any known third party patches do this?
Best regards,
gt
Achim Breidenbach <mailto:[email protected]>
24 août 2014 18:38
Hi Ben,
I don't know exactly how the iterator patch is implemented, but I
think there are some performance optimizations going on. I think they
are depending on if there changes on the inport ports of a patch.
If the inputs don't changes, the patch isn't processed. Maybe you can
force the processing by having an dummy input where you connect the
itorator index to, just as a test. Does this change some thing?
Just my 2 cents.
Achim Breidenbach
Boinx Software Ltd.
Benoît LAHOZ | L'ange Carasuelo <mailto:[email protected]>
24 août 2014 00:33
Hi !
That's not the first time I have this trouble with one of my custom
plug-ins in iterator patch, but now it's quite blocking.
I can't understand how the iterator patch is internally working : it
looks like I can't cache any variables in the plug-in if I want to use
it in iterator.
But, since 10.6 Smooth patches (which is the kind of patch I'm
actually building) seems to be working in iterators, and I would like
to know how it's possible.
Any of my "time based" (even with time mode set to none, only dealing
with cached variables) patch seems to be blocked.
I've made a "spring" patch that is estimating the next position of a
3D point (NSArray input to 3 double values -> output NSArray again)
and outputting the NSArray at each cycle, and it's like if the
iterator was forcing a median value between my points...
Any advice about this issue would be extremely appreciated !
Ben
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [email protected]
