This shows you the differences between two versions of the page.
software:sony-vegas-pro [2013/10/10 08:55] balazer [Rendering] |
software:sony-vegas-pro [2013/10/18 07:27] (current) balazer [Color Space] |
||
---|---|---|---|
Line 8: | Line 8: | ||
* 8-bit mode is quite fast for editing, preview, and rendering. | * 8-bit mode is quite fast for editing, preview, and rendering. | ||
* In 32-bit projects, RGB values are 32-bit floating point values. | * In 32-bit projects, RGB values are 32-bit floating point values. | ||
- | * 32-bit mode is quite slow for editing, preview, and rendering. | + | * 32-bit mode is quite slow for editing, preview, and rendering when your project resolution is high. |
- | * 32-bit mode is more accurate and less prone to banding and other color precision artifacts - especially the cumulative errors of long filter chains. | + | * 32-bit mode is more accurate and less prone to banding and other color precision artifacts - especially the cumulative errors of long filter chains. |
* 32-bit projects support values below 0 and above 255, and some filters allow access to these out-of-range values. For example, increasing the contrast could push a low value below 0, and decreasing the contrast could bring a below-0 value back above 0. | * 32-bit projects support values below 0 and above 255, and some filters allow access to these out-of-range values. For example, increasing the contrast could push a low value below 0, and decreasing the contrast could bring a below-0 value back above 0. | ||
* Compositing operates with 32-bit floating point precision in 32-bit projects. | * Compositing operates with 32-bit floating point precision in 32-bit projects. | ||
Line 15: | Line 15: | ||
* In 32-bit full range projects, you should set the compositing gamma to 2.22, which means that Vegas's compositing and filters operate linearly on the encoded RGB values, same as in 8-bit and 32-bit video levels projects. Setting the compositing gamma to 1 changes the behavior of compositing and some filters in a way that you probably don't want (but perhaps is appropriate for video sources with a linear transfer function). | * In 32-bit full range projects, you should set the compositing gamma to 2.22, which means that Vegas's compositing and filters operate linearly on the encoded RGB values, same as in 8-bit and 32-bit video levels projects. Setting the compositing gamma to 1 changes the behavior of compositing and some filters in a way that you probably don't want (but perhaps is appropriate for video sources with a linear transfer function). | ||
* Projects can be switched freely between 8-bit mode, 32-bit video levels mode, and 32-bit full range mode, but filters may behave differently depending on how your input formats are mapped to RGB level ranges. | * Projects can be switched freely between 8-bit mode, 32-bit video levels mode, and 32-bit full range mode, but filters may behave differently depending on how your input formats are mapped to RGB level ranges. | ||
- | * By default Vegas Pro makes no particular assumptions about the primary chromaticities or transfer function ("gamma") of the RGB encoding: operations are linear on the RGB values, and the scopes and preview window show the full range of RGB values with no conversion or remapping. | + | * Most filters behave similarly in 8-bit and 32-bit modes, but a few like Color Balance behave quite differently when the color corrections are strong. If you are making strong corrections (e.g. for log footage), it's best to stick with either 8-bit or 32-bit mode for color correction and rendering. |
+ | * By default Vegas Pro does no color management and makes no particular assumptions about the primary chromaticities or transfer function ("gamma") of the RGB encoding: operations are linear on the RGB values, and the scopes and preview window show the full range of RGB values with no conversion or remapping. | ||
Line 48: | Line 49: | ||
^ ::: ^ ::: ^ ::: ^ ::: ^ ::: ^ | ^ ::: ^ ::: ^ ::: ^ ::: ^ ::: ^ | ||
^ .MPG MPEG-1/2 input | 16-235 / yes | 16-235 / yes | 0-255 / yes | rec.709 for proj 1358x764+ | | ^ .MPG MPEG-1/2 input | 16-235 / yes | 16-235 / yes | 0-255 / yes | rec.709 for proj 1358x764+ | | ||
- | ^ .MP4 MPEG-2 input | 16-235 / yes | 16-235 / yes | 0-255 / yes | rec.709 | | + | ^ .MP4 MPEG-2 input | 16-235 / yes | 16-235 / yes | 0-255 / yes | rec.709 for hires file | |
- | ^ .MP4 h.264 input | 16-235 / yes | 16-235 / yes | 0-255 / yes | rec.709 | | + | ^ .MP4 h.264 input | 16-235 / yes | 16-235 / yes | 0-255 / yes | rec.709 for anyres file| |
^ .MTS h.264 input | 16-235 / yes | 16-235 / yes | 0-255 / yes | rec.709 | | ^ .MTS h.264 input | 16-235 / yes | 16-235 / yes | 0-255 / yes | rec.709 | | ||
^ .MOV h.264 input † | 0-255 / no | 0-255 / no | 0-255 / no | rec.601 | | ^ .MOV h.264 input † | 0-255 / no | 0-255 / no | 0-255 / no | rec.601 | | ||
Line 73: | Line 74: | ||
* Quicktime .MOV input requires Quicktime to be installed. I use Quicktime Alternative 3.2.2. | * Quicktime .MOV input requires Quicktime to be installed. I use Quicktime Alternative 3.2.2. | ||
* Quicktime input suffers from precision errors that produce banding. | * Quicktime input suffers from precision errors that produce banding. | ||
- | * Cineform .MOV and .AVI input and output in is enabled by installing the free GoPro Studio (version 2.0.0.285 tested). Vegas reads these files in 4:2:2 with 10-bit precision. | + | * Cineform .MOV and .AVI input and output are enabled by installing the free GoPro Studio (version 2.0.0.285 tested). Vegas reads these files in 4:2:2 with 10-bit precision. The codec included with GoPro Studio is supposed to support output of up to 1920 x 1080. |
- | * Compensate for an incorrect YCbCr->RGB conversion matrix by using [[http://www.dvinfo.net/forum/what-happens-vegas/115239-mixing-hd-709-sd-601-clips.html|601<->709 Channel Blend filter values]] at the beginning of your filter chain. | + | * .AVI input seems to support PCM audio of 16-bit precision at most. |
+ | * Compensate for an incorrect YCbCr<->RGB conversion matrix by using [[http://www.dvinfo.net/forum/what-happens-vegas/115239-mixing-hd-709-sd-601-clips.html|601<->709 Channel Blend filter values]] at the beginning or end of your filter chain. | ||
* If your output renderer allows out-of-range values, prevent out-of-range values by adding a Curves filter to the output: the default curve clips values below 0 and above 255. To clip values below 16 and above 235, add a "Studio RGB to Computer RGB" levels filter, then a default curve, then a "Computer RGB to Studio RGB" levels filter. | * If your output renderer allows out-of-range values, prevent out-of-range values by adding a Curves filter to the output: the default curve clips values below 0 and above 255. To clip values below 16 and above 235, add a "Studio RGB to Computer RGB" levels filter, then a default curve, then a "Computer RGB to Studio RGB" levels filter. | ||
=====Rendering====== | =====Rendering====== | ||
Line 81: | Line 83: | ||
* It supports output of up to 80 Mbps CBR | * It supports output of up to 80 Mbps CBR | ||
* It supports output greater than 4 GB | * It supports output greater than 4 GB | ||
+ | * YouTube will accept this as input and convert it with no resampling or remapping of levels. | ||
* Mainconcept AVC/MP4 is not recommended | * Mainconcept AVC/MP4 is not recommended | ||
* It's slow | * It's slow | ||
Line 101: | Line 104: | ||
* To make fine adjustments to a filter slider, click it, hold down the CTRL key, and then turn your mouse's scroll wheel. | * To make fine adjustments to a filter slider, click it, hold down the CTRL key, and then turn your mouse's scroll wheel. | ||
* Video filters may be applied to source media, the timeline video events, video tracks, or to the video output (tools menu, video, video output FX). | * Video filters may be applied to source media, the timeline video events, video tracks, or to the video output (tools menu, video, video output FX). | ||
- | * While editing, set the project to 8-bit mode and reduce the project resolution to match your full-screen preview device. This will make preview of filter adjustments much more responsive. Don't forget to change the project resolution back when you render. | + | * A video filter applied to a track can be made to affect every track below it as well as the track itself (i.e. post-compositing instead of pre-compositing) by dragging the filter to the right of "compositing" in the filter chain. |
+ | * While editing, set the project to 8-bit mode and/or reduce the project resolution to match your full-screen preview device, or to an even smaller size. This will make preview of filter adjustments much more responsive. Don't forget to change the project resolution back when you render. | ||
* To add a filter with a saved filter preset to multiple video events, select the events on the timeline, view Video FX, and then drag a preset onto the selected video events. | * To add a filter with a saved filter preset to multiple video events, select the events on the timeline, view Video FX, and then drag a preset onto the selected video events. | ||
* When adding video filters using the plug-in chooser, the filter chain can be saved as a filter package by clicking Save As in the plug-in chooser dialog. | * When adding video filters using the plug-in chooser, the filter chain can be saved as a filter package by clicking Save As in the plug-in chooser dialog. | ||
* To add a saved filter package to one or more events, view the plug-in manager, find the filter package and drag it onto the video event or onto multiple selected video events. Filters added this way use the filter's default. | * To add a saved filter package to one or more events, view the plug-in manager, find the filter package and drag it onto the video event or onto multiple selected video events. Filters added this way use the filter's default. |