madshi bug tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000630madVRbugpublic2019-12-21 14:272020-01-09 17:16
Reportermclingo 
Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
StatusnewResolutionopen 
PlatformwindowsOS10OS Version1809
Summary0000630: Low colour saturation when using AMD API on AMD 5700 series cards - not apparent on old RX 4/500 series
DescriptionWhen using AMD HDR APi in MADVR colours are very unsturated, it has been suggested BT2020 is not being selected for output by MADVR for this generation of cards.

So far this has been reported and confirmed by a number of people including huhn on the MADVR forum.

Steps To ReproducePlay and HDR movie using MADVR, output in HDR must be selected.
Additional InformationIf Windows HDR switch is used instead and AMD API is disabled in MADVR colours are correct and normal so this seems to be an issue with how MADVR and AMD API are interacting, we cant tell if this is a MADVR or AMD issue.

However this has been an issue since day one of this series of cards and AMD still havent fixed it, can a workaround be added to MADVR mabe to force BT2020 output?
TagsNo tags attached.
madVR Versionv0.92.17 + 112b madvrm beta
Media Player (with version info)all players, main drivers / kodi ds / mpc-hc
Splitter (with version info)lav 0.74.1
Decoder (with version info)lav 0.74.1
DecodingDXVA2 Copyback
Deinterlacingnone (progressive)
DXVA2 Scaling Activeno
Aero / Desktop CompositionOff
Problem occurs with modeall modes
GPU ManufacturerAMD
GPU ModelMSI amd rx 5700 8gb oc
GPU Driver Version19.12.3
Attached Files

- Relationships

-  Notes
(0002612)
mclingo (reporter)
2020-01-09 17:16

Hi, just some more info on this from user DMU on doom9, this is a support request he sent in to AMD which I dont think he's had a reply on yet, just thought it might be useful to you in case you had any ideas on a workaround as going forward its likely all new AMD will have this bug of this generation and it hasnt been fixed for months, so might not get fixed.



Hi there.
You have entered support for HDR mode. The agsSetDisplayMode() function used to set a specific display in HDR mode, does its job perfectly: it sends metadata to the display device, which is defined in section 6.9 «Dynamic Range and Mastering InfoFrame» according to Table 5 of the CTA-861 standard. But in the same Table 5 there is also «Auxiliary Video Information (AVI)» defined in section 6.4. And all display devices are required to use the color space (colorimetry) from this data section (AVI InfoFrame) for the current video signal.
Suppose we are in SDR mode with the standard sRGB color space. And we want to switch to the HDR mode with the BT.2020 color space, which is the main one for this mode. By calling the agsSetDisplayMode() function, we put the display device in HDR mode. And we see distorted or unsaturated colors. This is because the display device did not receive the corresponding flag from the GPU in the AVI InfoFrame and is trying to display our BT.2020 color space in its sRGB.
Please tell me, do you think that such HDR support in AGS_SDK is sufficient? If yes, then advise what else needs to be done so that the display device passes into the correct color space when activating the HDR mode using AGS?

- Issue History
Date Modified Username Field Change
2019-12-21 14:27 mclingo New Issue
2020-01-09 17:16 mclingo Note Added: 0002612


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker