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
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,
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
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
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
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.
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
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
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
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
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/
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...
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
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
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
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
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
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/
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
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
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
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
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
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
24 matches
Mail list logo
