

# Configuring color space handling in each output
<a name="hdr-output"></a>

After you have set up each input in the event, you must configure the outputs for the desired handling of color space. You can do the following:
+ Convert the color space in the content to a different color space in the output. See [Color space standards](color-space-standards.md) for the supported conversions.
+ Remove the color space metadata. Elemental Live doesn't touch the color space itself, it only removes the color space metadata. 

  You might choose to remove the color space metadata in situations such as the following:
  + The pixel data and color space data in the input is incorrect, so that the downstream player can't use it to enhance the color.
  + The color space (and its metadata) changes frequently within the input, or between one input and another, and you know that there is a system downstream of AWS Elemental Live that can't handle changes in the metadata. 

  Keep in mind that removing metadata doesn't necessarily make the color poorer. Removing it might only mean that the downstream player can't implement enhancements to make the color even richer.
+ Pass the color space metadata and the color space through to the output.

You can set up each output with different color space handling. For example, you can create one output that passes through the original color space, and another that converts it.

**Note**  
Elemental Live converts from one color space to another based on the metadata in the content. Elemental Live doesn't examine the video to try to determine whether it actually matches the color space identified in the metadata. Therefore, to successfully convert, the metadata must be as accurate as possible. To correct the metadata, see [Configuring the handling in the input](hdr-input-handling.md).

**Topics**
+ [Passing through color space](colorspace-output-passthrough.md)
+ [Converting color space: Procedure A](colorspace-output-procedure.md)
+ [Converting color space: Procedure B](colorspace-output-hdr10.md)
+ [Removing color space metadata](colorspace-output-remove.md)

# Passing through color space
<a name="colorspace-output-passthrough"></a>

You can pass through any color space that Elemental Live supports, except for Dolby Vision 5.0. You can pass through both color spaces that Elemental Live supports, and color spaces that it doesn't support, so long as the output type supports the passed-through color space standard.

**Note**  
This section assumes that you are familiar with creating or editing an event. 

**To set up each output**

Follow this procedure in each output. 

1. On the **Event **page, in the **Output groups **section, choose the output group, and choose the output that contains the video.

1. Open the **Advanced** section. More fields appear.

1. Leave **Insert Color Metadata** checked. You should never remove the color metadata if you are passing through the color space.

1. Scroll down to the **Preprocessors ** section and turn on **Color Corrector**. More fields appear.

1. Set **Color Space Conversion** to **None**, which means you don't want to convert the color space.

The following table shows how Elemental Live handles each type of color space that it encounters. Each row in the table describes a different handling.


|  Color space metadata that Elemental Live encounters  |  How Elemental Live handles the color space  | 
| --- | --- | 
|  Content in any color space that Elemental Live supports  |  It doesn't touch the color space or brightness (the pixel values) in the output. It passes through any of the three sets of metadata that are present.  | 
| Content marked with unknown or an unsupported color space |  It doesn't touch the color space or brightness (the pixel values) in the output. It leaves the content as marked with the unknown color space.  It passes through any brightness metadata and display metadata.  | 
|  Content with no color space metadata  |  It doesn't touch the color space or brightness (the pixel values) in the output. It leaves the content as unmarked (no color space metadata).  | 

# Converting color space: Procedure A
<a name="colorspace-output-procedure"></a>

Follow this procedure to convert to one of these color spaces:
+ 601
+ 709
+ SDR2020
+ HLG

For information about the source color spaces that you can convert to one of these color spaces, see [Support for conversion and passthrough](color-space-conversions.md).

For information about the results of conversion, see [The results of different types of conversions](color-space-conversion-results.md).

**Note**  
This section assumes that you are familiar with creating or editing an event. 

**To set up each output**

Follow this procedure in each output. 

1. On the **Event **page, in the **Output groups **section, choose the output group, and choose the output that contains the video.

1. Open the **Advanced** section. More fields appear.

1. Scroll down to the **Preprocessors ** section and turn on **Color Corrector**. More fields appear.

1. Complete fields in the **Video** section as described in the following table


|  Field  |  Description  | 
| --- | --- | 
|  **Video Codec**  |  Choose any codec.  | 
|  **Advanced**, then **Insert Color Metadata**  |  Leave this field checked.  You should never remove the color metadata if you are converting the color space.  | 
|  **Video Range**  |  Choose the correct option. For details, choose the icon above the field.  | 
|  **Preprocessors**, then **Color Space Conversion**  |  Choose the correct conversion: **Force 601** **Force 709** **Force SDR2020** **Force HLG 2020**  | 

# Converting color space: Procedure B
<a name="colorspace-output-hdr10"></a>

Follow this procedure to convert to one of these color spaces:
+ HDR10
+ Dolby Vision

For information about the source color spaces that you can convert to one of these color spaces, see [Support for conversion and passthrough](color-space-conversions.md).

