Some SCS types have said they like reading about workflow topics and changes in these forums. I am starting this thread as just such a topic.
Background:
Vegas is fundamentally full range. Most all video, at least what I do, wants video levels. This means were as users have work to do to get video levels.
There is a common host of cameras out there outputting full range video. My Canon DSLR and GoPro for example. The AVC video stream actually has an optional flag to tell a decoder that the stream contains full range data. A lot of DSLRs and GoPros out there.
I cannot count how many times, I and others have posted answers to someone complaining about crushed blacks on file encodes. Almost to exclusion this comes from people using full range cameras. Vegas gets a bit of a black eye from this. People do not expect levels to change when they do not do anything in their edits.
Fade to black/nothing in Vegas is fundamentally 0,0,0 and there is nothing Levels fx or broadcast colors fx can do about this. One has to put a solid color track with legal black under all others. At a minimum even if a proposal like this is rejected Vegas should lets us declare in a project setting what the nothing black level should be.
The vegas video preview window is fundamentally full range and absolutely cannot display video levels properly. We have to add a levels effect and remember to take it off when rendering. The external preview device does have to ability to adjust. Why the preview window does not get the same option is beyond me. Especially as it is by definition on a computer display, which are always full range.
My Proposal:
Preview devices declare themselves as full range or video levels devices. Both the preview window and external preview device.
Project properties declares itself as full range or video levels. Note that 32-bit float levels already have something similar to this. If a project is video levels then fade to black/nothing will be a legal video level.
Render As templates, declare themselves as video levels or full range. The default for templates would be "same as project setting".
With this information Vegas now has all the info it needs to properly display full range or video levels data streams on full range or video levels device. It knows what adjustment needs to be done, it any. For example, a video levels project displaying on a video levels device needs no adjustment. Maybe a warning needs to be given when attempting to display full range on a video levels device. Only because data is being compressed. Other other direction I feel is not an issue. Expansion is going from less to more levels. Obviously "perfect" is the playback device uses the same levels are your video stream.
Render As can also make an adjustment as necessary. With the default I propose, nothing would ever happen here. However, I would suggest that "Internet" templates default to video levels and not to "same as project". We all know Youtube/Vimeo/Smugmug expect video levels.
Compatibility
Vegas has a long history of working a certain way and the existing user base is used to this. A lot of people don't like change. These proposed changes can easily default to the status quo of current Vegas. All items would default to declaring themselves as full range. With this Vegas never makes adjustments at any time and you make all adjustments manually as we do now.
New feature support/capability for declared full range cameras
With AVC streams that have the full range flag. Vegas can help users here. When importing into a video levels project, vegas can prompt it the user wants the data converted to video levels. No behind the scenes function should occur here (ie no user control). The prompt would simply add a levels effect as a media effect if the user selects to have the data normalized to video levels. That effect can be taken off should the user later decide that would be preferred.
Effects on current plug-ins
What should Media generators do in video levels projects. Currently all media generators default to color values outside the legal video levels range. In a declared video levels project they should probably be clamped to legal levels probably like the Broadcast colors effect does.
Background:
Vegas is fundamentally full range. Most all video, at least what I do, wants video levels. This means were as users have work to do to get video levels.
There is a common host of cameras out there outputting full range video. My Canon DSLR and GoPro for example. The AVC video stream actually has an optional flag to tell a decoder that the stream contains full range data. A lot of DSLRs and GoPros out there.
I cannot count how many times, I and others have posted answers to someone complaining about crushed blacks on file encodes. Almost to exclusion this comes from people using full range cameras. Vegas gets a bit of a black eye from this. People do not expect levels to change when they do not do anything in their edits.
Fade to black/nothing in Vegas is fundamentally 0,0,0 and there is nothing Levels fx or broadcast colors fx can do about this. One has to put a solid color track with legal black under all others. At a minimum even if a proposal like this is rejected Vegas should lets us declare in a project setting what the nothing black level should be.
The vegas video preview window is fundamentally full range and absolutely cannot display video levels properly. We have to add a levels effect and remember to take it off when rendering. The external preview device does have to ability to adjust. Why the preview window does not get the same option is beyond me. Especially as it is by definition on a computer display, which are always full range.
My Proposal:
Preview devices declare themselves as full range or video levels devices. Both the preview window and external preview device.
Project properties declares itself as full range or video levels. Note that 32-bit float levels already have something similar to this. If a project is video levels then fade to black/nothing will be a legal video level.
Render As templates, declare themselves as video levels or full range. The default for templates would be "same as project setting".
With this information Vegas now has all the info it needs to properly display full range or video levels data streams on full range or video levels device. It knows what adjustment needs to be done, it any. For example, a video levels project displaying on a video levels device needs no adjustment. Maybe a warning needs to be given when attempting to display full range on a video levels device. Only because data is being compressed. Other other direction I feel is not an issue. Expansion is going from less to more levels. Obviously "perfect" is the playback device uses the same levels are your video stream.
Render As can also make an adjustment as necessary. With the default I propose, nothing would ever happen here. However, I would suggest that "Internet" templates default to video levels and not to "same as project". We all know Youtube/Vimeo/Smugmug expect video levels.
Compatibility
Vegas has a long history of working a certain way and the existing user base is used to this. A lot of people don't like change. These proposed changes can easily default to the status quo of current Vegas. All items would default to declaring themselves as full range. With this Vegas never makes adjustments at any time and you make all adjustments manually as we do now.
New feature support/capability for declared full range cameras
With AVC streams that have the full range flag. Vegas can help users here. When importing into a video levels project, vegas can prompt it the user wants the data converted to video levels. No behind the scenes function should occur here (ie no user control). The prompt would simply add a levels effect as a media effect if the user selects to have the data normalized to video levels. That effect can be taken off should the user later decide that would be preferred.
Effects on current plug-ins
What should Media generators do in video levels projects. Currently all media generators default to color values outside the legal video levels range. In a declared video levels project they should probably be clamped to legal levels probably like the Broadcast colors effect does.