[Bf-compositor] Compositor Awareness

[Jeroen Bakker]

Hi all,

This is a different kind of speedup It is more in the area of 
usability/user friendliness. As developer it seems easy to implement and 
lowers user stress-levels, by that they don't have to wait until the 
previous compositor run is finished, before the next will start up.

Just to be clear IMO it should not change the hurdle of implementing 
buffering/caching and so on for the better or worse.

Also as this only impacts the compositor when in editing mode it should 
be able to predict what paths are valid as blenders compositor works 
from output to input. so if the changed node is not connected to these 
output (direct or indirect) we should not start up the calculation run. 
(But sergey is free to come up with his own idea on this subject)

Greetings,
Jeroen & Monique
  - At Mind -


On 08/25/2014 07:29 PM, Francesco Paglia wrote:
> Isn't this request by Aditia part of the compositing improvement?
> Along with caching shouldn't be the node evaluation?
>
>
>
> 2014-08-25 19:05 GMT+02:00 Diego Gangl <dnicolas at gmail.com 
> <mailto:dnicolas at gmail.com>>:
>
>     Hi, I agree. However I wonder how it's going to work in some
>     cases, like rendering an animation. Should we remember to
>     remove/mute viewer nodes or will Blender detect it?
>
>     What I mean is, how will Blender decide when to route to viewer,
>     and when to composite/file output?
>
>     Cheers,
>
>
>     On Monday, August 25, 2014, Aditia A. Pratama
>     <aditia.ap at gmail.com> wrote:
>
>         Hi all,
>
>         I've been discussing with Sergey about compositor awareness.
>         Well for current compositor, the issue is each time we add
>         node, compo will automatically calculated even that node is
>         not connected to viewer.
>
>         There's workaround to solve this by set 'use nodes' option to
>         false, but we have to do this manually.
>
>         We both agree that compo should become aware of  what is
>         needed for current display and so even changing values in node
>         that not affecting viewer will not calculated.
>
>         So, what do you think?
>
>         -- 
>
>         <http://kampoongmonster.com>
>
>         Aditia A. Pratama / Chief Technical Officer
>         +62 813 4747 8111 <tel:%2B62%20813%204747%208111>/
>         aditia at kampoongmonster.com
>
>         Kampoong Monster Studios
>         Jl. Geger Kalong Hilir No. 47 Menara RDC Telkom Lt.4 Bandung
>         Digital Valley 40153
>         http://kampoongmonster.com
>
>         <http://twitter.com/aditia_ap>
>         <http://www.linkedin.com/in/aditiapratama>
>
>
>     _______________________________________________
>     Bf-compositor mailing list
>     Bf-compositor at blender.org <mailto:Bf-compositor at blender.org>
>     http://lists.blender.org/mailman/listinfo/bf-compositor
>
>
>
>
> -- 
> Francesco Paglia
> Vfx and Production Supervisor
>
> mobile  +39 347.82.12.473
> e-mail f.paglia.80 at gmail.com <mailto:f.paglia.80 at gmail.com>
>
>
>
> _______________________________________________
> Bf-compositor mailing list
> Bf-compositor at blender.org
> http://lists.blender.org/mailman/listinfo/bf-compositor

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-compositor/attachments/20140825/b7aafe9a/attachment-0001.htm