This may be due to the use of ffmpeg. At a previous company it was necessary for me to modify the ffmpeg lib to use rec709 primaries instead of rec601 to get accurate color Quicktimes. It was a real bear to find the responsible code...
Ignore me if ffmpeg is not involved in this case… -jonathan > 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
