<div dir="ltr">Hey Angus,<div>at first glance I haven't understand what you where talking about but after reading the thread on BA I found your proof of concept really interesting,</div><div>I've already replied there (on BA) but let me repeat what I said here:</div>
<div><br></div><div><div>You made a really nice addon, and it works very smoothly as I can see from a quick test, even the generation of nodes as soon as you add a new strip is great!</div><div>Once completed it would certainly speed up tremendously the workflow while compositing</div>
<div>Just a couple of comment about stuff that agoose77 may have already thought about and would be very nice to have:</div><div>1. offset isn't taken into account: if a sequence starts from a value different from 1 you can't see the picture where expected according to the position of strip in the timeline</div>
<div>2. extrapolation of the sequence: you could take into account the behavior of the strip before and after the first and last frame with something like old first/last frame, loop or ping pong taking into account the extra length of the strip if you move the end over the last frame</div>
<div>3. trim point of the sequence: at the moment if a sequence is shortened at the start or at the end this isn't reflected on the node</div><div>4. more instances of the same clip: it would be great if we can have many instances of the same strip that simply have a different offset </div>
<div><br></div><div><br></div></div><div><br></div><div>Let me add here a couple of extra thing just for my information:</div><div>How can be useful the groupnode output start frame end frame and Current frame?</div><div>
Did you intended them as readable information to move outside the group?</div><div><br></div><div> Again, your add on is tremendously useful hope you would move this proof of concept to a complete tool!</div><div>We definitely have to rise the attention to your addon here! :)</div>
<div>Cheers</div><div>Francesco</div><div> </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-05-28 21:33 GMT+02:00 Angus Hollands <span dir="ltr"><<a href="mailto:goosey15@gmail.com" target="_blank">goosey15@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Ton's earlier response was somewhat clear on the subject, but I feel it was directed towards previous discussions. It might be worth starting a BA thread on the subject, if only for discussions sake.<br>
<br>In my opinion, layer strips would work as my previous contribution directed:<div><a href="https://drive.google.com/file/d/0B-k8UZd_BS9nV2RXMGRLanF0dk0/edit?usp=sharing" target="_blank">https://drive.google.com/file/d/0B-k8UZd_BS9nV2RXMGRLanF0dk0/edit?usp=sharing</a></div>
<br>Ultimately however, once you start giving such direct compositor access, it would seem more sensible to just allow the VSE to act as a layered front-end to the compositor. It is already trivial to perform most of the effects that the VSE offers, purely in the compositor. However, the VSE layering is what makes it user-friendly for video editing. Hence, If one was speaking hypothetically, it might make sense to have VSE specific nodes that are used as flow-guides in the compositor. Instead of having different effects in the VSE, you'd simply have "layer" strips, and "transition" strips.<div>
<br>They are used to guide the compositor,such that the VSE doesn't have any file-handling code (so this is naturally a drastic measure).</div><div><br>Creating an input strip in the VSE creates an input node and a VSE layer node. The VSE layer node would accept an image and cut it off when the layer "ends".</div>
<div><br></div><div>Creating an effect strip across two strips would perform a similar operation, except it wouldn't create the input strips. Instead, it would have a single output, akin to the "factor" of progress between two clips. Perhaps also the start and end frame and current frame. </div>
<div><br></div><div>Most of this could probably be completed purely in Python, without the compositor UI-nodes which can be replaced with Python<br><br>Might be fun to discuss<br><div class="gmail_extra"><br><div class="gmail_quote">
On 28 May 2014 18:48, <span dir="ltr"><<a href="mailto:bf-compositor-request@blender.org" target="_blank">bf-compositor-request@blender.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Send Bf-compositor mailing list submissions to<br>
<a href="mailto:bf-compositor@blender.org" target="_blank">bf-compositor@blender.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:bf-compositor-request@blender.org" target="_blank">bf-compositor-request@blender.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:bf-compositor-owner@blender.org" target="_blank">bf-compositor-owner@blender.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Bf-compositor digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Extending some node functions to VSE (Christian Krupa)<br>
2. Re: Clamping (Mix, Math, RGB Curves) (Diego Gangl)<br>
3. Re: Clamping (Mix, Math, RGB Curves) (Francesco Paglia)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 28 May 2014 16:43:32 +0100<br>
From: Christian Krupa <<a href="mailto:blender@christiankrupa.net" target="_blank">blender@christiankrupa.net</a>><br>
Subject: [Bf-compositor] Extending some node functions to VSE<br>
To: <a href="mailto:bf-compositor@blender.org" target="_blank">bf-compositor@blender.org</a><br>
Message-ID:<br>
<<a href="mailto:CABFx4YPYGp7CMma52a8x_0orENzzuvvxh5Bi-6zDB03RYZZ0HA@mail.gmail.com" target="_blank">CABFx4YPYGp7CMma52a8x_0orENzzuvvxh5Bi-6zDB03RYZZ0HA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
While I can see that full integration of the compositor and sequencer is a<br>
difficult / non trivial thing for the programmers to achieve and possibly<br>
not desirable for the users, I agree with the notion of having a comp node<br>
that can access edit info, be it from a particular strip in a sequence, a<br>
VSE channel or even a whole VSE edit as an input. This would keep the<br>
realtime(ish) nature of the VSE intact and also allow further work to be<br>
done on edits in progress without full commitment to the timeline - Shaun's<br>
mockup is a pretty good example of what might be useful. (maybe only the<br>
strip input would work in this way as it wouldn't have to deal with the VSE<br>
at all besides getting the IN/OUT points of the actual media on disk...)<br>
<br>
<a href="https://www.dropbox.com/s/u5nfbms8asltbsn/timeline_node.jpg" target="_blank">https://www.dropbox.com/s/u5nfbms8asltbsn/timeline_node.jpg</a><br>
<br>
This debate seems legitimate to me and there are a good few users who would<br>
like to see it progress to the point of action.<br>
<br>
cheers<br>
<br>
Chris<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.blender.org/pipermail/bf-compositor/attachments/20140528/f5c56793/attachment-0001.htm" target="_blank">http://lists.blender.org/pipermail/bf-compositor/attachments/20140528/f5c56793/attachment-0001.htm</a><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 28 May 2014 14:27:40 -0300<br>
From: Diego Gangl <<a href="mailto:dnicolas@gmail.com" target="_blank">dnicolas@gmail.com</a>><br>
Subject: Re: [Bf-compositor] Clamping (Mix, Math, RGB Curves)<br>
To: <a href="mailto:bf-compositor@blender.org" target="_blank">bf-compositor@blender.org</a><br>
Message-ID:<br>
<<a href="mailto:CAEAjNq5rwc_4Zm_U7XAcfHh_5oPybCywg%2BCBwNN9mkMUyDv7qA@mail.gmail.com" target="_blank">CAEAjNq5rwc_4Zm_U7XAcfHh_5oPybCywg+CBwNN9mkMUyDv7qA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
It's working for me, but Blender gave me a different datapath:<br>
nodes["RGB"].outputs[0].default_value[0] .<br>
If I change it the 0 to RGBA I get an error too. I guess you can't use<br>
dictionaries for sockets in drivers?<br>
<br>
2014-05-28 9:15 GMT-03:00 Francesco Paglia <<a href="mailto:f.paglia.80@gmail.com" target="_blank">f.paglia.80@gmail.com</a>>:<br>
> Hey Diego,<br>
> I successfully added the driver,<br>
> I got the problem in the path of the RGB..<br>
> Here the picture I made to explain the problem:<br>
><br>
> <a href="https://lh6.googleusercontent.com/-k6GDiWl4uNU/U4XRy1AzQ_I/AAAAAAAAJy8/C-xuqUDrNKM/w1357-h784-no/value.jpg" target="_blank">https://lh6.googleusercontent.com/-k6GDiWl4uNU/U4XRy1AzQ_I/AAAAAAAAJy8/C-xuqUDrNKM/w1357-h784-no/value.jpg</a><br>
><br>
> I forgot to open the panel in the left of the drivers ..<br>
> I'm working on the red channel of the ramp and I was trying to evaluate the<br>
> red value of the RGB node that is perfectly showed in the python console but<br>
> as you can see return a red background on the path of the driver....<br>
><br>
> Am I missing something?<br>
><br>
><br>
><br>
><br>
> 2014-05-28 13:15 GMT+02:00 Diego Gangl <<a href="mailto:dnicolas@gmail.com" target="_blank">dnicolas@gmail.com</a>>:<br>
><br>
>> Hey,<br>
>><br>
>> Nice work on those nodegroups, I'd like to see them too. It would be<br>
>> great to have some kind of standard library of nodes for motion/video<br>
>> work in the compositor with stuff like this.<br>
>><br>
>> Francesco,<br>
>> Have you tried the outliner workaround for problem #2? You'd have to<br>
>> find the node in the outliner, then the socket, select it and press D<br>
>> to add the driver. Btw, it doesn't change color in the ui sometimes.<br>
>><br>
>> I tried the nodes addon but I get a missing paths error, maybe it<br>
>> hasn't been updated?<br>
>><br>
>> Cheers,<br>
>><br>
>> 2014-05-28 7:15 GMT-03:00 Francesco Paglia <<a href="mailto:f.paglia.80@gmail.com" target="_blank">f.paglia.80@gmail.com</a>>:<br>
>> > Hey Sean,<br>
>> > I'm really interested in seeing your node and much more on the match<br>
>> > color<br>
>> > node...<br>
>> > I've tried by myself making one but I couldn't find a nice way to have<br>
>> > the<br>
>> > setup embedded in a node group.<br>
>> ><br>
>> > Looking at the tutorial the artist simply match low and hi valuse of a<br>
>> > levels effects for each channel.<br>
>> > So I though I can mimic that result just with a simple setup:<br>
>> > 1. separate RGB of the input,<br>
>> > 2. add a color ramp to each channel (to get a remap of Hi and LOW value)<br>
>> > 3. add a combine channel to recreate the final image<br>
>> ><br>
>> > The result looked promising but<br>
>> > 1. to expose the value of the ramp you have to add a driver on each stop<br>
>> > of<br>
>> > the ramp<br>
>> > 2. the driver (don't know why) in official 2.70 build seems cannot read<br>
>> > the<br>
>> > value of a node RGB.output or the input of the group even if it is<br>
>> > readable<br>
>> > in the python console (the driver simply show the path background in red<br>
>> > color)<br>
>> > 3. value are clamped in the 0-1 range so if values exceed this range<br>
>> > they<br>
>> > are remapped.. (well this is a known side effect driven by the node<br>
>> > used...)<br>
>> ><br>
>> > I'm curious to know your approach :)<br>
>> > Thanks,<br>
>> > Francesco<br>
>> ><br>
>> ><br>
>> > 2014-05-28 7:57 GMT+02:00 David McSween <<a href="mailto:3pointedit@gmail.com" target="_blank">3pointedit@gmail.com</a>>:<br>
>> ><br>
>> >> I would certainly be interested in a 'colour matcher' node group.<br>
>> >> Especially if it Rock My World as Mark says in the link ;-)<br>
>> >><br>
>> >> These look really useful, it would be great if everyone could at least<br>
>> >> match pedestal across their elements.<br>
>> >><br>
>> >><br>
>> >> On Wed, May 28, 2014 at 2:07 PM, Sean Kennedy <<a href="mailto:mack_dadd2@hotmail.com" target="_blank">mack_dadd2@hotmail.com</a>><br>
>> >> wrote:<br>
>> >>><br>
>> >>> Hey guys,<br>
>> >>><br>
>> >>> I made a few nodegroups we were discussing.<br>
>> >>><br>
>> >>><br>
>> >>> <a href="https://www.dropbox.com/s/uj9kw6dm1sp3cot/clamp_nodes_screenshot_02.jpg" target="_blank">https://www.dropbox.com/s/uj9kw6dm1sp3cot/clamp_nodes_screenshot_02.jpg</a><br>
>> >>><br>
>> >>> I made a Value clamp, as Deigo had made. Then I made a RGB clamp,<br>
>> >>> where<br>
>> >>> you can set R, G, and B individually. And then I made the node I<br>
>> >>> really<br>
>> >>> wanted, a black levels node.<br>
>> >>><br>
>> >>> When you're compositing one image over another, and they come from two<br>
>> >>> different sources, they usually have completely different color values<br>
>> >>> in<br>
>> >>> the highs and lows (obviously, we all know this). At R&H, we had a<br>
>> >>> great<br>
>> >>> Black Levels node where we could simply sample a dark spot of a<br>
>> >>> background<br>
>> >>> plate, and the darks of the foreground plate would just shift to<br>
>> >>> match. This<br>
>> >>> works the same exact way. It was ideal for CG elements going over live<br>
>> >>> action plates, because usually the general highs and overall color of<br>
>> >>> the CG<br>
>> >>> matched the plate fine, but the blacks always came in as absolute<br>
>> >>> blacks, or<br>
>> >>> sometimes negative blacks. This node made fixing it a 1-click<br>
>> >>> operation.<br>
>> >>><br>
>> >>> If anyone is interested, I can upload a blend file with the<br>
>> >>> nodegroups.<br>
>> >>> The clamps are super easy to make, though. But maybe the black levels<br>
>> >>> one<br>
>> >>> would be interesting to someone?<br>
>> >>><br>
>> >>> Tomorrow I'm going make a node setup to easily replicate Mark<br>
>> >>> Christiansen's techniques for matching the general colors of one plate<br>
>> >>> to<br>
>> >>> another. You can see the technique here in the free sample videos, if<br>
>> >>> you're<br>
>> >>> interested.<br>
>> >>><br>
>> >>><br>
>> >>> <a href="http://www.lynda.com/After-Effects-tutorials/After-Effects-Compositing-Essentials-Matching-Foreground-Background/114913-2.html" target="_blank">http://www.lynda.com/After-Effects-tutorials/After-Effects-Compositing-Essentials-Matching-Foreground-Background/114913-2.html</a><br>
>> >>><br>
>> >>> It's fun making these!<br>
>> >>><br>
>> >>> Sean<br>
>> >>><br>
>> >>> ________________________________<br>
>> >>> From: <a href="mailto:f.paglia.80@gmail.com" target="_blank">f.paglia.80@gmail.com</a><br>
>> >>> Date: Sun, 25 May 2014 09:50:01 +0200<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>
>> >>> Thanks for the advices Diego and David!<br>
>> >>> Just a little thought:<br>
>> >>> Adding lot of nodegroups in a single "category" - I mean in the same<br>
>> >>> menu<br>
>> >>> list - isn't that efficient... is there a way to manage their position<br>
>> >>> in<br>
>> >>> the SHIFT+A menu?<br>
>> >>><br>
>> >>> Referenced node group are quite "risky" since compositing session<br>
>> >>> works<br>
>> >>> most likely WYSIWYG and as soon as you change something you have to<br>
>> >>> check<br>
>> >>> back each project... but I get your point Diego... I'm very used to<br>
>> >>> linked<br>
>> >>> group, they are so useful and I hope they will be empowered a lot with<br>
>> >>> gooseberry since Proxyfication have room for for lot of improvement.<br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>> 2014-05-25 4:26 GMT+02:00 David McSween <<a href="mailto:3pointedit@gmail.com" target="_blank">3pointedit@gmail.com</a>>:<br>
>> >>><br>
>> >>> Don't forget the addon Node Presets<br>
>> >>><br>
>> >>> <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><br>
>> >>> I think you can add node groups and store them in a portable file.<br>
>> >>><br>
>> >>> On 25 May 2014 09:59, "Diego Gangl" <<a href="mailto:dnicolas@gmail.com" target="_blank">dnicolas@gmail.com</a>> wrote:<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<br>
>> >>> >> time.<br>
>> >>> >> 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<br>
>> >>> > recall<br>
>> >>> > them in a personal group list or add them in the lists we already<br>
>> >>> > 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<br>
>> >>> > recall<br>
>> >>> > them in a personal group list or add them in the lists we already<br>
>> >>> > have?<br>
>> >>> > Could it be a python add-on?<br>
>> >>> > This would help us skip the tedious part of reloading those node<br>
>> >>> > every<br>
>> >>> > time<br>
>> >>> > a new blend file is created and also could help us distribute those<br>
>> >>> > 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<br>
>> >>> >> time.<br>
>> >>> >> 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<br>
>> >>> >> yours?<br>
>> >>> >> If it's more than one second - it? too much. It should be: Decision<br>
>> >>> >> =><br>
>> >>> >> 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>><br>
>> >>> >> wrote:<br>
>> >>> >><br>
>> >>> >> Ah, great idea! We could even set one up with RGB, one on each<br>
>> >>> >> 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<br>
>> >>> >> > 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<br>
>> >>> >> > > defaults<br>
>> >>> >> > > of<br>
>> >>> >> > > 1.0 and<br>
>> >>> >> > > 0.0, but we could alter it to whatever we wanted. At R&H, most<br>
>> >>> >> > > of<br>
>> >>> >> > > the<br>
>> >>> >> > > time<br>
>> >>> >> > > we clamped brights around 14-16. We'd only turn it down under<br>
>> >>> >> > > that<br>
>> >>> >> > > 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<br>
>> >>> >> > > a<br>
>> >>> >> > > clamp<br>
>> >>> >> > > of 1<br>
>> >>> >> > > on it, obviously it's going to set each value to 1, so what was<br>
>> >>> >> > > red<br>
>> >>> >> > > now<br>
>> >>> >> > > reads as white. But it would still be useful.<br>
>> >>> >> > ><br>
>> >>> >> > > After Effects clamp tool<br>
>> >>> >> ><br>
>> >>> >> > ><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>
>> >>> >> > ><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<br>
>> >>> >> > > it",<br>
>> >>> >> > > but<br>
>> >>> >> > > rather,<br>
>> >>> >> > > to say it is useful and professional compositors would indeed<br>
>> >>> >> > > use<br>
>> >>> >> > > it<br>
>> >>> >> > > often.<br>
>> >>> >> > ><br>
>> >>> >> > > In fact, I was working on a shot this week that could have used<br>
>> >>> >> > > it. I<br>
>> >>> >> > > was<br>
>> >>> >> > > given stock footage from a client, and I have no idea how much<br>
>> >>> >> > > they'll<br>
>> >>> >> > > color<br>
>> >>> >> > > correct it in post once I deliver the final vfx shot. SO I have<br>
>> >>> >> > > to<br>
>> >>> >> > > make sure<br>
>> >>> >> > > all my blacks are in line with what is in the plate. I put a<br>
>> >>> >> > > gamma<br>
>> >>> >> > > on<br>
>> >>> >> > > the<br>
>> >>> >> > > plate just to view the black levels and see how they match up<br>
>> >>> >> > > 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<br>
>> >>> >> > > right<br>
>> >>> >> > > after<br>
>> >>> >> > > the<br>
>> >>> >> > > stock footage node, setting it to Lighten, and making the color<br>
>> >>> >> > > over<br>
>> >>> >> > > it<br>
>> >>> >> > > black. then I slowly raised it while watching until the blacks<br>
>> >>> >> > > all<br>
>> >>> >> > > came in<br>
>> >>> >> > > line. Would have been much easier to sample the value of the<br>
>> >>> >> > > darkest<br>
>> >>> >> > > dark I<br>
>> >>> >> > > wanted in the shot, throw a clamp node on with the black clamp<br>
>> >>> >> > > set<br>
>> >>> >> > > to<br>
>> >>> >> > > those<br>
>> >>> >> > > values.<br>
>> >>> >> > ><br>
>> >>> >> > > In fact, at R&H, the Black Clamp node let you set an individual<br>
>> >>> >> > > value<br>
>> >>> >> > > for R,<br>
>> >>> >> > > G, and B. And it had a color picker so you could just sample<br>
>> >>> >> > > the<br>
>> >>> >> > > image<br>
>> >>> >> > > and<br>
>> >>> >> > > the values would fill in automatically.<br>
>> >>> >> > ><br>
>> >>> >> > > Anyway, just throwing out my $0.02. Obviously I've found a<br>
>> >>> >> > > workaround<br>
>> >>> >> > > and<br>
>> >>> >> > > can live with it, but it would sure be great to someday see a<br>
>> >>> >> > > 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<br>
>> >>> >> > >> below<br>
>> >>> >> > >> 0.0<br>
>> >>> >> > >> to<br>
>> >>> >> > >> 0.0.<br>
>> >>> >> > >> When I say: "clamp whites" I always mean: set every value<br>
>> >>> >> > >> above<br>
>> >>> >> > >> 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<br>
>> >>> >> > > model,<br>
>> >>> >> > > and as<br>
>> >>> >> > > such, you have to be careful as to not write nodes that break<br>
>> >>> >> > > the<br>
>> >>> >> > > system.<br>
>> >>> >> > ><br>
>> >>> >> > > It is that simple. No white. No brighter than white. So sorry,<br>
>> >>> >> > > "Every<br>
>> >>> >> > > artist..." is actually "Every artist unfamiliar with HDR work."<br>
>> >>> >> > ><br>
>> >>> >> > > So a clamp node _must_ not make the erroneous assumption that<br>
>> >>> >> > > 1.0<br>
>> >>> >> > > means<br>
>> >>> >> > > anything special, and rather provide for an arbitrary value<br>
>> >>> >> > > range.<br>
>> >>> >> > ><br>
>> >>> >> > > If this all seems like speaking an alien language, it is<br>
>> >>> >> > > precisely<br>
>> >>> >> > > 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<div><div class="h5"><br>
>> >>> >> > ><br>
>> >>> >> > ><br>
>> >>> >> > > _______________________________________________ Bf-compositor<br>
>> >>> >> > > 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>
>> >>><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>
>> >>> _______________________________________________ Bf-compositor mailing<br>
>> >>> list <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>
>> >><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>
><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>
<br></div></div>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 28 May 2014 19:48:18 +0200<br>
From: Francesco Paglia <<a href="mailto:f.paglia.80@gmail.com" target="_blank">f.paglia.80@gmail.com</a>><br>
Subject: Re: [Bf-compositor] Clamping (Mix, Math, RGB Curves)<br>
To: <a href="mailto:bf-compositor@blender.org" target="_blank">bf-compositor@blender.org</a><br>
Message-ID:<br>
<<a href="mailto:CAJ8L8Fzmd8iAsqCGOd1P7scZwf3L10z4J_A-%2Ba3nVXBvoCkAzw@mail.gmail.com" target="_blank">CAJ8L8Fzmd8iAsqCGOd1P7scZwf3L10z4J_A-+a3nVXBvoCkAzw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I tried this datapath too...<br>
could you tell me which release of blender are you using?<br>
<br>
<br>
<br>
<br>
2014-05-28 19:27 GMT+02:00 Diego Gangl <<a href="mailto:dnicolas@gmail.com" target="_blank">dnicolas@gmail.com</a>>:<br>
<br>
> It's working for me, but Blender gave me a different datapath:<br>
> nodes["RGB"].outputs[0].default_value[0] .<br>
> If I change it the 0 to RGBA I get an error too. I guess you can't use<br>
> dictionaries for sockets in drivers?<br>
><br>
> 2014-05-28 9:15 GMT-03:00 Francesco Paglia <<a href="mailto:f.paglia.80@gmail.com" target="_blank">f.paglia.80@gmail.com</a>>:<br>
> > Hey Diego,<br>
> > I successfully added the driver,<br>
> > I got the problem in the path of the RGB..<br>
> > Here the picture I made to explain the problem:<br>
> ><br>
> ><br>
> <a href="https://lh6.googleusercontent.com/-k6GDiWl4uNU/U4XRy1AzQ_I/AAAAAAAAJy8/C-xuqUDrNKM/w1357-h784-no/value.jpg" target="_blank">https://lh6.googleusercontent.com/-k6GDiWl4uNU/U4XRy1AzQ_I/AAAAAAAAJy8/C-xuqUDrNKM/w1357-h784-no/value.jpg</a><br>
> ><br>
> > I forgot to open the panel in the left of the drivers ..<br>
> > I'm working on the red channel of the ramp and I was trying to evaluate<br>
> the<br>
> > red value of the RGB node that is perfectly showed in the python console<br>
> but<br>
> > as you can see return a red background on the path of the driver....<br>
> ><br>
> > Am I missing something?<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > 2014-05-28 13:15 GMT+02:00 Diego Gangl <<a href="mailto:dnicolas@gmail.com" target="_blank">dnicolas@gmail.com</a>>:<br>
> ><br>
> >> Hey,<br>
> >><br>
> >> Nice work on those nodegroups, I'd like to see them too. It would be<br>
> >> great to have some kind of standard library of nodes for motion/video<br>
> >> work in the compositor with stuff like this.<br>
> >><br>
> >> Francesco,<br>
> >> Have you tried the outliner workaround for problem #2? You'd have to<br>
> >> find the node in the outliner, then the socket, select it and press D<br>
> >> to add the driver. Btw, it doesn't change color in the ui sometimes.<br>
> >><br>
> >> I tried the nodes addon but I get a missing paths error, maybe it<br>
> >> hasn't been updated?<br>
> >><br>
> >> Cheers,<br>
> >><br>
> >> 2014-05-28 7:15 GMT-03:00 Francesco Paglia <<a href="mailto:f.paglia.80@gmail.com" target="_blank">f.paglia.80@gmail.com</a>>:<br>
> >> > Hey Sean,<br>
> >> > I'm really interested in seeing your node and much more on the match<br>
> >> > color<br>
> >> > node...<br>
> >> > I've tried by myself making one but I couldn't find a nice way to have<br>
> >> > the<br>
> >> > setup embedded in a node group.<br>
> >> ><br>
> >> > Looking at the tutorial the artist simply match low and hi valuse of a<br>
> >> > levels effects for each channel.<br>
> >> > So I though I can mimic that result just with a simple setup:<br>
> >> > 1. separate RGB of the input,<br>
> >> > 2. add a color ramp to each channel (to get a remap of Hi and LOW<br>
> value)<br>
> >> > 3. add a combine channel to recreate the final image<br>
> >> ><br>
> >> > The result looked promising but<br>
> >> > 1. to expose the value of the ramp you have to add a driver on each<br>
> stop<br>
> >> > of<br>
> >> > the ramp<br>
> >> > 2. the driver (don't know why) in official 2.70 build seems cannot<br>
> read<br>
> >> > the<br>
> >> > value of a node RGB.output or the input of the group even if it is<br>
> >> > readable<br>
> >> > in the python console (the driver simply show the path background in<br>
> red<br>
> >> > color)<br>
> >> > 3. value are clamped in the 0-1 range so if values exceed this range<br>
> >> > they<br>
> >> > are remapped.. (well this is a known side effect driven by the node<br>
> >> > used...)<br>
> >> ><br>
> >> > I'm curious to know your approach :)<br>
> >> > Thanks,<br>
> >> > Francesco<br>
> >> ><br>
> >> ><br>
> >> > 2014-05-28 7:57 GMT+02:00 David McSween <<a href="mailto:3pointedit@gmail.com" target="_blank">3pointedit@gmail.com</a>>:<br>
> >> ><br>
> >> >> I would certainly be interested in a 'colour matcher' node group.<br>
> >> >> Especially if it Rock My World as Mark says in the link ;-)<br>
> >> >><br>
> >> >> These look really useful, it would be great if everyone could at<br>
> least<br>
> >> >> match pedestal across their elements.<br>
> >> >><br>
> >> >><br>
> >> >> On Wed, May 28, 2014 at 2:07 PM, Sean Kennedy <<br>
> <a href="mailto:mack_dadd2@hotmail.com" target="_blank">mack_dadd2@hotmail.com</a>><br>
> >> >> wrote:<br>
> >> >>><br>
> >> >>> Hey guys,<br>
> >> >>><br>
> >> >>> I made a few nodegroups we were discussing.<br>
> >> >>><br>
> >> >>><br>
> >> >>><br>
> <a href="https://www.dropbox.com/s/uj9kw6dm1sp3cot/clamp_nodes_screenshot_02.jpg" target="_blank">https://www.dropbox.com/s/uj9kw6dm1sp3cot/clamp_nodes_screenshot_02.jpg</a><br>
> >> >>><br>
> >> >>> I made a Value clamp, as Deigo had made. Then I made a RGB clamp,<br>
> >> >>> where<br>
> >> >>> you can set R, G, and B individually. And then I made the node I<br>
> >> >>> really<br>
> >> >>> wanted, a black levels node.<br>
> >> >>><br>
> >> >>> When you're compositing one image over another, and they come from<br>
> two<br>
> >> >>> different sources, they usually have completely different color<br>
> values<br>
> >> >>> in<br>
> >> >>> the highs and lows (obviously, we all know this). At R&H, we had a<br>
> >> >>> great<br>
> >> >>> Black Levels node where we could simply sample a dark spot of a<br>
> >> >>> background<br>
> >> >>> plate, and the darks of the foreground plate would just shift to<br>
> >> >>> match. This<br>
> >> >>> works the same exact way. It was ideal for CG elements going over<br>
> live<br>
> >> >>> action plates, because usually the general highs and overall color<br>
> of<br>
> >> >>> the CG<br>
> >> >>> matched the plate fine, but the blacks always came in as absolute<br>
> >> >>> blacks, or<br>
> >> >>> sometimes negative blacks. This node made fixing it a 1-click<br>
> >> >>> operation.<br>
> >> >>><br>
> >> >>> If anyone is interested, I can upload a blend file with the<br>
> >> >>> nodegroups.<br>
> >> >>> The clamps are super easy to make, though. But maybe the black<br>
> levels<br>
> >> >>> one<br>
> >> >>> would be interesting to someone?<br>
> >> >>><br>
> >> >>> Tomorrow I'm going make a node setup to easily replicate Mark<br>
> >> >>> Christiansen's techniques for matching the general colors of one<br>
> plate<br>
> >> >>> to<br>
> >> >>> another. You can see the technique here in the free sample videos,<br>
> if<br>
> >> >>> you're<br>
> >> >>> interested.<br>
> >> >>><br>
> >> >>><br>
> >> >>><br>
> <a href="http://www.lynda.com/After-Effects-tutorials/After-Effects-Compositing-Essentials-Matching-Foreground-Background/114913-2.html" target="_blank">http://www.lynda.com/After-Effects-tutorials/After-Effects-Compositing-Essentials-Matching-Foreground-Background/114913-2.html</a><br>
> >> >>><br>
> >> >>> It's fun making these!<br>
> >> >>><br>
> >> >>> Sean<br>
> >> >>><br>
> >> >>> ________________________________<br>
> >> >>> From: <a href="mailto:f.paglia.80@gmail.com" target="_blank">f.paglia.80@gmail.com</a><br>
> >> >>> Date: Sun, 25 May 2014 09:50:01 +0200<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>
> >> >>> Thanks for the advices Diego and David!<br>
> >> >>> Just a little thought:<br>
> >> >>> Adding lot of nodegroups in a single "category" - I mean in the same<br>
> >> >>> menu<br>
> >> >>> list - isn't that efficient... is there a way to manage their<br>
> position<br>
> >> >>> in<br>
> >> >>> the SHIFT+A menu?<br>
> >> >>><br>
> >> >>> Referenced node group are quite "risky" since compositing session<br>
> >> >>> works<br>
> >> >>> most likely WYSIWYG and as soon as you change something you have to<br>
> >> >>> check<br>
> >> >>> back each project... but I get your point Diego... I'm very used to<br>
> >> >>> linked<br>
> >> >>> group, they are so useful and I hope they will be empowered a lot<br>
> with<br>
> >> >>> gooseberry since Proxyfication have room for for lot of improvement.<br>
> >> >>><br>
> >> >>><br>
> >> >>><br>
> >> >>><br>
> >> >>><br>
> >> >>><br>
> >> >>> 2014-05-25 4:26 GMT+02:00 David McSween <<a href="mailto:3pointedit@gmail.com" target="_blank">3pointedit@gmail.com</a>>:<br>
> >> >>><br>
> >> >>> Don't forget the addon Node Presets<br>
> >> >>><br>
> >> >>><br>
> <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><br>
> >> >>> I think you can add node groups and store them in a portable file.<br>
> >> >>><br>
> >> >>> On 25 May 2014 09:59, "Diego Gangl" <<a href="mailto:dnicolas@gmail.com" target="_blank">dnicolas@gmail.com</a>> wrote:<br>
> >> >>><br>
> >> >>> >> It is possible to clamp (blacks and whites individually even),<br>
> but<br>
> >> >>> >> whenever I want to do it I have to add gazillion nodes. It takes<br>
> >> >>> >> time.<br>
> >> >>> >> 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<br>
> the<br>
> >> >>> group menu.<br>
> >> >>><br>
> >> >>> > Isn't there a way to develop few nodegroup store them somewhere<br>
> and<br>
> >> >>> > recall<br>
> >> >>> > them in a personal group list or add them in the lists we already<br>
> >> >>> > 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<br>
> new<br>
> >> >>> file you make.<br>
> >> >>><br>
> >> >>> 2- Make a "Node Library" file. Make all your groups there, then<br>
> make a<br>
> >> >>> new empty file and link all the groups from the library file. Save<br>
> 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<br>
> 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<br>
> and<br>
> >> >>> > recall<br>
> >> >>> > them in a personal group list or add them in the lists we already<br>
> >> >>> > have?<br>
> >> >>> > Could it be a python add-on?<br>
> >> >>> > This would help us skip the tedious part of reloading those node<br>
> >> >>> > every<br>
> >> >>> > time<br>
> >> >>> > a new blend file is created and also could help us distribute<br>
> those<br>
> >> >>> > 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),<br>
> but<br>
> >> >>> >> whenever I want to do it I have to add gazillion nodes. It takes<br>
> >> >>> >> time.<br>
> >> >>> >> 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<br>
> of<br>
> >> >>> >> yours?<br>
> >> >>> >> If it's more than one second - it? too much. It should be:<br>
> Decision<br>
> >> >>> >> =><br>
> >> >>> >> 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>><br>
> >> >>> >> wrote:<br>
> >> >>> >><br>
> >> >>> >> Ah, great idea! We could even set one up with RGB, one on each<br>
> >> >>> >> 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<br>
> 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<br>
> >> >>> >> > node?)<br>
> >> >>> >> ><br>
> >> >>> >> > Cheers,<br>
> >> >>> >> ><br>
> >> >>> >> > 2014-05-23 18:46 GMT-03:00 Sean Kennedy <<br>
> <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<br>
> >> >>> >> > > defaults<br>
> >> >>> >> > > of<br>
> >> >>> >> > > 1.0 and<br>
> >> >>> >> > > 0.0, but we could alter it to whatever we wanted. At R&H,<br>
> most<br>
> >> >>> >> > > of<br>
> >> >>> >> > > the<br>
> >> >>> >> > > time<br>
> >> >>> >> > > we clamped brights around 14-16. We'd only turn it down under<br>
> >> >>> >> > > that<br>
> >> >>> >> > > 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<br>
> put<br>
> >> >>> >> > > a<br>
> >> >>> >> > > clamp<br>
> >> >>> >> > > of 1<br>
> >> >>> >> > > on it, obviously it's going to set each value to 1, so what<br>
> was<br>
> >> >>> >> > > red<br>
> >> >>> >> > > now<br>
> >> >>> >> > > reads as white. But it would still be useful.<br>
> >> >>> >> > ><br>
> >> >>> >> > > After Effects clamp tool<br>
> >> >>> >> ><br>
> >> >>> >> > ><br>
> >> >>> >> > > ><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>
> >> >>> >> > ><br>
> >> >>> >> > > ><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<br>
> >> >>> >> > > it",<br>
> >> >>> >> > > but<br>
> >> >>> >> > > rather,<br>
> >> >>> >> > > to say it is useful and professional compositors would indeed<br>
> >> >>> >> > > use<br>
> >> >>> >> > > it<br>
> >> >>> >> > > often.<br>
> >> >>> >> > ><br>
> >> >>> >> > > In fact, I was working on a shot this week that could have<br>
> used<br>
> >> >>> >> > > it. I<br>
> >> >>> >> > > was<br>
> >> >>> >> > > given stock footage from a client, and I have no idea how<br>
> much<br>
> >> >>> >> > > they'll<br>
> >> >>> >> > > color<br>
> >> >>> >> > > correct it in post once I deliver the final vfx shot. SO I<br>
> have<br>
> >> >>> >> > > to<br>
> >> >>> >> > > make sure<br>
> >> >>> >> > > all my blacks are in line with what is in the plate. I put a<br>
> >> >>> >> > > gamma<br>
> >> >>> >> > > on<br>
> >> >>> >> > > the<br>
> >> >>> >> > > plate just to view the black levels and see how they match up<br>
> >> >>> >> > > when<br>
> >> >>> >> > > pushed<br>
> >> >>> >> > > really far.<br>
> >> >>> >> > ><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<br>
> >> >>> >> > > right<br>
> >> >>> >> > > after<br>
> >> >>> >> > > the<br>
> >> >>> >> > > stock footage node, setting it to Lighten, and making the<br>
> color<br>
> >> >>> >> > > over<br>
> >> >>> >> > > it<br>
> >> >>> >> > > black. then I slowly raised it while watching until the<br>
> blacks<br>
> >> >>> >> > > all<br>
> >> >>> >> > > came in<br>
> >> >>> >> > > line. Would have been much easier to sample the value of the<br>
> >> >>> >> > > darkest<br>
> >> >>> >> > > dark I<br>
> >> >>> >> > > wanted in the shot, throw a clamp node on with the black<br>
> clamp<br>
> >> >>> >> > > set<br>
> >> >>> >> > > to<br>
> >> >>> >> > > those<br>
> >> >>> >> > > values.<br>
> >> >>> >> > ><br>
> >> >>> >> > > In fact, at R&H, the Black Clamp node let you set an<br>
> individual<br>
> >> >>> >> > > value<br>
> >> >>> >> > > for R,<br>
> >> >>> >> > > G, and B. And it had a color picker so you could just sample<br>
> >> >>> >> > > the<br>
> >> >>> >> > > image<br>
> >> >>> >> > > and<br>
> >> >>> >> > > the values would fill in automatically.<br>
> >> >>> >> > ><br>
> >> >>> >> > > Anyway, just throwing out my $0.02. Obviously I've found a<br>
> >> >>> >> > > workaround<br>
> >> >>> >> > > and<br>
> >> >>> >> > > can live with it, but it would sure be great to someday see a<br>
> >> >>> >> > > 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<br>
> >> >>> >> > >> below<br>
> >> >>> >> > >> 0.0<br>
> >> >>> >> > >> to<br>
> >> >>> >> > >> 0.0.<br>
> >> >>> >> > >> When I say: "clamp whites" I always mean: set every value<br>
> >> >>> >> > >> above<br>
> >> >>> >> > >> 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<br>
> >> >>> >> > > model,<br>
> >> >>> >> > > and as<br>
> >> >>> >> > > such, you have to be careful as to not write nodes that break<br>
> >> >>> >> > > the<br>
> >> >>> >> > > system.<br>
> >> >>> >> > ><br>
> >> >>> >> > > It is that simple. No white. No brighter than white. So<br>
> sorry,<br>
> >> >>> >> > > "Every<br>
> >> >>> >> > > artist..." is actually "Every artist unfamiliar with HDR<br>
> work."<br>
> >> >>> >> > ><br>
> >> >>> >> > > So a clamp node _must_ not make the erroneous assumption that<br>
> >> >>> >> > > 1.0<br>
> >> >>> >> > > means<br>
> >> >>> >> > > anything special, and rather provide for an arbitrary value<br>
> >> >>> >> > > range.<br>
> >> >>> >> > ><br>
> >> >>> >> > > If this all seems like speaking an alien language, it is<br>
> >> >>> >> > > precisely<br>
> >> >>> >> > > 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<div><div class="h5"><br>
> >> >>> >> > ><br>
> >> >>> >> > ><br>
> >> >>> >> > > _______________________________________________ Bf-compositor<br>
> >> >>> >> > > 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>
> >> >>><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>
> >> >>> _______________________________________________ Bf-compositor<br>
> mailing<br>
> >> >>> list <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>
> >> >><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>
> ><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>
><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></div></div>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.blender.org/pipermail/bf-compositor/attachments/20140528/9ac1141e/attachment.htm" target="_blank">http://lists.blender.org/pipermail/bf-compositor/attachments/20140528/9ac1141e/attachment.htm</a><br>
<br>
------------------------------<div class=""><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></div>
End of Bf-compositor Digest, Vol 7, Issue 18<br>
********************************************<br>
</blockquote></div><br></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>