# Handling a straightforward color space conversion You can control how MediaLive takes the color space and color space metadata in a video source and manipulates it in the video output. You can set up each output video encode to convert or pass through the color space, and to include or omit the color space metadata. All video belongs to a specific color space. The color space defines the range of color for the video. Video can include color space metadata that provides information about the color space. When metadata is missing, the video still has a color space, but it is impossible for MediaLive to manipulate the color space. **Default behavior** The default behavior is to pass through the color space and pass through the color space metadata. **Topics** + [ ## Determine if this section applies to your channel ](#color-space-simplified-which-section) + [ # Color space versus video resolution ](color-space-vs-resolution.md) + [ # General information about color space ](about-color-metadata-simplified.md) + [ # Passing through the color space ](color-space-simplified-options-passthrough.md) + [ # Converting the color space ](color-space-simplified-options-convert.md) + [ # Configuring the inputs ](color-space-simplified-setup-input.md) + [ # Configuring color space handling in each output ](color-space-simplified-output-handling.md) + [ # Results for different color space handling ](colorspace-simplified-output-results.md) + [ # Reference: Location of fields ](colorspace-simplified-fields.md) ## Determine if this section applies to your channel In this guide there are two sections about handling color space — this *straightforward handling* section, and [Handling complex color space conversions](color-space.md). The current section provides procedures you can follow if the input color spaces and color space metadata are all *clean*. The procedures in this section are shorter than those in the other section. To determine if your content meets the requirements for these procedures, read the following table. Each row in the table describes a different scenario that this *straightforward handling* section covers. Find the scenario that applies to your content. If none of these scenarios applies to you, then you must you must read [Handling complex color space conversions](color-space.md). [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/color-space-simplified.html) # Color space versus video resolution Color space refers to the range of color. MediaLive supports the following color spaces: + SDR (standard dynamic range) + HDR (high dynamic range) color spaces Resolution refers to the video pixel count. MediaLive supports the following resolutions: + SD (standard definition). + HD (high definition). + UHD (ultra-high definition). For UHD, MediaLive resolutions up to 4K. The following combinations of color space and resolution are typically used: + SDR color space can be associated with SD, HD, and UHD video. + HDR color space can be associated with HD or UHD video. An HDR color space isn't typically associated with SD content, but MediaLive *does* support ingesting this combination. # General information about color space Following is some general information about how MediaLive handles color space. **Topics** + [ # Components of color space ](color-space-simplified-definitions.md) + [ # Color space standards that MediaLive supports ](color-space-simplified-standards.md) # Components of color space There are four components to color space: + The specific *color space* that applies to the video content. The color space specifies a range of pixel colors that can apply to the content. + The *color space metadata*, which identifies the color space being used. If this metadata is present, the content is said to be *marked* for a color space. + The *brightness function* that applies to the color space. The brightness function controls the brightness of each pixel. The brightness is also known as gamma tables, electro-optical transfer function (EOTF), and transfer function. + The *brightness metadata*, which identifies the brightness function being used. + The *display metadata * that applies to the color space. Not all standards have this metadata. The video might use a specific *color space* and a specific *brightness function*. The video might also carry *color space metadata *that describes aspects of the color. # Color space standards that MediaLive supports Each color space standard follows a specific standard for the color space, and specific standards for the three sets of color data. To read this table, find a color space in the first column, then read across to identify the standards for the color space and the three sets of color data. | MediaLive term for the color space | Complies with this color space standard | Complies with this brightness function (gamma) standard | Complies with this standard for display metadata | | --- | --- | --- | --- | | Rec. 601 | Rec. 601 | BT.1886 | Not applicable. This color space doesn't include display metadata. | | Rec. 709 | Rec. 709 | BT.1886 | Not applicable. This color space doesn't include display metadata. | | HDR10 | Rec. 2020 | SMPTE ST 2084 (PQ) | SMPTE ST 2086 | | HLG or HLG 2020 | Rec. 2020 | HLG rec. 2020 (ARIB\$1STD-B67/HLG) | Not applicable. This color space doesn't include display metadata. | | Dolby Vision 8.1 | Rec. 2020 | SMPTE ST 2084 (PQ) | Proprietary Dolby Vision 8.1 metadata (RPU), on a per-frame basis, and SMPTE ST 2086 on a per-stream basis. | **Default behavior** The default behavior for a channel is to pass through the color space and pass through the uncorrected color space metadata. Therefore, if you want to pass through the color space to all the outputs, you can stop reading this entire section about handling color space. # Passing through the color space You can set up to *pass through* the color space in a MediaLive output. These rules apply: + The color space can be a supported color space or an unsupported color space. + You can set up to include or remove the color space metadata. + You can set up to pass through the color space in some outputs and to convert it in other outputs. # Converting the color space You can set up to *convert* the color space itself, to change the pixels in the video. MediaLive can perform specific color space conversions. You can set up each output in the channel for different handling. For example, you can set up one output to convert the color space to HDR10, set up one output to convert to HLG, and set up another output to pass through the color space. **Topics** + [ # Supported types of conversion in MediaLive ](color-space-simplified-supported-conversions.md) + [ # Getting ready to use 3D LUTs files with MediaLive ](color-space-process-with-lut.md) + [ # Input requirements ](color-space-simplified-supported-inputs.md) + [ # Output requirements ](color-space-simplified-input-output-requirements.md) + [ # Handling of metadata when converting ](color-space-simplified-options-metadata.md) # Supported types of conversion in MediaLive You can configure a channel to use the standard MediaLive color corrector when converting the color space. Or you can use a [3D LUTs color corrector file](color-space-process-with-lut.md) that you provide. The following table shows which conversions MediaLive supports. Read across each row. | From any of these color spaces in the source | To this color space in the output | Supported? | | --- | --- | --- | | Rec. 709, HLG, HDR10 | Rec. 601 | Yes | | Rec. 601, HLG, HDR10 | Rec. 709 | Yes | | Rec. 601, Rec. 709, HLG | HDR10 | Yes | | Rec. 601, Rec. 709, HDR10 | HLG | Yes | | Rec. 601, Rec. 709, HLG, HDR10 | Dolby Vision 8.1 | Yes | | Dolby Vision 8.1 | Any color space supported by MediaLive | Not supported | # Getting ready to use 3D LUTs files with MediaLive You can configure a channel to use a 3D LUTs color correct file for conversion, instead of using the standard MediaLive color corrector file for conversion. You provide a list of 3D LUTs files. Each 3D LUTs file contains color mapping information for a specific source/output combination. For example, one file contains information for converting Rec. 709 to HDR10. ## Using 3D LUTs files These rules apply to using 3D LUTs files: + **Sourcing of 3D LUTs files. **You must provide the 3D LUTs files. MediaLive doesn't have built-in files. + **One file for each combination.** You must provide a file for each source/output combination. For example, a file for converting Rec. 601 to HDR10. + **Maximum 8 files. **You can provide a maximum of 8 files for each channel. This means that MediaLive supports up to 8 source/output conversion combinations. + **Global application. **MediaLive uses a specific file in all the outputs where that file applies. For example, if there is a file to convert Rec. 601 to HDR10, MediaLive uses that file in every output that it applies to. You can't configure some outputs to use the standard mechanism for conversion. ## Contents of the 3D LUTs files The following rules apply to the contents of the files: + **Format.** You must make sure that each 3D LUTs file follows the .cube 3D LUTs format. + **Maximum one file per combination.** You can provide only one 3D LUTs file for each combination. You can't configure some outputs to use a different 3D LUTs file. When MediaLive reads the list of 3D LUTs files, it uses the first file that it finds for a source/output combination. + **HDR10 luminance. **MediaLive supports conversion of HDR10 content with a maximum luminance of 1000 nits to 4000 nits, but it only supports one maximum luminance. When MediaLive reads the list of 3D LUTs files, it finds the first file for each conversion from HDR10. Even if you one file for 1000 nits and one for 4000 nits (for example), MediaLive uses only the first file it encounters. Therefore the following guidelines apply: + You should make sure that all the HDR10 content in all the inputs in one channel have the same maximum luminance. If a source has a different maximum luminance, MediaLive will convert the content, but the outputs will have sub-optimal luminance. + In each 3D LUTs file for converting from HDR10, make sure that the luminance handling is appropriate for the luminance of the source. # Input requirements MediaLive can work with the [supported color space](color-space-simplified-standards.md) in all [supported types of input](inputs-supported-formats.md) with the following notes. **Elemental Link input** MediaLive can't read the color space metadata in a source from an AWS Elemental Link device. The workaround when you set up the input is to specify the color space that applies, as described in [Configuring the inputs](color-space-simplified-setup-input.md). **Source when converting to Dolby Vision 8.1** + The video source must be HD or 4K resolution. In other words, the source must be 1080p or higher. + The video source can't be a file. This means that the source can't be a VOD asset in an MP4 file or in a transport stream file. These constraints are stipulated by Dolby Vision 8.1, and relate to the minimal video quality required to produce Dolby Vision 8.1 outputs that meet the Dolby Vision 8.1 standard. # Output requirements **Supported output types** All color space types except Dolby Vision 8.1 can be set up in all MediaLive output group types. Dolby Vision 8.1 can be set up only in the following output group types: + Archive + CMAF Ingest + HLS + SRT caller + UDP **Supported output codecs** The following table specifies the supported video codecs for the output color spaces. A value of Yes means that when the video output uses this codec, you can convert to the specified color space. | Output color space | AV1 | AVC (H.264) | HEVC (H.265) | | --- | --- | --- | --- | | Rec. 601 | Yes | Yes | Yes | | Rec. 709 | Yes | Yes | Yes | | HDR10 | Yes | | Yes | | HLG | Yes | | Yes | | Dolby Vision 8.1 | | | Yes | **Supported video profile for HDR10 or Dolby Vision 8.1 outputs** For HDR10 or Dolby Vision 8.1 outputs, the video profile must include the term *10BIT*. # Handling of metadata when converting When you set up in MediaLive to convert the color space, you can set up to include or omit the color space metadata. + Include color space metadata. MediaLive will convert the color space metadata to accurately describe the new color space. + Omit the color space metadata. You might want to remove the color space metadata because the downstream system can't handle it properly. When MediaLive removes the metadata, the source still has a color space but it doesn't have information that identifies the color space. Removing the metadata doesn't necessarily degrade the color. Removing it might only mean that the downstream player can't implement enhancements to make the color even richer. # Configuring the inputs **Note** This section assumes that you are familiar with creating or editing a channel, as described in [Creating a channel from scratch](creating-channel-scratch.md). This section describes how to set up each of the sources (inputs) in a MediaLive channel. It applies both when you pass through the color space to the output and when you convert the color space. Follow these steps for each input in the channel. 1. Make sure that your inputs comply with [the requirements](color-space-simplified-supported-inputs.md). 1. On the **Create channel** page, in the **Input attachment** section for the input, in the **General input settings** section, group, open the **Video selector** field. 1. Set these fields: + **Color space**: Choose **Follow**. (The other options apply only to [complicated color space situations](color-space.md).) + **Color space usage**: Leave the default. This field is ignored when you set **Color space** to **Follow**. This combination of values indicates that the color space metadata in the content correctly identifies the color space, therefore MediaLive can use that metadata. 1. Obtain the values for the Max CLL and Max FALL for the content, but only if the following situation applies: + The input is for a MediaLive device such as AWS Elemental Link. + The input color space is HDR10. (This means that the output from the Link device is HDR10.) + You plan to pass through the color space to the output. You need this information because MediaLive can't read the metadata from an AWS Elemental Link device. Instead, you will be able to enter the color space and the display metadata (Max CLL and Max FALL) manually, in the next step. You don't need these values if you plan to convert this input from HDR10 to another color space. 1. Complete **Color space settings** as follows: + If the situation in step 4 applies, choose **HDR10** (to identify the source color space). Then, if you obtained metadata values, enter them in the **Max CLL** and **Max Fall** fields that appear (to provide the metadata that is missing from the input). + If the situation doesn't apply, choose **Don't include**. # Configuring color space handling in each output **Note** This section assumes that you are familiar with creating or editing a channel, as described in [Creating a channel from scratch](creating-channel-scratch.md). This section describes how to set up each output in the MediaLive channel for the desired color space handling — passthrough or conversion. You can set up each output in a different way. Follow these steps for each output in the channel. **Topics** + [ ## Step 1: Configure enhanced VQ mode ](#color-space-simplified-output-config-vq) + [ ## Step 2: Prepare 3D LUTs files ](#color-space-simplified-get-ready-lut) + [ ## Step 3: Configure the channel to use 3D LUTs files ](#color-space-simplified-output-configure-lut) + [ ## Step 4: Setting up for passthrough ](#colorspace-simplified-output-setup-passthrough) + [ ## Step 5: Setting up to convert ](#colorspace-simplified-output-setup-convert) ## Step 1: Configure enhanced VQ mode You must decide if you should enable enhanced VQ mode in the MediaLive output. This mode applies only to outputs that use H.264. 1. In the following table, find the planned handling in the first column, then read across to identify the action to take. 1. To enable enhanced VQ mode, see [Setting up enhanced VQ mode](video-enhancedvq.md). | Planned handling | Details | Action | | --- | --- | --- | | Pass through | You already plan to enable enhanced VQ to improve the video quality. | Enable the mode. | | Convert to SDR | The inputs contain both SDR and HDR content. | You must enable the mode. | | Convert to SDR | The inputs contain only SDR content. For example, all the inputs are Rec. 709, and you want to convert the content to Rec. 601. | Enabling the mode is optional. | | Any conversion | There is no HDR10 or HLG in any of the inputs. | Enabling the mode is optional. | | Any conversion | You already plan to enable enhanced VQ to improve the video quality. | Enable the mode. | ## Step 2: Prepare 3D LUTs files Perform these steps if you plan to convert the color space in a MediaLive output, and you want to use 3D LUTs files for that conversion. You must obtain the 3D LUTs files and store them in an accessible location. 1. Read [Getting ready to use 3D LUTs files with MediaLive](color-space-process-with-lut.md) for rules and requirements. 1. Identify the conversion combinations that you want to perform across all outputs in the channel. You can perform a maximum of 8 conversion combinations, because you can specify a maximum of 8 files. 1. Obtain the 3D LUTs file for each combination. For files for HDR sources, make sure that you obtain the file that matches the maximum luminance of the source. Make sure that you know which source/output combination each 3D LUTs file handles. There is no metadata in the files that lets MediaLive discover the combination. Instead, when MediaLive needs to choose a file, it reads the information that you specify when you configure the channel (in the next step). 1. Store the files in one or more buckets in Amazon S3. Make a note of the URLs for the files you want to use in this channel. Make sure that [MediaLive has access](trusted-entity-requirements.md) to the Amazon S3 bucket or buckets. **Example** For example, you might have sources in Rec. 601, Rec. 709, and HDR10. You might want to convert the HDR10 sources to Rec. 709 in one output, and you might want to convert the SDR sources to HDR10 in another output. The following table summarizes your intentions. | Source | Rec. 709 output | HDR10 output | | --- | --- | --- | | Rec. 601 | Convert using standard mechanism | Convert using 3D LUTs file | | Rec. 709 | No conversion | Convert using 3D LUTs file | | HDR10 | Convert using 3D LUTs file | No conversion | Therefore you need to provide three files: + Rec. 601 to HDR10 + Rec. 709 to HDR10 + HDR10 to Rec. 709 Note that when there is no conversion, you shouldn't provide a file. MediaLive doesn't support handling that retains the source color space and only changes the color mapping. MediaLive would never use that file. Note also that you decided not to provide a file to convert Rec. 601 to Rec. 709 because the difference in the output is minimal. MediaLive will convert the Rec. 601 source to Rec. 709, but it will do so using the standard mechanism. ## Step 3: Configure the channel to use 3D LUTs files Perform these steps if you plan to convert the color space in a MediaLive output, and you want to use 3D LUTs files for that conversion. You must configure MediaLive to use those files. 1. On the **Create channel **page, in the **General settings** section, select **Color Correction Settings**. Slide the **Enable Color correction settings** field. 1. Choose **Add global color corrections** up to 8 times. In each line, enter the following information: + The URL for the 3D LUTs file. + The input (source) color space that the file handles. + The output color space that the file handles. Choose HDR10 for a file that handles either HDR10 or Dolby Vision 8.1. HDR10 and Dolby Vision 8.1 are the same in terms of color correction. **Runtime handling** When you start the channel, MediaLive will use the 3D LUTs files as follows: + MediaLive reads the color space metadata in each source video frame. For example, for one frame, the metadata might specify that the color space is Rec. 601. + MediaLive reads the color space you have configured for each output. For example, the video output might be set up for conversion to HDR10. + MediaLive reads the information you configured about each file and finds the first file that matches the source and output. If the source and output are the same (for example, Rec. 601 source and Rec. 601 output), MediaLive doesn't look for a file. It always passes through the color space. If there is more than one 3D LUTs file with the same input and output specified, MediaLive uses the first file it encounters. + MediaLive uses that file to convert that combination of source and output. + If there is no file for this combination, MediaLive performs the conversion using the standard mechanism (that is, without using 3D LUTs color mapping). ## Step 4: Setting up for passthrough You can set up to pass through the source color space in one or more MediaLive outputs. The key fields to set are **Color space** and **Color metadata**. 1. On the **Create channel **page, in the **Output groups **section, choose the output that contains the video. Display the **Stream settings **section, and choose the **Video **section. 1. For **Codec settings**, choose a codec. For information about the color spaces that each codec supports, see [Output requirements](color-space-simplified-input-output-requirements.md). 1. Choose **Codec details**. More fields appear. Choose **Additional settings**. More fields appear. In **Color metadata**, choose **Insert** or **Ignore** to specify how you want to handle the color space metadata. 1. Choose **Color space**. The **Color space settings** field appears. Choose **Color space passthrough**. (Or choose **Don't include**, which is equivalent to **Color space passthrough**.) ## Step 5: Setting up to convert You can set up to convert the color space in one or more MediaLive outputs. You must set up several fields, each in a specific way. 1. On the **Create channel **page, in the **Output groups **section, select the output that contains the video. Display the **Stream settings **section, and choose the **Video **section. 1. Complete the **Width** and **Height** fields to specify a valid resolution. Make a note of whether you are specifying an SD, an HD, or a UHD resolution. 1. In **Codec settings**, choose a codec. For information about the color spaces that each codec supports, see [Output requirements](color-space-simplified-input-output-requirements.md). 1. Choose **Codec details**. More fields appear. Set the **Profile**, **Tier**, and **Level** fields, if they appear for the codec that you chose: + If the resolution is SD, enter values that suit your requirements. + If the resolution is an HD or UHD resolution, set the tier and level to suit your requirements, and set the profile as follows: + If the output color space will be an HDR color space, you must choose one of the profiles that has **10BIT** in the name. + If the output color space will be an SDR color space, you can choose any profile. 1. Choose **Color space**. The **Color space settings** field appears. Set the field to the color space to convert to. If you choose **HDR10**, the **Max CLL** and **Max FALL** fields appear. Complete these fields to set the display metadata for the HDR10 output video. 1. Go back to **Codec details** and choose **Additional settings**. More fields appear, including **Color metadata**. In **Color metadata**, choose **Insert** or **Ignore** to specify how you want to handle the color space metadata. Typically, you omit it only if you know that the downstream system can't handle it properly. # Results for different color space handling This section describes how MediaLive handles the color space and color space metadata that it encounters in the source input, depending on how you set up the color space in the output. **Topics** + [ ## General process for handling color space conversion ](#color-space-simplified-results-general) + [ ## Result when passing through color space ](#colorspace-simplified-output-passthrough) + [ ## Result when converting color space to SDR ](#color-space-simplified-output-sdr) + [ ## Result when converting color space to HDR10 ](#colorspace-simplified-output-hdr10) + [ ## Result when converting color space to Dolby Vision 8.1 ](#color-space-simplified-output-dolby81) ## General process for handling color space conversion In an output that specifies to convert the color space, MediaLive performs the following steps on each video frame in the output. **Initial verifications** + MediaLive verifies that the source video meets the [input requirements](color-space-simplified-supported-inputs.md) and that it is in a supported color space. If it fails this verification, MediaLive always passes through the color space. + If the source video does meet the requirements, MediaLive verifies that you have [correctly configured](color-space-simplified-output-handling.md) the output video and codec. If it fails this verification, MediaLive uses the specified codec, but it passes through the color space. + MediaLive determines if the channel has been configured to [use 3D LUTs files](color-space-simplified-output-handling.md#color-space-simplified-output-configure-lut). **Handling with 3D LUTs files configured** MediaLive looks at the source and output color space for each frame. + If the source and color space are identical, MediaLive doesn't change the color space and therefore doesn't look for a 3D LUTs file. For example, if the source is HDR10 and you set up an output for HDR10, MediaLive leaves the color space as it is in the source. + If the source and color space are different, MediaLive looks for a file that corresponds to the source/output color space combination: + If it finds a file, it uses that file for conversion. + If it doesn't find a file, it converts the color space using the standard mechanism. **Handling without 3D LUTs files configured** If the channel hasn't been configured to use 3D LUTs files, then MediaLive converts the color space using the standard mechanism. For detailed information about the results of each kind of source/output conversion, see the sections that follow. ## Result when passing through color space Read this section if you set up one or more outputs to [pass through the color space](color-space-simplified-output-handling.md#colorspace-simplified-output-setup-passthrough). The following table shows how MediaLive handles each type of color space that it encounters in the source. | Color space that MediaLive encounters | How MediaLive handles the color space | | --- | --- | | Content in any color space that MediaLive supports | Doesn't touch the color space or brightness in the output. Passes through any of the three color format metadata fields that are present. | ## Result when converting color space to SDR Read this section if you set up one or more outputs to [convert the color space](color-space-simplified-output-handling.md#colorspace-simplified-output-setup-convert) to Rec. 601 or Rec. 709. The following table shows how MediaLive handles each type of color space that it encounters in the source. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/colorspace-simplified-output-results.html) ## Result when converting color space to HDR10 Read this section if you set up one or more outputs to [convert the color space](color-space-simplified-output-handling.md#colorspace-simplified-output-setup-convert) to HDR10. The following table shows how MediaLive handles each type of color space that it encounters in the source. | Color space that MediaLive encounters | How MediaLive handles the color space | | --- | --- | | Content in an SDR color space | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/colorspace-simplified-output-results.html) There is no change to the pixel values of the content. In effect, this conversion fits the smaller SDR color space into the larger HDR color space and maps the pixels to new code values that represent the same color. The conversion doesn't actually make the existing color richer. However, the bright parts of the content are brighter, and the dark parts are darker. | | Content in HDR10 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/colorspace-simplified-output-results.html) | | Content in HLG | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/colorspace-simplified-output-results.html) | ## Result when converting color space to Dolby Vision 8.1 Read this section if you set up one or more outputs to [convert the color space](color-space-simplified-output-handling.md#colorspace-simplified-output-setup-convert) to Dolby Vision 8.1. The following table shows how MediaLive handles each type of color space that it encounters in the source. | Color space that MediaLive encounters | How MediaLive handles the color space | | --- | --- | | Content in an SDR color space | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/colorspace-simplified-output-results.html) There is no change to the pixel values of the content. In effect, this conversion fits the smaller SDR color space into the larger HDR color space and maps the pixels to new code values that represent the same color. The conversion doesn't actually make the existing color richer. However, the bright parts of the content are brighter, and the dark parts are darker. | | Content in HDR10 | MediaLive makes the following changes:[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/colorspace-simplified-output-results.html)After the conversion, the color space hasn't changed. However, the bright parts of the content are brighter, and the dark parts are darker. | | Content in HLG | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/colorspace-simplified-output-results.html) | # Reference: Location of fields Read this section if you know how to handle color space in MediaLive, and you only need a reminder of where the fields are located in the MediaLive Console. The information is sorted by the location of the fields on the **Channel** page, from top to bottom. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/medialive/latest/ug/colorspace-simplified-fields.html)