Wasn't so much feedback here. But this patch was considered extremly useful for 4K ToS project by Francesco. So i moved it to trunk.
Further tweaks are possible for sure, but currently couldn't think of any. On Thu, Mar 14, 2013 at 6:08 PM, Sergey Sharybin <[email protected]>wrote: > Quick patch implementing Ton's idea: http://www.pasteall.org/40502/diff > > What it does: > - If there's no render result visible when editing tree, compo output node > would be ignored on compositing > - If there/s no viewer image opened in image editor, and no backdrop > visible in node editor, viewer nodes will be ignored. > > What it doesn't do: > - Final rendering didn't change -- it'll still calculate all compo output > and viewers. Arguable, but that's how things used to work for ages, easy to > check on whether viewer nodes are needed before doing final compo. > - If render result is visible and tree is editing in a way that only > viewer node is reconnecting, compo output would be recalculated every time > you're reconnecting viewer node. It is technically possible to avoid, but > would need some changes in how node tree is tagging for refresh in editor. > Think better to wait for after pynodes merge before solving this. > > > On Thu, Mar 14, 2013 at 12:15 AM, Ton Roosendaal <[email protected]> wrote: > >> Hi, >> >> It is very straightforward to make the UI tag nodes that need updates. >> That's for the changed node, the visible viewer, and whether a >> composite-out is visible in Image Editor. >> >> No options needed! >> >> -Ton- >> >> ------------------------------------------------------------------------ >> Ton Roosendaal Blender Foundation [email protected] www.blender.org >> Blender Institute Entrepotdok 57A 1018AD Amsterdam The Netherlands >> >> On 9 Mar, 2013, at 14:58, Sergey Sharybin wrote: >> >> > Hi, >> > >> > Noticed that currently compositor output node will be fully recalculated >> > every time you're editing compositor node tree. This adds quite enough >> of >> > CPU consumption and only benefit from this is having Render Result image >> > up-to-date. >> > >> > Is it something indeed expected by artists? From what i've noticed >> during >> > Mango and some post-mango artists feedback -- they're usually >> disconnecting >> > compo output node to make compositing faster. But this often leads to >> > troubles when you forget to connect node back, send 12hrs shot to the >> farm >> > and.. Well, nothing fun out of this. >> > >> > So, the question is: is it even helpful to have Render Result updating >> > every time you're editing the tree? And if so, what about: >> > >> > - Making it a compositor option to ignore compo output while editing >> > - Making it possible to mute compo output node, which will mean it's >> > ignored while editing (but not while rendering) >> > >> > -- >> > With best regards, Sergey Sharybin >> > _______________________________________________ >> > Bf-committers mailing list >> > [email protected] >> > http://lists.blender.org/mailman/listinfo/bf-committers >> >> _______________________________________________ >> Bf-committers mailing list >> [email protected] >> http://lists.blender.org/mailman/listinfo/bf-committers >> > > > > -- > With best regards, Sergey Sharybin > -- With best regards, Sergey Sharybin _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
