Result when converting color space to HDR10 - MediaLive

Result when converting color space to HDR10

Read this section if you set up one or more MediaLive outputs to convert the color space 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

  • Converts the content to the new color space and brightness function. The conversion maps the pixels to code values that represent the same color as the original code values.

  • Changes the color space metadata to specify the new color space.

  • Changes the brightness metadata to specify the new standard.

  • If you completed Max CLL and Max FALL, the values in those fields are inserted in the display metadata.

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
  • Doesn't touch the color space (the pixel values) in the output.

  • Passes through the color space metadata.

  • Passes through the brightness metadata and the display metadata.

Content in HLG
  • There is no color space conversion—there is no change to the pixel values of the content. This is appropriate because HDR10 and HLG use the same color space (they are different only in brightness function and display metadata).

  • Converts the content to the new brightness function.

  • Changes the color space metadata to the new color space.

  • Change the brightness metadata to specify the new standard.

  • If you completed Max CLL and Max FALL, MediaLive inserts the values from those fields into the display metadata.

Content in Dolby Vision 8.1 This conversion isn't supported. After conversion, the color map of the content could be completely wrong.
Content marked with an unknown or unsupported color space

We can't make any promises about how MediaLive will handle source content that is in an unsupported color space. Any of the following might apply:

  • MediaLive might be able to ingest the input, and to pass through the color space and all the color space metadata.

  • Or it might ingest the input but produce unacceptable output.

  • Or it might fail to ingest the input, so that the event follows the input loss behavior routine (for example, it might display a slate in the output).

Content with no color space metadata

  • No change to the pixel values of the content.

  • Leaves the content as unmarked.

  • Passes through any brightness metadata and display metadata.