On Thu, 24 Jan 2008 14:00:51 +0100, Ichthyostega <[EMAIL PROTECTED]>
wrote:
Martin Ellison schrieb:
OK, though I suspect many plugin writers would like to avoid all the
extra complexity, so perhaps the interface needs a render context hints
object.
Hi Martin,
answering directly to this: no, it's not an issue, because the effect
plugins
will never see anything of these heuristics. Remember: in cin3 (as in
cin2)
we use exclusively the "pull" approach. The engine decides and then pulls
frame XYZ from some "exit node", which causes this one to request the
necessary frame(s) from its predecessor(s).
Hm. How will a frame range request propagate through all the nodes,
unless the nodes are aware of such ranges (instead of just a frame number)?
The problem at hand is that we want the "puller" to query the pipeline if
a frame can be delivered in time. Is this negotiated between all the
nodes?
External plugins will sit in an adapter node handling the internal
communication and just requesting the bare calculations from the plugin.
Seems reasonable. The adapter can "learn" about the latency and the
throughput of the external plugins by running a pattern test.
--
Herman Robak
_______________________________________________
Cinelerra mailing list
[email protected]
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
