Can you share a screenshot of the render template and project properties? There are a lot of variables here.

@RogerS here you go:

@RogerS,
I am not really welcome in this Forum.

• Before he presented his project, I was already foreseeing: He uses this so called 32-bit floating point (video levels) which is since decades a pure render mode for Legacy 8-bit mode - both with one characteristic: They don't touch/change the color range of footage.
• Surely no VEGAS render template will follow changing the output color range under these 2 legacy modes which should be removed for a long time.
• Fundamentals about VEGAS pro, if not obtained, can be learnt/studied before man starts.
• You are a hard-working moderator; yet hard working doesn't guarantee rich harvest.

(Studio RGB must be unchecked in scopes, though the histogram scope isn't affected by this).

StudioRGB will be checked when your editing (preview window) located on a TV-display, and uncheched if it's a computer display.

The Histogram presents footage color range (or its pixel light distribution), nothing to do with scopes setting.

@Yelandkeil I think he's making changes to the footage that is breaking the 16-235 limits and seeing these screenshots would confirm that.

However VEGAS 23 does change the levels in 32 bit video mode if the extended color space conversions are active in internal preferences. So I suggest checking renders in an older version.

For this purpose studio RGB levels should be unchecked, we don't need VEGAS changing the levels we see in the scopes. The histogram isn't very precise compared to the other scopes so I recommend looking at more than one.

1. Precondition to judge is a project with right mode.
2. Again, studioRGB is a thing depending on display property, no relationship to "we don't need VEGAS changing the levels we see".
3. The color conversion format in V23 seems broken or not correct. I set it to FALSE.
4. The pure 32-bit mode has issues with its compositing gamma since versions, many discussions already; change it to 2.2 (video) level can avoid the issue.

This is 8-bit fullRange project and its render file:

The rendered file put into (the modified) 32-bit mode and edited:

And rendered out using same template, where shows problems?

@Yelandkeil Please don't delete posts as it makes it impossible to follow the thread.

Scope values are useless if we don't know if they are studio or full range. For this purpose I'd like the absolute, uncorrected values.

Now you understand what I was talking about with 32 bit video levels and the color space conversion. I also think it's broken. We don't know the settings Mindmatter is using.

Scope values are useless if we don't know if they are studio or full range.

But you know what a display you're using!!!

I feel wasting my time now...OK, I'll not delete my comments supposing I do any in future.

For scopes, VEGAS defaults to studio RGB checked even if a computer monitor is being used.

Great, thanks for not deleting comments as it makes it hard to follow the post.

My God, my Dearrrr!
Are you discussing without any logic, or just have the appetite to argue?

I say Histogram shows the pixel distribution of a footage, none to scopes settings.
And you argue "The histogram isn't very precise compared to the other scopes..."
.....

VEGAS has many defaults. Do you take them all into your heart?
e.g. the default project...

So, if people unsure whether the "StudioRGB" -- studio = TV-environment -- would be checked or not, just import a chart image and see if its max color range exceeds the 100% circle or not.
No matter what project, no matter what HW!

@Yelandkeil Both your writing and your thinking isn't very clear. I try to speak clearly and help you clarify it but you then get upset for some reason.

The histogram is a useful tool that is not affected by the studio RGB checkbox in scopes- I already wrote that above.

That's an interesting use of the vectorscope and in this case it shows that this is computer RGB image data and does not fit within a studio RGB range (as expected).

In general I'd think RGB parade or waveform is more useful for the task of seeing where image data starts and ends.

Guys, a lot of this is simply confusing to me. Blame it on my limited ( pun not intended ) understanding.
But might I remind you of one thing: whatever the reason of my issue,

the adding of the bt709 tags solved the problem on Youtube.

Sorry that's all I know. It seems not to make sense to anyone as of now.

Now, why and what the chain if errors is that makes this so, i still don't seem to grasp and the discussion here seems to indicate that so far, no one really does, either, yet.

But thanks for all your efforts to make sense of this. I hope we'll eventually find a solution, and maybe make a sticky note concerning how to handle 32bit exports for all users.

@Yelandkeil I think he's making changes to the footage that is breaking the 16-235 limits and seeing these screenshots would confirm that.

However VEGAS 23 does change the levels in 32 bit video mode if the extended color space conversions are active in internal preferences. So I suggest checking renders in an older version.

For this purpose studio RGB levels should be unchecked, we don't need VEGAS changing the levels we see in the scopes. The histogram isn't very precise compared to the other scopes so I recommend looking at more than one.

Here's the screenshot of the rendered file I uploaded after adding the bt709 tags. in V22, with studio levels unchecked in the waveform properties. V22 set to 8bit full range.

Can you set VP 22 to 8 bit video? Otherwise it's not showing us what's in the file. The bt709 tags don't matter for this.

Also the blue channel may be clipped- if the source video's blue channel is not cut off I'd revisit the entire color workflow not just for proper levels transformations but to preserve image quality.

Can you set VP 22 to 8 bit video? Otherwise it's not showing us what's in the file. The bt709 tags don't matter for this.

Also the blue channel may be clipped- if the source video's blue channel is not cut off I'd revisit the entire color workflow not just for proper levels transformations but to preserve image quality.

here you go.
That particular scene you're referring had the sky over exposed, all the highlights had already been reduced to a max.

I now tested the limited range file on different media players. Only pot player got the levels wrong, although I tried all possible settings concerning the range. It displays things either too washed out or with crushed blacks. VLC and media player were OK, although I still don`t understand why the black bars aren't true black.

Interestingly, the video players show the blacks slightly washed out, while the screenshot PNGs are displayed almost true black, in Windows 11 as well as here.

VLC / media player / POTplayer