Re: [Nuke-users] 32 bit to 8 bit conversion?

2012-03-08 Thread Simon Björk
Look here to create a linear ICC profile:
http://fnordware.blogspot.com/2008/05/making-linear-icc-profile.html. With
that set as your working space, you should be able to get correct blending.

If you only have a couple of layers, you could try adding a Levels effect
and set gamma to 0.4545 to each layer. On the top of your layers you would
then need to set an adjustment layer with a gamma of 2.2.

/Simon


2012/3/8 Randy Little rlit...@rslittle.com

 because you are using blend modes in photoshop that do not support
 float math(s)   AND/Or you your working space ICC is not set up right.

 Randy S. Little
 http://reel.rslittle.com
 http://imdb.com/name/nm2325729/




 On Wed, Mar 7, 2012 at 20:43, Richard Bobo richb...@mac.com wrote:
  Adrian,
 
  Thanks for wanting to help!
 
  Here are the parameters:
  -- CG render passes, comped and beautified in Nuke (auto work)...
  -- Ultimate deliverables for client are layered 8 bit TIFF files with
 alpha
  out of Photoshop (different parts of vehicle)...
 
  In order to ease the workload, we are trying to render layered files out
 of
  Nuke that get loaded into Photoshop. There is some automated work that is
  done with a recorded macro/droplet in Photoshop and the end result is our
  client-ready 8 bit layered TIFF .psd file.
 
  It would be *perfect* if we could render out an 8 bit layered file of
 some
  kind from Nuke. The only reliable layered file format that I know of
 coming
  out of Nuke is EXR. And, I don't think Nuke will produce a layered TIFF
 or
  DPX that Photoshop can read properly. I could be wrong about that and if
 I
  am, I'd love to know how to do it! Also, EXR output does not allow 8
 bit, as
  far as I can tell. So, we've tried 32 and 16 bit EXRs.
 
  The OpenEXR Photoshop plugin does a nice job of loading the EXR files,
  either as premultiplied layers with transparency or as unpremultiplied,
  separated layers for fill and alpha. The look of the layer comp in
 Photoshop
  matches Nuke as long as we stay in 32 bit linear space in Photoshop.
  However, changing the bit depth to 8 bit results in a general darkening
 of
  the image layers and a different gamma look to the transparent areas.
 In
  other words, the nice linear gradients are squashed in some areas and
 not as
  spread out.
 
  The ProEXR manual does speak about this kind of problem and suggests
  bringing in the layers unpremultiplied and using Levels adjustments on
 the
  layer masks only of each layer before changing the bit depth. With some
  trial and error, I have been able to find some values that will *almost*
  work. However, the levels adjustment values are not the same for each
 layer.
  And, it still does not look quite right.
 
  Photoshop *will* produce the correct result, however, *if* we choose to
  Merge the layers before doing the 32--8 conversion - but that's not
 what we
  need - we need the layers...
 
  So, for the moment, we are going to try and see if we can live with
  individual Levels adjustments for each layer in Photoshop, prior to the
 bit
  depth conversion. That may be the path of least resistance - but it sure
  ain't pretty!   (8^P
 
  So, Adrian, I hope that explains things a bit better. if you have any
  suggestions, I would love to hear them!
 
  Thanks,
 
  Rich
 
 
  Rich Bobo
  Senior VFX Compositor
 
  Mobile:  (248) 840-2665
  Web:  http://richbobo.com/
 
  Man has been endowed with reason, with the power to create, so that he
 can
  add to what he's been given.
  - Anton Chekhov
 
 
 
 
 
  On Mar 7, 2012, at 6:24 PM, Adrian Baltowski wrote:
 
  Hi
 
  I want help or advise you something but I don't fully understand your
  workflow...
  You can of course make color conversion in nuke. Nuke is brilliant
 software
  to make such a conversions BUT What next?? You cannot export layered
  tiffs out of Nuke (at least not in usable form). Do you want to export
  layers as separate tif files?
  If you could explain your workflow then we could advise you more.
 
 
 
  Best
  Adrian
 
 
  W dniu 2012-03-07 16:33:54 użytkownik Juan Galva juan.ga...@gmail.com
  napisał:
 
  keep us posted, please!
 
  On 7 March 2012 16:27, Richard Bobo richb...@mac.com wrote:
 
  Thanks, Julik, Andy, Diogo and Simon for your suggestions, ideas and
  questions...
 
  After trying a number of things and reading some more about the way
 ProEXR
  and Photoshop handle things, we're going to try to make our tweaks in
 Nuke
  and let Photoshop do whatever it does. It may take a few rounds of
 tweaking
  and converting to see just what we need to do on the Nuke side to make
 it
  come out the way we want on the Photoshop end. However, it seems like
 there
  are just too many variables there. So, we'll not try to fight it...  (8^
 
  Thanks for your help!
 
  Rich
 
 
  Rich Bobo
  Senior VFX Compositor
  Email:  richb...@mac.com
  Mobile:  248.840.2665
  Web:  http://richbobo.com
 
 
  On Mar 07, 2012, at 07:00 AM, Simon Björk si...@stillerstudios.se
 wrote:
 
  In 

Re: [Nuke-users] 32 bit to 8 bit conversion?

2012-03-08 Thread Ron Ganbar
When I try to do this I usually set Photoshop to an sRGB working space,
then in Nuke before each merge I use a ColorSpace node to convert to sRGB,
then I do the Merge, and then I use another ColorSpace node to convert back
to Linear. I'm not in front of Nuke at the moment, but if memory serves
that managed to give me exactly what photoshop does.


Ron Ganbar
email: ron...@gmail.com
tel: +44 (0)7968 007 309 [UK]
 +972 (0)54 255 9765 [Israel]
url: http://ronganbar.wordpress.com/



2012/3/8 Simon Björk si...@stillerstudios.se

 Look here to create a linear ICC profile:
 http://fnordware.blogspot.com/2008/05/making-linear-icc-profile.html. With
 that set as your working space, you should be able to get correct blending.

 If you only have a couple of layers, you could try adding a Levels effect
 and set gamma to 0.4545 to each layer. On the top of your layers you would
 then need to set an adjustment layer with a gamma of 2.2.

 /Simon


 2012/3/8 Randy Little rlit...@rslittle.com

 because you are using blend modes in photoshop that do not support
 float math(s)   AND/Or you your working space ICC is not set up right.

 Randy S. Little
 http://reel.rslittle.com
 http://imdb.com/name/nm2325729/




 On Wed, Mar 7, 2012 at 20:43, Richard Bobo richb...@mac.com wrote:
  Adrian,
 
  Thanks for wanting to help!
 
  Here are the parameters:
  -- CG render passes, comped and beautified in Nuke (auto work)...
  -- Ultimate deliverables for client are layered 8 bit TIFF files with
 alpha
  out of Photoshop (different parts of vehicle)...
 
  In order to ease the workload, we are trying to render layered files
 out of
  Nuke that get loaded into Photoshop. There is some automated work that
 is
  done with a recorded macro/droplet in Photoshop and the end result is
 our
  client-ready 8 bit layered TIFF .psd file.
 
  It would be *perfect* if we could render out an 8 bit layered file of
 some
  kind from Nuke. The only reliable layered file format that I know of
 coming
  out of Nuke is EXR. And, I don't think Nuke will produce a layered TIFF
 or
  DPX that Photoshop can read properly. I could be wrong about that and
 if I
  am, I'd love to know how to do it! Also, EXR output does not allow 8
 bit, as
  far as I can tell. So, we've tried 32 and 16 bit EXRs.
 
  The OpenEXR Photoshop plugin does a nice job of loading the EXR files,
  either as premultiplied layers with transparency or as unpremultiplied,
  separated layers for fill and alpha. The look of the layer comp in
 Photoshop
  matches Nuke as long as we stay in 32 bit linear space in Photoshop.
  However, changing the bit depth to 8 bit results in a general darkening
 of
  the image layers and a different gamma look to the transparent areas.
 In
  other words, the nice linear gradients are squashed in some areas and
 not as
  spread out.
 
  The ProEXR manual does speak about this kind of problem and suggests
  bringing in the layers unpremultiplied and using Levels adjustments on
 the
  layer masks only of each layer before changing the bit depth. With some
  trial and error, I have been able to find some values that will *almost*
  work. However, the levels adjustment values are not the same for each
 layer.
  And, it still does not look quite right.
 
  Photoshop *will* produce the correct result, however, *if* we choose to
  Merge the layers before doing the 32--8 conversion - but that's not
 what we
  need - we need the layers...
 
  So, for the moment, we are going to try and see if we can live with
  individual Levels adjustments for each layer in Photoshop, prior to the
 bit
  depth conversion. That may be the path of least resistance - but it sure
  ain't pretty!   (8^P
 
  So, Adrian, I hope that explains things a bit better. if you have any
  suggestions, I would love to hear them!
 
  Thanks,
 
  Rich
 
 
  Rich Bobo
  Senior VFX Compositor
 
  Mobile:  (248) 840-2665
  Web:  http://richbobo.com/
 
  Man has been endowed with reason, with the power to create, so that he
 can
  add to what he's been given.
  - Anton Chekhov
 
 
 
 
 
  On Mar 7, 2012, at 6:24 PM, Adrian Baltowski wrote:
 
  Hi
 
  I want help or advise you something but I don't fully understand your
  workflow...
  You can of course make color conversion in nuke. Nuke is brilliant
 software
  to make such a conversions BUT What next?? You cannot export layered
  tiffs out of Nuke (at least not in usable form). Do you want to export
  layers as separate tif files?
  If you could explain your workflow then we could advise you more.
 
 
 
  Best
  Adrian
 
 
  W dniu 2012-03-07 16:33:54 użytkownik Juan Galva juan.ga...@gmail.com
  napisał:
 
  keep us posted, please!
 
  On 7 March 2012 16:27, Richard Bobo richb...@mac.com wrote:
 
  Thanks, Julik, Andy, Diogo and Simon for your suggestions, ideas and
  questions...
 
  After trying a number of things and reading some more about the way
 ProEXR
  and Photoshop handle things, we're going to try to make our tweaks in
 Nuke
  and 

Re: [Nuke-users] 32 bit to 8 bit conversion?

2012-03-08 Thread Randy Little
Well in Nuke sRGB is purely a gamma curve. Unless you are really using
the colorspace node to do more then apply the gamma curve.In
Photoshop its a color space always.  Also regarless of what icc you
use. Even if its linear  the blend modes are still your probably I
beat.
Randy S. Little
http://reel.rslittle.com
http://imdb.com/name/nm2325729/




On Wed, Mar 7, 2012 at 07:14, Rich Bobo richb...@me.com wrote:
 Thanks, Julik, Andy and Simon for your suggestions, ideas and questions.
 After trying a number of things and reading some more about the way ProEXR
 and Photoshop handles things, we're going to try to make our tweaks in Nuke
 and let Photoshop do whatever it does. It may take a few rounds of tweaking
 and converting to see what we need to do on the Nuke side to make it come
 out the way we want on the Photoshop end. However, it seems like there are
 just too many variables there. So, we'll not try to fight it...  (8^\


 Thanks for your help!

 Rich


 Rich Bobo
 Senior VFX Compositor
 Email:  richb...@mac.com  
 Mobile:  248.840.2665
 Web:  http://richbobo.com


 On Mar 07, 2012, at 07:00 AM, Simon Björk si...@stillerstudios.se wrote:

 In what application are you comparing the result of the TIFFs? Nuke or
 Photoshop? I believe Photoshop use linear light math when in 32bpc and in
 that case, the blending of layers (and brightness) will look different if
 you change your project to 8 or 16-bit.



 2012/3/7 Julik Tarkhanov ju...@hecticelectric.nl


 On 7 mrt 2012, at 01:51, Rich Bobo wrote:

 The problem is that we need to get 8 bit layered TIFs out of Photoshop.

 I think the first problem is that the Photoshop blending is profoundly
 affected by the bit depth.
 The second problem is that if Nuke does a 1D lookp table conversion from
 one kind of RGB to another
 (including bit depth upgrades), Photoshop goes via Lab so what is
 happening is more like to a 3D LUT.

 What happens in your case is that probably Photoshop is converting the
 layers first, and then the result of the blending
 modes changes the way the images look. Maybe it's an issue with layer mask
 and front unpremultiplication and conversion.

 For me the first thing to check would be the PS profile settings for 8-bit
 RGB. Also, where do the discrepancies occur the most?
 Blended layer edges? Maybe your workflow needs to be related to manually
 unpremulting layers by the layer transparency and
 preadjusting the transparency grays...
 --
 Julik Tarkhanov | HecticElectric | Keizersgracht 736 1017 EX
 Amsterdam | The Netherlands | tel. +31 20 330 8250

 cel. +31 61 145 06 36 | http://hecticelectric.nl







 ___
 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




 --
 
 Stiller Studios
 Lidingö/Sweden

 Simon Björk
 Stiller Studios
 +46 (0)8 555 23 560
 Ekholmsnäsvägen 40, S-181 41 Lidingö
 si...@stillerstudios.se
 www.stillerstudios.se

 find us:
 http://www.eniro.se/query?search_word=stiller+studiosgeo_area=liding%F6what=all


 ___
 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] 32 bit to 8 bit conversion?

