Broadcast Safe - V22 vs V17

Roger Bansemer wrote on 4/13/2025, 6:55 PM

Here's a screen shot of a clip rendered in MXF format in V22 with the "Broadcast Color" filter applied to the master bus in order to bring the levels to broadcast safe. That clip was rendered in V22 and it looks fine on the scopes before rendering. However when I take that rendered clip and place it back on the V22 timeline (with broadcast color unchecked) the levels are hot.

Now when I take that same exact rendered clip (pictured on the right side of the screen) and put it into V17 and it reads OK. So.... I'm getting two different reads on the same exact clip.

I'm in a crunch here and need to know what is going on and how to fix this. Which waveform is actually telling me the truth.
My project properties are "pixal format-legacy 8bit on both V17 and V22.
I'd sure appreciate some answers. Thanks very much.
Roger

Back to post

Comments

Roger Bansemer wrote on 4/15/2025, 11:24 AM

I think you can say that all substantive image data is below 100% with only luma noise above it as far as you can tell. Could they review it again? You can push everything down further but it might affect how the highlights look.

Great phrasing. I'll use it when I talk with them. Thanks.

john_dennis wrote on 4/15/2025, 11:44 AM

@Roger Bansemer

Open a new Vegas Pro project and set the pixel Format to 8-bit Full Range.
Drag your finished project (project.veg) file to the timeline of the newly opened project.
Don't add any fX to the newly created master project.
Render to your delivery template.
Report

I got decent results with this method...

Roger Bansemer wrote on 4/15/2025, 12:09 PM

Tried that before. Tried it again just now and it makes it worse. I'm about to call them and discuss it. Wish me luck.
Here's the full 8 bit render.

Roger Bansemer wrote on 4/15/2025, 1:07 PM

I just spoke with the people at NETA and discussed the broadcast safe issue with them. Since I've done so many shows in the past, they told me they would take care of the issue so I wouldn't have to be concerned about it anymore for at least this season of shows which is very, very kind of them.
I bet I've spent a dozen or more hours fussing with this and I sure appreciate all the feedback I've gotten from Roger and John. Thank you so very much. I'd still like to know what I might have done to fix it on my end but for now I'm burned out and glad to know NETA is giving me this grace period to let me off the hook. It does seem crazy that no matter what manipulation or filters is put on the file, it always ends up with a few pieces above the 100 mark.
Enough for now. Thanks again. The forum is the best!
Roger