Advise: Vegas Pro should add 8bit Colorspace option like Video Pro X

rock-c wrote on 7/15/2020, 6:27 AM

Magix Video Pro X: One in project setting:  Another in render setting:

 

BT.709 Colorspace is 0-235, sRGB Colorspace is 0-255.

It will solve the stubborn problem that preview too gray or render too dark which 90% Vegas users have encountered.

.

Someone say using Levels FX, SeMW Plugin, color grading panel's "Broadcast Colors" button. Everyone should know Levels FX, SeMW Plugin, "Broadcast Colors" are ridiculous manual remedial measures and it will damage still image's levels.

Because Video's level in Vegas 8 bit project will get gray than in somewhere else like potplayer, vlc player, youtube, facebook, etc. But still image's level in Vegas 8bit project will not get gray and is the same as in potplayer, vlc player, youtube, facebook, etc.

So, Levels FX, SeMW Plugin, "Broadcast Colors" button will definitely damage still image's level. And it is definitely a ridiculous manual remedial measure. Do you want to see the still image in your video looks abnormal?

Comments

fr0sty wrote on 7/15/2020, 11:49 AM

There are colorspace settings in render settings.

Last changed by fr0sty on 7/15/2020, 11:49 AM, changed a total of 1 times.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Marco. wrote on 7/15/2020, 1:43 PM

By the way - those color space options offered by Video Pro X for UHD rendering don't make sense. BT.601 and SMPTE-240M are for SD video and BT.470 is for analogue video. Also in most cases the current Y'CbCr video color spaces do not yet define the color range but still leaves options for limited or full range levels.

Afaik, these Vegas Pro render color spaces only can be used for ACES processing, not in 8 bit projects. But it's so simple to get your levels right. Watch your waveform monitor, know your goal, adopt an output level FX (or use the SeMW Preview Levels render option).

Musicvid wrote on 7/15/2020, 1:50 PM

In nineteen years, I have never had a reason to change the colorspace, in or out, in Vegas. It is not a discretionary user control.

rock-c wrote on 7/15/2020, 4:51 PM

From youtube, 90% Vegas users encountered the stubborn problem that preview too gray or render too dark. So it is urgent to add Colorspace options for project setting, AVC, HEVC, etc.

Other professional NLEs solve it well like Magix Video Pro X's colorspace options. Vegas should add these options to resolve 90% Vegas users' stubborn problem.

Marco. wrote on 7/15/2020, 6:07 PM

That YouTube issue has zero to do with color spaces but is a matter of color ranges as mentioned before. It's the difference between limited range and full range and all you need is a proper use of the Levels FX. You could also use an FFmpeg color range patch instead. No need to touch the color space.

And once again, the color range render options of Video Pro X you showed above are not professional at all but lack any sense. Not a good example.

rock-c wrote on 7/15/2020, 7:16 PM

a proper use of the Levels FX

@Marco. You need to understand Levels FX can't resolve the problem. Levels FX will broke still image's level. And Levels FX is a ridiculous manual remedial measure.

zero to do with color spaces but is a matter of color ranges as mentioned before

You need to understand BT.709 Colorspace is 0-235, sRGB Colorspace is 0-255.

Both BT.709 and sRGB Colorspace are included in Magix Video Pro X's 8bit Project setting. Please face the reality, don't cheat yourself any more. Don't impede Vegas Pro to improve.

john_dennis wrote on 7/15/2020, 7:50 PM

@rock-c

Do you have any idea who you're talking to? Apologize publicly and move on.

Graeme-Kritzinger wrote on 7/15/2020, 8:09 PM

Try using the broadcast colours tab under the color grading panel or by adding the plugin chain as a layer effect to resolve this issue with dark rendering, also be certain of your target audience and what device type will be most used for viewing. Make sure IRE function is selected. As a general starting point i find Lenient 7.5 IRE as a good starting point. Also make sure your main control and external monitors are set to the same colour space to avoid conflicting visual info prior to rendering.

Chief24 wrote on 7/15/2020, 8:14 PM

+10! @john_dennis

