[Nuke-users] Tiff format - single strip ?
I have a client requesting tiff format in 1 single strip, containing all rows. Apparently what I am writing out from Nuke is not in this format. I am writing out 8 bit, uncompressed. How can I force Nuke to write out 1 single strip tiff ? Also, how can I check that this is the case ? Cheers M. From: nuke-users-requ...@support.thefoundry.co.uk Subject: Nuke-users Digest, Vol 43, Issue 28 To: nuke-users@support.thefoundry.co.uk Date: Mon, 26 Sep 2011 12:00:05 +0100 Send Nuke-users mailing list submissions to nuke-users@support.thefoundry.co.uk To subscribe or unsubscribe via the World Wide Web, visit http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users or, via email, send a message with subject or body 'help' to nuke-users-requ...@support.thefoundry.co.uk You can reach the person managing the list at nuke-users-ow...@support.thefoundry.co.uk When replying, please edit your Subject line so it is more specific than Re: Contents of Nuke-users digest... Today's Topics: 1. Re: Keying Issues with Alexa (Justin Ball) 2. associate account to the forum interface of this mail list (jason huang) 3. Re: On set data template (Deke Kincaid) 4. Re: On set data template (Ron Ganbar) 5. Re: make an rv session on render end (Frank Rueter) I have a client requesting tiff format in 1 single strip, containing all rows. Apparently what I am writing out from Nuke is not in this format. I am writing out 8 bit, uncompressed. How can I force Nuke to write out 1 single strip tiff ? Also, how can I check that this is the case ? Cheers G. -- Message: 1 Date: Sun, 25 Sep 2011 10:14:06 -0400 From: Justin Ball blamsamm...@gmail.com Subject: Re: [Nuke-users] Keying Issues with Alexa To: Nuke user discussion nuke-users@support.thefoundry.co.uk Message-ID: ca+qx0lo2nckgm12u7h7v6eu8menu7okuvdewdphgribpmky...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 On my latest show I tested shooting uncompressed for vfx, especially for screens. And counter intuitively the prores actually plays a little nicer, at least on the old lenses we are shooting with. The uncompressed was giving us a hard edge ringing that had to be stomped down while the prores softened it out and we could pull keys more efficiently. Justin On Sep 23, 2011 9:41 AM, Aaron Weintraub aa...@mrxfx.com wrote: Alexa also has an option to record the actual raw uncompressed data straight to a hard drive as 2880x1620 .ari files, which is the true native format of the camera. It's not so popular because you have to lug around (and pay for) an extra storage unit, but any projects with significant VFX will insist on it. The Prores encoding is done on-board and saved in realtime to lightweight flash cards, but even with 4:4:4:4, there are definitely compression artifacts in the quicktimes that aren't there in the raw files, not to mention the down-res to 1920. -A On 9/22/2011 9:39 PM, Nick Guth wrote: Confirmed. It is Apple ProRes 1920x1080 23.98 278.55 mbits/s ___ 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 -- next part -- An HTML attachment was scrubbed... URL: http://support.thefoundry.co.uk/cgi-bin/mailman/private/nuke-users/attachments/20110925/e1f8d5b3/attachment-0001.htm -- Message: 2 Date: Sun, 25 Sep 2011 11:25:40 -0500 From: jason huang jasonhuang1...@gmail.com Subject: [Nuke-users] associate account to the forum interface of this maillist To: nuke-user mail list nuke-users@support.thefoundry.co.uk Message-ID: CAN6e2OFbsz_BzmSViEMcW46s6=U5fi6t=omvucluyfbhrrr...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hi, First of all, I have no intention to bother all members in this regard but looking for some help about the mail list and its corresponding forum interface. I tried to log in the forum (http://forums.thefoundry.co.uk/phpBB2/index.php) but have no clue about the user name? There is no user name when I subscribe the mail list. The only info I have is my subscription email and corresponding password to the mail list. I couldn't create an user name with the same email address I used for mail list registration as it'll show the email address is used. Should I create a new account with a different email address just for the forum log-in? Thanks, Jason -- next part -- An HTML attachment was scrubbed... URL: http://support.thefoundry.co.uk/cgi-bin/mailman/private/nuke-users/attachments/20110925/35a483bd/attachment-0001.htm -- Message: 3 Date: Sun, 25 Sep 2011 12:55:21 -0700 From:
Re: [Nuke-users] Tiff format - single strip ?
I know what mean but that is about as obscure a use of tiff encoding that exist. Its for multipage tiff files. This is not used by any movie image program I am aware off. Its most often used for the same way a PDF would work. What is this delivery for? Randy S. Little http://www.rslittle.com http://reel.rslittle.com On Mon, Sep 26, 2011 at 05:57, Ron Ganbar ron...@gmail.com wrote: What do you mean by a single strip? Just a single file with the images one to the right of the other? Like how photoshop used to work with non still footage? 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 26 September 2011 14:55, Mike Pope mikey_p...@hotmail.com wrote: I have a client requesting tiff format in 1 single strip, containing all rows. Apparently what I am writing out from Nuke is not in this format. I am writing out 8 bit, uncompressed. How can I force Nuke to write out 1 single strip tiff ? Also, how can I check that this is the case ? Cheers M. From: nuke-users-requ...@support.thefoundry.co.uk Subject: Nuke-users Digest, Vol 43, Issue 28 To: nuke-users@support.thefoundry.co.uk Date: Mon, 26 Sep 2011 12:00:05 +0100 Send Nuke-users mailing list submissions to nuke-users@support.thefoundry.co.uk To subscribe or unsubscribe via the World Wide Web, visit http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users or, via email, send a message with subject or body 'help' to nuke-users-requ...@support.thefoundry.co.uk You can reach the person managing the list at nuke-users-ow...@support.thefoundry.co.uk When replying, please edit your Subject line so it is more specific than Re: Contents of Nuke-users digest... Today's Topics: 1. Re: Keying Issues with Alexa (Justin Ball) 2. associate account to the forum interface of this mail list (jason huang) 3. Re: On set data template (Deke Kincaid) 4. Re: On set data template (Ron Ganbar) 5. Re: make an rv session on render end (Frank Rueter) I have a client requesting tiff format in 1 single strip, containing all rows. Apparently what I am writing out from Nuke is not in this format. I am writing out 8 bit, uncompressed. How can I force Nuke to write out 1 single strip tiff ? Also, how can I check that this is the case ? Cheers G. -- Message: 1 Date: Sun, 25 Sep 2011 10:14:06 -0400 From: Justin Ball blamsamm...@gmail.com Subject: Re: [Nuke-users] Keying Issues with Alexa To: Nuke user discussion nuke-users@support.thefoundry.co.uk Message-ID: ca+qx0lo2nckgm12u7h7v6eu8menu7okuvdewdphgribpmky...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 On my latest show I tested shooting uncompressed for vfx, especially for screens. And counter intuitively the prores actually plays a little nicer, at least on the old lenses we are shooting with. The uncompressed was giving us a hard edge ringing that had to be stomped down while the prores softened it out and we could pull keys more efficiently. Justin On Sep 23, 2011 9:41 AM, Aaron Weintraub aa...@mrxfx.com wrote: Alexa also has an option to record the actual raw uncompressed data straight to a hard drive as 2880x1620 .ari files, which is the true native format of the camera. It's not so popular because you have to lug around (and pay for) an extra storage unit, but any projects with significant VFX will insist on it. The Prores encoding is done on-board and saved in realtime to lightweight flash cards, but even with 4:4:4:4, there are definitely compression artifacts in the quicktimes that aren't there in the raw files, not to mention the down-res to 1920. -A On 9/22/2011 9:39 PM, Nick Guth wrote: Confirmed. It is Apple ProRes 1920x1080 23.98 278.55 mbits/s ___ 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 -- next part -- An HTML attachment was scrubbed... URL: http://support.thefoundry.co.uk/cgi-bin/mailman/private/nuke-users/attachments/20110925/e1f8d5b3/attachment-0001.htm -- Message: 2 Date: Sun, 25 Sep 2011 11:25:40 -0500 From: jason huang jasonhuang1...@gmail.com Subject: [Nuke-users] associate account to the forum interface of this mail list To: nuke-user mail list nuke-users@support.thefoundry.co.uk Message-ID: CAN6e2OFbsz_BzmSViEMcW46s6=U5fi6t=omvucluyfbhrrr...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hi, First of all, I have no intention to bother all members in this regard but looking for some help about the mail list and its corresponding forum interface. I tried
Re: [Nuke-users] Tiff format - single strip ?
I'm assuming that by strip we're referring to the TIFF usage, which means the image is not tiled. Nuke does write out a single strip TIFF image with all rows. Here's the TIFF header of a file from Nuke: TIFF Directory at offset 0x3ff1c (261916) Image Width: 2048 Image Length: 1556 Resolution: 72, 72 (unitless) Bits/Sample: 8 Compression Scheme: Deflate Photometric Interpretation: RGB color Samples/Pixel: 3 Rows/Strip: 21 Planar Configuration: single image plane I think you need to get more information from your client as to what is wrong with the images. You can use the tiffcopy command available from libtiff.org to convert TIFF images between tiled and stripped. Jerry On 26 Sep 2011, at 13:10, Randy Little wrote: I know what mean but that is about as obscure a use of tiff encoding that exist. Its for multipage tiff files. This is not used by any movie image program I am aware off. Its most often used for the same way a PDF would work. What is this delivery for? Randy S. Little http://www.rslittle.com On Mon, Sep 26, 2011 at 05:57, Ron Ganbar ron...@gmail.com wrote: What do you mean by a single strip? Just a single file with the images one to the right of the other? Like how photoshop used to work with non still footage? 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 26 September 2011 14:55, Mike Pope mikey_p...@hotmail.com wrote: I have a client requesting tiff format in 1 single strip, containing all rows. Apparently what I am writing out from Nuke is not in this format. I am writing out 8 bit, uncompressed. How can I force Nuke to write out 1 single strip tiff ? Also, how can I check that this is the case ? Cheers M. From: nuke-users-requ...@support.thefoundry.co.uk Subject: Nuke-users Digest, Vol 43, Issue 28 To: nuke-users@support.thefoundry.co.uk Date: Mon, 26 Sep 2011 12:00:05 +0100 Send Nuke-users mailing list submissions to nuke-users@support.thefoundry.co.uk To subscribe or unsubscribe via the World Wide Web, visit http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users or, via email, send a message with subject or body 'help' to nuke-users-requ...@support.thefoundry.co.uk You can reach the person managing the list at nuke-users-ow...@support.thefoundry.co.uk When replying, please edit your Subject line so it is more specific than Re: Contents of Nuke-users digest... Today's Topics: 1. Re: Keying Issues with Alexa (Justin Ball) 2. associate account to the forum interface of this maillist (jason huang) 3. Re: On set data template (Deke Kincaid) 4. Re: On set data template (Ron Ganbar) 5. Re: make an rv session on render end (Frank Rueter) I have a client requesting tiff format in 1 single strip, containing all rows. Apparently what I am writing out from Nuke is not in this format. I am writing out 8 bit, uncompressed. How can I force Nuke to write out 1 single strip tiff ? Also, how can I check that this is the case ? Cheers G. -- Message: 1 Date: Sun, 25 Sep 2011 10:14:06 -0400 From: Justin Ball blamsamm...@gmail.com Subject: Re: [Nuke-users] Keying Issues with Alexa To: Nuke user discussion nuke-users@support.thefoundry.co.uk Message-ID: ca+qx0lo2nckgm12u7h7v6eu8menu7okuvdewdphgribpmky...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 On my latest show I tested shooting uncompressed for vfx, especially for screens. And counter intuitively the prores actually plays a little nicer, at least on the old lenses we are shooting with. The uncompressed was giving us a hard edge ringing that had to be stomped down while the prores softened it out and we could pull keys more efficiently. Justin On Sep 23, 2011 9:41 AM, Aaron Weintraub aa...@mrxfx.com wrote: Alexa also has an option to record the actual raw uncompressed data straight to a hard drive as 2880x1620 .ari files, which is the true native format of the camera. It's not so popular because you have to lug around (and pay for) an extra storage unit, but any projects with significant VFX will insist on it. The Prores encoding is done on-board and saved in realtime to lightweight flash cards, but even with 4:4:4:4, there are definitely compression artifacts in the quicktimes that aren't there in the raw files, not to mention the down-res to 1920. -A On 9/22/2011 9:39 PM, Nick Guth wrote: Confirmed. It is Apple ProRes 1920x1080 23.98 278.55 mbits/s ___ 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 -- next part
Re: [Nuke-users] Re: I got a weird one here guys....
Sorry, yes, I should have mentioned that. When I write out the exr and read it back, it still has the errors I see when just viewing the write node. -ak On Sat, Sep 24, 2011 at 4:22 PM, Sean Looper sloo...@imageworks.com wrote: The Write node passthrough does make certain assumptions when your output is exr. Try writing the file out and compare the written frames to your last node. -sean Sent from my cellular device On Sep 24, 2011, at 2:16 PM, Anthony Kramer anthony.kra...@gmail.com wrote: NukeX 6.3v2 Windows 7 On Sat, Sep 24, 2011 at 2:11 PM, Anthony Kramer anthony.kra...@gmail.com anthony.kra...@gmail.com wrote: It gets worse.. Seems like it's also calculating a few other key operations in my comp differently when selecting EXR as the output format in a write. Besides the neg values below which seem to be coming from a grade, it also makes my Zblur and LensDistortion look different. If I disable those 3 nodes, I get no difference between the last node and the write. If I enable ANY ONE of those nodes I get a slight difference in their calculation when viewing the write node only. Bizarre. Serves me right for working on a Saturday. -ak On Sat, Sep 24, 2011 at 1:06 PM, Anthony Kramer anthony.kra...@gmail.com anthony.kra...@gmail.com wrote: So I have a fairly simple comp here and at the end when it goes to the write node, all of a sudden I get negative values. Take a look at the screen caps below and let me know if you seen anything like this. If I switch the write node to dpx/Cineon the problem goes away. If I switch to exr/Cineon the problem stays so it seems to be something with the filetype being exr, not the colorspace. -ak image.png ___ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.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] support returning mails with attachment
Hey, I cannot attach zips to mails send to support. I get a returned email: 582 The file attached violates our email policy Is it just me or did they (accidently) change their policy? Sebastian -- Sebastian Elsner - Pipeline TD - r i s e | fx t: +49 30 201 803 00 sebast...@risefx.com c: +49 175 336 5739 7548 www.risefx.com r i s e | fx GmbH Schlesische Strasse 28, Aufgang B 10997 Berlin Richard-Byrd-Strasse 12, 50829 Cologne Geschaeftsfuehrer: Sven Pannicke, Robert Pinnow Handelsregister Berlin HRB 106667 B ___ 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: I got a weird one here guys....
32 bit Floating Point EXR permits negative values. Sounds like you are getting these values from your comp and EXR is not clipping those values. -Mason On Sep 26, 2011, at 4:24 PM, Anthony Kramer anthony.kra...@gmail.com wrote: Sorry, yes, I should have mentioned that. When I write out the exr and read it back, it still has the errors I see when just viewing the write node. -ak On Sat, Sep 24, 2011 at 4:22 PM, Sean Looper sloo...@imageworks.com wrote: The Write node passthrough does make certain assumptions when your output is exr. Try writing the file out and compare the written frames to your last node. -sean Sent from my cellular device On Sep 24, 2011, at 2:16 PM, Anthony Kramer anthony.kra...@gmail.com wrote: NukeX 6.3v2 Windows 7 On Sat, Sep 24, 2011 at 2:11 PM, Anthony Kramer anthony.kra...@gmail.com wrote: It gets worse.. Seems like it's also calculating a few other key operations in my comp differently when selecting EXR as the output format in a write. Besides the neg values below which seem to be coming from a grade, it also makes my Zblur and LensDistortion look different. If I disable those 3 nodes, I get no difference between the last node and the write. If I enable ANY ONE of those nodes I get a slight difference in their calculation when viewing the write node only. Bizarre. Serves me right for working on a Saturday. -ak On Sat, Sep 24, 2011 at 1:06 PM, Anthony Kramer anthony.kra...@gmail.com wrote: So I have a fairly simple comp here and at the end when it goes to the write node, all of a sudden I get negative values. Take a look at the screen caps below and let me know if you seen anything like this. If I switch the write node to dpx/Cineon the problem goes away. If I switch to exr/Cineon the problem stays so it seems to be something with the filetype being exr, not the colorspace. -ak image.png ___ 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] Re: I got a weird one here guys....
Its not that the neg values are being retained by the write node, its that the negative values APPEAR when viewing the write node. This morning I open up the same comp and the issues were gone for about an hour, and then they came back. Deleted the viewer node, and it went away again. I'm pretty sure this is a bug of some sort but unfortunately I cant consistently reproduce it at this point. I'll keep you all posted. -ak On Mon, Sep 26, 2011 at 10:47 AM, Mason masondo...@gmail.com wrote: 32 bit Floating Point EXR permits negative values. Sounds like you are getting these values from your comp and EXR is not clipping those values. -Mason On Sep 26, 2011, at 4:24 PM, Anthony Kramer anthony.kra...@gmail.com wrote: Sorry, yes, I should have mentioned that. When I write out the exr and read it back, it still has the errors I see when just viewing the write node. -ak On Sat, Sep 24, 2011 at 4:22 PM, Sean Looper sloo...@imageworks.com sloo...@imageworks.com wrote: The Write node passthrough does make certain assumptions when your output is exr. Try writing the file out and compare the written frames to your last node. -sean Sent from my cellular device On Sep 24, 2011, at 2:16 PM, Anthony Kramer anthony.kra...@gmail.com anthony.kra...@gmail.com wrote: NukeX 6.3v2 Windows 7 On Sat, Sep 24, 2011 at 2:11 PM, Anthony Kramer anthony.kra...@gmail.comanthony.kra...@gmail.com anthony.kra...@gmail.com wrote: It gets worse.. Seems like it's also calculating a few other key operations in my comp differently when selecting EXR as the output format in a write. Besides the neg values below which seem to be coming from a grade, it also makes my Zblur and LensDistortion look different. If I disable those 3 nodes, I get no difference between the last node and the write. If I enable ANY ONE of those nodes I get a slight difference in their calculation when viewing the write node only. Bizarre. Serves me right for working on a Saturday. -ak On Sat, Sep 24, 2011 at 1:06 PM, Anthony Kramer anthony.kra...@gmail.comanthony.kra...@gmail.com anthony.kra...@gmail.com wrote: So I have a fairly simple comp here and at the end when it goes to the write node, all of a sudden I get negative values. Take a look at the screen caps below and let me know if you seen anything like this. If I switch the write node to dpx/Cineon the problem goes away. If I switch to exr/Cineon the problem stays so it seems to be something with the filetype being exr, not the colorspace. -ak image.png ___ Nuke-users mailing list Nuke-users@support.thefoundry.co.ukNuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://forums.thefoundry.co.uk/ http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users ___ Nuke-users mailing list Nuke-users@support.thefoundry.co.ukNuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 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://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] automatio shuffleCopy
hello everyone, I am trying to create an auto ShuffleCopy python script. I wonder if there is a way to check what channels have information and what not. For example, if one read node has only the red channel I want the shuffleCopy to create automatically that new channel and not the blue or greenany help will help! ___ 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] Crashes with Alexa footage - retiming - view Meta Data
You encountered old bug in Nuke. When you fetch metadata from movie format readers (mov, avi, ffmpeg, r3d) Nuke from time to time (quite often) gives black frame, colorfull noise or shows error messages. In older versions of Nuke and movReader when this error occurs Nuke shows unhandled pixel format error. But in recent versions (6.2 and 6.3) this error causes Nuke to crash imediately, without any message. There isn't any workaround of this problem. There is only Gold Rule of old nukers: never use movie formats directly in Nuke unless you really know what you are doing Best Adrian W dniu 2011-09-26 13:24:43 użytkownik MonkeyBwoy nuke-users-re...@thefoundry.co.uk napisał: -- Hi, I'm doing a comp with a couple of Alexa shots and need to conform the different clips to the same time. I'm using the Retime-Node to do that and attach a ViewMetaData-Node to check the timecode. That works fine in general, but when scrubbing through the footage to get the right timecode, Nuke crashes all the time. Is there any better way to deal with that? What might be the weak part in this workflow? The retime node? The MetaData node? I'm on Nuke 6.3v4 Thank you! ___ 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: I got a weird one here guys....
This sounds like a cache issue more than anything elsehave you tried emptying the cache and the buffer? Do you still get the same thing? If you change the viewer lut do you still get it or does it go away until you go back to the last used lut? On Sep 26, 2011 11:28 AM, Anthony Kramer anthony.kra...@gmail.com wrote: Its not that the neg values are being retained by the write node, its that the negative values APPEAR when viewing the write node. This morning I open up the same comp and the issues were gone for about an hour, and then they came back. Deleted the viewer node, and it went away again. I'm pretty sure this is a bug of some sort but unfortunately I cant consistently reproduce it at this point. I'll keep you all posted. -ak On Mon, Sep 26, 2011 at 10:47 AM, Mason masondo...@gmail.com wrote: 32 bit Floating Point EXR permits negative values. Sounds like you are getting these values from your comp and EXR is not clipping those values. -Mason On Sep 26, 2011, at 4:24 PM, Anthony Kramer anthony.kra...@gmail.com wrote: Sorry, yes, I should have mentioned that. When I write out the exr and read it back, it still has the errors I see when just viewing the write node. -ak On Sat, Sep 24, 2011 at 4:22 PM, Sean Looper sloo...@imageworks.com sloo...@imageworks.com wrote: The Write node passthrough does make certain assumptions when your output is exr. Try writing the file out and compare the written frames to your last node. -sean Sent from my cellular device On Sep 24, 2011, at 2:16 PM, Anthony Kramer anthony.kra...@gmail.com anthony.kra...@gmail.com wrote: NukeX 6.3v2 Windows 7 On Sat, Sep 24, 2011 at 2:11 PM, Anthony Kramer anthony.kra...@gmail.comanthony.kra...@gmail.com anthony.kra...@gmail.com wrote: It gets worse.. Seems like it's also calculating a few other key operations in my comp differently when selecting EXR as the output format in a write. Besides the neg values below which seem to be coming from a grade, it also makes my Zblur and LensDistortion look different. If I disable those 3 nodes, I get no difference between the last node and the write. If I enable ANY ONE of those nodes I get a slight difference in their calculation when viewing the write node only. Bizarre. Serves me right for working on a Saturday. -ak On Sat, Sep 24, 2011 at 1:06 PM, Anthony Kramer anthony.kra...@gmail.comanthony.kra...@gmail.com anthony.kra...@gmail.com wrote: So I have a fairly simple comp here and at the end when it goes to the write node, all of a sudden I get negative values. Take a look at the screen caps below and let me know if you seen anything like this. If I switch the write node to dpx/Cineon the problem goes away. If I switch to exr/Cineon the problem stays so it seems to be something with the filetype being exr, not the colorspace. -ak image.png ___ Nuke-users mailing list Nuke-users@support.thefoundry.co.ukNuke-users@support.thefoundry.co.uk , http://forums.thefoundry.co.uk/ http://forums.thefoundry.co.uk/ http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users ___ Nuke-users mailing list Nuke-users@support.thefoundry.co.ukNuke-users@support.thefoundry.co.uk , http://forums.thefoundry.co.uk/http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 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://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] Keying Issues with Alexa
I've just had a terrible time with exactly that format - used the new denoise tool which cleaned it up well but was very very noisey to begin with - the blue channel was awful. Howard From: Nick Guth nick.g...@gmail.com To: Nuke user discussion nuke-users@support.thefoundry.co.uk Sent: Friday, 23 September 2011, 1:56 Subject: Re: [Nuke-users] Keying Issues with Alexa They were shot to AppleProRes444 (which is the Alexa native format). It's straight from the camera in a .mov file format. They were converted to DPX and are in the AlexaV3LogC colorspace in nuke. We also tried pulling the raw .mov directly into Nuke, but have the exact same result. -- Nick On Thu, Sep 22, 2011 at 5:51 PM, Deke Kincaid dekekinc...@gmail.com wrote: What file format we're they shot to and which colorspace? -deke On Thu, Sep 22, 2011 at 17:44, Nick Guth nick.g...@gmail.com wrote: Read brought in using AlexaV3LogC. Has anyone had success with keying footage shot on the Alexa? It seems to have a weird 422 look, but according to the documents it shoots 444. We brought in the raw .mov from the camera and we're still getting poor results. I attached an example of the before and after (one click key with primatte). Why is it keying the edges around highlights? Two of our shows are now shot on this camera and we're having a difficult time getting positive results from it. If this was shot on RED it wouldn't be a problem. Our work around for now is to roto everything and add selective keys to the roto for details, unfortunately TV schedules don't allow for such detailed workarounds. Any help would be appreciated. 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 ___ 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 -- Nick Guth motion . composite . design www.nickguth.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] Convolve crashing in 6.3v3
and on mac OSX Howard From: Hugo Leveille hu...@fastmail.net To: Nuke user discussion nuke-users@support.thefoundry.co.uk Sent: Friday, 23 September 2011, 3:40 Subject: Re: [Nuke-users] Convolve crashing in 6.3v3 Yep crash on linux centos and win7. I have reported it and its logged as high priority So now we have to choose between a release with a tracker with no cancel button and one with no convolve... Not to mention a non working pyqt under windows 7 (almost any signal make nuke crash) Too bad Sent from my iPhone On Sep 22, 2011, at 10:22 PM, Ben Dickson ben.dick...@rsp.com.au wrote: Yep, crashes here too (linux build), with pretty much any input except a blank format I would have hoped this sort of bug would be picked up by some do all the nodes still work/do these scripts render test-suite :( Hugo Léveillé wrote: Is it me or the convolve is not working in 6.3v3 ? See included script ___ 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 -- ben dickson 2D TD | ben.dick...@rsp.com.au rising sun pictures | www.rsp.com.au ___ 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] Keying Issues with Alexa
800 asa too, tungsten balanced (which I think will add more noise to blue). prores 4.4.4 but came out looking like 4.2.2 with so much noise I thought I was back on 16mm high asa stock. What ASA are people recommending, as low as you can go? Howard From: Howard Jones mrhowardjo...@yahoo.com To: Nuke user discussion nuke-users@support.thefoundry.co.uk Sent: Monday, 26 September 2011, 20:28 Subject: Re: [Nuke-users] Keying Issues with Alexa I've just had a terrible time with exactly that format - used the new denoise tool which cleaned it up well but was very very noisey to begin with - the blue channel was awful. Howard From: Nick Guth nick.g...@gmail.com To: Nuke user discussion nuke-users@support.thefoundry.co.uk Sent: Friday, 23 September 2011, 1:56 Subject: Re: [Nuke-users] Keying Issues with Alexa They were shot to AppleProRes444 (which is the Alexa native format). It's straight from the camera in a .mov file format. They were converted to DPX and are in the AlexaV3LogC colorspace in nuke. We also tried pulling the raw .mov directly into Nuke, but have the exact same result. -- Nick On Thu, Sep 22, 2011 at 5:51 PM, Deke Kincaid dekekinc...@gmail.com wrote: What file format we're they shot to and which colorspace? -deke On Thu, Sep 22, 2011 at 17:44, Nick Guth nick.g...@gmail.com wrote: Read brought in using AlexaV3LogC. Has anyone had success with keying footage shot on the Alexa? It seems to have a weird 422 look, but according to the documents it shoots 444. We brought in the raw .mov from the camera and we're still getting poor results. I attached an example of the before and after (one click key with primatte). Why is it keying the edges around highlights? Two of our shows are now shot on this camera and we're having a difficult time getting positive results from it. If this was shot on RED it wouldn't be a problem. Our work around for now is to roto everything and add selective keys to the roto for details, unfortunately TV schedules don't allow for such detailed workarounds. Any help would be appreciated. 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 ___ 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 -- Nick Guth motion . composite . design www.nickguth.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] Remove chromatic aberration
I have a shot with some heavy aberration that's red/cyan in color and it's affecting my key on a blue screen. Is there a way to shift the color channels and make the aberration less prominent? Thanks. Darren Coombes darren.coom...@me.com 0418 631 079___ 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] Remove chromatic aberration
If you have the full Furnace suite you can try F_ChannelRepair. If you don't have furnace, you can try translating the color channels individually through a radial grad using a transform masked node to re-align the color channels. On Mon, Sep 26, 2011 at 9:08 PM, Darren Coombes dar...@resolutiondesign.com.au wrote: I have a shot with some heavy aberration that's red/cyan in color and it's affecting my key on a blue screen. Is there a way to shift the color channels and make the aberration less prominent? Thanks. Darren Coombes darren.coom...@me.com 0418 631 079___ 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 -- John Mangia 908.616.1796 j...@johnmangia.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] Remove chromatic aberration
Sometimes I will individually lensDistort the r,g,b, channels. There isn't a channel knob on it though so you have to do them separately and remerge them. Also sometimes basic scale/transforms on individual channels will work. -deke On Mon, Sep 26, 2011 at 20:15, John Mangia j...@johnmangia.com wrote: If you have the full Furnace suite you can try F_ChannelRepair. If you don't have furnace, you can try translating the color channels individually through a radial grad using a transform masked node to re-align the color channels. On Mon, Sep 26, 2011 at 9:08 PM, Darren Coombes dar...@resolutiondesign.com.au wrote: I have a shot with some heavy aberration that's red/cyan in color and it's affecting my key on a blue screen. Is there a way to shift the color channels and make the aberration less prominent? Thanks. Darren Coombes darren.coom...@me.com 0418 631 079___ 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 -- John Mangia 908.616.1796 j...@johnmangia.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
