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
