both calibrate and profile your monitors, but it seems rare enough anyone calibrates the monitor these days. Which is why most users and ALL Mac users should set the preferences option for Display Color Management to 'on'. So do not rely on your camera's screen image as "correct" for anything. On-set, they'll have an expensive and hignly calibrated monitor to check image values, not the camera screen. NO camera has an accurate screen, not even the Red, Arri, & Sony rigs above $70,000. Premiere is set to follow the standards rather tightly. So it works perfectly as long as the standards are followed all the way through from camera to monitor. And RGB media is also displayed at 0-255 even though encoded as 0-255. In a properly setup system, YUV Rec.709 media is displayed at 0-255 even though encoded 16-235. It doesn't give you one iota more dynamic range, as that only controls how the data is encoded to the file, not the range of date recorded. So the vast majority of cameras record their Rec.709 as YUV (technically Y/Cb-Cr) files.īut there are a few cameras that allow users to set 'full' range on shooting Rec.709 even though they only produce YUV media. all Rec.709 video is set by standards to be encoded to 'limited' range code values, unless it's the full RGB 4:4:4:4 12 bit stuff. Are you using a C-log form? That would be useful data.Īs. Have you set either your camera, your monitor's settings or the Nvidia control panel settings to assume all Rec.709 is full range rather than limited? Which is wrong, but so confusing a lot of people do.Īnd the IPB Light is the file compression setting, not the codec. Please help me resolve this before I lose my sanity! I can confirm the footage format is not the problem, as I experience this even with the proxy files I generate. The sample shot above was captured with the Canon R6 using the IPB Light Codec in 4K at 23.976 FPS. 1 Correct answer Kamae Community Beginner, Maybe interesting for others facing the same problem, I solved it by adding the following line to the file C:\ProgramData\Adobe\Premiere Elements\20.0\Online\Hw Acc Render\AllLang\HW\Files\allowlistedcards. I have also tried using the most recent version of the NVIDIA Game Ready Driver (526.47) and several earlier versions. Graphics Driver: NVIDIA Studio Driver 522.30 This problem also used to occur with Premiere CC 22.0 (all version updates). Specifications of machine and all other details below: Mercury Software Engine simply isn't a reasonable solution for me, so I'd appreciate any assistance I can get with this issue. and here's what I see in the program monitor when I'm using CUDA GPU Acceleration :Īs you can see, my black levels are completely incorrect, making it impossible for me to color grade with CUDA GPU Acceleration turned on. These colors also accurately reflect what I see when viewing the original video clip outside of Premiere: These colors are correct, and accurately reflect what I see in-camera. Here's what I see in the program monitor when I'm using the Mercury Software Engine. My colors are wrong when I use CUDA GPU Acceleration, but not when I use the Mercury Software Engine. I'm desperate for a solution to this problem.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |