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.