Broadcast level issue

Roger Bansemer wrote on 1/10/2023, 1:45 PM

I've rendered a number of projects in which I've used levels, etc to eliminate clipping for broadcast and also used the "broadcast filter" so they should be good to go for broadcast. Problem is when I put this same file back into Vegas and take a look at the levels they're high as if I never rendered them with the levels corrected. What's going on. Shouldn't the rendered video reflect the correct levels when that rendered project is viewed back in Vegas?

Comments

john_dennis wrote on 1/10/2023, 4:11 PM

@Roger Bansemer

In Vegas Pro 18 and later, set Pixel Format to Legacy 8 bit (video levels) and Vegas Pro become a neutral arbiter.

Musicvid wrote on 1/10/2023, 5:29 PM

In addition to a using a Legacy Project, use the Histogram, which shows true RGB. No way to tell "how" your Waveform levels index is set.

That all said, the use of Broadcast Levels for analog IRE output is obsolete in favor of the Levels plugin for digital 709 Limited output.

Readread this explanation please, which was offered in response to your similar question six weeks ago:

https://www.vegascreativesoftware.info/us/forum/broadcast-safe-zone-not-apparent-in-final-render--138159/#ca864483

RogerS wrote on 1/10/2023, 7:13 PM

No as Vegas expands the levels back out for viewing in 8 bit full mode.

Roger Bansemer wrote on 1/11/2023, 7:59 AM

@Roger Bansemer

In Vegas Pro 18 and later, set Pixel Format to Legacy 8 bit (video levels) and Vegas Pro become a neutral arbiter.

Hi John. Thanks for keeping up with the postings on this. I'm barely getting a grasp on this. I took a break from producing shows for PBS since the pandemic but now I'm at it again and I didn't have to worry about this since I had been using Vegas17.
Now I have to deliver 13 episodes to PBS and used V20 using full 89 bit so you can see concern.

The good news is that if I drop my finished programs rendered in full 8 bit and then drop them into V17 the scopes are still correct. So unless I learn something new, I think I'm good to go. Am I right in this?

Sure appreciate your help.
Roger
 

 

RogerS wrote on 1/11/2023, 8:03 AM

VP 19 in 8 bit legacy mode is the same as VP 17 for "checking your work."

The point of 8-bit full is to take care of the level transformations for you so you are good to go.

Vincent-Brice wrote on 1/20/2023, 2:16 PM

Hi @Roger Bansemer , did you get this sussed? I tried replicating it but just couldn't, even bringing in interlaced HDV from my old Sony HVR-V1. But this led me to a question; in your screen shot, your project is interlaced but your preview is progressive, how do you get that? I just could not get the same. Just curious :)

Gigabyte Aorus Pro V2 motherboard, AMD Ryzen 9 5950X, Gigabyte AMD RX 6800XT, 64GB Corsair Vengeance 3600MHz ("Ryzen tuned", whatever that is), 500GB Corsair Force MP600 Gen 4 M.2 C:drive for windows and programs, 500GB Samsung Sata SSD EVO D:drive for video files, 1TB Samsung Sata SSD EVO E:drive for all other data, Gigabyte Aorus Waterforce 360 CPU cooler, Thermaltake Core P5 TG open case, Contour ShuttleXpress.

Windows 11 Pro 24H2, Vegas Pro 22 (Build 248)

Roger Bansemer wrote on 1/20/2023, 2:26 PM

I have no idea. This entire 8 bit thing still baffles me. I do know that at least for what I do I can edit and render in 8 bit full with V20 and then if I bring the rendered file over to Vegas 17 which doesn't have the 8 bit full but only legacy, it still reads OK which means I'm good to send the file for TV broadcast.

RogerS wrote on 1/20/2023, 7:43 PM

Vegas Pro 18 + 8-bit video (legacy) = Vegas Pro 17 8-bit mode.

In this case what you see is what you get, take a look at the scopes.

EricLNZ wrote on 1/21/2023, 1:27 AM

in your screen shot, your project is interlaced but your preview is progressive,

@Vincent-Brice Probably because the preview is only showing one field from each frame.