It's rather annoying

Don't be annoyed, be informed.

Thank you very much vKmast! I am very happy that this worked, but not impressed with the idea of having to uncheck my video output FX everytime. Do you know if there will be a fix for this? VP16? Thanks again!

There's nothing to fix. It's a feature for professionals, so they can see the full dynamic range without clipping.

Thank you very much vKmast! I am very happy that this worked, but not impressed with the idea of having to uncheck my video output FX everytime. Do you know if there will be a fix for this? VP16? Thanks again!

It is a feature but this may help you.

First, the SEMW extensions are great. I just tend to run on autopilot.

An alternative procedure, assuming camera footage that was shot at full, not limited range, is to edit and grade in native Vegas preview space, and apply the "Computer RGB -> Studio RGB" filter last in the output filter chain, just prior to rendering. This is the method I teach and use most often.

Pros:

-- Truly inclusive WYSIWYG editing, unlike many consumer NLEs.

-- Reveals the full native range of source during preview and edit.

-- Allows precision conformity to YUV production levels, such as several Cable and Broadcast TV providers request.

Cons

-- Not recommended for limited range source, such as one would download, purchase, or legally rip. Redundancies affecting actual output bit depth can occur.

-- In these cases I use the mainstream method linked above, but I get irritable if I've forgotten to take the RGB filter off before starting an overnight render.

Above All Else

Leave the stupid "Dynamic Contrast" or "Full Range PC" graphics switch left at its defaults. Reload the drivers if in doubt. The only thing you need to know is that it was not put there for editors. It just adds another whole layer of errors if you touch it ;?)

There's nothing to fix. It's a feature for professionals, so they can see the full dynamic range without clipping.

So you're saying that all other versions of Vegas that did not have to do this was used by non professionals? That makes sense to add this feature, but not allow beginners the ability to just do non professional work. Question, where can one take your course you teach?

With apologies, I believe every version of Vegas, at least in the past 18 years, has had exactly the same Preview behavior. I know that changing the preview for convenience, especially for Movie Studio users, was discussed, but not implemented as the default, as it has been in certain other editors. Unfortunately, this has been underexlained both by Sony and Magix.

Question, where can one take your course you teach?

Well, an early example of this approach was explained starting at about 04:30 in our 2011 tutorial for Movie Studio users, which although not updated since, still contains a few nuggets.

Then, if you want to dig even further into the absurdity of all of this:

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

Some other quirky stuff to be found in my signature as well..

Musicvid, any problem just slapping 16-235 levels at the final output stage? I use it while grading too of course

@wwjd, that's all I do. You know what to look for; not everyone does.

It's just bedeviling to explain why what we see isn't right. That bothers a lot of people.

First, the SEMW extensions are great. I just tend to run on autopilot.

An alternative procedure, assuming camera footage that was shot at full, not limited range, is to edit and grade in native Vegas preview space, and apply the "Computer RGB -> Studio RGB" filter last in the output filter chain, just prior to rendering. This is the method I teach and use most often.

Pros:

-- Truly inclusive WYSIWYG editing, unlike many consumer NLEs.

-- Reveals the full native range of source during preview and edit.

-- Allows precision conformity to YUV production levels, such as several Cable and Broadcast TV providers request.

Cons

-- Not recommended for limited range source, such as one would download, purchase, or legally rip. Redundancies affecting actual output bit depth can occur.

-- In these cases I use the mainstream method linked above, but I get irritable if I've forgotten to take the RGB filter off before starting an overnight render.

Above All Else

Leave the stupid "Dynamic Contrast" or "Full Range PC" graphics switch left at its defaults. Reload the drivers if in doubt. The only thing you need to know is that it was not put there for editors. It just adds another whole layer of errors if you touch it ;?)

 

Thank you again for all your help in this. After looking through and talking with a friend who is very knowledgeable with Vegas I am excited to have learned the importance of this. I just got to remember to disable the dang RGB filter. =)

I just got to remember to disable the dang RGB filter. =)

Again, I believe the advice to use the free extension is probably the best. I know it would be for me if I was using the preview rgb filter, because it drove me mad.

"One definition of insanity is repeating the same behavior over and over, and expecting different results. "