Thank you! You definitely said it much more eloquently than I would have.

Self Build: #1 MSI TRX40 Pro Wi-Fi w/3960X (be Quiet! Dark Rock Pro TR4) @ stock; 128GB Team Group 3200 MHz; OS/Apps - WDSN850X PCI-e 4.0x4 4TB, Documents/Extras - WDSN850X PCI-e 4.0x4 4TB; XFX AMD Radeon 7900XTX (24.12.1); Samsung 32 Inch UHD 3840x2160; Windows 11 Pro 64-Bit (24H2 26100.2894); (2) Inland Performance 2TB/(2) PNY 3040 4TB PCI-e on Asus Quad M.2x16; (2) WD RED 4TB; ProGrade USB CFExpress/SD card Reader; LG 16X Blu-Ray Burner; 32 inch Samsung UHD 3840x2160.

VEGAS Pro 20 Edit (411); VEGAS Pro 21 Suite (315); VEGAS Pro 22 Suite (239) & HOS (Happy Otter Scripts); DVD Architect 7.0 (100);

Sound Forge Audio Studio 15; ACID Music Studio 11; SonicFire Pro 6.6.9 (with Vegas Pro/Movie Studio Plug-in); DaVinci Resolve (Free) 19.1.3

#2: Gigabyte TRX50 Aero D w/7960x (Noctua NH-U14S TR5-SP6) @ stock; 128GB Kingston Fury Beast RDIMM @4800 MHz; OS/Apps - Seagate Firecuda 540 2TB PCI-e 5.0x4; Documents/Extras/Source/Transcodes - 4TB WDSN850X PCI-e 4.0x4; 4TB Inland Performance PCI-e 3.0x4; 2TB Inland Performance PCI-e 4.0x4; BlackMagic PCI-e Decklink 4K Mini-Recorder; ProGrade USB SD & Micro SD card readers; LG 32 Inch UHD 3840.x2160: PowerColor Hellhound RX Radeon 7900XT (24.12.1); Windows 11 Pro 64-Bit (24H2 26100.2894)

VEGAS Pro 20 Edit (411); VEGAS Pro 21 Suite (315); VEGAS Pro 22 Suite (239) & HOS; DVD Architect 7.0 (100); Sound Forge Audo Studio 15; Acid Music Studio 11

Canon EOS R6 MkII, Canon EOS R6, Canon EOS R7 (All three set for 4K 24/30/60 Cinema Gamut/CLog3); GoPro Hero 5+ & 6 Black & (2) 7 Black & 9 Black & 10 Black & 11 Black & 12 Black (All set at highest settings - 4K, 5K, & 5.3K mostly at 29.970); Sony FDR AX-53 HandyCam (4K 100Mbps XAVC-S 23.976/29.970)

adis-a3097 wrote on 7/15/2020, 8:16 PM

From youtube, 90% Vegas users encountered the stubborn problem that preview too gray or render too dark. So it is urgent to add Colorspace options for project setting, AVC, HEVC, etc.

Other professional NLEs solve it well like Magix Video Pro X's colorspace options. Vegas should add these options to resolve 90% Vegas users' stubborn problem.

Well, 100% of that 90% should do their homework first.

Former user wrote on 7/15/2020, 8:42 PM

 

Other professional NLEs solve it well like Magix Video Pro X's colorspace options. Vegas should add these options to resolve 90% Vegas users' stubborn problem.

Well, 100% of that 90% should do their homework first.

I disagree. I think non technical people should be protected due to ignorance, and the big commercial editors do that. In 2016 when the only displays I had was 1 cheap computer monitor and 1 cheap android phone I had a moderately successful non commercial YT channel. 1.5 million views, and every video I uploaded was in full color space. And I knew they looked too contrasty when looking at the youtube videos, but for some reason they looked better on my cheap phone, so I had decided through failed logic somehow my monitor viewing YT was to blame and actually everyone else was seeing it properly. I trusted my scopes, I knew exposure was fine within vegas, but because I did not understand the intricacies of color space I ruined a year's worth of videos

