[Bf-committers] Proposal: Canvas compositing

François T. francoistarlier at gmail.com
Tue Aug 2 21:54:28 CEST 2011

here a few points which is important IMO :

Canvas Size can be different from Render Size. In our case the Composite
node defines all those outputs param (render size, frame rate, )... Canvas
Size could be of any size and most of the time would be bigger than the
render size for sure (ie matter painting)

Transform node (I think Sergey just did one a few days ago), It's fine to
have param in the node option to change as Trans, rot, scale, anchor point,
.... But a handler is needed in Image Editor. So clicking on a transform
node should draw an handler on your viewer

I don't think backdrop is very useful in itself except when you are on a
laptop with only one tiny screen that can help. But image viewer is more
what you would use to work. You got the scopes, all the set for tools, can
easly view the channels, select different viewer easly, choose slots,...
looks more like a place where it should be. Plus it doesn't have some
spaghetti in the middle of your image :)

as for axis, I don't thing there is render order of canvas until you
introduce 3D canvas. (which by the way the approach of Sergey with camera
and bundles could be an idea of representing your comp in 3D view).
But for now on the only order is controlled by the way your mix and merge
layers together

I can't wait for this :)



2011/8/2 Troy Sobotka <troy.sobotka at gmail.com>

> On Tue, Aug 2, 2011 at 10:03 AM, michael williamson
> <michaelw at cowtoolsmedia.co.uk> wrote:
> > As a dual screen user I'd question why this has to be "just" the
> > backdrop of the node editor...
> I don't know if that is in Jeroen's design plan, but I'd heartily +1 this.
> The backdrop viewing option has more than a few design shortcomings.
> The backdrop is difficult to translate, to zoom, and to analyze with
> the degrees of freedom and efficiency that dedicated viewports permit.
> If we can learn anything from other industry applications, it is that
> the composite node breakdown region should be a dedicated area
> strictly to visualize and organize the node groups. The double duty
> this region has evolved into within Blender is sub optimal at best.
> With respect,
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

François Tarlier

More information about the Bf-committers mailing list