2012-03-08 Thread Rich Bobo
Thanks, Julik, Andy and Simon for your suggestions, ideas and questions. After trying a number of things and reading some more about the way ProEXR and Photoshop handles things, we're going to try to make our tweaks in Nuke and let Photoshop do whatever it does. It may take a few rounds of tweaking and converting to see what we need to do on the Nuke side to make it come out the way we want on the Photoshop end. However, it seems like there are just too many variables there. So, we'll not try to fight it... (8^\Thanks for your help!RichRich Bobo 
Senior VFX Compositor
Email:  richb...@mac.com			
Mobile:  248.840.2665
Web:  http://richbobo.comOn Mar 07, 2012, at 07:00 AM, Simon Björk si...@stillerstudios.se wrote:In what application are you comparing the result of the TIFFs? Nuke or Photoshop? I believePhotoshop use linear light math when in 32bpc and in that case, the blending of layers (and brightness) will look different if you change your project to 8 or 16-bit.2012/3/7 Julik Tarkhanov ju...@hecticelectric.nlOn 7 mrt 2012, at 01:51, Rich Bobo wrote:The problem is that we need to get 8 bit layered TIFs out of Photoshop.I think the first problem is that the Photoshop blending is profoundly affected by the bit depth.The second problem is that if Nuke does a 1D lookp table conversion from one kind of RGB to another(including bit depth upgrades), Photoshop goes via Lab so what is happening is more like to a 3D LUT.What happens in your case is that probably Photoshop is converting the layers first, and then the result of the blendingmodes changes the way the images look. Maybe it's an issue with layer mask and front unpremultiplication and conversion.For me the first thing to check would be the PS profile settings for 8-bit RGB. Also, where do the discrepancies occur the most?Blended layer edges? Maybe your workflow needs to be related to manually unpremulting layers by the layer transparency andpreadjusting the transparency grays...--Julik Tarkhanov | HecticElectric | Keizersgracht 736 1017 EX Amsterdam | The Netherlands | tel. +31 20 330 8250cel. +31 61 145 06 36 |http://hecticelectric.nl___ 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-- Stiller StudiosLidingö/SwedenSimon BjörkStiller Studios+46 (0)8 555 23 560Ekholmsnäsvägen 40, S-181 41 Lidingösi...@stillerstudios.se www.stillerstudios.sefind us: http://www.eniro.se/query?search_word=stiller+studiosgeo_area=liding%F6what=all ___ 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] concatenation in nuke

2012-03-08 Thread Peter Hartwig
Hey y'all

I was talking to my colleague, trying to figure out if there is a way
to see when transform nodes, colorgrades etc concatenate in nuke... we
both seem to rememeber it being possible in older versions...

anyone?

cheers
Peter
___
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] concatenation in nuke

2012-03-08 Thread James Etherington
Colour grades don't concatenate in Nuke 'cos it's all in float.

On Thu, Mar 8, 2012 at 10:11 AM, Peter Hartwig peter.hart...@gmail.comwrote:

 Hey y'all

 I was talking to my colleague, trying to figure out if there is a way
 to see when transform nodes, colorgrades etc concatenate in nuke... we
 both seem to rememeber it being possible in older versions...

 anyone?

 cheers
 Peter
 ___
 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] ClipExporter - Final Cut Pro X to Nuke

2012-03-08 Thread Thomas - Mindtransplant
Hello,

I´m not sure how many of you use Final Cut Pro X but if you do this might be 
interesting:

we released an application called ClipExporter which is a simple workflow and 
export tool for Final Cut Pro X. It opens exported Final Cut Pro X projects 
(fcpxml) and exports each clip as a Quicktime reference movie, Nuke file or 
Syntheyes importable file. It creates shot based folders with custom subfolders 
and extends each clip with handle frames. ClipExporter for Final Cut Pro X is 
available on the Mac App Store.

I think this might be very interesting for a lot of people who work with FCP X 
and want to send their clips to other post-production applications.

Please visit the product page (http://clipexporter.mindtransplant.com/) for 
more informations and take a look at the demo video on 
http://vimeo.com/36157075.


Best regards, Thomas.

P.S.: sorry for spamming.



MINDTRANSPLANT
Audio  Video Produktion
www.mindtransplant.com

___
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] concatenation in nuke

2012-03-08 Thread Ron Ganbar
Purple colored Transform nodes concatenate together, far as I remember.


Ron Ganbar
email: ron...@gmail.com
tel: +44 (0)7968 007 309 [UK]
 +972 (0)54 255 9765 [Israel]
url: http://ronganbar.wordpress.com/



On 8 March 2012 12:14, James Etherington james.ethering...@gmail.comwrote:

 Colour grades don't concatenate in Nuke 'cos it's all in float.


 On Thu, Mar 8, 2012 at 10:11 AM, Peter Hartwig peter.hart...@gmail.comwrote:

 Hey y'all

 I was talking to my colleague, trying to figure out if there is a way
 to see when transform nodes, colorgrades etc concatenate in nuke... we
 both seem to rememeber it being possible in older versions...

 anyone?

 cheers
 Peter
 ___
 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] Gizmo - Dynamic Properties Tab

2012-03-08 Thread barba
Hi all,
i'm a newbie about Gizmo and Python ..i'm happy to be here...i hope to learn a 
lot of things with your help, for become a big master ninja compositor! [Wink]
i'm trying to create a Gizmo for manage my multiEXR render... and i would like 
to know if is possibile Hide a Tab if his node is not plugged. i try to 
explain...for example i have a group with 2 input...A and B...in the Properties 
Tab i have two tab...one for the attributes of input A and one for the 
attributes of input B..
is possibile hide the second tab when the B input is not plugged??..

i know...it's not a big problem...but i think that would be cool have a dynamic 
properties tab for my gizmo!

thanks

regards

R.



___
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] ClipExporter - Final Cut Pro X to Nuke

2012-03-08 Thread Ron Ganbar
Very nice, Thomas.
I'm in!

A couple of questions regarding future releases (if you indeed plan to
update this periodically):

   1. Are you planning to add speed change support?
   2. Are you planning to add more software choices?
   3. What about the round trip? Going back to FCPX from Nuke?

Thanks,
Ron Ganbar
email: ron...@gmail.com
tel: +44 (0)7968 007 309 [UK]
 +972 (0)54 255 9765 [Israel]
url: http://ronganbar.wordpress.com/



On 8 March 2012 12:15, Thomas - Mindtransplant tho...@mindtransplant.comwrote:

 Hello,

 I´m not sure how many of you use Final Cut Pro X but if you do this might
 be interesting:

 we released an application called ClipExporter which is a simple workflow
 and export tool for Final Cut Pro X. It opens exported Final Cut Pro X
 projects (fcpxml) and exports each clip as a Quicktime reference movie,
 Nuke file or Syntheyes importable file. It creates shot based folders with
 custom subfolders and extends each clip with handle frames. ClipExporter
 for Final Cut Pro X is available on the Mac App Store.

 I think this might be very interesting for a lot of people who work with
 FCP X and want to send their clips to other post-production applications.

 Please visit the product page (http://clipexporter.mindtransplant.com/)
 for more informations and take a look at the demo video on
 http://vimeo.com/36157075.


 Best regards, Thomas.

 P.S.: sorry for spamming.



 *MINDTRANSPLANT*
 Audio  Video Produktion
 www.mindtransplant.com


 ___
 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] ClipExporter - Final Cut Pro X to Nuke

2012-03-08 Thread Thomas - Mindtransplant
Thanks Ron,

Speed changes or retimed clips will not be supported in the near future. It´s 
impossible to reconstruct the original (Normal) speed from the data that is 
stored in the fcpxml. This is something that really bothers me.
Any suggestions for other software packages? After Effects is on my list. I 
don´t have copies of other apps like PFTrack so it´s getting complicated at 
some point.
I thought about this but haven´t found an easy and elegant solution yet. At the 
moment it´s easier (for me) to import the Nuke output. Therefore I don´t use 
the Copy Files to Events folder so FCP X creates Aliases in it Original 
Media. Relinking media is much easier this way.

I am very open for any workflow suggestions. Tell me what you need :)
I have a growing new features list but first I wait and see how many people 
were interested. I wrote this app for my own workflow since I´m an all-in-one 
video-artist myself and use this in my own productions. So please understand 
that I think twice before adding features that I don´t use.

Short tip: if you select all generated .nk files in the Finder (using the 
search function) and drag them all in an empty Nuke window you import all 
Read-Nodes at once and theoretically reconstruct the whole FCP X timeline in 
Nuke.

Thomas.

MINDTRANSPLANT
Audio  Video Produktion
www.mindtransplant.com


Am 08.03.2012 um 11:43 schrieb Ron Ganbar:

 Very nice, Thomas.
 I'm in!
 
 A couple of questions regarding future releases (if you indeed plan to update 
 this periodically):
 Are you planning to add speed change support?
 Are you planning to add more software choices?
 What about the round trip? Going back to FCPX from Nuke?
 Thanks,
 Ron Ganbar
 email: ron...@gmail.com
 tel: +44 (0)7968 007 309 [UK]
  +972 (0)54 255 9765 [Israel]
 url: http://ronganbar.wordpress.com/
 
 
 
 On 8 March 2012 12:15, Thomas - Mindtransplant tho...@mindtransplant.com 
 wrote:
 Hello,
 
 I´m not sure how many of you use Final Cut Pro X but if you do this might be 
 interesting:
 
 we released an application called ClipExporter which is a simple workflow and 
 export tool for Final Cut Pro X. It opens exported Final Cut Pro X projects 
 (fcpxml) and exports each clip as a Quicktime reference movie, Nuke file or 
 Syntheyes importable file. It creates shot based folders with custom 
 subfolders and extends each clip with handle frames. ClipExporter for Final 
 Cut Pro X is available on the Mac App Store.
 
 I think this might be very interesting for a lot of people who work with FCP 
 X and want to send their clips to other post-production applications.
 
 Please visit the product page (http://clipexporter.mindtransplant.com/) for 
 more informations and take a look at the demo video on 
 http://vimeo.com/36157075.
 
 
 Best regards, Thomas.
 
 P.S.: sorry for spamming.
 
 
 
 MINDTRANSPLANT
 Audio  Video Produktion
 www.mindtransplant.com
 
 
 ___
 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] Gizmo - Dynamic Properties Tab

2012-03-08 Thread Hugo Léveillé
hey

this should get you started. For this exemple, I just created a
Blur and added a slider to it so that the User tabs knob is
created. Then I seected the node and run this script in the
script editor

s = nuke.selectedNode()
s['knobChanged'].setValue('''
n = nuke.thisNode()
k = nuke.thisKnob()
if k.name() == inputChange:
if n.input(0):
n['User'].clearFlag(nuke.INVISIBLE)
else:
n['User'].setFlag(nuke.INVISIBLE)
''')

This will add a code to be run everytime the input of your node
is changed. So in this case, if the blur is connected to another
node, the tab will be shown. For a 2 input node, just change the
input number to match the one you need to track.

Hope this get you started



On Thu, Mar 8, 2012, at 11:12, barba wrote:

Hi all,
i'm a newbie about Gizmo and Python ..i'm happy to be here...i
hope to learn a lot of things with your help, for become a big
master ninja compositor! Wink
i'm trying to create a Gizmo for manage my multiEXR render... and
i would like to know if is possibile Hide a Tab if his node is
not plugged. i try to explain...for example i have a group with 2
input...A and B...in the Properties Tab i have two tab...one for
the attributes of input A and one for the attributes of input B..
is possibile hide the second tab when the B input is not
plugged??..
i know...it's not a big problem...but i think that would be cool
have a dynamic properties tab for my gizmo!
thanks
regards
R.

___
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


-- 
  Hugo Léveillé
  TD Compositing, Vision Globale
  hu...@fastmail.net

___
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] concatenation in nuke

2012-03-08 Thread Diogo Girondi
From what I know (most if not all) transform nodes concatenate as long
their filtering methods are the same. Color correction nodes don't, since
they are already calculated in 32bit linear float.

On Thu, Mar 8, 2012 at 7:36 AM, Ron Ganbar ron...@gmail.com wrote:

 Purple colored Transform nodes concatenate together, far as I remember.


 Ron Ganbar
 email: ron...@gmail.com
 tel: +44 (0)7968 007 309 [UK]
  +972 (0)54 255 9765 [Israel]
 url: http://ronganbar.wordpress.com/



 On 8 March 2012 12:14, James Etherington james.ethering...@gmail.comwrote:

 Colour grades don't concatenate in Nuke 'cos it's all in float.


 On Thu, Mar 8, 2012 at 10:11 AM, Peter Hartwig 
 peter.hart...@gmail.comwrote:

 Hey y'all

 I was talking to my colleague, trying to figure out if there is a way
 to see when transform nodes, colorgrades etc concatenate in nuke... we
 both seem to rememeber it being possible in older versions...

 anyone?

 cheers
 Peter
 ___
 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] concatenation in nuke

2012-03-08 Thread Peter Hartwig
it would just be nice to have a visual indication that it's all
good... but thanks guys



On Thu, Mar 8, 2012 at 3:46 PM, Diogo Girondi diogogiro...@gmail.com wrote:
 From what I know (most if not all) transform nodes concatenate as long
 their filtering methods are the same. Color correction nodes don't, since
 they are already calculated in 32bit linear float.


 On Thu, Mar 8, 2012 at 7:36 AM, Ron Ganbar ron...@gmail.com wrote:

 Purple colored Transform nodes concatenate together, far as I remember.


 Ron Ganbar
 email: ron...@gmail.com
 tel: +44 (0)7968 007 309 [UK]
      +972 (0)54 255 9765 [Israel]
 url: http://ronganbar.wordpress.com/



 On 8 March 2012 12:14, James Etherington james.ethering...@gmail.com
 wrote:

 Colour grades don't concatenate in Nuke 'cos it's all in float.


 On Thu, Mar 8, 2012 at 10:11 AM, Peter Hartwig peter.hart...@gmail.com
 wrote:

 Hey y'all

 I was talking to my colleague, trying to figure out if there is a way
 to see when transform nodes, colorgrades etc concatenate in nuke... we
 both seem to rememeber it being possible in older versions...

 anyone?

 cheers
 Peter
 ___
 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
