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
...@support.thefoundry.co.uk] On Behalf Of James
Etherington
Sent: 27 September 2011 12:23
To: Nuke user discussion
Subject: Re: [Nuke-users] Keying Issues with Alexa
Neat still gives better results for me. The new Denoise is generally
pretty good but makes it look a bit like shakes median
@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
: 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
Hey Randy,
No worries! When I can get some better quality Alexa footage that I can post
up here I'll definitely do that! Maybe once the shows airs I can put a few
frames up.
Cheers.
--
Nick
___
Nuke-users mailing list
Nick not to be a thorn but to completely agree with John Mangia. This isn't
bad footage to key.Don't you have a comp sup there that can help you
understand how to use the Nuke Keyers? If you would like to send me one frame
in the next hour or a portion of a frame maybe I can do a quick
I only click send once I promise. Did that really just show up on the list
9 times?
Randy S. Little
http://www.rslittle.com http://reel.rslittle.com
On Fri, Sep 23, 2011 at 12:08, randy Little randyslit...@gmail.com wrote:
Nick not to be a thorn but to completely agree with John Mangia.
I'm actually keying your PNG files and I do get some good result.
I do use both IBK and Keylight. of course the center area of the greenscreen
has loads of grain but you can actually remove it with a garbage mask,
however I dont know whether in your footage your actors are moving that
much,
Yeah they move all over the place. For now I'm using Primatte as my main
fill matte, eroding it down a bit to create a decent core. Merging that with
a soft edge key, and then applying a luma keymix for some of the details.
Filling in the rest of the holes with selective roto's. Unfortunately, it
That one click looks pretty normal to me. Nothing that weird at all. It
does look like you are clicking the first click with primatte in the wrong
spot. the first color selection with primatte is very key to its success
as it defines the middle of the polyhedron used to isolate the rest of
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
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
21 matches
Mail list logo