For information about the results of conversion, see [The results of different types of conversions](color-space-conversion-results.md).

**To set up each output**
**Note**  
This section assumes that you are familiar with creating or editing an event. 

Follow this procedure in each output. 

1. On the **Event **page, in the **Output groups **section, choose the output group, and choose the output that contains the video.

1. Open the **Advanced** section. More fields appear.

1. Scroll down to the **Preprocessors ** section and turn on **Color Corrector**. More fields appear.

1. Complete fields in the **Video** section as described in the following table.


|  Field  |  Description  | 
| --- | --- | 
|  **Video Codec**  |  If you are converting to HDR10, choose **MPEG-4 AVC (H.264)** or **HEVC (H.265)**. If you are converting to Dolby Vision, choose **HEVC (H.265)**.  | 
|  **Advanced**, then **Insert Color Metadata**  |  Leave this field checked.  You should never remove the color metadata if you are converting the color space.  | 
|  **Advanced**, then **Profile** This field is towards the end of the **Advanced** section  |  Choose a profile that includes the term **Main10**.  | 
|  **Preprocessors**, then **Video Range**  |  Choose the correct option, according to the information you [obtained from the content provider](color-space-input-procedure.md): [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/elemental-live/latest/ug/colorspace-output-hdr10.html)  | 
|  **Preprocessors**, then **Color Space Conversion**  |  Choose the correct conversion: **Force HDR10**  **Dolby Vision Profile 5** **Dolby Vision Profile 8.1**  | 
|  **Preprocessors**, then **HDR Master Display Information**  |  These fields appear after you complete the **Color Space Conversion**. You can optionally complete the **HDR Master Display Information** fields. For information about master display information, see [Tips for HDR master display information](#hdr-tips-for-hdr-master-display-information).   | 

## Tips for HDR master display information
<a name="hdr-tips-for-hdr-master-display-information"></a>

The HDR Master Display Information fields appear if you are converting to HDR10 or Dolby Vision. Take the appropriate action:
+ If you have previously converted similar content to HDR10 and a color grading specialist in your organization has given you metadata, then enter it here. The values to enter here depend on the downstream player, so there is no point to asking your content provider for values.

  For details about a field on the web interface, choose the question mark next to the field. 
+ If you don't have metadata to use, set all fields to null values. It's better to set the fields to null values, rather than to make up values or to use the default values.

### Red, green, blue, white point x and y
<a name="hdr-output-rgb"></a>

Your color grader might provide numbers like this for X and Y points:
+ G (x=0.265, y=0.690)
+ B (x=0.150, y=0.060)
+ R (x=0.680, y=0.320)

You must convert these numbers to numbers like this: 
+ G (13250, 34500)
+ B (7500, 3000)
+ R (34000, 16000)

To convert between the two formats, divide each number by 0.00002 as per the HEVC specification.

For example, 0.265 divided by 0.00002 is 13250.

### Max luminance and min luminance
<a name="hdr-output-cll-fall"></a>

The maximum and minimum luminance are given in units of **0.0001 candelas per square meter**. Your color grader might provide this value in candelas per square meter instead. If so, then convert these numbers by multiplying by 10,000, then entering the result in the web interface.

For example, a value of 1000.0000 cd/m2 for max luminance would be converted to 10,000,000 and entered as that in the web interface.

# Removing color space metadata
<a name="colorspace-output-remove"></a>

Follow this procedure in each output where you want to remove the color space metadata.

You might choose to remove the color space metadata in situations such as the following:
+ The pixel data and color space data in the input is incorrect, so that the downstream player can't use it to enhance the color.
+ The color space (and its metadata) changes frequently within the input, or between one input and another, and you know that there is a system downstream of AWS Elemental Live that can't handle changes in the metadata. 

Keep in mind that removing metadata doesn't necessarily make the color poorer. Removing it might only mean that the downstream player can't implement enhancements to make the color even richer.

**Note**  
This section assumes that you are familiar with creating or editing an event. 

**To set up each output**

1. On the **Event **page, in the **Output groups **section, choose the output group, and choose the output that contains the video.

1. Open the **Advanced** section. More fields appear.

1. Set **Insert Color Metadata** to unchecked.

1. Scroll down to the **Preprocessors ** section and turn on **Color Corrector**. More fields appear.

1. Set **Color Space Conversion** to **None**, which means you don't want to convert the color space.

The following table shows how Elemental Live handles each type of color space it encounters.


|  Color space metadata that Elemental Live encounters  |  How Elemental Live handles the color space  | 
| --- | --- | 
|  Content in any color space that Elemental Live supports Content with no color space metadata Content with unknown or unsupported color space metadata  | It doesn't touch the color space or brightness (the pixel values) in the output.It removes all the metadata. The output won't contain any color space metadata, brightness metadata, or display metadata. | 