madVR - high quality video renderer (GPU assisted)

[Manni]

Odd, my Receiver is reporting 8bit

I'll double check later today and I'll report back.

[mclingo]

In KODI DS player there is full screen, full screen windowed and just windowed, HDR doesnt work in just windowed, has to be full screen or full screen windowed to work, although that didnt for my NVIDA 1050 card either but I havent bothered to try that for months so that must have changed.

Not sure i'f have a use for none full screen mode though.

[brazen1]

Hi folks. I'm humbled to request your help. I know it's off topic somewhat. Please don't rip me new one for asking here. I'm desperate! I've sought confirmations for months in the appropriate forums elsewhere and it fell on deaf ears. I know many of you are testers and perhaps in the same boat, so to speak, and I value your conclusions. Here is the problem and why it's related to madVR somewhat:

Presently using official KODI v.17.6 with external players including MPC players with LAV and madVR and all is well. I want to start using official KODI v.18 and all is not well anymore. I want to present the problem to its bugtracker so it can be addressed before v.18 releases or goes release candidate (RC). I've been using nightlies since the 1st one up to the last.

An nVidia resolution change needs to occur when a 3D MVC frame packed (iso) title is called played via MPC, LAV, and madVR. I use a native refresh rate of 2160p for everything in my full chain 4k setup. Resolution needs to change from 2160p to 1080p for 3D compliance. madVR provides this change as it always has. KODI v.18 crashes when it does. v.17.6 does not and never did. I have no idea if it's my problem exclusively or widespread? No one has been willing to confirm or deny after asking many times, many different ways, in many different threads. So I'm here... begging and infringing.