___
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] 32 bit to 8 bit conversion?

2012-03-08 Thread Richard Bobo
Simon,Are you saying that the .4545 levels effect on the layer masks and the overall 2.2 gamma adjustment should be done before the 32 to 8 bit depth conversion or after...?Thanks,RichRich Bobo 
Senior VFX Compositor
Email:  richb...@mac.com			
Mobile:  248.840.2665
Web:  http://richbobo.comOn Mar 08, 2012, at 03:46 AM, Simon Björk si...@stillerstudios.se wrote:Look here to create a linear ICC profile: http://fnordware.blogspot.com/2008/05/making-linear-icc-profile.html.With that set as your working space, you should be able to get correct blending.If you only have a couple of layers, you could try adding a Levels effect and set gamma to 0.4545 to each layer. On the top of your layers you would then need to set an adjustment layer with a gamma of 2.2./Simon2012/3/8 Randy Little rlit...@rslittle.combecause you are using blend modes in photoshop that do not support float math(s)  AND/Or you your working space ICC is not set up right.  Randy S. Little http://reel.rslittle.com http://imdb.com/name/nm2325729/On Wed, Mar 7, 2012 at 20:43, Richard Bobo richb...@mac.com wrote:  Adrian,   Thanks for wanting to help!   Here are the parameters:  -- CG render passes, comped and beautified in Nuke (auto work)...  -- Ultimate deliverables for client are layered 8 bit TIFF files with alpha out of Photoshop (different parts of vehicle)...  In order to ease the workload, we are trying to render layered files out of  Nuke that get loaded into Photoshop. There is some automated work that is  done with a recorded macro/droplet in Photoshop and the end result is our  client-ready 8 bit layered TIFF .psd file.   It would be *perfect* if we could render out an 8 bit layered file of some  kind from Nuke. The only reliable layered file format that I know of coming  out of Nuke is EXR. And, I don't think Nuke will produce a layered TIFF or  DPX that Photoshop can read properly. I could be wrong about that and if I  am, I'd love to know how to do it! Also, EXR output does not allow 8 bit, as  far as I can tell. So, we've tried 32 and 16 bit EXRs.   The OpenEXR Photoshop plugin does a nice job of loading the EXR files,  either as premultiplied layers with transparency or as unpremultiplied,  separated layers for fill and alpha. The look of the layer comp in Photoshop  matches Nuke as long as we stay in 32 bit linear space in Photoshop.  However, changing the bit depth to 8 bit results in a general darkening of  the image layers and a different "gamma look" to the transparent areas. In  other words, the nice linear gradients are squashed in some areas and not as  "spread out".   The ProEXR manual does speak about this kind of problem and suggests  bringing in the layers unpremultiplied and using Levels adjustments on the  layer masks only of each layer before changing the bit depth. With some  trial and error, I have been able to find some values that will *almost*  work. However, the levels adjustment values are not the same for each layer.  And, it still does not look quite right.   Photoshop *will* produce the correct result, however, *if* we choose to  Merge the layers before doing the 32--8 conversion - but that's not what we  need - we need the layers...   So, for the moment, we are going to try and see if we can live with  individual Levels adjustments for each layer in Photoshop, prior to the bit  depth conversion. That may be the path of least resistance - but it sure  ain't pretty!  (8^P   So, Adrian, I hope that explains things a bit better. if you have any  suggestions, I would love to hear them!   Thanks,   RichRich Bobo  Senior VFX Compositor   Mobile: (248) 840-2665  Web: http://richbobo.com/   "Man has been endowed with reason, with the power to create, so that he can  add to what he's been given."  - Anton Chekhov   On Mar 7, 2012, at 6:24 PM, Adrian Baltowski wrote:   Hi   I want help or advise you something but I don't fully understand your  workflow...  You can of course make color conversion in nuke. Nuke is brilliant software  to make such a conversions BUT What next?? You cannot export layered  tiffs out of Nuke (at least not in usable form). Do you want to export  layers as separate tif files?  If you could explain your workflow then we could advise you more. Best  AdrianW dniu 2012-03-07 16:33:54 użytkownik Juan Galva juan.ga...@gmail.com  napisał:   keep us posted, please!   On 7 March 2012 16:27, Richard Bobo richb...@mac.com wrote:   Thanks, Julik, Andy, Diogo and Simon for your suggestions, ideas and  questions...   After trying a number of things and reading some more about the way ProEXR  and Photoshop handle things, we're going to try to make our tweaks in Nuke  and let Photoshop do whatever it does. It may take a few rounds of tweaking  and converting to see just what we need to do on the Nuke side to make it  come out the way we want on the Photoshop end. However, it seems like there  are just too many variables there. So, we'll not try to fight it... (8^   Thanks for your 

Re: [Nuke-users] 32 bit to 8 bit conversion?

2012-03-08 Thread Simon Björk
After, as it will make the layers blend in linear light instead of sRGB.
The overall gamma will be the same as the sRGB viewer lut you have in
Nuke. Although, you might introduce problems with banding as your really
bending the colors of 8-bit. Of course you will also clamp values above 1.
It might be better to do your compositing in sRGB space in Nuke as other
suggested, but it's worth a try. Essentially, this would be somewhat the
same thing as using a linear ICC profile in PS.


