[Nuke-users] Stereoscopic Viewer
Hi Guys, I've found a lot about this topic in here but noch exactly an answer to my question. So I planned on working on an stereoscopic Project an I want to use the stereoscopic viewer, but not in analglyph mode. So I figured, I would use passive polarized glasses for this, mainly because of the price. So my question is, which hardware do in need for this? I read a lot about Quadro-Cards for the Quad-Buffered GL. So I probably need one?! And a 3D-Monitor? Any good adviced? I read a lot about Zalman and iZ3D-Monitors, but don't really know what I need. So I would appreciate any help on this topic, I'm pretty new to this stuff. :) ___ 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] Convolve crashing in 6.3v3
Is it me or the convolve is not working in 6.3v3 ? See included script -- Hugo Léveillé TD Compositing, Vision Globale hu...@fastmail.net convolve.nk Description: Binary data ___ 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] Stereoscopic Viewer
If you already have a quadro card and a monitor that does 120hz(which is most lcd monitors these days). Then you only need to buy the nvidia 3d kit which is just shutter glasses and a usb transmitter. Nuke will add an opengl stereo option to your stereo modes. [image: 20110922-f58pgrx7yaeaf6i1waii85a3u.jpg] -deke On Thu, Sep 22, 2011 at 07:56, Dome nuke-users-re...@thefoundry.co.ukwrote: ** Hi Guys, I've found a lot about this topic in here but noch exactly an answer to my question. So I planned on working on an stereoscopic Project an I want to use the stereoscopic viewer, but not in analglyph mode. So I figured, I would use passive polarized glasses for this, mainly because of the price. So my question is, which hardware do in need for this? I read a lot about Quadro-Cards for the Quad-Buffered GL. So I probably need one?! And a 3D-Monitor? Any good adviced? I read a lot about Zalman and iZ3D-Monitors, but don't really know what I need. So I would appreciate any help on this topic, I'm pretty new to this stuff. [image: Smile] ___ 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] Stereoscopic Viewer
Am 9/22/11 4:56 PM, schrieb Dome: So my question is, which hardware do in need for this? Hey we used the Zalman 24 screens and one JVC 40 (I think). The Zalmans are really cheap therefore the light distribution is not that good and colors are delicate too. You cant really watch s3d in fullscreen, because the angle in which the polarization between L/R works is so narrow that it almost does not work over the whole surface of the screen. Except you take a step back and change your distance from the screen aswell. But I always made the images smaller on the Zalman so I would use a about 2/3 of the screen and have a black border around the image. The Zalman has a resolution of 1920x1080 which means you have 540 lines horizontally for each eye. In case you want to work on higher resolutions and want to see the material 1:1 you have to zoom in. I think it is a good tool to spot errors, you get a nice idea of the s3d and you see quite fast if there is something wrong between L/R The polarized glasses are lightweight and the screen is circular polarized so all realD glasses are working with the Zalman. More than 3 people cant use the screen contemporarelly because of the narrow viewing angle. I am not sure if you need a quadro for nuke with the zalman. I would say no because interlacing the images is not that big of a deal. Technically the quad buffered GL makes sense for dual projector systems. So the images get synced in the quad buffer, so each projector is displaying the images at the same time. On one screen however this is not necessary. We used nvidia 560 cards with the zalman but our main comp program was fusion. and there you can tell the viewer to display a side by side image interlaced... Does that work in nuke too ? Hope that hepls a bit. johannes ___ 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] Stereoscopic Viewer
On passive displays: The only passive dislpays I have used are the Zalman and the LG D2342. I much prefer the LG. With both these passive displays (and I would assume all of them) there is a sweet spot where there is the least amount of ghosting when your eyes are most perpendicular to the screen. In my experience, the LG has a much larger tolerance on how close you get to the sweet spot. I found myself constantly bobbing my head on the Zalman to find that perfect spot, where as on the LG, I don't have to strain my neck so much. Both work fine in nuke but since they are passive displays and every other line on the display is polarized for each eye, you only get every other line of resolution in each eye when viewing stereo. With an active display, you will get full res on both eyes. Just something to be aware of. -ak On Thu, Sep 22, 2011 at 7:56 AM, Dome nuke-users-re...@thefoundry.co.ukwrote: ** Hi Guys, I've found a lot about this topic in here but noch exactly an answer to my question. So I planned on working on an stereoscopic Project an I want to use the stereoscopic viewer, but not in analglyph mode. So I figured, I would use passive polarized glasses for this, mainly because of the price. So my question is, which hardware do in need for this? I read a lot about Quadro-Cards for the Quad-Buffered GL. So I probably need one?! And a 3D-Monitor? Any good adviced? I read a lot about Zalman and iZ3D-Monitors, but don't really know what I need. So I would appreciate any help on this topic, I'm pretty new to this stuff. [image: Smile] ___ 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] CameraTracker: Theoretical Frame Limit?
How many features are you using and how many frames is the shot? -deke On Thu, Sep 22, 2011 at 15:51, Ned Wilson nedwil...@gmail.com wrote: Hello all, I'm working on camera solving a shot which is 909 frames. I started the feature track about 2 hours ago, and the solve about 1.5 hours ago. As of right now, the solve is only 63% complete. Have any of you noticed a rather severe slowdown when a certain number of frames is reached? I know that Nuke has not locked up. It is printing messages to the command shell, like: Frame: 908 points 167 triangulated 171 rejected 1 rms error = 5.26 pix Hmm. It would appear that it just finished as I was typing this... but has anyone seen these types of severe slowdowns? ___ 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] CameraTracker: Theoretical Frame Limit?
I used 300 features ( I couldn't get a solve to work with 150, the default ) and the shot is 909 frames long. On Sep 22, 2011, at 4:25 PM, Deke Kincaid wrote: How many features are you using and how many frames is the shot? -deke On Thu, Sep 22, 2011 at 15:51, Ned Wilson nedwil...@gmail.com wrote: Hello all, I'm working on camera solving a shot which is 909 frames. I started the feature track about 2 hours ago, and the solve about 1.5 hours ago. As of right now, the solve is only 63% complete. Have any of you noticed a rather severe slowdown when a certain number of frames is reached? I know that Nuke has not locked up. It is printing messages to the command shell, like: Frame: 908 points 167 triangulated 171 rejected 1 rms error = 5.26 pix Hmm. It would appear that it just finished as I was typing this... but has anyone seen these types of severe slowdowns? ___ 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
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
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
Re: [Nuke-users] Keying Issues with Alexa
The Alexa has an option to capture 422 prores, so when you said it looked 422 I thought maybe it was. -deke On Thu, Sep 22, 2011 at 17:56, Nick Guth nick.g...@gmail.com wrote: 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] Keying Issues with Alexa
Unfortunately, I'm not on set for these shoots - but I've been told they were shot 444! Hrm... ___ 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
You should be able to see what codec from the metadata in Nuke or the quicktime player info window. -deke On Thu, Sep 22, 2011 at 18:23, Nick Guth nick.g...@gmail.com wrote: Unfortunately, I'm not on set for these shoots - but I've been told they were shot 444! Hrm... ___ 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
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
Re: [Nuke-users] Keying Issues with Alexa
Check the RGB values around highlights on the affected areas to see if there is some sort of problem there. By looking at your grab on this tiny little portable screen here I would say the highlights look like blooming causing aberration. So maybe there is you problem. Cheers, Diogo On 22/09/2011, at 21: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! Screen shot 2011-09-22 at 5.37.16 PM.png Screen shot 2011-09-22 at 5.37.39 PM.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
Re: [Nuke-users] Keying Issues with Alexa
did you try the UV blur simple trick already? Did you try aligned the plates with the transforms and using the UV blur? Randy S. Little http://www.rslittle.com http://reel.rslittle.com On Thu, Sep 22, 2011 at 20:12, Diogo Girondi diogogiro...@gmail.com wrote: Check the RGB values around highlights on the affected areas to see if there is some sort of problem there. By looking at your grab on this tiny little portable screen here I would say the highlights look like blooming causing aberration. So maybe there is you problem. Cheers, Diogo On 22/09/2011, at 21: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! Screen shot 2011-09-22 at 5.37.16 PM.png Screen shot 2011-09-22 at 5.37.39 PM.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
Re: [Nuke-users] Convolve crashing in 6.3v3
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
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
Re: [Nuke-users] Keying Issues with Alexa
Can you elaborate a bit on the UV blur trick? I've never heard of that before. Thanks for the tips! ___ 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
Throw the colorspace into YCbCr, Throw down a blur with the red channel disabled (blurring only blue and green), and apply a slight blur to those channels, convert back to whatever colorspace you started with. There's no need to do this normally, it's a trick used to deal with chroma subsampling problems caused by 4:2:2 compression. On Thu, Sep 22, 2011 at 8:47 PM, Nick Guth nick.g...@gmail.com wrote: Can you elaborate a bit on the UV blur trick? I've never heard of that before. Thanks for the tips! ___ 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] Keying Issues with Alexa
convert to YCbCr with colorspace node then blur only g and b channels in a blur node set say 3-5. convert back to RGB. You can also isolate the RGB channels with shuffle and plus/screen them back together but transform the channels to try and align them better. Randy S. Little http://www.rslittle.com http://reel.rslittle.com On Thu, Sep 22, 2011 at 20:47, Nick Guth nick.g...@gmail.com wrote: Can you elaborate a bit on the UV blur trick? I've never heard of that before. Thanks for the tips! ___ 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] Re: J_Ops 1.0v1a8 available - rewritten rawReader 6.2 supp
Hello, I posted on Nukepedia, but perhaps someone here can assist: Nuke.6.2v3, Linux, J_rawReader. We can render from the interactive session, but if I try to render from the shell, I am left with an exr.tmp. Scene setup: one Read with a raw image, one Write. I'm not too familiar with the plugin, but in both cases, I know it is loaded with the other plugins. Anyone has had this problem? Still trying to figure out what might not be loaded during a batch render, whether it is the pipeline or the tool... Thanks. nico. ___ 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: J_Ops 1.0v1a8 available - rewritten rawReader 6.2 supp
Had the same problem here. On both OS X and Linux the raw reader works fine in GUI mode, but segfaults in command line mode (gdb implies it's some null pointer related crash) Didn't look into it much, I initially thought it was something to do with the files I was trying with.. but if you are having the same problem, it's likely a bug in the node itself nico wrote: Hello, I posted on Nukepedia, but perhaps someone here can assist: Nuke.6.2v3, Linux, J_rawReader. We can render from the interactive session, but if I try to render from the shell, I am left with an exr.tmp. Scene setup: one Read with a raw image, one Write. I'm not too familiar with the plugin, but in both cases, I know it is loaded with the other plugins. Anyone has had this problem? Still trying to figure out what might not be loaded during a batch render, whether it is the pipeline or the tool... Thanks. nico. ___ 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
Re: [Nuke-users] Re: J_Ops 1.0v1a8 available - rewritten rawReader 6.2 supp
Yeah, it's a bug in the recent libraw centric build. Gotta find some spare time to roll out an update with the fix in. ta Jack On 23 September 2011 04:16, Ben Dickson ben.dick...@rsp.com.au wrote: Had the same problem here. On both OS X and Linux the raw reader works fine in GUI mode, but segfaults in command line mode (gdb implies it's some null pointer related crash) Didn't look into it much, I initially thought it was something to do with the files I was trying with.. but if you are having the same problem, it's likely a bug in the node itself nico wrote: Hello, I posted on Nukepedia, but perhaps someone here can assist: Nuke.6.2v3, Linux, J_rawReader. We can render from the interactive session, but if I try to render from the shell, I am left with an exr.tmp. Scene setup: one Read with a raw image, one Write. I'm not too familiar with the plugin, but in both cases, I know it is loaded with the other plugins. Anyone has had this problem? Still trying to figure out what might not be loaded during a batch render, whether it is the pipeline or the tool... Thanks. nico. ___ 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] Re: J_Ops 1.0v1a8 available - rewritten rawReader 6.2 supp
Thanks for the update, Jack. Appreciated. ___ 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
