<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:tahoma,new york,times,serif;font-size:10pt">From a user perspective, there are two problems that need a solution. The first is that a shot is just off-color, perhaps is not snappy enough. The second issue may be that different shots are filmed under different lighting conditions, and in order for shot 2 to look contiguous to shot 3, the color balance and luminance have to match pretty closely in the rendered output. A related issue is that you want all shots related to a topic or set to have a certain color spectrum, regardless of their actual filmed color. Therefore, you want to adjust the actual footage (strip) to have some color historgram.<br><br>We already have display modes that give us color spectrum info, and act like gauges. What we need is a tool to help us adjust our input so that we get the "right" values, at least according to the
gauges give us the right values. <br><br>For the first issue, just a good understanding of what to fiddle with to make certain kinds of corrections is needed. Anything that is in somewhat common with other areas of Blender (shaders, nodes) would be easier to remember. For the second issue, some fairly straightforward way to use the other VSE display modes (historgram, vectorscope, luma) and a tool to make them match some other (rendered or reference image) is needed; some way/lift/gain/adjustment tool color correct/adjust different shots (strips), each differently, so that together they flow. in other words, strip A + adjustment A == strip B + adjustment B. <br><div> </div>----------------<br>Sent by Roger Wickes for intended recipient. If you are not the intended recipient, please delete this message and contact Mr. Wickes immediately.<br><br><div>Atlantica Investments, Inc.<br>PO Box 680310, Marietta, GA 30068 USA<div><br></div><div
style="font-family: tahoma,new york,times,serif; font-size: 10pt;"><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Xavier Thomas <xavier.thomas.1980@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> bf-blender developers <bf-committers@blender.org><br><b><span style="font-weight: bold;">Sent:</span></b> Wednesday, December 10, 2008 6:28:02 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [Bf-committers] Color correction in sequencer.<br></font><br>
they are not really intuitives, but they works like "Levels" in gimp<br>Lift must set the black level<br>Gain the white<br>and Gamme the mid point<br><br>The problem here is that the the values are manipulated for :<br>
- "1,1,1" to be "no change value" <br>- Values between 0 and 1 to darken the image<br>- An "inverse" button tho permit values > 1 wich brighten the image<br>More than being unintuitives, it does not permit full control (inversing gain invers for all channels)<br>
<br>What solution:<br>- Curves will take big UI<br>- Levels maybe also<br><br>But it is not preferable to do this as an sequencer effect, This will permit the user to choose the effect acording to the type of correction he wants to make (Level, curves, ...)<br>
<br>For primary color correction this is not really important as for me "Levels" and "Lift/Gamma/Gain" are the same with different way of setting the parameter and they can be done with curves. <br><br>
But if complex secondary collor correction (like changing saturation and value acording to hue with a curve, ...) is going to make is way in blender the user must choose the one he wants<br><br>Note that with nodes doing a "not so complex secondary color correction" (like the exemple below) requires:<br>
-color space conversion<br>-doing a difference map with a constant value<br>-using this map as factor for color<br><br>It will need about 10 nodes and that is uaualy done in one in shake or with one effect in finalcut.<br>
<br>I am interested in this kind of stuff and I can code it but as I said if is going to be used by nodes, sequencer and image editor ther must be a way to unify it.<br><br>xavier<br><br><div class="gmail_quote">2008/12/10 Campbell Barton <span dir="ltr"><<a rel="nofollow" ymailto="mailto:ideasman42@gmail.com" target="_blank" href="mailto:ideasman42@gmail.com">ideasman42@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c">On Thu, Dec 11, 2008 at 9:33 AM, Xavier Thomas<br>
<<a rel="nofollow" ymailto="mailto:xavier.thomas.1980@gmail.com" target="_blank" href="mailto:xavier.thomas.1980@gmail.com">xavier.thomas.1980@gmail.com</a>> wrote:<br>
> Yes, that is what I ment but is it ok to add an UI parameter "ofset" with is<br>
> button "Inv ofset" at the side of the Lift gamma and gain parameters because<br>
> the UI will get really charged.<br>
><br>
> And what about an image treatment library, because I already have made this<br>
> function in my keyer node and crating a color correction node with these<br>
> controls might be usefull also: this will result in a lot of code<br>
> duplication.<br>
><br>
><br>
> 2008/12/10 Dalai Felinto <<a rel="nofollow" ymailto="mailto:dfelinto@gmail.com" target="_blank" href="mailto:dfelinto@gmail.com">dfelinto@gmail.com</a>><br>
>><br>
>> Hi Xavier.<br>
>><br>
>> Can't you do a do_version()?<br>
>> In readfile.c you can see a lot of parameters that need to be updated<br>
>> over Blender version.<br>
>> If what you need is a simple offset for old blender files work in the<br>
>> same way as new blender files (with this bug fixed), this should work.<br>
>><br>
>> I didn't see the bug or this part of the code, but do_version()<br>
>> sometimes is the better way to go.<br>
>><br>
>> Cheers,<br>
>> Dalai<br>
>> <a rel="nofollow" target="_blank" href="http://blenderecia.orgfree.com">http://blenderecia.orgfree.com</a><br>
>><br>
>> 2008/12/10 Xavier Thomas <<a rel="nofollow" ymailto="mailto:xavier.thomas.1980@gmail.com" target="_blank" href="mailto:xavier.thomas.1980@gmail.com">xavier.thomas.1980@gmail.com</a>>:<br>
>> > Hello,<br>
>> ><br>
>> > Lately, I was trying to implicate me in blender developement, and<br>
>> > begining<br>
>> > with small things (after the keyr node) I desided to correct this bug:<br>
>> ><br>
>> > <a rel="nofollow" target="_blank" href="http://projects.blender.org/tracker/index.php?func=detail&aid=18010&group_id=9&atid=125">http://projects.blender.org/tracker/index.php?func=detail&aid=18010&group_id=9&atid=125</a><br>
>> ><br>
>> > Basicly the lift parameter of color correction in sequencer works more<br>
>> > like<br>
>> > a "value" color correction than a "lift" (exept that it work on RGB<br>
>> > channel<br>
>> > separately so I think "ofset" is more apropriate then "value")<br>
>> ><br>
>> > Fixing it would be simple but old files that use this parameter will<br>
>> > have a<br>
>> > diferent render result, and after discussing with Matt Ebb on IRC it<br>
>> > seems<br>
>> > that this is not acceptable.<br>
>> > So the only solution to have a proper color correction in the sequencer<br>
>> > is<br>
>> > to add an "ofset" parameter. Is this OK ? (maybe the UI will get too<br>
>> > compact)<br>
>> ><br>
>> > Further, why do not put this kind of function in an image library so it<br>
>> > will<br>
>> > be accesible form other part of the program (nodes and maybe image<br>
>> > editor)<br>
>> > like the quick blur function in the nodes CMP_util.h<br>
>> ><br>
>> > Sorry to disturb, I know lot of you are really buzzy but I prefer to get<br>
>> > good directions before coding.<br>
>> ><br>
>> > Thanks<br>
>> ><br>
>> > Xavier<br>
>> ><br>
>> > _______________________________________________<br>
>> > Bf-committers mailing list<br>
>> > <a rel="nofollow" ymailto="mailto:Bf-committers@blender.org" target="_blank" href="mailto:Bf-committers@blender.org">Bf-committers@blender.org</a><br>
>> > <a rel="nofollow" target="_blank" href="http://lists.blender.org/mailman/listinfo/bf-committers">http://lists.blender.org/mailman/listinfo/bf-committers</a><br>
>> ><br>
>> ><br>
>> _______________________________________________<br>
>> Bf-committers mailing list<br>
>> <a rel="nofollow" ymailto="mailto:Bf-committers@blender.org" target="_blank" href="mailto:Bf-committers@blender.org">Bf-committers@blender.org</a><br>
>> <a rel="nofollow" target="_blank" href="http://lists.blender.org/mailman/listinfo/bf-committers">http://lists.blender.org/mailman/listinfo/bf-committers</a><br>
><br>
><br>
> _______________________________________________<br>
> Bf-committers mailing list<br>
> <a rel="nofollow" ymailto="mailto:Bf-committers@blender.org" target="_blank" href="mailto:Bf-committers@blender.org">Bf-committers@blender.org</a><br>
> <a rel="nofollow" target="_blank" href="http://lists.blender.org/mailman/listinfo/bf-committers">http://lists.blender.org/mailman/listinfo/bf-committers</a><br>
<br>
</div></div>Recently I tried making sense of the sequencer's color functions and<br>
found them quite confusing. Even after tweaking them for 5min I don't<br>
really understand what they do exactly.<br>
<br>
Id much prefer convert these values into either, gimp/photoshop color<br>
'Levels' or 'Curves'.<br>
Curves are already used in other parts of blender so I'ts probably not<br>
that hard to make this change,<br>
<br>
Peter, if your reading, Could these settings be converted to curves?<br>
(even a close approximation would be ok I think)<br>
<br>
--<br>
<font color="#888888">- Campbell<br>
</font><div><div></div><div class="Wj3C7c">_______________________________________________<br>
Bf-committers mailing list<br>
<a rel="nofollow" ymailto="mailto:Bf-committers@blender.org" target="_blank" href="mailto:Bf-committers@blender.org">Bf-committers@blender.org</a><br>
<a rel="nofollow" target="_blank" href="http://lists.blender.org/mailman/listinfo/bf-committers">http://lists.blender.org/mailman/listinfo/bf-committers</a><br>
</div></div></blockquote></div><br>
</div></div></div></div><br>
</body></html>