-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions regarding HDR encoding and color conversion #268
Comments
|
Thanks for your quick response.
|
Yes, please use AMF_VIDEO_ENCODER_HEVC_INPUT_HDR_METADATA. We can consider the conversion that you are describing. What use cases do you have in mind and which tone mapping would be preferrable? |
Self hosted media server like Plex.tv, Emby.media and Jellyfin.org to utilize GPU to serve transcoded adaptive bitrate video streams in Dash/HLS to the PC/mobile client app. Since not all client/display supports HDR and HEVC playback, the HDR-to-SDR tonemapping have to be done in the transcoding pipeline on the server side. Using a custom OpenCL kernel is feasible, but it way more convenient to get it done inside the AMFConverter along with the scaler. Tonemapper like BT.2390, Hable or Reinhard are preferred. In this case, for encoding to H.264 videos, AMFConverter also need to implement SURFACE_P010 to SURFACE_NV12 conversion. For reference: |
Hello!
Seeing that “HDR color conversion in the encoder” is list in the release note of AMF 1.4.21. I have some questions as follows.
use
_INPUT_
or_OUTPUT_
? And what is the difference between these two?Are these fields above just to set VUI header into the video?
Or doing some color conversion inside the encoder using this capability.
AMF_VIDEO_ENCODER_HEVC_CAP_COLOR_CONVERSION
Does the Converter accept P010 surface when using tonemapping options on HDR input? As we know most of the HDR films are encoded in 10-bit. So can I use this option to map HDR(smpte2084) into SDR(bt709) without clipping too much color details?
AMF_VIDEO_CONVERTER_TONEMAPPING_AMD
The text was updated successfully, but these errors were encountered: