<div dir="ltr">Thanks for the advices Diego and David!<div>Just a little thought:</div><div>Adding lot of nodegroups in a single "category" - I mean in the same menu list - isn't that efficient... is there a way to manage their position in the SHIFT+A menu?</div>
<div><br></div><div>Referenced node group are quite "risky" since compositing session works most likely WYSIWYG and as soon as you change something you have to check back each project... but I get your point Diego... I'm very used to linked group, they are so useful and I hope they will be empowered a lot with gooseberry since Proxyfication have room for for lot of improvement.</div>
<div><br></div><div> </div><div><br></div><div> <br><div class="gmail_extra"><br><br><div class="gmail_quote">2014-05-25 4:26 GMT+02:00 David McSween <span dir="ltr"><<a href="mailto:3pointedit@gmail.com" target="_blank">3pointedit@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Don't forget the addon Node Presets <a href="http://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Compositing/Compositing_Presets" target="_blank">http://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Compositing/Compositing_Presets</a> I think you can add node groups and store them in a portable file.</p>
<div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On 25 May 2014 09:59, "Diego Gangl" <<a href="mailto:dnicolas@gmail.com" target="_blank">dnicolas@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
>> It is possible to clamp (blacks and whites individually even), but<br>
>> whenever I want to do it I have to add gazillion nodes. It takes time. My<br>
>> intention is to make it with a single click.<br>
<br>
You can turn them into a group, plug the math values into group<br>
inputs, name it and bam! your own Clamp Node that you can add from the<br>
group menu.<br>
<br>
> Isn't there a way to develop few nodegroup store them somewhere and recall<br>
> them in a personal group list or add them in the lists we already have?<br>
<br>
There's two ways:<br>
<br>
1- Make the groups in a new (empty) blend file, then save it as your<br>
start-up file (ctrl+U). The node groups will be available in every new<br>
file you make.<br>
<br>
2- Make a "Node Library" file. Make all your groups there, then make a<br>
new empty file and link all the groups from the library file. Save it<br>
as your start-up file and you get all the groups. The cool thing is<br>
that if you tweak the groups inside the lib file, they will be upated<br>
in all the blend files that link them.<br>
<br>
Gooseberry is going to bring a lot of developement into asset<br>
management, so it will get better.<br>
<br>
<br>
2014-05-24 7:00 GMT-03:00 Francesco Paglia <<a href="mailto:f.paglia.80@gmail.com" target="_blank">f.paglia.80@gmail.com</a>>:<br>
> Isn't there a way to develop few nodegroup store them somewhere and recall<br>
> them in a personal group list or add them in the lists we already have?<br>
> Could it be a python add-on?<br>
> This would help us skip the tedious part of reloading those node every time<br>
> a new blend file is created and also could help us distribute those nodes in<br>
> their coherent place.<br>
><br>
><br>
><br>
> 2014-05-24 11:31 GMT+02:00 Bartek Skorupa (priv)<br>
> <<a href="mailto:bartekskorupa@bartekskorupa.com" target="_blank">bartekskorupa@bartekskorupa.com</a>>:<br>
><br>
>> It is possible to clamp (blacks and whites individually even), but<br>
>> whenever I want to do it I have to add gazillion nodes. It takes time. My<br>
>> intention is to make it with a single click.<br>
>> How much time did it take you to set up this fantastic node tree of yours?<br>
>> If it's more than one second - itś too much. It should be: Decision => 1<br>
>> second later: DONE.<br>
>><br>
>><br>
>> Bartek Skorupa<br>
>><br>
>> <a href="http://www.bartekskorupa.com" target="_blank">www.bartekskorupa.com</a><br>
>><br>
>> On 24 maj 2014, at 00:10, Sean Kennedy <<a href="mailto:mack_dadd2@hotmail.com" target="_blank">mack_dadd2@hotmail.com</a>> wrote:<br>
>><br>
>> Ah, great idea! We could even set one up with RGB, one on each channel,<br>
>> and save it as a nodegroup.<br>
>> Thanks! So obvious, don't know why we didn't think of this. :)<br>
>><br>
>> I'm going to set one up today.<br>
>><br>
>> sean<br>
>><br>
>> > From: <a href="mailto:dnicolas@gmail.com" target="_blank">dnicolas@gmail.com</a><br>
>> > Date: Fri, 23 May 2014 19:07:28 -0300<br>
>> > To: <a href="mailto:bf-compositor@blender.org" target="_blank">bf-compositor@blender.org</a><br>
>> > Subject: Re: [Bf-compositor] Clamping (Mix, Math, RGB Curves)<br>
>> ><br>
>> > Hi all, I don't know how Blender's handles colors internally but<br>
>> > wouldn't this work?<br>
>> > <a href="http://www.pasteall.org/pic/show.php?id=71736" target="_blank">http://www.pasteall.org/pic/show.php?id=71736</a><br>
>> > (or are the V values already mapped to 0-1 from the separate node?)<br>
>> ><br>
>> > Cheers,<br>
>> ><br>
>> > 2014-05-23 18:46 GMT-03:00 Sean Kennedy <<a href="mailto:mack_dadd2@hotmail.com" target="_blank">mack_dadd2@hotmail.com</a>>:<br>
>> > > Could we set the value of the clamp? It could come in as defaults of<br>
>> > > 1.0 and<br>
>> > > 0.0, but we could alter it to whatever we wanted. At R&H, most of the<br>
>> > > time<br>
>> > > we clamped brights around 14-16. We'd only turn it down under that if<br>
>> > > we got<br>
>> > > bad pixels when rendering.<br>
>> > ><br>
>> > > If you had a superbright red, like R 12, G 3, B 4, and you put a clamp<br>
>> > > of 1<br>
>> > > on it, obviously it's going to set each value to 1, so what was red<br>
>> > > now<br>
>> > > reads as white. But it would still be useful.<br>
>> > ><br>
>> > > After Effects clamp tool<br>
>> ><br>
>> > > ><a href="http://cdn.aescripts.com/media/catalog/product/cache/1/image/800x600/040ec09b1e35df139433887a97daa66f/f/t/ft-clamp-ui_1.png" target="_blank">http://cdn.aescripts.com/media/catalog/product/cache/1/image/800x600/040ec09b1e35df139433887a97daa66f/f/t/ft-clamp-ui_1.png</a><br>
>> > ><br>
>> > > Nuke clamp is in the color grade node<br>
>> ><br>
>> > > ><a href="http://docs.thefoundry.co.uk/nuke/63/pythondevguide/_images/getMinMax_01.png" target="_blank">http://docs.thefoundry.co.uk/nuke/63/pythondevguide/_images/getMinMax_01.png</a><br>
>> > ><br>
>> > > I'm not posting the images to say "this is how we should do it", but<br>
>> > > rather,<br>
>> > > to say it is useful and professional compositors would indeed use it<br>
>> > > often.<br>
>> > ><br>
>> > > In fact, I was working on a shot this week that could have used it. I<br>
>> > > was<br>
>> > > given stock footage from a client, and I have no idea how much they'll<br>
>> > > color<br>
>> > > correct it in post once I deliver the final vfx shot. SO I have to<br>
>> > > make sure<br>
>> > > all my blacks are in line with what is in the plate. I put a gamma on<br>
>> > > the<br>
>> > > plate just to view the black levels and see how they match up when<br>
>> > > pushed<br>
>> > > really far.<br>
>> > ><a href="https://dl.dropboxusercontent.com/u/10553822/clamp_blacks_01.jpg" target="_blank">https://dl.dropboxusercontent.com/u/10553822/clamp_blacks_01.jpg</a><br>
>> > ><br>
>> > > Since we don't have a clamp, I ended up putting a mix node right after<br>
>> > > the<br>
>> > > stock footage node, setting it to Lighten, and making the color over<br>
>> > > it<br>
>> > > black. then I slowly raised it while watching until the blacks all<br>
>> > > came in<br>
>> > > line. Would have been much easier to sample the value of the darkest<br>
>> > > dark I<br>
>> > > wanted in the shot, throw a clamp node on with the black clamp set to<br>
>> > > those<br>
>> > > values.<br>
>> > ><br>
>> > > In fact, at R&H, the Black Clamp node let you set an individual value<br>
>> > > for R,<br>
>> > > G, and B. And it had a color picker so you could just sample the image<br>
>> > > and<br>
>> > > the values would fill in automatically.<br>
>> > ><br>
>> > > Anyway, just throwing out my $0.02. Obviously I've found a workaround<br>
>> > > and<br>
>> > > can live with it, but it would sure be great to someday see a clamp<br>
>> > > node.<br>
>> > ><br>
>> > > ________________________________<br>
>> > > Date: Fri, 23 May 2014 14:21:40 -0700<br>
>> > ><br>
>> > > From: <a href="mailto:troy.sobotka@gmail.com" target="_blank">troy.sobotka@gmail.com</a><br>
>> > > To: <a href="mailto:bf-compositor@blender.org" target="_blank">bf-compositor@blender.org</a><br>
>> > > Subject: Re: [Bf-compositor] Clamping (Mix, Math, RGB Curves)<br>
>> > ><br>
>> > ><br>
>> > > On May 23, 2014 1:56 PM, "Bartek Skorupa (priv)"<br>
>> > > <<a href="mailto:bartekskorupa@bartekskorupa.com" target="_blank">bartekskorupa@bartekskorupa.com</a>> wrote:<br>
>> > ><br>
>> > >> When I say: "clamp blacks" I always mean: set every value below 0.0<br>
>> > >> to<br>
>> > >> 0.0.<br>
>> > >> When I say: "clamp whites" I always mean: set every value above 1.0<br>
>> > >> to<br>
>> > >> 1.0.<br>
>> > >> Every compositing artist will know what I mean.<br>
>> > ><br>
>> > > If we can generate a clamp / scale node, I am all for it.<br>
>> > ><br>
>> > > I am saying there is no concept of white in a scene referred model,<br>
>> > > and as<br>
>> > > such, you have to be careful as to not write nodes that break the<br>
>> > > system.<br>
>> > ><br>
>> > > It is that simple. No white. No brighter than white. So sorry, “Every<br>
>> > > artist...” is actually “Every artist unfamiliar with HDR work.”<br>
>> > ><br>
>> > > So a clamp node _must_ not make the erroneous assumption that 1.0<br>
>> > > means<br>
>> > > anything special, and rather provide for an arbitrary value range.<br>
>> > ><br>
>> > > If this all seems like speaking an alien language, it is precisely why<br>
>> > > I<br>
>> > > chimed in and said “Whoa.”<br>
>> > ><br>
>> > > There are already nodes that are broken because of erroneous<br>
>> > > assumptions. It<br>
>> > > would be a shame to make more.<br>
>> > ><br>
>> > > With respect,<br>
>> > > TJS<br>
>> > ><br>
>> > ><br>
>> > > _______________________________________________ Bf-compositor mailing<br>
>> > > list<br>
>> > > <a href="mailto:Bf-compositor@blender.org" target="_blank">Bf-compositor@blender.org</a><br>
>> > > <a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
>> > ><br>
>> > > _______________________________________________<br>
>> > > Bf-compositor mailing list<br>
>> > > <a href="mailto:Bf-compositor@blender.org" target="_blank">Bf-compositor@blender.org</a><br>
>> > > <a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
>> > ><br>
>> > _______________________________________________<br>
>> > Bf-compositor mailing list<br>
>> > <a href="mailto:Bf-compositor@blender.org" target="_blank">Bf-compositor@blender.org</a><br>
>> > <a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
>> _______________________________________________<br>
>> Bf-compositor mailing list<br>
>> <a href="mailto:Bf-compositor@blender.org" target="_blank">Bf-compositor@blender.org</a><br>
>> <a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Bf-compositor mailing list<br>
>> <a href="mailto:Bf-compositor@blender.org" target="_blank">Bf-compositor@blender.org</a><br>
>> <a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
>><br>
><br>
><br>
><br>
> --<br>
> Francesco Paglia<br>
> Vfx and Production Supervisor<br>
><br>
> mobile <a href="tel:%2B39%20347.82.12.473" value="+393478212473" target="_blank">+39 347.82.12.473</a><br>
> e-mail <a href="mailto:f.paglia.80@gmail.com" target="_blank">f.paglia.80@gmail.com</a><br>
><br>
><br>
> _______________________________________________<br>
> Bf-compositor mailing list<br>
> <a href="mailto:Bf-compositor@blender.org" target="_blank">Bf-compositor@blender.org</a><br>
> <a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
><br>
_______________________________________________<br>
Bf-compositor mailing list<br>
<a href="mailto:Bf-compositor@blender.org" target="_blank">Bf-compositor@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
</blockquote></div>
</div></div><br>_______________________________________________<br>
Bf-compositor mailing list<br>
<a href="mailto:Bf-compositor@blender.org">Bf-compositor@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Francesco Paglia<div>Vfx and Production Supervisor</div><div><br></div><div>mobile +39 347.82.12.473</div><div><div>e-mail <a href="mailto:f.paglia.80@gmail.com" target="_blank">f.paglia.80@gmail.com</a></div>
</div><div><br></div>
</div></div></div>