I can't even look at those videos today, If I was using Premiere Pro, or Video Pro X or most NLE's I wouldn't have messed up like that. Also some of the most gifted artistic people are the least technical, different brain types, by saying you must be engineer technical to use vegas limits creativity

 

Musicvid wrote on 7/15/2020, 9:15 PM

 

That YouTube issue has zero to do with color spaces but is a matter of color ranges as mentioned before. It's the difference between limited range and full range and all you need is a proper use of the Levels FX. You could also use an FFmpeg color range patch instead. No need to touch the color space.

And once again, the color range render options of Video Pro X you showed above are not professional at all but lack any sense. Not a good example.

I erased my comment because it has already been said better by Marco. See emphasis added above.

@rock-c

Do you have any idea who you're talking to? Apologize publicly and move on.

There seems to be quite a lot of that lately. It's like telling Ferrari to change out the engine before learning to drive.

adis-a3097 wrote on 7/15/2020, 9:28 PM

 

Other professional NLEs solve it well like Magix Video Pro X's colorspace options. Vegas should add these options to resolve 90% Vegas users' stubborn problem.

Well, 100% of that 90% should do their homework first.

I disagree. I think non technical people should be protected due to ignorance, and the big commercial editors do that. In 2016 when the only displays I had was 1 cheap computer monitor and 1 cheap android phone I had a moderately successful non commercial YT channel. 1.5 million views, and every video I uploaded was in full color space. And I knew they looked too contrasty when looking at the youtube videos, but for some reason they looked better on my cheap phone, so I had decided through failed logic somehow my monitor viewing YT was to blame and actually everyone else was seeing it properly. I trusted my scopes, I knew exposure was fine within vegas, but because I did not understand the intricacies of color space I ruined a year's worth of videos

I can't even look at those videos today, If I was using Premiere Pro, or Video Pro X or most NLE's I wouldn't have messed up like that. Also some of the most gifted artistic people are the least technical, different brain types, by saying you must be engineer technical to use vegas limits creativity

 

Well, I too disagree; I think that non technical people should be punished instead of being protected for the same reason. Which, actually, they are by their own displeasance while looking at their work.

Call it instant karma if you will... :)

fr0sty wrote on 7/15/2020, 11:16 PM

I too can't stand it when a NLE tries to hold my hand too much, FCP is really bad about that, being too preset-based and not giving enough customization for people that actually know what they are doing.

VEGAS has 2 different ways to fix the issue you mention in a matter of clicks...

Method 1: Apply levels FX onto the master output FX, select studio levels. Select Computer RGB to Studio RGB.

Method 2: Use the SeMW Plugin

Method 3: Press the "Broadcast Colors" button on the color grading panel.

Who knows what other options may come in the future to make this process even easier, but for now we have plenty of very quick and easy methods to solve this issue.

Musicvid wrote on 7/15/2020, 11:22 PM

Problem with Broadcast Colors is they are analog voltage based, and chroma is allowed to slop outside the defined digital delivery range. Some major broadcasters (e.g., PBS) are very picky about this.

rock-c wrote on 7/16/2020, 12:55 AM

From youtube, 90% Vegas users encountered the stubborn problem that preview too gray or render too dark. So it is urgent to add Colorspace options for project setting, AVC, HEVC, etc.

Other professional NLEs solve it well like Magix Video Pro X's colorspace options. Vegas should add these options to resolve 90% Vegas users' stubborn problem.

Well, 100% of that 90% should do their homework first.

@adis-a3097 They would rather spent time on video creation design. Rather than spent time in curing a ridiculous bug only in Vegas Pro, not in other Video software. They have paid for Vegas Pro, should not suffer such a ridiculous stupid bug. Their money is also earned by their hardworking, it shouldn't suffer a tease.

fr0sty wrote on 7/16/2020, 1:42 AM

It isn't a bug, it's a feature for those who know how to use it properly. For those that don't, use the workaround I suggested until the team can come up with a more elegant solution.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

RogerS wrote on 7/16/2020, 5:06 AM

