Sorry, I should qualify that it is only limited to legal ranges in 422 modes, not 444. Though Alexa still doesn't give the option to record extended range in 444.
-deke On Friday, January 6, 2012, Deke Kincaid <[email protected]> wrote: > Prores always clips to legal range. That's why Alexa won't even let you pick extended range when recording to prores in the camera. > > -deke > > On Friday, January 6, 2012, Lewis Saunders <[email protected]> wrote: >> Adrian Baltowski wrote: >>> There is an internal bug in movReader which cause, that >>> Nuke doesn't import correctly rec709 colorspace quicktimes. >> >> Yes, this is a bit of a bummer. To be clear, when reading most >> Quicktimes, Nuke seems to use the Rec601 matrix instead of the Rec709 >> one. This causes chroma and saturation shifts compared to FCP, Smoke >> or Baselight's reading of the same files. >> >> The legal range problem is a a separate thing. In the past I've been >> able to read the full range from uncompressed Quicktimes by ticking >> the raw data box on the Read, which causes the superwhites/blacks to >> come in as over 1/below 0. This can then be graded back into place as >> Howard said above. I'm not sure if this works in current versions or >> with ProRes though. >> >> I mostly avoid Quicktimes getting anywhere near Nuke :-/ >> >> -- >> Lewis Saunders >> 8 bit .sgi all the way >> London >> _______________________________________________ >> Nuke-users mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >>
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
