madshi bug tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000547madVRbugpublic2018-03-11 18:242018-03-28 12:21
Assigned Tomadshi 
StatusclosedResolutionno change required 
PlatformwindowsOSwindowsOS Versionwindows 10
Summary0000547: incorrect colour output for calibraion off setting in MADVR with AMD RX cards
DescriptionWhen calibation off is set in MADVR i'm getting blown out reds.
Steps To ReproduceTo achieve this DIRECT3D has to be enabled, as does 10 bit on GFX card, here are some results of some tests I did.

AMD control panel - MADVR - result
8 bit 442 8 bit ok
8 bit 442 10 bit ok
10 bit 442 10 bit blown reds
10 bit 442 8 bit ok
8 bit 444 RGB 8 bit ok
8 bit 444 RGB 10 bit blown reds
Additional Informationworkaround for now would be to disabled DIRECT3D11 but this means no HDR playback, however i've discovered that setting up a calibration corrects the colour, i'm using DCI-P3 with BT709 2.20 curve.
TagsNo tags attached.
madVR Versionall latest versions
Media Player (with version info)all players
Splitter (with version info)n/a
Decoder (with version info)n/a
DecodingDXVA2 Copyback
Deinterlacingnone (progressive)
DXVA2 Scaling Activeyes
Aero / Desktop CompositionOff
Problem occurs with modeall modes
GPU ManufacturerAMD
GPU ModelAMD RX 550
GPU Driver Versionlast 5 latest versions tested
Attached Files

- Relationships

-  Notes
mclingo (reporter)
2018-03-28 02:15

more info on this. If I put my TV in PC mode this problem goes away.

if I play movies at 60hz this problem goes away

if I turn off use DIRECT3D11 in MADVR it goes away

it appears that a high colour gamut is being applied to 23p movies when calibration is set to OFF, however there is no calibration settings which fix this, BT2020 seems to be the nearest but my TV is nearer to DCI-P3 which still looks too red.

I've put a workaround in place, two profiles, one for HDR and one for SDR, HDR requires DIRECT3D11 turned on to work and there are no colour issues with it so I can just invoke the SDR profile for non HDR material with this unticked.
mclingo (reporter)
2018-03-28 02:16

just to confirm again, this does not affect NVIDIA card I dont think, I didnt get chance to thoroughly test that though.
madshi (administrator)
2018-03-28 10:33

Try switching your display output bitdepth to 8bit when using D3D11. Does the problem then also go away?

From all the information here, it seems to be a GPU driver problem to me. So there's probably nothing I can do to fix this.
mclingo (reporter)
2018-03-28 11:55

Hi, I tried that, that didnt work, I also went back to s drive that was nearly two years old and that didnt work either, not sure where to do with this at all.
madshi (administrator)
2018-03-28 11:58

Well, I suppose then your workaround is the best way to go right now. Alternatively you could try reinstalling the GPU driver, with cleaning out of all GPU driver settings, and then make sure all the GPU driver color controls are set to neutral values or to "application controlled".
mclingo (reporter)
2018-03-28 12:18

Hi, the odd thing is I went back to august 2016 versions of MADVR and AMD drievrs and it still had the problem.

the oddest thing for me is it only happens @23,976 hz, if I turn off refresh rate switching and play the movies at 60hz its fine, its like a higher colour gamut is being invoked when DIRECT3D11 / 23hz is enabled.

its also odd that it doesnt happen if my TV is in PC mode.

But yeah, if it doesnt happen with NVIDIA cards it must be a driver issue but then again it only does this with MADVR, no other renderers have this issue, EVR, VLC, stock KODI all play fine.
madshi (administrator)
2018-03-28 12:21

There's probably a technical reason why it occurs with madVR but not with EVR, VLC and Kodi, e.g. fullscreen exclusive mode, or 10bit output or something similar. Anyway, if it occurs with 23.976 but not with 60.000 then it CANNOT be madVR's fault, because madVR does not change its rendering at all based on refresh rate.

So I'm closing this bug report, because I don't see how it could be a bug in madVR.

- Issue History
Date Modified Username Field Change
2018-03-11 18:24 mclingo New Issue
2018-03-28 02:15 mclingo Note Added: 0002248
2018-03-28 02:16 mclingo Note Added: 0002249
2018-03-28 10:33 madshi Note Added: 0002250
2018-03-28 10:33 madshi Assigned To => madshi
2018-03-28 10:33 madshi Status new => feedback
2018-03-28 11:55 mclingo Note Added: 0002251
2018-03-28 11:55 mclingo Status feedback => assigned
2018-03-28 11:58 madshi Note Added: 0002252
2018-03-28 11:58 madshi Status assigned => feedback
2018-03-28 12:18 mclingo Note Added: 0002253
2018-03-28 12:18 mclingo Status feedback => assigned
2018-03-28 12:21 madshi Note Added: 0002254
2018-03-28 12:21 madshi Status assigned => closed
2018-03-28 12:21 madshi Resolution open => no change required

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker