[Bf-funboard] Render size percent in compositor

[W. Nelson]

I have been looking at this issue also for a while.  I have a simple py addon panel to give more control but I think more needs to be done than py can do.  Another point is 50% is of the resolution H and V numbers not the pixel count.  It doesn't result in 50% less pixels.  It only halves each resolution number.   I regularly need half of the pixel count or a specific reduced resolution target such as 240.  The speed of the workflow is important here also.

A quick reduction of 1920x1080 to 720, 480 or 240 are most useful to me.  Not some arbitrary percentage.  As mentioned other side effects are also should be reconsidered.  So a 1+ to the previous posts.  The biggest value of this feature in general is as test renders or web targets IMHO.   

JTa




________________________________
 From: David Jeske <davidj at gmail.com>
To: "bf-funboard at blender.org" <bf-funboard at blender.org> 
Sent: Friday, August 30, 2013 12:26 AM
Subject: Re: [Bf-funboard] Render size percent in compositor
 

On Thu, Aug 29, 2013 at 11:23 PM, Tony Mullen <tony.mullen at gmail.com> wrote:

> The problem is that if I do my compositing at a smaller percent, all
> pixel-based values such as translations, blurs, etc are all wrong for the
> final render.


This is also true if you have any composite video-inputs, as they are not
re-sized by render-percentage either.

I agree, it would be nice to have a clear and separate concept of a
"proofing" or "proxy" render-percentage, which causes every part of
blender-render to operate on a 50% proxy with a scaled virtual coordinate
system.  (video-input, VSE, compositor transform nodes, masking outputs,
etc)
_______________________________________________
Bf-funboard mailing list
Bf-funboard at blender.org
http://lists.blender.org/mailman/listinfo/bf-funboard