2012/3/8 Richard Bobo richb...@mac.com

 Simon,

 Are you saying that the .4545 levels effect on the layer masks and the
 overall 2.2 gamma adjustment should be done before the 32 to 8 bit depth
 conversion or after...?

 Thanks,

 Rich

 Rich Bobo
 Senior VFX Compositor
 Email:  richb...@mac.com  
 Mobile:  248.840.2665
 Web:  http://richbobo.com


 On Mar 08, 2012, at 03:46 AM, Simon Björk si...@stillerstudios.se wrote:

 Look here to create a linear ICC profile:
 http://fnordware.blogspot.com/2008/05/making-linear-icc-profile.html. With
 that set as your working space, you should be able to get correct blending.

 If you only have a couple of layers, you could try adding a Levels effect
 and set gamma to 0.4545 to each layer. On the top of your layers you would
 then need to set an adjustment layer with a gamma of 2.2.

 /Simon


 2012/3/8 Randy Little rlit...@rslittle.com

 because you are using blend modes in photoshop that do not support
 float math(s)   AND/Or you your working space ICC is not set up right.

 Randy S. Little
 http://reel.rslittle.com
 http://imdb.com/name/nm2325729/




 On Wed, Mar 7, 2012 at 20:43, Richard Bobo richb...@mac.com wrote:
  Adrian,
 
  Thanks for wanting to help!
 
  Here are the parameters:
  -- CG render passes, comped and beautified in Nuke (auto work)...
  -- Ultimate deliverables for client are layered 8 bit TIFF files with
 alpha
  out of Photoshop (different parts of vehicle)...
 
  In order to ease the workload, we are trying to render layered files
 out of
  Nuke that get loaded into Photoshop. There is some automated work that
 is
  done with a recorded macro/droplet in Photoshop and the end result is
 our
  client-ready 8 bit layered TIFF .psd file.
 
  It would be *perfect* if we could render out an 8 bit layered file of
 some
  kind from Nuke. The only reliable layered file format that I know of
 coming
  out of Nuke is EXR. And, I don't think Nuke will produce a layered TIFF
 or
  DPX that Photoshop can read properly. I could be wrong about that and
 if I
  am, I'd love to know how to do it! Also, EXR output does not allow 8
 bit, as
  far as I can tell. So, we've tried 32 and 16 bit EXRs.
 
  The OpenEXR Photoshop plugin does a nice job of loading the EXR files,
  either as premultiplied layers with transparency or as unpremultiplied,
  separated layers for fill and alpha. The look of the layer comp in
 Photoshop
  matches Nuke as long as we stay in 32 bit linear space in Photoshop.
  However, changing the bit depth to 8 bit results in a general darkening
 of
  the image layers and a different gamma look to the transparent areas.
 In
  other words, the nice linear gradients are squashed in some areas and
 not as
  spread out.
 
  The ProEXR manual does speak about this kind of problem and suggests
  bringing in the layers unpremultiplied and using Levels adjustments on
 the
  layer masks only of each layer before changing the bit depth. With some
  trial and error, I have been able to find some values that will *almost*
  work. However, the levels adjustment values are not the same for each
 layer.
  And, it still does not look quite right.
 
  Photoshop *will* produce the correct result, however, *if* we choose to
  Merge the layers before doing the 32--8 conversion - but that's not
 what we
  need - we need the layers...
 
  So, for the moment, we are going to try and see if we can live with
  individual Levels adjustments for each layer in Photoshop, prior to the
 bit
  depth conversion. That may be the path of least resistance - but it sure
  ain't pretty!   (8^P
 
  So, Adrian, I hope that explains things a bit better. if you have any
  suggestions, I would love to hear them!
 
  Thanks,
 
  Rich
 
 
  Rich Bobo
  Senior VFX Compositor
 
  Mobile:  (248) 840-2665
  Web:  http://richbobo.com/
 
  Man has been endowed with reason, with the power to create, so that he
 can
  add to what he's been given.
  - Anton Chekhov
 
 
 
 
 
  On Mar 7, 2012, at 6:24 PM, Adrian Baltowski wrote:
 
  Hi
 
  I want help or advise you something but I don't fully understand your
  workflow...
  You can of course make color conversion in nuke. Nuke is brilliant
 software
  to make such a conversions BUT What next?? You cannot export layered
  tiffs out of Nuke (at least not in usable form). Do you want to export
  layers as separate tif files?
  If you could explain your workflow then we could advise you more.
 
 
 
  Best
  Adrian
 
 
  W dniu 2012-03-07 16:33:54 

Re: [Nuke-users] 32 bit to 8 bit conversion?

2012-03-08 Thread Simon Björk
And the levels should be applied to the actual layers, not on masks. Unless
I'm misunderstanding you.

2012/3/8 Simon Björk si...@stillerstudios.se

 After, as it will make the layers blend in linear light instead of sRGB.
 The overall gamma will be the same as the sRGB viewer lut you have in
 Nuke. Although, you might introduce problems with banding as your really
 bending the colors of 8-bit. Of course you will also clamp values above 1.
 It might be better to do your compositing in sRGB space in Nuke as other
 suggested, but it's worth a try. Essentially, this would be somewhat the
 same thing as using a linear ICC profile in PS.


 2012/3/8 Richard Bobo richb...@mac.com

 Simon,

 Are you saying that the .4545 levels effect on the layer masks and the
 overall 2.2 gamma adjustment should be done before the 32 to 8 bit depth
 conversion or after...?

 Thanks,

 Rich

 Rich Bobo
 Senior VFX Compositor
 Email:  richb...@mac.com 
 Mobile:  248.840.2665
 Web:  http://richbobo.com


 On Mar 08, 2012, at 03:46 AM, Simon Björk si...@stillerstudios.se
 wrote:

 Look here to create a linear ICC profile:
 http://fnordware.blogspot.com/2008/05/making-linear-icc-profile.html. With
 that set as your working space, you should be able to get correct blending.

 If you only have a couple of layers, you could try adding a Levels effect
 and set gamma to 0.4545 to each layer. On the top of your layers you would
 then need to set an adjustment layer with a gamma of 2.2.

 /Simon


 2012/3/8 Randy Little rlit...@rslittle.com

 because you are using blend modes in photoshop that do not support
 float math(s)   AND/Or you your working space ICC is not set up right.

 Randy S. Little
 http://reel.rslittle.com
 http://imdb.com/name/nm2325729/




 On Wed, Mar 7, 2012 at 20:43, Richard Bobo richb...@mac.com wrote:
  Adrian,
 
  Thanks for wanting to help!
 
  Here are the parameters:
  -- CG render passes, comped and beautified in Nuke (auto work)...
  -- Ultimate deliverables for client are layered 8 bit TIFF files with
 alpha
  out of Photoshop (different parts of vehicle)...
 
  In order to ease the workload, we are trying to render layered files
 out of
  Nuke that get loaded into Photoshop. There is some automated work that
 is
  done with a recorded macro/droplet in Photoshop and the end result is
 our
  client-ready 8 bit layered TIFF .psd file.
 
  It would be *perfect* if we could render out an 8 bit layered file of
 some
  kind from Nuke. The only reliable layered file format that I know of
 coming
  out of Nuke is EXR. And, I don't think Nuke will produce a layered
 TIFF or
  DPX that Photoshop can read properly. I could be wrong about that and
 if I
  am, I'd love to know how to do it! Also, EXR output does not allow 8
 bit, as
  far as I can tell. So, we've tried 32 and 16 bit EXRs.
 
  The OpenEXR Photoshop plugin does a nice job of loading the EXR files,
  either as premultiplied layers with transparency or as unpremultiplied,
  separated layers for fill and alpha. The look of the layer comp in
 Photoshop
  matches Nuke as long as we stay in 32 bit linear space in Photoshop.
  However, changing the bit depth to 8 bit results in a general
 darkening of
  the image layers and a different gamma look to the transparent
 areas. In
  other words, the nice linear gradients are squashed in some areas and
 not as
  spread out.
 
  The ProEXR manual does speak about this kind of problem and suggests
  bringing in the layers unpremultiplied and using Levels adjustments on
 the
  layer masks only of each layer before changing the bit depth. With some
  trial and error, I have been able to find some values that will
 *almost*
  work. However, the levels adjustment values are not the same for each
 layer.
  And, it still does not look quite right.
 
  Photoshop *will* produce the correct result, however, *if* we choose to
  Merge the layers before doing the 32--8 conversion - but that's not
 what we
  need - we need the layers...
 
  So, for the moment, we are going to try and see if we can live with
  individual Levels adjustments for each layer in Photoshop, prior to
 the bit
  depth conversion. That may be the path of least resistance - but it
 sure
  ain't pretty!   (8^P
 
  So, Adrian, I hope that explains things a bit better. if you have any
  suggestions, I would love to hear them!
 
  Thanks,
 
  Rich
 
 
  Rich Bobo
  Senior VFX Compositor
 
  Mobile:  (248) 840-2665
  Web:  http://richbobo.com/
 
  Man has been endowed with reason, with the power to create, so that
 he can
  add to what he's been given.
  - Anton Chekhov
 
 
 
 
 
  On Mar 7, 2012, at 6:24 PM, Adrian Baltowski wrote:
 
  Hi
 
  I want help or advise you something but I don't fully understand your
  workflow...
  You can of course make color conversion in nuke. Nuke is brilliant
 software
  to make such a conversions BUT What next?? You cannot export
 layered
  tiffs out of Nuke (at least not in usable form). Do you want to 

Re: [Nuke-users] 32 bit to 8 bit conversion?

2012-03-08 Thread chris

some notes to all the good info already suggested:

- if you do your gamma correction in photoshop, use the gamma in 
exposure rather then levels. last time i checked, the one in 
levels was not a mathematical gamma correction but has some 
adobe visually pleasing stuff added.


- also, do your gamma correction in 32bit, then first drop down 
to 16bit to undo the gamma, then drop to 8it. this will avoid 
banding issues.


- and lastly, note that photoshop introduces dither when 
dropping to 8bit. this might or might not be what you want.


so basically, you're probably better off comping in sRGB in nuke 
(so that it looks slightly wrong), then write out exr, import 
into PS, dropping to 8bit (so they look like you would have 
comped in nuke linearly). can't see a way to avoid the dither 
issue if you take the exr route though.


++ chris


On 3/8/12 at 5:17 PM, si...@stillerstudios.se (Simon Björk) wrote:


After, as it will make the layers blend in linear light
instead of sRGB. The overall gamma will be the same as the
sRGB viewer lut you have in Nuke. Although, you might
introduce problems with banding as your really bending the
colors of 8-bit. Of course you will also clamp values
above 1. It might be better to do your compositing in sRGB
space in Nuke as other suggested, but it's worth a try.
Essentially, this would be somewhat the same thing as
using a linear ICC profile in PS.



___
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] Re: concatenation in nuke

2012-03-08 Thread mattdleonard
Hiya,

Transform nodes in Nuke that concatenate include:

• Transform
• TransformMasked
• CameraShake
• Reformat
• CornerPin
• Tracker
• Stabilize
• Reconcile3D
• Card3D
• Transform3D (hidden under Other / T)
• MotionBlur2D (will receive a concatenated Transform, but doesn't pass it on)

However some of the Transform nodes do not concatenate so make sure they aren’t 
interspersed with those nodes that do. The non-concatenating Transform nodes 
are:

• Mirror
• Position
• TVIscale
• GridWarp
• SplineWarp
• Crop
• PlanarTracker (though the PlanarTracker Corner Pin exports will concatenate)

Concatenation also affects the filtering hit you get when Transforming an 
image. The way Nuke handles this with multiple concatenated Transforms is to 
only apply one filter hit based on the settings of the final Transform node. 
The other Transform nodes’ filters are ignored.

Although the Nuke documents currently state that Colour nodes concatenate (page 
93, Nuke 6.3v6) they in fact don't. This is because, as already said above, 
Nuke is 32bit float (integer: 4,294,967,296 colours per channel = 80 octillion 
colours (80x10²⁸)) and doesn’t need too. :)

Hope this helps,

Matt


Sphere VFX Ltd
3D . VFX . Training
www.spherevfx.com



___
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] Re: concatenation in nuke

2012-03-08 Thread Julien Chandelle
And why a merge node block the concatenation like that :

set cut_paste_input [stack 0]
version 6.3 v4
CheckerBoard2 {
 inputs 0
 name CheckerBoard1
 selected true
 xpos -525
 ypos -17
}
Transform {
 scale 0.1
 center {960 540}
 name Transform1
 selected true
 xpos -525
 ypos 77
}
Constant {
 inputs 0
 channels rgb
 name Constant1
 selected true
 xpos -403
 ypos -27
}
Merge2 {
 inputs 2
 name Merge1
 selected true
 xpos -403
 ypos 77
}
Transform {
 scale 10
 center {960 540}
 name Transform2
 selected true
 xpos -403
 ypos 130
}

I think if I remember well in Fusion this setup works.
It would be great if you include this in Nuke.


On Thu, Mar 8, 2012 at 8:53 PM, mattdleonard 
nuke-users-re...@thefoundry.co.uk wrote:

 **
 Hiya,

 Transform nodes in Nuke that concatenate include:

 • Transform
 • TransformMasked
 • CameraShake
 • Reformat
 • CornerPin
 • Tracker
 • Stabilize
 • Reconcile3D
 • Card3D
 • Transform3D (hidden under Other / T)
 • MotionBlur2D (will receive a concatenated Transform, but doesn't pass it
 on)

 However some of the Transform nodes do not concatenate so make sure they
 aren’t interspersed with those nodes that do. The non-concatenating
 Transform nodes are:

 • Mirror
 • Position
 • TVIscale
 • GridWarp
 • SplineWarp
 • Crop
 • PlanarTracker (though the PlanarTracker Corner Pin exports will
 concatenate)

 Concatenation also affects the filtering hit you get when Transforming an
 image. The way Nuke handles this with multiple concatenated Transforms is
 to only apply one filter hit based on the settings of the final Transform
 node. The other Transform nodes’ filters are ignored.

 Although the Nuke documents currently state that Colour nodes concatenate
 (page 93, Nuke 6.3v6) they in fact don't. This is because, as already said
 above, Nuke is 32bit float (integer: 4,294,967,296 colours per channel = 80
 octillion colours (80x10²⁸)) and doesn’t need too. [image: Smile]

 Hope this helps,

 Matt


 --

 Sphere VFX Ltd
 3D . VFX . Training
 www.spherevfx.com

 ___
 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