What is required:
4k display.
nVidia GPU for certain or perhaps an AMD. ( I am unable to determine if other GPU's are affected) Also, I've tried with various drivers which made no difference.
Official KODI v.18 beta or nightly. No amount of settings fiddling made any difference such as fullscreen, windowed, fullscreen windowed, etc.
*note* You do not need 3D capability or even a title for that matter.

How to reproduce:
Open GPU control panel and set native resolution to 2160p. No other settings matter afaik.
Open KODI v.18 and leave it open. (no particular settings required afaik except that the GUI is set to 2160p which will be automatic since it matches GPU setting)
Window or any other method KODI so you can access your open GPU control panel.
Change resolution in GPU control panel to 1080p. You may have to change it back to 2160p before KODI crash happens but I didn't.

Either all is well with KODI and the crash is all my own or you too will notice KODI has resized, the GUI looks primitive, and it is unresponsive leading to a MS error report the moment you try to interact with the GUI.

Sorry to intrude. Please confirm or deny if possible and thank you in advance...
P.S. Reply here if acceptable and/or to thread linked in my signature and thank you again.

[Klaus1189]

turn on logging and scroll through the created file in appdata kodi folder

[brazen1]

Log was 1st diagnostic I did. Nothing to indicate in it. Advanced debug log can't create either. Crashes.

[mclingo]

if you start KODI with your desktop in 1080p mode and setup KODI gui as 1080p does it still crash?

[brazen1]

Of course not but using 1080p with a 2160p chain is not very appealing for desktop use and/or KODI GUI usage. Again, 17.6 works perfectly and always has. V.18 is a different story. Just seeking tester(s) duplicating exactly what I asked so I can submit a bug report on the bugtracker. Without a confirmation, it's futile. To make matters worse, there is only one Windows dev and he doesn't have any 4k test bed afaik. Thanks for your input though...

[mclingo]

I have a bug when using MADVR refresh rate switching from 4k to 1080p when playing MVC 3D stuff, this is why i was asking. Try turning off refresh rate switching in MADVR and have your external player do it maybe?

[brazen1]

I'm using official KODI. DSPlayer has your problem (built on 17.6 which is not version problem for me at all in any way). Turning off refresh rate in official KODI has nothing to do with external player refresh rates, only KODI internal VideoPlayer (which in your case is DSPlayer). Fwiw, I did turn it off/on just for kicks when testing but made no difference. I ran into problems in the past using match refresh rates in MPC external player(s) with no refresh rate control in madVR. Switching to allowing madVR to control them instead of the player(s) worked perfect and always has been since.

The variable here is v.17.6 (working perfect) vs v.18 (problematic). Unless someone actually tests and denies my results. Hoping for a confirmation because if it's my very own problem and not widespread, I will never (fix) my setup because I've no idea what is to blame and will never know tbh.

[iSeries]

or you too will notice KODI has resized, the GUI looks primitive, and it is unresponsive leading to a MS error report the moment you try to interact with the GUI.

I get this sometimes when I close a 4k HDR film, no problem going to HDR but when I close the player (MPC-BE as external player) and go back from HDR to SDR , Kodi (17.6) is resized to a 4:3 format and looks extremely low res with big icons. I have to kill it through task manager and as soon as its killed, the desktop is back to normal. This only happens going from HDR back to SDR, and not all the time. No problem when not using Kodi.

[brazen1]

Fwiw, I don't experience what you have using 17.6. You can see my specs in my sig to compare that might help you. Everything I use is the latest available except GPU driver which is 385.28 although for testing I've tried many others and revert back to 385.28 because all newer drivers introduce specific bugs detrimental to my usage and yours too if you cared. Also try ALT + F4 when closing player instead of letting player auto close (if you are using the setting). Also do exactly the opposite DSPlayer recommends, set KODI to 'use fullscreen' and madVR to use FSE. Problem solved I think. Sounding like others are having issues with 17.6 so v.18 would be out of the question for you guys to test if 17.6 isn't even working correctly for your setups. Maybe others will step up also. Really seeking tester(s) for my description if you are non-problematic with 17.6.

[Manni]

Odd, my Receiver is reporting 8bit

I'll double check later today and I'll report back.

I have no idea why it seemed to work when I tested briefly last night. Although the levels are definitely fixed, the custom res doesn't seem to stick, even after it's been manually enabled. Even when you select 23p manually, the custom res (incorrectly labelled 24p) isn't selected automatically by MadVR anymore. So I do get 12bits, but with the crappy default nVidia refresh rate.

I'm not going to fiddle with drivers every time I reboot, so I'm back to 385.28. :(

[tij]

this is not an osd bug.

the desktop still runs at 60 Hz while the GPU runs at 24 hz.


I am having same problem with this composition rate (not sure when it started … definitely on Windows 1709 never noticed it … noticed it only after 1803).

Was running Win10 1803 (build 17134.254) and GF1070 with 399.07 when noticed the problem. Since then tried 391.35 397.93 398.98 (drivers for which I recall it used to work correctly), but all exhibit same problem (trying to download latest 399.24 now)

So here is summary (both HD and SD material):

FSE: display 29.79, composition 60, D3D11 (10bit)
Fullscreen Windowed: display 29.79, composition 29.8, D3D (8bit)

Reason I start investigating it cause could not get Fullscreen Windowed to output 10 bit (actually if OS HDR is turn on … Fullscreen Windowed does output 10bit … but 3D with OS HDR flickers at low rate … unwatchable)

Using LG OLED E6 that does not show refresh rate … but can guess its probably receiving stated display rate (3D stuff in FSE also shows composition rate of 60, but 3D works … this implies GPU sending 23 to TV … otherwise, TV wont switch to 3D mode since there is no standard that defines 3D at 60 rate)

Also rendering times goes up by around 4ms when in FSE with that weird 60 composite rate (for both 2D and 3D … HD and SD)

I don't think OSD report is wrong too … can move mouse and see cursor but MadVR is still in FSE (bringing play control does drop MadVR to Fullscreen Window though)

What worries me is … Windows 1803 somehow hijack MadVR (reimplemented its api?) … so MadVR writes 23.97 to DWM (desktop window manager) instead of directly to screen … DWM process it at 60 and then outputs to screen at 23.97 … certainly would explain seeing cursor on FSE screen, unless I misunderstand FSE definition completely

[tij]

I am wrong … setting mouse cursor to have trail … and the mouse disappears from FSE … so Windows cannot draw anything on MadVR FSE … at least exclusive is still exclusive

still wonder if MadVR directly send frames to display … or have to pass through that 60fps composition desktop that somehow honors exclusivity mode (ie does not draw anything on FSE and does not allow other apps to do so too)

or maybe in 1709 DWM was temporary suspended when in FSE (so no composition rate can be reported in OSD) … and in 1803 DWM still runs in background (and hopefully allows app that requested FSE to directly write to display)

[thighhighs]

Also rendering times goes up by around 4ms when in FSE with that weird 60 composite rate (for both 2D and 3D … HD and SD)
Compared to windowed mode? Currently windowed mode show wrong and useless OSD, because it broken (by windows update).
Dont care match about FSE if it work fine. Also i hope new madvr build comes soon and 10bit back again for windowed mode.

[el Filou]

I've tried the latest HDR convert/process test build and it is awesome on my plasma.
Previously I had to make a choice between natural skin tones and good highlights and saturated colours and now I can enjoy both. :)

[oldpainlesskodi]

I have no idea why it seemed to work when I tested briefly last night. Although the levels are definitely fixed, the custom res doesn't seem to stick, even after it's been manually enabled. Even when you select 23p manually, the custom res (incorrectly labelled 24p) isn't selected automatically by MadVR anymore. So I do get 12bits, but with the crappy default nVidia refresh rate.

I'm not going to fiddle with drivers every time I reboot, so I'm back to 385.28. :(

Yeah, way to go Nvidia!

Mine is exactly as you described, but, even though the custom refresh is not ticked in the NVCP, using Kodi Dsplayer to do the refresh switching it somehow manages to select it, so I have one drop frame every 1.2 days, but at 8bit.

Maybe one day....

Update: 399.24 is out, but still unable to select custom @ 12bit, but, performance has improved a fair amount, on my set up at least.

Branch Info:
399.07 WHQL: r396_00-312
399.24 WHQL: r399_07-8

[oldpainlesskodi]

@ el Filou - yes, it is very very good....fingers crossed Madshi adds his new detail recovery/sharpening algo selectable for all sources, as I think he has hinted at.

[Axelpowa]

Hi!

I have a doubt about how to downscale UHD the best way.

I run a JVC X7500, but the eshift feature softens the picture a lot, so I decided to set the desktop to 1080p and disable the eshift.

This way and with filters(image enhancements) in madvr I get more sharpness.

The doubt is, is it normal to have to use DXVA for downscaling in madvr? Its the only way, otherwise I get huge rendering times with any other algorithm (jinc, lanzcos, etc....)

My gpu is a gtx1080.

Regards!

[huhn]

check your GPU power setting and make sure it is not set to optimal.

after you did that can you make a screen of the OSD?

[blu3wh0]

I recently upgraded from a 1050 to a 1080 Ti and I started to see some weird performance in the rendering statistics. No matter what settings I choose, max rendering times always seem to spike at times up to 50ms+, but without affecting average times or dropping frames. GPU queue does seem to jump up and down more often than I expected, but setting it at 16 and presentation frames at 8 prevents any kind of impact from that. Also, if I turn on smooth motion, I almost always get consistent presentation glitches every minute or so, again no matter what settings I choose. I know that my GPU is barely using 60% at these times, so I don't understand all this activity. I'm on Windows 10 1803 4K23p with the latest nvidia drivers going through a Denon x3400h to LG OLED B7. One other piece of strange behavior with both nvidia cards is that I can only get 23.980hz presentation at 4K, while 1080p can get a perfect 23.976hz, and no amount of measuring changes this. Does anyone with a 1080 Ti see this type of behavior?

[mclingo]

I recently upgraded from a 1050 to a 1080 Ti

did you definitely create a CRU in madvr for 2160p?

[blu3wh0]

I did, I initially tested it with the 1050 and gave up on it after I realized it could only do 8-bit. The numbers it computed were good, I setup a custom resolution manually with those numbers, but it always stuck to a 23.980hz composition rate (~4 min for repeated frames) at only 4k. I didn't have to do anything for 1080p since nvidia actually uses 23.976hz for that resolution.

[mclingo]

Something isnt right there then, the 1050's can do 10bit, there have been some driver issues though getting 10bit in some situations, I dont know enough about NVIDIA cards though, in fact I didnt think NVIDIA fully supported 23,976 at any res, I knew there were improvements with later drivers but I'm sure you still had to create custom resolutions in MADVR to get decent timings compared to AMD cards.

[blu3wh0]

No, nvidia can only do custom resolutions at 8-bit, but normal configs at 8/12-bit, which is what I use. They fixed timings for 1080p at 23.976hz a few drivers back, but did not fix 4k, leaving that still stuck at 23.980hz for me.

[iSeries]

There are some instructions some pages back on how to use MadVR to optimize timings, and then take those numbers and create a custom resolution with CRU. With the CRU-created custom res, you can switch between 8 bit and 12 bit. I did this and can confirm I can switch between bit depths. However, I can't for the life of me make MadVR switch to this custom res - MadVR switches to the native 23p res, which like you say is more like 23.980hz.

Another problem is even after creating the custom res with CRU, and then going into Nvidia control panel and switching to it and then switching to 12 bit, if you reboot and go back into the control panel, you'll see it has reverted back to 8 bit. Man, Nvidia drivers suck. Seriously thinking about switching to AMD (currently have 1050ti 4gb).

I am not sure why CRU can create a custom res that can switch between bit depths, but MadVR custom res cannot. I guess Madshi is the only one who could answer that one.

[Stereodude]

Its curious that people try to come up with new use-cases while we already had a Neural Network algorithm in madVR before, for image doubling: NNEDI3. Image scaling should be a breeze for the Tensor Cores, considering they are even using that as a gaming feature called DLSS - Deep Learning Super Sampling. Now their algorithm is not going to be quite as high quality as a madVR scaler might be, but it also needs to run on top of 3D rendering and whatnot, so it has to be ultra fast.

A new Neural Network based scaler with more complexity/quality then NNEDI3, but compensating for the low performance of the added complexity by using Tensor Cores sounds like a rather logical step.
madshi posted on AVSforum (https://www.avsforum.com/forum/24-digital-hi-end-projectors-3-000-usd-msrp/2996950-new-jvc-rs3000-nx9-rs2000-n7-rs1000-n5-native-4k-projectors-anticipation-thread-post56728078.html?#post56728078) that NGU sharp is neural network based.
This is actually very near to how madVR's "NGU Sharp" algorithm was designed: It tries to undo/revert a 4K -> 2K downscale in the best possible way. There's zero artificial sharpening going on. The algo is just looking at the 2K downscale and then tries to take a best guess at how the original 4K image might have looked like, by throwing lots and lots of GLOPS on the task. The core part of the whole algo is a neural network (AI) which was carefully trained to "guess" the original 4K image, given only the 2K image. The training of such a neural network works by feeding it with both the downscaled 2K and the original 4K image, and then the training automatically analyzes what the neural network does and how much its output differs from the original 4K image, and then applies small corrections to the neural network to get nearer to the ideal results. This training is done hundreds of thousands of times, over and over again.

Sadly, if a video wasn't actually downscaled from 4K -> 2K, but is actually a native 2K source, the algorithm doesn't produce as good results as otherwise, but it's usually still noticably better than conventional upscaling algorithms.

[tij]

I did, I initially tested it with the 1050 and gave up on it after I realized it could only do 8-bit. The numbers it computed were good, I setup a custom resolution manually with those numbers, but it always stuck to a 23.980hz composition rate (~4 min for repeated frames) at only 4k. I didn't have to do anything for 1080p since nvidia actually uses 23.976hz for that resolution.

I have 1070 (with 2016 LG OLED E6) … it all used to work - 3D, 10bit, HDR … I think 1803 windows 10 update broke it (went back to known working NVIDIA drivers … but it still the same):

1. Fullscreen windowed D3D11 only outputs 8-bit (HDR and SDR)
2. FSE D3D11 outputs 10-bit (HDR and SDR) … but
3. Composition rate is now weird … 23.98Hz for windowed … 60Hz for FSE (which did not have composite rate before)
4. if you turn Windows HDR on … Fullscreen windowed D3D11 will outputs 10-bit … but that will make 3D unusable

However, display rate was 23.97 in all scenario.

Think 1803 made changes to Desktop Window Manager (DWM) … specifically how it behaves when some App start directly access screen through DXGI (intel and amd) or NVAPI (nvidea) … since madVR uses DXGI and NVAPI that pretty much guarantees (theoretically) that madVR directly accesses screen, so reported composite rate is irrelevant (my guess is DWM now leaves composition desktop active in background even though it is bypassed by DXGI and NVAPI … probably in order to go back to it as quickly as possible when needed)

This is all my best educational guess lol

So now I run my stuff all in FSE (used to run in Fulscreen Windowed for a bit faster response)

[kostik]

I have 1070 (with 2016 LG OLED E6) … it all used to work - 3D, 10bit, HDR … I think 1803 windows 10 update broke it (went back to known working NVIDIA drivers … but it still the same):

1. Fullscreen windowed D3D11 only outputs 8-bit (HDR and SDR)
2. FSE D3D11 outputs 10-bit (HDR and SDR) … but

4. if you turn Windows HDR on … Fullscreen windowed D3D11 will outputs 10-bit … but that will make 3D unusable

However, display rate was 23.97 in all scenario.



I think madshi fixed some of the issues in his testing builds and will work when the final build is done.

Try this build for example:
http://madshi.net/madVRhdrRestoreDetails20.zip

[tij]

I think madshi fixed some of the issues in his testing builds and will work when the final build is done.

Try this build for example:
http://madshi.net/madVRhdrRestoreDetails20.zip
Thx ... great work by madshi as usual ... that fix 10bit output in fullscreen windowed for me

Also in OSD, additional info on display (bit depth, full range) is welcome.

Composition rate are still there in FSE, but i dont think madshi can do anything about it ... just the way Windows work now post 1803 (read somewhere that DX12 has no FSE at all now)

[waldnebel]

Is this new HDR to SDR conversion feature of madVR also an option if you have a HDR capable display with a fairly low maximum brightness of say around 300 nits? Might this HDR video look better converted to SDR?

[huhn]

the FSE in windows 10 is simulated

10 bit windowed fullscreen was buggy on nvidia cards so madshi blocked it for nvidia cards so he just removed the block because nvidia fixed it.

source file bit deep information and range information are in the OSD.

[Manni]

I think madshi fixed some of the issues in his testing builds and will work when the final build is done.

Try this build for example:
http://madshi.net/madVRhdrRestoreDetails20.zip

Please do not post direct links to test builds in this thread, especially the latest one.

There seems to be many issues with test build 20 and linking it here might cause a lot of issues and confusion. Please can you delete this link (or at least provide a link to the post where Madshi linked to it, so that people know where to comment if they have issues with it)?

There is a reason why Madshi is doing this experimental work in a separate thread, and hasn't posted a public build yet.

If anyone has any issue with a test build, please post in the appropriate thread in the other forum, not here.

[mclingo]

Is this new HDR to SDR conversion feature of madVR also an option if you have a HDR capable display with a fairly low maximum brightness of say around 300 nits? Might this HDR video look better converted to SDR?

You should not need to do this, my ageing 2015 HDR OLED has very low nits and its generally fine with HDR content, stuff looks better than the original SDR blurays, there is only one exception i've found so far, star trek 2009 looks awful to me. its doesnt map very well on my display at all, skin looks bleached out and highlights are none existent at times, its all a bit yellow too. i've also tried using the HDR to SDR convert instead, still looks bad to me, its either just me or a bad conversion.

[Axelpowa]

check your GPU power setting and make sure it is not set to optimal.

after you did that can you make a screen of the OSD?

Hi,

Managed to solve the issue. Unchecked the enhancements.Now I can use chroma ngu sharp and lanzcos for downscaling. I also can now use again the mpc of my jvc and I get better sharpness.

Would like to use jinc, but it uses a lot of gpu and I get frame drops.

Regards!

[Warner306]

Is this new HDR to SDR conversion feature of madVR also an option if you have a HDR capable display with a fairly low maximum brightness of say around 300 nits? Might this HDR video look better converted to SDR?

It could make sense if you want to watch both SDR and HDR at the same brightness, likely at 300 nits. There is the issue of sharing a color gamut. If your display has a setting to automatically detect the input gamut and display it without a conversion (typically, Auto), it could be a good option. Otherwise, you would have to choose either BT.709 or BT.2020/DCI-P3 as the shared gamut between HDR and SDR. A 3D LUT could also solve this issue.

It also depends on the quality of the tone mapping provided by your display. At 300 nits, you lose a lot of detail through compression that madVR could restore with its highlight recovery setting. Also, some displays can't tone map all pixels with the correct hue. At least, with madVR you always get the correct hue. The image could also be potentially brighter. It depends on the display.

It is definitely worth trying. I would guess madVR would do a better job of tone mapping than a display that dim.

Here are a couple of images that show how highlight recovery strength works:

highlight recovery strength: none (https://www.flickr.com/photos/157142275@N08/30733268368/in/album-72157693495764482/lightbox/)
highlight recovery strength: medium (https://www.flickr.com/photos/157142275@N08/44604195661/in/album-72157693495764482/lightbox/)

This is also an image I made from the latest build that I think looks pretty attractive:

1,000 nits BT.2020 -> 150 nits BT.709 (390 target nits) (highlight recovery strength: medium) (https://www.flickr.com/photos/157142275@N08/43900844724/in/album-72157693495764482/lightbox/)

[Damien147]

What's better for Madvr?10 bit and 4:2:2 or 8 bit and 4:4:4?

[el Filou]

Depends on your display. On most, 8-bit 4:4:4 will be better as long as you use RGB Full (not YCbCr).

[Damien147]

Yes,RGB Full.Thank you.

[Asmodian]

8-bit YCbCr 4:4:4 is not bad either, it is much better than YCbCr 4:2:2 and only very slightly worse than RGB (RGB cannot be subsampled).

4:2:2 means two out of the three image planes are at half resolution, the way humans perceive color is weird so we don't notice all the information loss but the signal does have a lower spacial resolution. Bluring together the color of every two pixels horizontally so you can get some extra steps between color values is not helpful and preserving the dithering at full resolution is important. The exception is when your display uses 4:2:2 internally, then it often isn't any worse to have the GPU do it first. :p

[Damien147]

I was 8 bit full RGB 4:4:4 but some settings made me wonder.Thanks for the info.:)

[YGPMOLE]

To keep the video signal untouched and to avoid unwanted colorspace conversion, I set the LAV Video decoder to output RGB24, madVR range at 0-255 and video driver to full RGB 4:4:4 (as from the F.A.Q.). Works fine for SD and HD 8 Bit videos WITHOUT hardware acceleration (unchecked for SD and HD files).

To watch UHD HEVC 10 Bit videos, I do need hardware acceleration, so I have to uncheck RGB24 8 Bit and output at P010 10 Bit dxva in the LAV video decoder.

In this case, does madVR the P010 -> RGB conversion? It's possible to avoid it (I mean, does exist a way to output RGB 10 Bit directly from the LAV filter)?

[Asmodian]

That is wrong. If you want to avoid unwanted color space conversion do not uncheck any options in LAV. You are forcing LAV to do a color space conversion. The video is not RGB. LAV does not do very high quality conversion to RGB either, since it should only very rarely be used. Leave LAV on defaults or even check every option (assuming you are using madVR). LAV will only do conversions if they are required (or forced by the user), otherwise it will pass the video to madVR completely untouched.

You do not want LAV to covert the P010 to RGB, let madVR do that. madVR is much better at it and this keeps all color space conversions internal to madVR, and in 16 bit.

Sorry to nitpick but "RGB 4:4:4" makes no sense and I don't think any driver has a "RGB 4:4:4" option. :p

[Clammerz]

To keep the video signal untouched and to avoid unwanted colorspace conversion, I set the LAV Video decoder to output RGB24

You are actually doing the opposite of what you want to achieve. You are introducing an unwanted colorspace conversion. You are forcing LAV to upscale the chroma data to match the luma resolution bypassing madVR, so your chrome setting in madVR are having no affect at all.

Leave LAV colorspace options as default.

[Megalith]

I can't figure out why the 3DLUTs I get from DisplayCAL all result in a very dark picture. Source profile BT.709, destination profile default 2.2 Gamma, so it should be pretty straightforward (no HDR). The picture is easier to see on the profile without VCGT applied, though I heard that option should be checked.

[Asmodian]

In an effort to be on topic could you post in Display Calibration (https://forum.doom9.org/showthread.php?t=172783)? :)

[YGPMOLE]

@ Asmodian & Clammerz

Thank you for the explaination!!! I was totally wrong thinking that the first spacecolor conversion was done by the O.S. when MPC-BE is playing the original YCbCr videos, because with LAV in default mode I got YV12 8 Bit output: instead, YV12 is the codec used to read the YCbCr information. My bad (and ignorance).

Asmodian, AMD drivers say RGB 4:4:4 Full RGB pixel format.

[Asmodian]

Asmodian, AMD drivers say RGB 4:4:4 Full RGB pixel format.

Of course they do. :rolleyes: :mad:

What are you doing AMD? :o

[huhn]

what am i missing here?
what is AMD doing wrong here?

[Klaus1189]

Of course they do. :rolleyes: :mad:

What are you doing AMD? :o

agree with huhn, what is wrong?

Driver displays RGB when you force LAV to output as RGB.
So what's the matter?