[Nuke-users] Re: ZDefocus driven by Axis
If your depth pass is reliably in the same units as your camera, you can directly calculate the distance from the camera to your axis with an expression on the focus plane knob, e.g.: 1/sqrt(pow(Axis1.translate.x-Camera1.translate.x, 2)+pow(Axis1.translate.y-Camera1.translate.y, 2)+pow(Axis1.translate.z-Camera1.translate.z, 2)) The above works for ScanlineRender's depth output, with the ZDefocus math knob set to the default far=0. If your CG uses absolute depths (really big numbers, background shows colour of inf) the above works if you remove the 1/ at the begining and change the math knob to depth. (Technically I think a lot of depth passes are distance to the camera plane rather than the camera point but the difference wasn't too big a deal last time I compared) John Mangia wrote: even the best focus pullers in real life aren't dead on with their focus +1! Removing 90% of the keyframes and leaving some overshoot helps... -- Lewis Saunders loves to steal axis data from maya rivets London ___ 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: [Nuke-python] Writing IPTC photometadata
you could try using exiftool in an afterFrameRender callback: http://www.sno.phy.queensu.ca/~phil/exiftool/ jrab On 03/31/2014 09:47 PM, Richard Bobo wrote: Hi all, Has anyone had to write IPTC metadata in their PNG output images before? And, if so, how did you do it? I need to output PNGs with some metadata that can be viewed in Photoshop under the IPTC tab of the File Info command... Thanks for any help, Rich Rich Bobo Senior VFX Compositor Email: richb...@mac.com Mobile: 248.840.2665 Web: http://richbobo.com ___ Nuke-python mailing list nuke-pyt...@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python ___ 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] MochaImport+ for NUKE available now
Hi everyone, I just wanted to share the news that we’ve published MochaImport+ for NUKE today. It simplifies the workflow to get tracking data from Imagineer Systems mocha to NUKE. You can, for example, directly import the tracking data into NUKE’s nodes Tracker, Roto, RotoPaint, GridWarp and Transform. You also get the 1-click rig for the “stabilized precomps” that are so popular in MochaImport+ for After Effects. It is also worth mentioning that all planar tracking data (translation/scale/rotation/shear/perspective) is imported. In contrast to that, most manual approaches to import mocha data just consider translation/rotation/scale and hence are not just more cumbersome, but are also less accurate as they ignore shear and perspective data. buy MochaImport+ (20% off introductory price) http://aescripts.com/mochaimport-for-nuke/ in depth tutorial http://mamoworld.com/tutorials/mochaimport-nuke-depth-tutorial I am also going to demo MochaImport+ for NUKE at NAB show - both that the booth of The Foundry and at the booth of Imagineer Systems. See you there! Cheers, Mathias mamoworld.com simplify your cgi Dr. Mathias Möhl Marlow 52 , 18551 Sagard, Germany Phone +49 (0)38302 - 88 75 61 i...@mamoworld.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] Writing IPTC photometadata
What’s your target app - PS or Bridge or non-adobe ? If it’s adobe then I would try finding some way to kluge it via automation / droplet. A quick bingle seemed to imply that IPTC support in the png spec’s was limited which might explain why PS use’s it’s own category header in an attempt to do no harm but then proceeds to ignore any other headers since it doesn’t no how interpret it since it’s not in the spec. Other IPTC tools I’ve used in case they are helpful mainly mac based :- Image Ingester / Exif Changer www.basepath.com - exiftool based Meta Machine http://www.hindsightltd.com/metamachine/index.html Media Pro formerly iView / WIndows Media - www.phaseone.com - pretty solid and scriptable Photo Mechanic www.camerabits.com is the gold standard for anything to do with metadata “Good luck with all that” - Seinfeld circa 2005 --- Andrew Mumford a_mumf...@mac.com 1 (310) 619 0208 On Mar 31, 2014, at 6:31 PM, Richard Bobo richb...@mac.com wrote: Thanks, Andrew. After sending my email, I came across Exiftool and Exiv2. Both seemed to do the trick, but the problem I am running into has to do with the way Photoshop reads and writes IPTC data - which seems to be non-standard (what a surprise). If I write the IPTC metadata in Photoshop, it’s invisible to the readers in those programs. And, if I write the data with those programs, Photoshop does not see it. Looking through the docs for Exiftool, I believe it might be because PS puts the data in its own category header area. Unfortunately, I need the data to be viewable in PS. So, I am now researching a bit more to see if there is a standalone/commandline tool that will read and write Photoshop’s metadata… Thanks! Rich On Mar 31, 2014, at 3:58 PM, Andrew Mumford a_mumf...@mac.com wrote: Exiftool - http://www.sno.phy.queensu.ca/~phil/exiftool/ is bulletproof and cross platform ... --- Andrew Mumford a_mumf...@mac.com 1 (310) 619 0208 On Mar 31, 2014, at 12:47 PM, Richard Bobo richb...@mac.com wrote: Hi all, Has anyone had to write IPTC metadata in their PNG output images before? And, if so, how did you do it? I need to output PNGs with some metadata that can be viewed in Photoshop under the IPTC tab of the File Info command... Thanks for any help, Rich Rich Bobo Senior VFX Compositor Email: richb...@mac.com Mobile: 248.840.2665 Web: http://richbobo.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 ___ 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] Greenscreen studio cam/setup
I just came back from a shoot where I did just that - insist on 2k compression. We were meant to shoot 3k raw but since production failed to secure a T-Link, 2k prores was the next best thing I could ask for. I told them 422 would be unacceptable for vfx, especially for keying. I always ask the vfx house why and they shrug their shoulders The only "problem" on set is simply the increased data rate, hence the need to swap ou the card a little more more often and require more disc space (and a little bit of more time) for the data wrangler to manage backups etc. I can see this as an argument for drama only shots when you try to decide between 2k and 4k raw, but in I would never take this as an excuse to shoot 422 footage for vfx use. I'd rather not take the job. The more severe reason for this is usually simply lack of knowledge on the production side and lack of communication up front to establish the required camera settings before it's too late. It's a good idea to have the camera's spec sheet handy and refer to that before the shoot to avoid any misconceptions. Sorry if this sounds a bit smart-arsy, but since I just had that very scenario last week I thought I'd chime in. Cheers, frank On 3/30/14, 1:23 PM, Deke Kincaid wrote: The lowend Alexa shoots 12 bit Prores 444 on the SxS cards in LogC. Though for whatever reason tv shows always seem to shoot it in 422 mode. I'm not sure if it's out of habit or they are trying to get more time on each SxS card? I always ask the vfx house why and they shrug their shoulders and say they couldn't sway production to do it differently. I would just try to push production to shot prores 444 instead of getting another device. -- Deke Kincaid Creative Specialist The Foundry Skype:dekekincaid Tel:(310) 399 4555-Mobile: (310)883 4313 Web:www.thefoundry.co.uk Email: d...@thefoundry.co.uk On Sat, Mar 29, 2014 at 4:10 PM, J Bills jbillsn...@flickfx.com wrote: Hey y'all - might be a little behind the curve here but doing a batch of greenscreen shots shot on Alexa and it's pretty ratty. this is 4:2:2, but just doing a couple of google searches shows that there's a not terribly expensive (relatively) "Gemini" recorder that can get 4:4:4 off of it, so it seems like I might need to forward a couple of links and make some "suggestions" for next time. ;) Just curious since I've not looked into it for a while - is there a new killer setup that can get nice clean 4:4:4 GS HD footage on a reasonable budget? bonus points for 10 bit, log, dng, etc. You hear blips about the Blackmagic cams or Magic Lantern setups or whatever but I'm just curious if anyone has been keying any of this stuff and been impressed with anything, or done some testing? Anything reasonably portable out there you've come across or do you still need to tether to a RAID and capture through HDMI? NAB is just around the corner! ___ 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 -- vfx compositing | workflow customisation and consulting ___ 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] Greenscreen studio cam/setup
We had a problem on a shoot a few years ago. Was 4:4:4 afaik on an Arri but at the time they were recommending 800 ASA. As it was a night scene the DOP underlit. Now because of the gamma curve, especially as it was set to gain detail in blacks, the noise levels were awful. Worst keying I've ever had to do. I understand 200 ASA is now recommended. Unfortunatly here 4:4:4 didn't help at all. Howard On 1 Apr 2014, at 22:19, Frank Rueter|OHUfx fr...@ohufx.com wrote: I just came back from a shoot where I did just that - insist on 2k compression. We were meant to shoot 3k raw but since production failed to secure a T-Link, 2k prores was the next best thing I could ask for. I told them 422 would be unacceptable for vfx, especially for keying. I always ask the vfx house why and they shrug their shoulders The only problem on set is simply the increased data rate, hence the need to swap ou the card a little more more often and require more disc space (and a little bit of more time) for the data wrangler to manage backups etc. I can see this as an argument for drama only shots when you try to decide between 2k and 4k raw, but in I would never take this as an excuse to shoot 422 footage for vfx use. I'd rather not take the job. The more severe reason for this is usually simply lack of knowledge on the production side and lack of communication up front to establish the required camera settings before it's too late. It's a good idea to have the camera's spec sheet handy and refer to that before the shoot to avoid any misconceptions. Sorry if this sounds a bit smart-arsy, but since I just had that very scenario last week I thought I'd chime in. Cheers, frank On 3/30/14, 1:23 PM, Deke Kincaid wrote: The lowend Alexa shoots 12 bit Prores 444 on the SxS cards in LogC. Though for whatever reason tv shows always seem to shoot it in 422 mode. I'm not sure if it's out of habit or they are trying to get more time on each SxS card? I always ask the vfx house why and they shrug their shoulders and say they couldn't sway production to do it differently. I would just try to push production to shot prores 444 instead of getting another device. -- Deke Kincaid Creative Specialist The Foundry Skype: dekekincaid Tel: (310) 399 4555 - Mobile: (310) 883 4313 Web: www.thefoundry.co.uk Email: d...@thefoundry.co.uk On Sat, Mar 29, 2014 at 4:10 PM, J Bills jbillsn...@flickfx.com wrote: Hey y'all - might be a little behind the curve here but doing a batch of greenscreen shots shot on Alexa and it's pretty ratty. this is 4:2:2, but just doing a couple of google searches shows that there's a not terribly expensive (relatively) Gemini recorder that can get 4:4:4 off of it, so it seems like I might need to forward a couple of links and make some suggestions for next time. ;) Just curious since I've not looked into it for a while - is there a new killer setup that can get nice clean 4:4:4 GS HD footage on a reasonable budget? bonus points for 10 bit, log, dng, etc. You hear blips about the Blackmagic cams or Magic Lantern setups or whatever but I'm just curious if anyone has been keying any of this stuff and been impressed with anything, or done some testing? Anything reasonably portable out there you've come across or do you still need to tether to a RAID and capture through HDMI? NAB is just around the corner! ___ 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 -- ohufxLogo_50x50.png vfx compositing | workflow customisation and consulting ___ 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] Writing IPTC photometadata
Andrew, Thanks for the help. After a lot of fruitless research trying to make PNG files display metadata in Photoshop (target app by client request), I have moved to TIFF. With some more work today, I now have a Python afterRender function in Nuke that adds the metadata fields to the rendered images - which *do* show up in Photoshop! I'm calling exiftool in my python function to do the work of adding the metadata tags, referencing a text file that holds all of the arguments for the exiftool command. Through the process of elimination, I discovered which xmp tags that Photoshop uses in their file info display. They are a hodgepodge from the xmp-photoshop, xmp-dc and xmp-itpsCore groups. ...So, to make a long story a little bit shorter, we will be telling our clients that, if they *really* want the metadata visible in PS, they'll need to move away from PNG file deliverables to TIFFs. I spent *way* too many hours figuring this out (mostly beating my head on a wall of PNGs), but I suppose I learned a few things in the process! ;^) Rich Sent from my iPod On Apr 1, 2014, at 3:44 PM, Andrew Mumford a_mumf...@mac.com wrote: What’s your target app - PS or Bridge or non-adobe ? If it’s adobe then I would try finding some way to kluge it via automation / droplet. A quick bingle seemed to imply that IPTC support in the png spec’s was limited which might explain why PS use’s it’s own category header in an attempt to do no harm but then proceeds to ignore any other headers since it doesn’t no how interpret it since it’s not in the spec. Other IPTC tools I’ve used in case they are helpful mainly mac based :- Image Ingester / Exif Changer www.basepath.com - exiftool based Meta Machine http://www.hindsightltd.com/metamachine/index.html Media Pro formerly iView / WIndows Media - www.phaseone.com - pretty solid and scriptable Photo Mechanic www.camerabits.com is the gold standard for anything to do with metadata “Good luck with all that” - Seinfeld circa 2005 --- Andrew Mumford a_mumf...@mac.com 1 (310) 619 0208 On Mar 31, 2014, at 6:31 PM, Richard Bobo richb...@mac.com wrote: Thanks, Andrew. After sending my email, I came across Exiftool and Exiv2. Both seemed to do the trick, but the problem I am running into has to do with the way Photoshop reads and writes IPTC data - which seems to be non-standard (what a surprise). If I write the IPTC metadata in Photoshop, it’s invisible to the readers in those programs. And, if I write the data with those programs, Photoshop does not see it. Looking through the docs for Exiftool, I believe it might be because PS puts the data in its own category header area. Unfortunately, I need the data to be viewable in PS. So, I am now researching a bit more to see if there is a standalone/commandline tool that will read and write Photoshop’s metadata… Thanks! Rich On Mar 31, 2014, at 3:58 PM, Andrew Mumford a_mumf...@mac.com wrote: Exiftool - http://www.sno.phy.queensu.ca/~phil/exiftool/ is bulletproof and cross platform ... --- Andrew Mumford a_mumf...@mac.com 1 (310) 619 0208 On Mar 31, 2014, at 12:47 PM, Richard Bobo richb...@mac.com wrote: Hi all, Has anyone had to write IPTC metadata in their PNG output images before? And, if so, how did you do it? I need to output PNGs with some metadata that can be viewed in Photoshop under the IPTC tab of the File Info command... Thanks for any help, Rich Rich Bobo Senior VFX Compositor Email: richb...@mac.com Mobile: 248.840.2665 Web: http://richbobo.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 ___ 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] Greenscreen studio cam/setup
Yeah, we shot everything on 800 which seems to be every DOPs' standard flavor. I also had to fight with the gaffer to give me a little bit of light on his rather orange "green screen". He kept insisting that, because it was perfectly on exposure, "it will sing - trust me". The fact that the colour of a green screen is important as well didn't seem to occur to him at all (quote: "the colour is shit but it's perfectly exposed"). I had to show him GreenScreener on my phone to convince him that some lighting was in order, though he refused to give me the blue/green gels I was asking for, so I now have a perfectly exposed orange screen with under exposed warm interior in the fg. Can't wait to get the plates :) On 4/2/14, 11:00 AM, Howard Jones wrote: We had a problem on a shoot a few years ago. Was 4:4:4 afaik on an Arri but at the time they were recommending 800 ASA. As it was a night scene the DOP underlit. Now because of the gamma curve, especially as it was set to gain detail in blacks, the noise levels were awful. Worst keying I've ever had to do. I understand 200 ASA is now recommended. Unfortunatly here 4:4:4 didn't help at all. Howard On 1 Apr 2014, at 22:19, Frank Rueter|OHUfx fr...@ohufx.com wrote: I just came back from a shoot where I did just that - insist on 2k compression. We were meant to shoot 3k raw but since production failed to secure a T-Link, 2k prores was the next best thing I could ask for. I told them 422 would be unacceptable for vfx, especially for keying. I always ask the vfx house why and they shrug their shoulders The only "problem" on set is simply the increased data rate, hence the need to swap ou the card a little more more often and require more disc space (and a little bit of more time) for the data wrangler to manage backups etc. I can see this as an argument for drama only shots when you try to decide between 2k and 4k raw, but in I would never take this as an excuse to shoot 422 footage for vfx use. I'd rather not take the job. The more severe reason for this is usually simply lack of knowledge on the production side and lack of communication up front to establish the required camera settings before it's too late. It's a good idea to have the camera's spec sheet handy and refer to that before the shoot to avoid any misconceptions. Sorry if this sounds a bit smart-arsy, but since I just had that very scenario last week I thought I'd chime in. Cheers, frank On 3/30/14, 1:23 PM, Deke Kincaid wrote: The lowend Alexa shoots 12 bit Prores 444 on the SxS cards in LogC. Though for whatever reason tv shows always seem to shoot it in 422 mode. I'm not sure if it's out of habit or they are trying to get more time on each SxS card? I always ask the vfx house why and they shrug their shoulders and say they couldn't sway production to do it differently. I would just try to push production to shot prores 444 instead of getting another device. -- Deke Kincaid Creative Specialist The Foundry Skype:dekekincaid Tel:(310) 399 4555-Mobile: (310)883 4313 Web:www.thefoundry.co.uk Email: d...@thefoundry.co.uk On Sat, Mar 29, 2014 at 4:10 PM, J Bills jbillsn...@flickfx.com wrote: Hey y'all - might be a little behind the curve here but doing a batch of greenscreen shots shot on Alexa and it's pretty ratty. this is 4:2:2, but just doing a couple of google searches shows that there's a not terribly expensive (relatively) "Gemini" recorder that
Re: [Nuke-users] Linux read DNxHD Quicktimes
Well, in Nuke chances are that you may need FrameHolds or other retime nodes that require multiples frames to be read from the input clip at the same time. That is usually when quicktime files fall apart and frame sequences can't be beaten for efficiency and stability. In Hiero you are much less likely to do that sort of thing. On 3/31/14, 6:16 PM, Jimmy Christensen wrote: Hiero uses pretty much the same reader as in Nuke, so even for Hiero the prefered solution is to not use MOVs (on Linux that is). Hilsen Jimmy Christensen Developer Ghost A/S On 28/03/14 18:57, Thomas Volkmann wrote: Yes, the common procedure when working in Nuke is to convert all the quicktimes before. But I have the same problem in HieroPlayer and converting all the shots for a whole movie is not a option I'm afraid :/ cheers, Thomas Nathan Rusch nathan_ru...@hotmail.com hat am 28. März 2014 um 18:45 geschrieben: The best solution is to not use MOVs in Nuke. There are numerous stability problems with various codecs, especially on Linux. -Nathan *From:* Thomas Volkmann mailto:li...@thomasvolkmann.com *Sent:* Friday, March 28, 2014 10:34 AM *To:* Nuke user discussion mailto:nuke-users@support.thefoundry.co.uk *Subject:* Re: [Nuke-users] Linux read DNxHD Quicktimes So what is the workaround? I just tried using the system libraries, but that gave me a segmentation fault :/ Nathan Rusch nathan_ru...@hotmail.com hat am 28. März 2014 um 18:27 geschrieben: Nuke’s ffmpegReader plugin has certain codecs blacklisted, some because of licensing issues and others for unknown reasons. DNxHD is definitely on that list in 7.0, and even though the plugin has changed in 8.0, there is still a codecBlacklist.h file included that I can only assume still contains DNxHD. -Nathan *From:* Thomas Volkmann mailto:li...@thomasvolkmann.com *Sent:* Friday, March 28, 2014 9:29 AM *To:* Nuke user discussion mailto:nuke-users@support.thefoundry.co.uk *Subject:* Re: [Nuke-users] Linux read DNxHD Quicktimes Didn't know about that one, thanks. But unfortunately Nuke continues to give me "unsupported codec" :/ Py Fave pyf...@gmail.com hat am 28. März 2014 um 17:09 geschrieben: add ffmpeg: in loader url ? ffmpeg:/home/user/myvideo.mov 2014-03-28 15:18 GMT+01:00 Thomas Volkmann li...@thomasvolkmann.com: Hi, my Nuke and HieroPlayer installations (Fedora20) are not able to read DNxHD Quicktimes. What is the regular procedure to get this to work? I have no problem watching them with different players. Google brought up a couple of threads, but the useful one ended with "I got it to work" :/ thanks, Thomas ___ 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/