Problem with Broadcast Colors is they are analog voltage based, and chroma is allowed to slop outside the defined digital delivery range. Some major broadcasters (e.g., PBS) are very picky about this.

Interesting. Is there a preferred way to address this in Vegas if Broadcast Colors doesn't work well for digital broadcast?

@rock-c As frosty said, this isn't a bug, but I agree with you that users should have an automatic option where the software reads the metadata for video files and still images. Editing is complex enough for new editors. Vegas could know what is video vs full range. However, since we don't have that, you have to do it by hand.

(To your previous comment- if your video is video range and still images are on their own track, use a levels preset (computer to video levels) to get the photos into video range so they will look correct when you use SEMW to preview the proper levels. In this scenario you don't have to do anything upon render as it's all video levels.)

adis-a3097 wrote on 7/16/2020, 7:29 AM

From youtube, 90% Vegas users encountered the stubborn problem that preview too gray or render too dark. So it is urgent to add Colorspace options for project setting, AVC, HEVC, etc.

Other professional NLEs solve it well like Magix Video Pro X's colorspace options. Vegas should add these options to resolve 90% Vegas users' stubborn problem.

Well, 100% of that 90% should do their homework first.

@adis-a3097 They would rather spent time on video creation design. Rather than spent time in curing a ridiculous bug only in Vegas Pro, not in other Video software. They have paid for Vegas Pro, should not suffer such a ridiculous stupid bug. Their money is also earned by their hardworking, it shouldn't suffer a tease.

You don't say? 😂

How come everybody wants to be a great writer but nobody wants to spend time learning letters first? Eh?

Here's a personal question: Who did your homework? Was it mommy? Aunt Mary? The invisible man? Who did it, rocky? 😜

Dexcon wrote on 7/16/2020, 8:14 AM

Nothing in the world is perfect. And that includes Vegas Pro. There are workarounds and alternative methods of addressing so many problems and procedures in so many products on the world stage. The suggestions offered earlier by @fr0sty are valid and reasonable suggestions. They really are not hard to do - they are easy-peasy - and these are what I have done for years, and I do not find myself getting in to a lather over them. Why do some on the forum bog themselves down in trifling negatives? Yes, there might be a slightly better way of doing something from an individual's point-of-view, but for heavens sake please keep it in perspective. The OP seems to have enough time on his/her hands to trawl the internet in order to find all and any VP negatives rather than concentrate on his/her NLE work and then complain about the time it takes to do a simple workaround in VP.

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

Musicvid wrote on 7/16/2020, 8:51 AM

@rock-c

This was written years ago, and just for you, it would seem. I tried to keep it interesting enough for you to keep your eyes open. When that happens, so does learning. Even to the reluctant. There will be a quiz.

https://www.vegascreativesoftware.info/us/forum/pc-to-tv-levels-a-comedy-of-errors--107325/

 

Dexcon wrote on 7/16/2020, 8:56 AM

@Musicvid ... OMG ... I remember that post. Cheers.

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

Musicvid wrote on 7/16/2020, 9:13 AM

And here's a little zipped project that solves all of Mr. Rock's issues on the fly, visually. It works in both Pro and Movie Studio.

Credits: It was written in concert with ideas from both @Marco. and @john_dennis. Imagine two Engineers and a Teacher agreeing on something!

https://www.vegascreativesoftware.info/us/forum/new-free-video-levels-tool-for-ms-platinum--120709/

john-brown wrote on 7/17/2020, 10:32 AM

@rock-c

All is not so simple or obvious with VPX as you imply. This was discussed intensively for VPX11 here. I see that you must have VPX12 which just came out, as your screen shots are not the same as what I have in VPX11. On the export side, it looks like its missing BT.2020.

After all of that (the linked thread) and reading through the various links here several times, this is all still a mystery to me.

 

Vegas Pro 18 Edit, Vegas Movie Studio 16 Platinum, Magix Video Pro X16, Magix Movie Studio Platinum 2024, Xara Designer Pro X19, Samplitude Pro X8 Suite, Music Maker 2025 Premium, SF Audio Cleaning Lab 4, Sound Forge Pro 16 and more.