[Bf-committers] grading w/ compositor

Xavier Thomas xavier.thomas.1980 at gmail.com
Tue Nov 8 21:19:20 CET 2011


I am desperately missing the time to finish my "OpenColorIO" integration
and other opensources stuff I wass doing before. I hope this situation will
change in a few weeks/months. In the meantime being the coder of the scopes
here is my toughts:

- *Scopes are slow*
> I don't know if they are threaded or not, but I found out that having the
> scopes open in image viewer really slow down the computing time. To be
> honest when doing a primary to bring the footage at a neutral stage (white
> balance, saturation, ...)  I pretty much only look at the RGB waveform and
> the Vector Scope. (never trust what I see in the image viewer output).
> Moving a param in my comp (which basically have only one input, one RGB
> curves and one viewer, and waiting 1 or 2 sec for everything to update is
> not really efficient.
> I wonder if that cannot be faster ?

With big resolution it is slow  indeed. The indea was to make it use a
background job so that it does not freeze the UI while updating (threading
is also an option). I had a patch in the tracker for this but due to some
update notifier problem it was causing lots of redraw of the image and
scope regions so it was never applied to trunk, maybe now the situation is
better and it is worth taking another look a it.

> - *Fine tuning is impossible*
> adding a point in the RGB curve and moving it slightly with the mouse to
> adjust white balance is really challenging and almost impossible to get
> perfect. perhaps there is shortcut to move the selected point which I'm not
> aware of.
> A suggestion would be to not limit the zoom in the compositor and be able
> to scale the nodes as much as we want to have a more accurate values on
> those.
> Another suggestion would be to display the coord of the selected point
> where we can enter some values ?

Blender 2.4x style was to keep Shift pressed while draging for better
precision. This seems to have disapeared in some places since 2.5

- *Min/Max of waveform are difficult to see*
> the 3 lines on the right of a waveform defines the max and min of each
> channels. a good way to start to white balance your footage is by trying to
> have those 3 lines on the same level. Right now they are kind of hard to
> see. I don't know if we can make them bigger or find a better display for
> it

I don't find them hard to see, but as the original coder of the scopes I
had some feedback where people do not understand that it is min/max and
tought it was garbage. This king of style customusation is easy for anybody
with C/OpenGL knowlage, but it would be better to have a clear goal before
messing the code just for personal ahesteic preferences.

Also the scopes permits scaling but not panning, it would be good to add
panning to them. The problem: those key combination are hard coded and not
configarable by the user keymap.


More information about the Bf-committers mailing list