Re: [Nuke-users] Hide Transform overlay inside a gizmo

[adam jones]

Dear Darrenjust a little nicer nowscript attached Kind Regards-adam

burnIn_slate_v003.nk
Description: Binary data
On 10 Feb 2017, at 9:19 AM, Darren Coombes  wrote:Cheers, thanks Adam. Will check it out..
Check out some of my work…www.vimeo.com/darrencoombes/reel2017Mob:  +61 418 631 079IMDB: www.imdb.com/name/nm3719099/Instagram: @7secondstoblackInstagram: @durwood0781Skype:  darren.coombes81Twitter:  @durwood81

On 8 Feb 2017, at 4:46 pm, adam jones  wrote:Dear DarrenSo I added that auto font scale (option) based in the input frame size and the font scaling does not seem as glitchy as it was in the previous script I sent though.I am guessing the only other thing that could be added is for the gizmo to detect when there is nothing connected to the input and ref to a default frame size.any thing else would be specific things you might want to add to it your self, sorry if all the posts are a pain am a little bored no work on at the moment.new script attachedregards-adamOn 8 Feb 2017, at 1:54 PM, adam jones  wrote:Dear DarrenThis should do what you need, it could probably be a little more elegant with a couple of changes like having the font size change automatically based on the input frames size but it does solve your OSC issue.script attachedregards-adamOn 8 Feb 2017, at 9:28 AM, adam jones  wrote:probably not the answer you are after but hit the ‘Q’’ key I am thinking you are looking for some thing independent of that, specific to the gizmo controls its self ? yes ?regards-adamOn 8 Feb 2017, at 9:04 AM, Darren Coombes  wrote:Say I’ve got a gizmo where i have some text, but i don’t want to see the text box on screen when gizmo is open in properties panel.Can you hide the text box overlay? or a transform overlay?Thanks.Daz.set cut_paste_input [stack 0]version 10.0 v5push $cut_paste_inputGroup { name BURN_IN tile_color 0xffba00ff selected true xpos -175 ypos 149 addUserKnob {20 User} addUserKnob {4 outputsize l output M {"1920 x 1080" "1280 x 720" "Custom Format" ""}} addUserKnob {41 format l "custom format" T Constant1.format} addUserKnob {41 color T Text1.color} addUserKnob {41 translate T Transform1.translate} addUserKnob {41 global_font_scale l "global font scale" T Text3.global_font_scale}} NoOp {  inputs 0  name GlobalScale  xpos 1401  ypos 753  addUserKnob {20 User}  addUserKnob {7 globscale l "global scale"}  globscale 1 } Constant {  inputs 0  channels rgb  format "2880 1440 0 0 2880 1440 1 Arri 2K 2:1"  name Constant1  xpos 1000  ypos 409 }set N3f719c50 [stack 0] Text2 {  font_size_toolbar 50  font_width_toolbar 50  font_height_toolbar 50  message "\[basename \[value root.name]]       frame \[format %04d \[frame]]"  old_message {{48 49 53 95 108 116 99 95 48 49 48 95 112 114 101 112 95 98 114 101 97 107 100 111 119 110 95 101 100 105 116 95 118 48 49 95 116 48 49 95 100 99 46 110 107 32 32 32 32 32 32 32 102 114 97 109 101 32 49 48 49 49}    }  old_expression_markers {{0 44 58 61}    }  box {0 0 {width-(5/100*width)} {(10/100*height)}}  xjustify right  transforms {{0 2}    }  font_size_values {{0 50 1 50 2 50 3 50 4 50 5 50 6 50 7 50 8 50 9 50 10 50 11 50 12 50 13 50 14 50 15 50 16 50 17 50 18 50 19 50 20 50 21 50 22 50 23 50 24 50 25 50 26 50 27 50 28 50 29 50 30 50 31 50 32 50 33 50 34 50 35 50 36 50 37 50 38 50 39 50 40 50 41 50 42 50 43 50 44 50 45 50 46 50 47 50 48 50 49 50 50 50 51 50 52 50 53 50 54 50 55 50 56 50 57 50 58 50 59 50 60 50 61 50 0 5 1 5 2 5 3 5 4 5 5 5 6 5 7 5 8 5 9 5 10 5 11 5 12 5 13 5 14 5 15 5 16 5 17 5 18 5 19 5 20 5 21 5 22 5 23 5 24 5 25 5 26 5 27 5 28 5 29 5 30 5 31 5 32 5 33 5 34 5 35 5 36 5 37 5 38 5 39 5 40 5 41 5 42 5 43 5 44 5 45 5 46 5 47 5 48 5 49 5 50 5 51 5 52 5 53 5 54 5 55 5 56 5 57 5 58 5 59 5 60 5 61 5}    }  font_width_values {{0 {font_size} 1 {font_size} 2 {font_size} 3 {font_size} 4 {font_size} 5 {font_size} 6 {font_size} 7 {font_size} 8 {font_size} 9 {font_size} 10 {font_size} 11 {font_size} 12 {font_size} 13 {font_size} 14 {font_size} 15 {font_size} 16 {font_size} 17 {font_size} 18 {font_size} 19 {font_size} 20 {font_size} 21 {font_size} 22 {font_size} 23 {font_size} 24 {font_size} 25 {font_size} 26 {font_size} 27 {font_size} 28 {font_size} 29 {font_size} 30 {font_size} 31 {font_size} 32 {font_size} 33 {font_size} 34 {font_size} 35 {font_size} 36 {font_size} 37 {font_size} 38 {font_size} 39 {font_size} 40 {font_size} 41 {font_size} 42 {font_size} 43 {font_size} 44 {font_size} 45 {font_size} 46 {font_size} 47 {font_size} 48 {font_size} 49 {font_size} 50 {font_size} 51 {font_size} 52 {font_size} 53 {font_size} 54 {font_size} 55 {font_size} 56 {font_size} 57 {font_size} 58 {font_size} 59 {font_size} 60 {font_size} 61 {font_size} 0 {font_size} 1 {font_size} 2 {font_size} 3 {font_size} 4 {font_size} 5 {font_size} 6 {font_size} 7 {font_size} 8 {font_size} 9 {font_size} 10 {font_size} 11 {font_size} 12 {font_size} 13 {font_size} 14 {font_size} 15 

Re: [Nuke-users] bokeh usage

[Michael Habenicht]

Yes, and even if you have the additional bg samples behind your 
defocused foreground bokeh is not using them.


Am 09.02.2017 um 19:04 schrieb Nathan Rusch:

This isn't too surprising. Your original deep data has discrete color
samples for each deep sample in places where objects overlap, but your
flattened color data has no "samples" to speak of. Thus, when you apply
your DeepRecolor, Nuke has to basically take each pixel and spread its
value out across all the deep samples at that pixel's coordinates with
no knowledge of what the original sample colors would have been.

Also, keep in mind that deep data isn't a silver bullet for depth-based
defocusing. It's important to remember that even deep images have blind
spots (unless you use tricks like telling the renderer that every object
is semi-transparent), so at a certain radius, your blur will start to
break down around the edges of overlapping objects. I'm guessing your
artifacts are the result of a combination of these two limitations.

-Nathan

On 2/9/2017 12:36 AM, Gabor L. Toth wrote:

Hi,

we are testing peregrine's bokeh in our pipeline. I would like to use
deep input for perfect defocus. With connecting the original deep read
to the node's deep input it works perfectly indeed. But when I do a
deep recolor, putting the comped rgba data to deep branch, it produces
a little halo around the sharp area, and other subtle imperfections.
The edges of the rgba look the same as the original deep input, no
blur or reformat happens there. Even if I just deeprecolor with the
flat beauty rgba, without any color corrections or other stuff, has
these halos. Anyone has idea what could be the difference? Or how to
solve it?

Thanks
Gabor



___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users


___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users


___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] Hide Transform overlay inside a gizmo

[Darren Coombes]

Cheers, thanks Adam. Will check it out..

Check out some of my work…
www.vimeo.com/darrencoombes/reel2017 


Mob:  +61 418 631 079 
IMDB: www.imdb.com/name/nm3719099/
Instagram: @7secondstoblack
Instagram: @durwood0781
Skype:  darren.coombes81
Twitter:  @durwood81

> On 8 Feb 2017, at 4:46 pm, adam jones  wrote:
> 
> Dear Darren
> 
> So I added that auto font scale (option) based in the input frame size and 
> the font scaling does not seem as glitchy as it was in the previous script I 
> sent though.
> 
> I am guessing the only other thing that could be added is for the gizmo to 
> detect when there is nothing connected to the input and ref to a default 
> frame size.
> 
> any thing else would be specific things you might want to add to it your 
> self, sorry if all the posts are a pain am a little bored no work on at the 
> moment.
> 
> new script attached
> 
> regards
> -adam
> 
> 
> 
> 
>> On 8 Feb 2017, at 1:54 PM, adam jones > > wrote:
>> 
>> Dear Darren
>> 
>> This should do what you need, it could probably be a little more elegant 
>> with a couple of changes like having the font size change automatically 
>> based on the input frames size but it does solve your OSC issue.
>> 
>> script attached
>> 
>> regards
>> -adam
>> 
>> 
>>> On 8 Feb 2017, at 9:28 AM, adam jones >> > wrote:
>>> 
>>> probably not the answer you are after but hit the ‘Q’’ key 
>>> 
>>> I am thinking you are looking for some thing independent of that, specific 
>>> to the gizmo controls its self ? yes ?
>>> 
>>> regards
>>> -adam
>>> 
>>> 
 On 8 Feb 2017, at 9:04 AM, Darren Coombes > wrote:
 
 Say I’ve got a gizmo where i have some text, but i don’t want to see the 
 text box on screen when gizmo is open in properties panel.
 
 Can you hide the text box overlay? or a transform overlay?
 
 Thanks.
 Daz.
 
 set cut_paste_input [stack 0]
 version 10.0 v5
 push $cut_paste_input
 Group {
  name BURN_IN
  tile_color 0xffba00ff
  selected true
  xpos -175
  ypos 149
  addUserKnob {20 User}
  addUserKnob {4 outputsize l output M {"1920 x 1080" "1280 x 720" "Custom 
 Format" ""}}
  addUserKnob {41 format l "custom format" T 
 Constant1.format}
  addUserKnob {41 color T Text1.color}
  addUserKnob {41 translate T Transform1.translate}
  addUserKnob {41 global_font_scale l "global font scale" T 
 Text3.global_font_scale}
 }
  NoOp {
   inputs 0
   name GlobalScale
   xpos 1401
   ypos 753
   addUserKnob {20 User}
   addUserKnob {7 globscale l "global scale"}
   globscale 1
  }
  Constant {
   inputs 0
   channels rgb
   format "2880 1440 0 0 2880 1440 1 Arri 2K 2:1"
   name Constant1
   xpos 1000
   ypos 409
  }
 set N3f719c50 [stack 0]
  Text2 {
   font_size_toolbar 50
   font_width_toolbar 50
   font_height_toolbar 50
   message "\[basename \[value root.name]]   frame \[format %04d 
 \[frame]]"
   old_message {{48 49 53 95 108 116 99 95 48 49 48 95 112 114 101 112 95 
 98 114 101 97 107 100 111 119 110 95 101 100 105 116 95 118 48 49 95 116 
 48 49 95 100 99 46 110 107 32 32 32 32 32 32 32 102 114 97 109 101 32 49 
 48 49 49}
 }
   old_expression_markers {{0 44 58 61}
 }
   box {0 0 {width-(5/100*width)} {(10/100*height)}}
   xjustify right
   transforms {{0 2}
 }
   font_size_values {{0 50 1 50 2 50 3 50 4 50 5 50 6 50 7 50 8 50 9 50 10 
 50 11 50 12 50 13 50 14 50 15 50 16 50 17 50 18 50 19 50 20 50 21 50 22 50 
 23 50 24 50 25 50 26 50 27 50 28 50 29 50 30 50 31 50 32 50 33 50 34 50 35 
 50 36 50 37 50 38 50 39 50 40 50 41 50 42 50 43 50 44 50 45 50 46 50 47 50 
 48 50 49 50 50 50 51 50 52 50 53 50 54 50 55 50 56 50 57 50 58 50 59 50 60 
 50 61 50 0 5 1 5 2 5 3 5 4 5 5 5 6 5 7 5 8 5 9 5 10 5 11 5 12 5 13 5 14 5 
 15 5 16 5 17 5 18 5 19 5 20 5 21 5 22 5 23 5 24 5 25 5 26 5 27 5 28 5 29 5 
 30 5 31 5 32 5 33 5 34 5 35 5 36 5 37 5 38 5 39 5 40 5 41 5 42 5 43 5 44 5 
 45 5 46 5 47 5 48 5 49 5 50 5 51 5 52 5 53 5 54 5 55 5 56 5 57 5 58 5 59 5 
 60 5 61 5}
 }
   font_width_values {{0 {font_size} 1 {font_size} 2 {font_size} 3 
 {font_size} 4 {font_size} 5 {font_size} 6 {font_size} 7 {font_size} 8 
 {font_size} 9 {font_size} 10 {font_size} 11 {font_size} 12 {font_size} 13 
 {font_size} 14 {font_size} 15 {font_size} 16 {font_size} 17 {font_size} 18 
 {font_size} 19 {font_size} 20 {font_size} 21 {font_size} 22 {font_size} 23 
 {font_size} 24 {font_size} 25 {font_size} 26 {font_size} 27 {font_size} 28 
 {font_size} 29 {font_size} 30 {font_size} 31 {font_size} 32 

Re: [Nuke-users] bokeh usage

[Gabor Hovanyi]

I've seen ppl fixing the halo by extending the edges first.
Hacky, but works...

Gabor

On Thu, Feb 9, 2017 at 1:27 PM, Gabor L. Toth  wrote:

> Hi Nathan, thanks for the clarification! But then what is the preferred
> workflow with this plugin? I assume many companies are using with deep
> input. We can't keep the comping fully in deep until the defocus node, we
> are putting together the passes before, with all kind of color corrections
> and other nodes...  Any advice?
>
> Thanks,
> Gabor
>
> On Thu, Feb 9, 2017 at 7:04 PM, Nathan Rusch 
> wrote:
>
>> This isn't too surprising. Your original deep data has discrete color
>> samples for each deep sample in places where objects overlap, but your
>> flattened color data has no "samples" to speak of. Thus, when you apply
>> your DeepRecolor, Nuke has to basically take each pixel and spread its
>> value out across all the deep samples at that pixel's coordinates with
>> no knowledge of what the original sample colors would have been.
>>
>> Also, keep in mind that deep data isn't a silver bullet for depth-based
>> defocusing. It's important to remember that even deep images have blind
>> spots (unless you use tricks like telling the renderer that every object
>> is semi-transparent), so at a certain radius, your blur will start to
>> break down around the edges of overlapping objects. I'm guessing your
>> artifacts are the result of a combination of these two limitations.
>>
>> -Nathan
>>
>> On 2/9/2017 12:36 AM, Gabor L. Toth wrote:
>> > Hi,
>> >
>> > we are testing peregrine's bokeh in our pipeline. I would like to use
>> > deep input for perfect defocus. With connecting the original deep read
>> > to the node's deep input it works perfectly indeed. But when I do a
>> > deep recolor, putting the comped rgba data to deep branch, it produces
>> > a little halo around the sharp area, and other subtle imperfections.
>> > The edges of the rgba look the same as the original deep input, no
>> > blur or reformat happens there. Even if I just deeprecolor with the
>> > flat beauty rgba, without any color corrections or other stuff, has
>> > these halos. Anyone has idea what could be the difference? Or how to
>> > solve it?
>> >
>> > Thanks
>> > Gabor
>> >
>> >
>> >
>> > ___
>> > Nuke-users mailing list
>> > Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
>> > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>>
>> ___
>> Nuke-users mailing list
>> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>>
>
>
> ___
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] bokeh usage

[Gabor L. Toth]

Hi Nathan, thanks for the clarification! But then what is the preferred
workflow with this plugin? I assume many companies are using with deep
input. We can't keep the comping fully in deep until the defocus node, we
are putting together the passes before, with all kind of color corrections
and other nodes...  Any advice?

Thanks,
Gabor

On Thu, Feb 9, 2017 at 7:04 PM, Nathan Rusch 
wrote:

> This isn't too surprising. Your original deep data has discrete color
> samples for each deep sample in places where objects overlap, but your
> flattened color data has no "samples" to speak of. Thus, when you apply
> your DeepRecolor, Nuke has to basically take each pixel and spread its
> value out across all the deep samples at that pixel's coordinates with
> no knowledge of what the original sample colors would have been.
>
> Also, keep in mind that deep data isn't a silver bullet for depth-based
> defocusing. It's important to remember that even deep images have blind
> spots (unless you use tricks like telling the renderer that every object
> is semi-transparent), so at a certain radius, your blur will start to
> break down around the edges of overlapping objects. I'm guessing your
> artifacts are the result of a combination of these two limitations.
>
> -Nathan
>
> On 2/9/2017 12:36 AM, Gabor L. Toth wrote:
> > Hi,
> >
> > we are testing peregrine's bokeh in our pipeline. I would like to use
> > deep input for perfect defocus. With connecting the original deep read
> > to the node's deep input it works perfectly indeed. But when I do a
> > deep recolor, putting the comped rgba data to deep branch, it produces
> > a little halo around the sharp area, and other subtle imperfections.
> > The edges of the rgba look the same as the original deep input, no
> > blur or reformat happens there. Even if I just deeprecolor with the
> > flat beauty rgba, without any color corrections or other stuff, has
> > these halos. Anyone has idea what could be the difference? Or how to
> > solve it?
> >
> > Thanks
> > Gabor
> >
> >
> >
> > ___
> > Nuke-users mailing list
> > Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
> ___
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] bokeh usage

[Nathan Rusch]

This isn't too surprising. Your original deep data has discrete color 
samples for each deep sample in places where objects overlap, but your 
flattened color data has no "samples" to speak of. Thus, when you apply 
your DeepRecolor, Nuke has to basically take each pixel and spread its 
value out across all the deep samples at that pixel's coordinates with 
no knowledge of what the original sample colors would have been.

Also, keep in mind that deep data isn't a silver bullet for depth-based 
defocusing. It's important to remember that even deep images have blind 
spots (unless you use tricks like telling the renderer that every object 
is semi-transparent), so at a certain radius, your blur will start to 
break down around the edges of overlapping objects. I'm guessing your 
artifacts are the result of a combination of these two limitations.

-Nathan

On 2/9/2017 12:36 AM, Gabor L. Toth wrote:
> Hi,
>
> we are testing peregrine's bokeh in our pipeline. I would like to use 
> deep input for perfect defocus. With connecting the original deep read 
> to the node's deep input it works perfectly indeed. But when I do a 
> deep recolor, putting the comped rgba data to deep branch, it produces 
> a little halo around the sharp area, and other subtle imperfections. 
> The edges of the rgba look the same as the original deep input, no 
> blur or reformat happens there. Even if I just deeprecolor with the 
> flat beauty rgba, without any color corrections or other stuff, has 
> these halos. Anyone has idea what could be the difference? Or how to 
> solve it?
>
> Thanks
> Gabor
>
>
>
> ___
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

[Nuke-users] "Other" Preference tab greyed out

[Bruno-Pierre Jobin]

I have a few tabs in the “other” section in the nuke preferences and they are 
all greyed out. Anyone knows what it’s due to? Permissions on my .nuke 
directory seems fine.

Thanks___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] bokeh usage

[Michael Habenicht]

Hm, used to work for me so far. The only thing that comes to my mind is that 
the two are not lining up perfectly before the recolor. Maybe different formats 
due to overscan rendering?

"Gabor L. Toth"  wrote:

>Hi, thanks for your reply! Unfortunately I tried it already, but stays
>the
>same with the halo.
>Any other tips?
>
>Thanks
>Gabor
>
>
>On Thu, Feb 9, 2017 at 2:34 PM, Michael Habenicht 
>wrote:
>
>> Hi,
>> do you have the 'target input alpha' checkbox on the DeepRecolor node
>> checked? Turning this option on might solve your problem.
>>
>> Kind regards,
>> Michael
>>
>> "Gabor L. Toth"  wrote:
>>
>> >Hi,
>> >
>> >we are testing peregrine's bokeh in our pipeline. I would like to
>use
>> >deep
>> >input for perfect defocus. With connecting the original deep read to
>> >the
>> >node's deep input it works perfectly indeed. But when I do a deep
>> >recolor,
>> >putting the comped rgba data to deep branch, it produces a little
>halo
>> >around the sharp area, and other subtle imperfections. The edges of
>the
>> >rgba look the same as the original deep input, no blur or reformat
>> >happens
>> >there. Even if I just deeprecolor with the flat beauty rgba, without
>> >any
>> >color corrections or other stuff, has these halos. Anyone has idea
>what
>> >could be the difference? Or how to solve it?
>> >
>> >Thanks
>> >Gabor
>> >___
>> >Nuke-users mailing list
>> >Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
>> >http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>>
>> --
>> Sent from my Android tab with K-9 Mail. Please excuse my brevity.
>> ___
>> Nuke-users mailing list
>> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
>>
>___
>Nuke-users mailing list
>Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
>http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

-- 
Sent from my Android tab with K-9 Mail. Please excuse my brevity.
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] bokeh usage

[Michael Habenicht]

Hi,
do you have the 'target input alpha' checkbox on the DeepRecolor node checked? 
Turning this option on might solve your problem.

Kind regards,
Michael

"Gabor L. Toth"  wrote:

>Hi,
>
>we are testing peregrine's bokeh in our pipeline. I would like to use
>deep
>input for perfect defocus. With connecting the original deep read to
>the
>node's deep input it works perfectly indeed. But when I do a deep
>recolor,
>putting the comped rgba data to deep branch, it produces a little halo
>around the sharp area, and other subtle imperfections. The edges of the
>rgba look the same as the original deep input, no blur or reformat
>happens
>there. Even if I just deeprecolor with the flat beauty rgba, without
>any
>color corrections or other stuff, has these halos. Anyone has idea what
>could be the difference? Or how to solve it?
>
>Thanks
>Gabor
>___
>Nuke-users mailing list
>Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
>http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

-- 
Sent from my Android tab with K-9 Mail. Please excuse my brevity.
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

[Nuke-users] bokeh usage

[Gabor L. Toth]

Hi,

we are testing peregrine's bokeh in our pipeline. I would like to use deep
input for perfect defocus. With connecting the original deep read to the
node's deep input it works perfectly indeed. But when I do a deep recolor,
putting the comped rgba data to deep branch, it produces a little halo
around the sharp area, and other subtle imperfections. The edges of the
rgba look the same as the original deep input, no blur or reformat happens
there. Even if I just deeprecolor with the flat beauty rgba, without any
color corrections or other stuff, has these halos. Anyone has idea what
could be the difference? Or how to solve it?

Thanks
Gabor
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users