Colours oversaturated after rendering (Studio RGB to Computer RGB)?

Milosz-Nasadowski wrote on 4/21/2022, 4:32 AM

I use some JPGs or PNGs for educational children's videos. After some time I noticed that often the videos are very oversaturated.

I posted this problem before when I used Movie Studio and then noticing that the recent Vegas Pro version saved OK I bought the pro version. Now when I am back to working on videos again the problem is still there! Previously someone advised it is something to do with Studio RGB to Computer RGB conversion and yes the simulation of the FX looks the same so it is probably the problem. But to be honest I am only interested in how to fix it in Vegas? What mixture of media or colour modes is causing it. Why Vegas is not representing colours as they should be. Please help. Screenshot below comparing the input and output result.

 

Comments

Dexcon wrote on 4/21/2022, 5:35 AM

When using VEGAS Levels 'Studio RGB to Computer RGB' in Vegas Pro 17 or earlier (usually at the Project FX level), the Levels FX needs to be disabled before rendering.

Fortunately, Vegas 18 and 19 no longer need to use VEGAS Levels - rendered colors now match the color grading on Vegas Pro 18/19's timeline. If you are using VEGAS Levels 'Studio RGB to Computer RGB' in Vegas Pro 18 or 19, that is likely causing the problem that you are encountering.

With the release of Vegas Pro 18, the recommendation has been to select '8-bit (full range)' as the Pixel Format in Project Properties. Maybe the Levels approach is needed if 'Legacy 8-bit (video levels)' is selected - I'm not really sure as I went straight away for full-range when I got Vegas Pro 18.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

Milosz-Nasadowski wrote on 4/21/2022, 7:23 AM

Wow! You are my saviour! ;-) Yes, I must have been just reopening old files in new Vegas versions and it kept the limited legacy 8bit format. After manual drag and drop copying to a different file or changing the setting in Project properties everything renders normal. Thank you very much!

Musicvid wrote on 4/21/2022, 10:36 AM

In the most basic project (legacy 8 bit), it is just the opposite. Your stills are Full Range RGB Unmanaged in Vegas, so you should use the Computer->Studio RGB fx.