-- 
Julien Chandelle
GSM : +32 (0) 494 277 542
julienchandelle.be http://www.julienchandelle.be
@jimbiscuit https://twitter.com/#%21/jimbiscuit ||
imdbhttp://www.imdb.com/name/nm2844171/
|| Nuke , AE  Fusion Compositor ||
___
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] Re: concatenation in nuke

2012-03-08 Thread Howard Jones
TransformMasked doesn't concatenate

Also the last node in line determines the filter type - not sure which how 
motion blur is determined though.

The visual clue is the image is too soft ;)

 
Howard




 From: mattdleonard nuke-users-re...@thefoundry.co.uk
To: nuke-users@support.thefoundry.co.uk 
Sent: Thursday, 8 March 2012, 19:53
Subject: [Nuke-users] Re: concatenation in nuke
 

Hiya,

Transform nodes in Nuke that concatenate include:

• Transform
• TransformMasked
• CameraShake
• Reformat
• CornerPin
• Tracker
• Stabilize
• Reconcile3D
• Card3D
• Transform3D (hidden under Other / T)
• MotionBlur2D (will receive a concatenated Transform, but doesn't pass it on)

However some of the Transform nodes do not concatenate so make sure they 
aren’t interspersed with those nodes that do. The non-concatenating Transform 
nodes are:

• Mirror
• Position
• TVIscale
• GridWarp
• SplineWarp
• Crop
• PlanarTracker (though the PlanarTracker Corner Pin exports will concatenate)

Concatenation also affects the filtering hit you get when Transforming an 
image. The way Nuke handles this with multiple concatenated Transforms is to 
only apply one filter hit based on the settings of the final Transform node. 
The other Transform nodes’ filters are ignored.

Although the Nuke documents currently state that Colour nodes concatenate 
(page 93, Nuke 6.3v6) they in fact don't. This is because, as already said 
above, Nuke is 32bit float (integer: 4,294,967,296 colours per channel = 80 
octillion colours (80x10²⁸)) and doesn’t need too. 

Hope this helps,

Matt




Sphere VFX Ltd
3D . VFX . Training
www.spherevfx.com
___
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] 32 bit to 8 bit conversion?

2012-03-08 Thread Richard Bobo
Simon,I made a linear ICC working space profile and I was able to successfully convert my 32 bit file to 8 bit with very little shifting of values. Yea! So, that was a "win" - thank you! The one wrinkle that I hadn't taken into account is that when I save out the 8 bit layered TIFF file from Photoshop - it's still in linear colorspace! And, if I do a convert to color space in Photoshop - from linear to sRGB - I still get the same darkening as before! So, I'll I've really done is to move the problem farther down the pipeline! Arrgghh...  Any suggestions?Thanks,RichRich Bobo 
Senior VFX Compositor
Email:  richb...@mac.com			
Mobile:  248.840.2665
Web:  http://richbobo.comOn Mar 08, 2012, at 11:17 AM, Simon Björk si...@stillerstudios.se wrote:After, as it will make the layers blend in linear light instead of sRGB. The overall gamma will be the same as the sRGB viewer lut you have in Nuke.Although, you might introduce problems with banding as your really bending the colors of 8-bit. Of course you will also clamp values above 1. It might be better to do your compositing in sRGB space in Nuke as other suggested, but it'sworth a try.Essentially, this would be somewhat the same thing as using a linear ICC profile in PS.2012/3/8 Richard Bobo richb...@mac.comSimon,Are you saying that the .4545 levels effect on the layer masks and the overall 2.2 gamma adjustment should be done before the 32 to 8 bit depth conversion or after...?Thanks,RichRich Bobo 
Senior VFX Compositor
Email:  richb...@mac.com			
Mobile:  248.840.2665
Web:  http://richbobo.comOn Mar 08, 2012, at 03:46 AM, Simon Björk si...@stillerstudios.se wrote: Look here to create a linear ICC profile: http://fnordware.blogspot.com/2008/05/making-linear-icc-profile.html.With that set as your working space, you should be able to get correct blending.If you only have a couple of layers, you could try adding a Levels effect and set gamma to 0.4545 to each layer. On the top of your layers you would then need to set an adjustment layer with a gamma of 2.2./Simon2012/3/8 Randy Little rlit...@rslittle.combecause you are using blend modes in photoshop that do not support float math(s)  AND/Or you your working space ICC is not set up right.  Randy S. Little http://reel.rslittle.com http://imdb.com/name/nm2325729/On Wed, Mar 7, 2012 at 20:43, Richard Bobo richb...@mac.com wrote:  Adrian,   Thanks for wanting to help!   Here are the parameters:  -- CG render passes, comped and beautified in Nuke (auto work)...  -- Ultimate deliverables for client are layered 8 bit TIFF files with alpha out of Photoshop (different parts of vehicle)...  In order to ease the workload, we are trying to render layered files out of  Nuke that get loaded into Photoshop. There is some automated work that is  done with a recorded macro/droplet in Photoshop and the end result is our  client-ready 8 bit layered TIFF .psd file.   It would be *perfect* if we could render out an 8 bit layered file of some  kind from Nuke. The only reliable layered file format that I know of coming  out of Nuke is EXR. And, I don't think Nuke will produce a layered TIFF or  DPX that Photoshop can read properly. I could be wrong about that and if I  am, I'd love to know how to do it! Also, EXR output does not allow 8 bit, as  far as I can tell. So, we've tried 32 and 16 bit EXRs.   The OpenEXR Photoshop plugin does a nice job of loading the EXR files,  either as premultiplied layers with transparency or as unpremultiplied,  separated layers for fill and alpha. The look of the layer comp in Photoshop  matches Nuke as long as we stay in 32 bit linear space in Photoshop.  However, changing the bit depth to 8 bit results in a general darkening of  the image layers and a different "gamma look" to the transparent areas. In  other words, the nice linear gradients are squashed in some areas and not as  "spread out".   The ProEXR manual does speak about this kind of problem and suggests  bringing in the layers unpremultiplied and using Levels adjustments on the  layer masks only of each layer before changing the bit depth. With some  trial and error, I have been able to find some values that will *almost*  work. However, the levels adjustment values are not the same for each layer.  And, it still does not look quite right.   Photoshop *will* produce the correct result, however, *if* we choose to  Merge the layers before doing the 32--8 conversion - but that's not what we  need - we need the layers...   So, for the moment, we are going to try and see if we can live with  individual Levels adjustments for each layer in Photoshop, prior to the bit  depth conversion. That may be the path of least resistance - but it sure  ain't pretty!  (8^P   So, Adrian, I hope that explains things a bit better. if you have any  suggestions, I would love to hear them!   Thanks,   RichRich Bobo  Senior VFX Compositor   Mobile: (248) 840-2665  Web: http://richbobo.com/   "Man has been endowed with reason, with the power to create, so that he