Log in

View Full Version : madVR - high quality video renderer (GPU assisted)


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 [1157] 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329

cork_OS
19th November 2019, 18:59
If you add "hdr=on" or "transfer=hdr" to the file name you'll get passthrough even using ffdshow. :D

I confirm it. I'm watching 4K HDR movies using MPC-HC+SVP+madVR thanks to this trick.
It would be better if madshi will add a hotkey to force HDR mode passthrough though.

mclingo
19th November 2019, 20:25
Yes it is clear. But how then to change the bitdepth of the output of the madVR depending on the HDR? This is necessary for owners of AMD video cards, as their API does not support HDR with 8 bits.

where would you come accross an 8bit HDR movie though?

DMU
19th November 2019, 20:48
maybe he will update the AGS which has been updated according to "user" feat back so it may support 8 bit finally.
This is sad. Now there is already the ability to dynamically control the Windows HDR switch using DXGI. So, there is no particular need for the use of the HDR private API's.

where would you come accross an 8bit HDR movie though?
8 bit output needed for SDR content. But profiles for switching between HDR and SDR do not work. I gave the link above (http://bugs.madshi.net/view.php?id=611).

huhn
19th November 2019, 21:18
where would you come accross an 8bit HDR movie though?

where did you come accross a 10 bit RGB source?

Devrim
19th November 2019, 21:50
Does anyone here use MadVR on Windows 10 LTSC? Are there any issues with it?

redbtn
20th November 2019, 00:03
Does anyone here use MadVR on Windows 10 LTSC? Are there any issues with it?I use. No issues whatsoever

mclingo
20th November 2019, 01:40
This is sad. Now there is already the ability to dynamically control the Windows HDR switch using DXGI. So, there is no particular need for the use of the HDR private API's.


8 bit output needed for SDR content. But profiles for switching between HDR and SDR do not work. I gave the link above (http://bugs.madshi.net/view.php?id=611).

i'm probably just misunderstanding what you are saying. Are you saying that MADVR is failing to recognise and switch to a HDR profile based on bit rate on AMD cards due to an API issue with HDR?

I tried creating a HDR profile ages ago and couldnt not get it work but I decided I didnt need it anyway so I havent looked at it again until now. I'm looking at it again now as I'm trying to get my processing below 30ms with tone mapping and using NGU AA on my RX580.

i'm pretty close now with these settings, can anyone recommend any other tweaks to give me a few exta miliseconds?

https://1drv.ms/u/s!AgvFafeelEBigqsK8zfvy9NX8SPe_g?e=Kthzck

huhn
20th November 2019, 03:07
the card it self has nothing to do with this it's the bad API from AMD that is related but the bug is in madVR. and the bug is that the properties are ignored in profiles when "HDR" is used for a check but work if bitdepth are used for the check.

if AMD would work with 8 bit he wouldn't need an profile because he would just use 8 bit (which was been proven to be better for consumer TVs over and over again) but that's not possible because the API is super limited.

all this doesn't change that there is a bug in madVR.

Alucard777
20th November 2019, 08:52
At some stage madshi was looking to add support for this but it will either happen in 5-10 years or not at all. I asked pinterf about 10bit parsing/support in ffdshow but he's too busy for this. Honestly I hold no hope of this ever being done in the 2020s if at all.

thank you for your replay & hopefully madshi will add it asap


If you add "hdr=on" or "transfer=hdr" to the file name you'll get passthrough even using ffdshow. :D

i kinda knew this trick ;)
https://www.svp-team.com/wiki/SVP:4K_and_HDR
, but i wanted something more easier :) , thank you any way

justnobody
20th November 2019, 09:01
question about HDR tone mapping, for monitor without HDR support, but with DCI-P3

I bought a 32" monitor and found out they just rolled out a newer model (like under same price lol), both no HDR supported, meaning 300cd/m2 max, but the newer added DCI-P3 gamut, they are basically the same panel but the later one has the DCI-P3 option (92%) besdies sRGB etc.

my question: the monitor I bought which is the older one, no DCI-P3 menu

when we enable the tone mapping, what if a monitor that can enable DCI-P3 in the menu (in monitor's own menu), will it get better result, than the old one, bascially the same panel?

DMU
20th November 2019, 09:05
the bug is that the properties are ignored in profiles when "HDR" is used for a check but work if bitdepth are used for the check.

Exactly! Thanks for explaining my bad English.
By the way, this bug allows you to set the bitdepth of dithering other than the bitdepth of the madVR output. For example, you can do 8-bit dithering, but transfer the necessary 10 bit stream to AMD API (AGS) for the correct output of HDR, if I'm not mistaken. The statistics window show this.

nsnhd
20th November 2019, 13:50
question about HDR tone mapping, for monitor without HDR support, but with DCI-P3

I bought a 32" monitor and found out they just rolled out a newer model (like under same price lol), both no HDR supported, meaning 300cd/m2 max, but the newer added DCI-P3 gamut, they are basically the same panel but the later one has the DCI-P3 option (92%) besdies sRGB etc.

my question: the monitor I bought which is the older one, no DCI-P3 menu

when we enable the tone mapping, what if a monitor that can enable DCI-P3 in the menu (in monitor's own menu), will it get better result, than the old one, bascially the same panel?

My SDR 32" monitor might reach 95% DCI-P3 after calibration, and does not have any menu settings.
So I guest you can try to change madVR settings for DCI-P3 in calibration tab to see if it can get some color enhancement.

Magik Mark
20th November 2019, 16:02
Can someone share the best way to watch HDR via madvr in LG C9?

What is the optimum setting?

Any solution on too bright subtitle using xysubfilter and asssubfilter? How do we dim this?



Sent from my iPhone using Tapatalk

SamuriHL
20th November 2019, 16:08
There's a reason "best" kind of posts are not generally considered useful. The settings for HDR are subjective. HDR in madvr is a rather complicated topic right now because the last official release is well over a year old now and doesn't have any of the enhancements to HDR that's been done in the test builds since that time. And those changes are nothing short of remarkable. There's a lot to set up and configure because they are test builds that are designed to test various parameters of the new Histogram Tone Mapping algorithm. People have posted screen shots of their various settings for different display types in the madvr test build thread on AVS. Find one that matches your C9 and start there. But this is not a "flip a couple switches and you get the absolute best quality" kind of thing right now. It'll get there, but, everything is in flux with the test builds.

tyguy
21st November 2019, 17:54
I have i7 7700k and a geforce 2070 super using the latest game ready drivers and the playback isn't smooth on my lg c9 in madvr despite the low rendering times. I'm using full screen exclusive and I keep vsync activated globally in the nvidia control panel. Is anybody else having issues with rtx cards with the latest game ready drivers?

Klaus1189
21st November 2019, 19:01
There was already an issue with LG C9, but not about "smoothness", but about wrong blacks, see also here:
AMD, Intel and Nvidia driver issues and last recommended version (https://forum.doom9.org/showthread.php?t=176013)
click link for more info in line of 441.20.

But there was/is also a stutter issue with RTX cards, for the workaround see the second Note before Nvidia driver history. Hope it helps ;)

tyguy
21st November 2019, 19:45
There was already an issue with LG C9, but not about "smoothness", but about wrong blacks, see also here:
AMD, Intel and Nvidia driver issues and last recommended version (https://forum.doom9.org/showthread.php?t=176013)
click link for more info in line of 441.20.

But there was/is also a stutter issue with RTX cards, for the workaround see the second Note before Nvidia driver history. Hope it helps ;)
Yeah, they fixed the black issues on the latest game ready drivers. I'll try out those settings in nvidia inspector when I get home and report back. thanks!

Someone else suggested using dx 11 native instead of nvenc, which doesn't make much sense to me.

"Set your video decoder to D3D11 Native (Automatic)."

huhn
21st November 2019, 20:14
cuvid is not in an optimal state it currently has no real advantages over dxva2 copyback but disadvantages.
nev had some ideas with it that would be really cool but that doesn't mean he will do it.

Klaus1189
21st November 2019, 20:25
What ideas?

tyguy
21st November 2019, 20:49
cuvid is not in an optimal state it currently has no real advantages over dxva2 copyback but disadvantages.
nev had some ideas with it that would be really cool but that doesn't mean he will do it.

Okay, ill go back to using dxva2 copyback I was using that with amd, I thought I was suppose to use cuvid with nvidia cards.

huhn
21st November 2019, 21:10
What ideas?

kinda like a d3d11 native with cuvid it's been a while and i don't known if he tested it if he still thinks it maybe worth it but that would be the best decoder available with just one major issue.

it's not worth it if i talk about it.

shimarin
22nd November 2019, 08:26
What are the minimum GPUs required from both Nvidia and AMD that can do NGU image upscaling from 1080p to 4K?

tyguy
22nd November 2019, 09:19
The suggestions helped for smoother playback and even lowered my render time a bit. I still get 1 repeated frame every 8 minutes or so, but I’m getting no dropped frames.

Is repeated frames something we just have to deal with or are we suppose to get 0 repeated and dropped frames for an entire film?

mclingo
22nd November 2019, 11:40
What are the minimum GPUs required from both Nvidia and AMD that can do NGU image upscaling from 1080p to 4K?


most if not all 4k HEVC GPUs can do this, it depends on lots of factors, too many to mention. If you want to throw default MADVR settings at a full bluray 1080p remux with NGU AA every card will play the movie but some will run hot and loud.

If you are on a budget i'd reocmmend a used GTX 1060 or a RX580/590.

The GTX 1060 is a better performer in NGU so if you are not playing 3D MVC movies this is probably the better choice.

The new AMD 5700 or XT is the best current choice for AMD users who need 3D but if you are on a budget look for a used RX580, this is what I am used, I can use NGU AA at medium and also do a bit of tone mapping keeping rendering time around 30ms, however I more than often run it at LOW to keep the noise down as my card can be quite loud,

Like gaming, the more you spend the better the card will be, just throw as much as you can at the GPU and then tweak it to get the most out of it.

ryrynz
22nd November 2019, 11:44
Is repeated frames something we just have to deal with or are we suppose to get 0 repeated and dropped frames for an entire film?

This is normal and not the result of render times. Either you use Smooth Motion or you match the refresh rate of your display as close as possible to your source content using madVR's 'custom modes' menu within 'display modes' under 'devices'

oldpainlesskodi
22nd November 2019, 11:54
Have to say, looking forward to the next public/official release - Neo-XP's latest curve over at AVS is quite phenomenal.

tyguy
22nd November 2019, 16:45
This is normal and not the result of render times. Either you use Smooth Motion or you match the refresh rate of your display as close as possible to your source content using madVR's 'custom modes' menu within 'display modes' under 'devices'


Isn’t this something variable refresh rate should be able to fix? I’m using a c9 with a GeForce 2070 super, and I have variable refresh rate working through “gsync compatibility.”

Of course my card can only do 60 hz at 4K since no hdmi 2.2 output, but shouldn’t this fix it when we have hdmi 2.1 cards?

huhn
22nd November 2019, 17:02
madVR doesn't support it(it''s complicated for video).
the VRR ranges is another problem. at a resolution with 120 hz support it should be fine but at UHD 60 is utterly useless because it can't do LFC making it very hard to get a video into the VRR range.

tyguy
22nd November 2019, 17:44
madVR doesn't support it(it''s complicated for video).
the VRR ranges is another problem. at a resolution with 120 hz support it should be fine but at UHD 60 is utterly useless because it can't do LFC making it very hard to get a video into the VRR range.

Yeah, the range on my tv is 40-120 hz. Xbox will do lfc at 20-30 fps because that doubles from 40-60 hz.

I dont think nvidia will do that though so I would have to drop to 1440p if I wanted full range (atleast until hdmi 2.1 graphic cards come out).

You would think using dx11 native would just engage variable refresh rate.

This seems like the ultimate solution to the repeated frames problem. This guide I read said your card can only output 8 bit in madvr if you use custom modes... Which seems far from optimal.

huhn
22nd November 2019, 18:08
Yeah, the range on my tv is 40-120 hz. Xbox will do lfc at 20-30 fps because that doubles from 40-60 hz.
the xbox can't do 120 hz uhd it does it at 1440p or 1080p and then this feature will work.

You would think using dx11 native would just engage variable refresh rate.
it's not that easy in my experience it is blocked and it's planned to be blocked for fixed FPS games too a video is part of this category too. this doesn't make sense to me 144 hz is very common and 60 fps at 144 is just bad but totally fine with g-sync.

and g-sync for video is very complicated it's not a game where A/V sync doesn't exist. audio that "need" sync in games is usually only a couple of secs so it doesn't matter and the sync of BGM is irrelevant. but for movie playback you have to sync an video to an hour or longer audio stream it not build for that.

to properly use that madVR needs to measure the difference between audio and video clock fix this using the system clock. yeah lot of fun.
This seems like the ultimate solution to the repeated frames problem. This guide I read said your card can only output 8 bit in madvr if you use custom modes... Which seems far from optimal.

you mean better for lg oleds.

tyguy
22nd November 2019, 18:16
the xbox can't do 120 hz uhd it does it at 1440p or 1080p and then this feature will work.

you mean better for lg oleds.I read somewhere if you set your xbox to 4k 60 it will still do LFC on 30 fps titles that dip below 30 fps since 25-30 doubles into samsungs vrr range. Well, im assuming the 2020 and beyond lineup of tvs will start to feature hdmi 2.1 from every manufacturer. So it wont just benefit lg oled.

ryrynz
22nd November 2019, 20:03
So it wont just benefit lg oled.

You can edit down quotes so they don't take up more forum space than your reply. Full quotes are not required most times. Cheers.

tyguy
22nd November 2019, 20:34
You can edit down quotes so they don't take up more forum space than your reply. Full quotes are not required most times. Cheers.
I posted it on the phone which makes it more difficult.

ryrynz
22nd November 2019, 20:42
I feel that. Missing the [ is a common occurrence for me on the first reply. The bigger the quote the more meaningful it is though imo.

Asmodian
22nd November 2019, 20:50
This seems like the ultimate solution to the repeated frames problem. This guide I read said your card can only output 8 bit in madvr if you use custom modes... Which seems far from optimal.

Why? On LG's OLEDs 8 bit has less banding than 10 bit when in PC or Game mode. 8 bit is more optimal than 10 bit.

I still think VRR support in madVR would be useful. Playback wouldn't be as good as a tuned fixed refresh rate but we wouldn't need to worry about refresh rates at all. madshi is less interested simply because it is going to be worse. I think the minor judder from imperfect presentation timing would be fine, way better than 23fps at 60 Hz, and audio sync is pretty easy if having all frames presented for the exact same amount of time is not considered too important. Simply adjust the frame times a tiny bit as you go to maintain sync.

madVR is all about quality so spending a bunch of work to get VRR support for gaming monitors to support a slightly worse playback mode was not reasonable. However, now that TVs are getting VRR too it might be more reasonable to look into it? Probably not. :o

huhn
22nd November 2019, 20:55
the problem is someone has to write the code for this and how do you even say the GPU this frame 0.5 ms later plz?

want to handle everything with chrono?

tyguy
22nd November 2019, 21:14
Why? On LG's OLEDs 8 bit has less banding than 10 bit when in PC or Game mode. 8 bit is more optimal than 10 bit.


I'm only using 8 bit color depth in madvr because im using rgb full 8 bit in my nvidia drivers and nvidia wont switch to 10/12 bit when it drops the refresh rate.

I dont label my hdmi input anything. I just keep it to default hdmi 1. With 8 bit I haven't noticed any banding. I will be getting a new card when 2.1 cards come out though. So ill be running my desktop at 4k 120 hz rgb full 10/12 bit.

Would there be an issues if I set madvr to 8 bit, but im using 10 or 12 bit with my nvidia drivers?

Asmodian
23rd November 2019, 04:17
I dont label my hdmi input anything. I just keep it to default hdmi 1. With 8 bit I haven't noticed any banding.

Using the default HDMI input the TV will convert to YCbCr 4:2:2 internally. This blurs the color information horizontally. Both color planes are resampled to 1920x2160 by the TV. This does eliminate banding with 8 or 10 bit RGB input but the image is blurred. I hope you are using very low power chroma scaling options because anything better is pointless.

Would there be an issues if I set madvr to 8 bit, but im using 10 or 12 bit with my nvidia drivers?

No issues except being totally pointless, why set Nvidia drivers to anything but 8 bit? There is absolutely zero improvement in quality on an LG 7/8/9 when sending it 10 bit instead of 8 bit when using any HDMI option, and 10 bit is worse quality when using PC or Game mode.

Ideally you want to send an LG C9 8 bit YCbCr limited range using the PC or game HDMI mode. Anything else either has banding or blurs the chroma. If you set the drivers to YCbCr limited set madVr to full range output.
gradient-perceptual-v2.1 24fps.mkv (http://www.mediafire.com/file/z1f4ahg3784lfwz/gradient-perceptual-v2.1_24fps.mkv/file)
gradient-perceptual-colored-v2.1 24fps.mkv (http://www.mediafire.com/file/4dia3lixs0n9xyo/gradient-perceptual-colored-v2.1_24fps.mkv/file)

I know 10 bit sounds cool but it really is pointless at best on an LG OLED. I will be using 8 bit YCbCr limited range 3840x2160 @ 120 Hz on my LG C9 when I get an HDMI 2.1 GPU unless I get a new TV that is not so bad with RGB full input. :mad:

YukonTrooper
23rd November 2019, 07:59
My aspect ratio for HDR files is broken using MadVR in any player. The film area is off-center and stretched. Playback without MadVR OK. Any ideas?

huhn
23rd November 2019, 08:53
you could start with a screen of the OSD (control+j).

tyguy
23rd November 2019, 09:02
Using the default HDMI input the TV will convert to YCbCr 4:2:2 internally. This blurs the color information horizontally. Both color planes are resampled to 1920x2160 by the TV. This does eliminate banding with 8 or 10 bit RGB input but the image is blurred. I hope you are using very low power chroma scaling options because anything better is pointless.







No issues except being totally pointless, why set Nvidia drivers to anything but 8 bit? There is absolutely zero improvement in quality on an LG 7/8/9 when sending it 10 bit instead of 8 bit when using any HDMI option, and 10 bit is worse quality when using PC or Game mode.



Ideally you want to send an LG C9 8 bit YCbCr limited range using the PC or game HDMI mode. Anything else either has banding or blurs the chroma. If you set the drivers to YCbCr limited set madVr to full range output.

gradient-perceptual-v2.1 24fps.mkv (http://www.mediafire.com/file/z1f4ahg3784lfwz/gradient-perceptual-v2.1_24fps.mkv/file)

gradient-perceptual-colored-v2.1 24fps.mkv (http://www.mediafire.com/file/4dia3lixs0n9xyo/gradient-perceptual-colored-v2.1_24fps.mkv/file)



I know 10 bit sounds cool but it really is pointless at best on an LG OLED. I will be using 8 bit YCbCr limited range 3940x2160 @ 120 Hz on my LG C9 when I get an HDMI 2.1 GPU unless I get a new TV that is not so bad with RGB full input. :mad:


Where did you get the information about the tv internally doing Ycbcr 422? I thought in Windows you always want to use rgb because windows will just convert ycbcr to rgb?

Also, why is my Apple TV able to do 10 bit without banding, but my windows pc can only send it 8 bit dithered or else I get banding?

Finally, why would I set madvr to full if I’m using limited and have my TV set to low hdmi black level?

I’ve seen a lot of conflicting information out there. It’s hard to know what to believe.

Asmodian
23rd November 2019, 11:09
Where did you get the information about the tv internally doing Ycbcr 422? I thought in Windows you always want to use rgb because windows will just convert ycbcr to rgb?

It is easy to test for yourself. With ChromaRes.png (https://www.mediafire.com/view/40a9jrk3q03s7gk/ChromaRes.png/file) you can test which modes use 4:2:2 or 4:4:4. View this image at 100% scaling, i.e. in a window on a 4K screen, and switch between hdmi and pc modes. With the gradient test patterns I linked above you can verify all of what I have said. :)

Windows will always render in 8 bit RGB but if you set the GPU to YCbCr it converts everything to YCbCr. madVR always outputs RGB too.

Also, why is my Apple TV able to do 10 bit without banding, but my windows pc can only send it 8 bit dithered or else I get banding?

Because you have your HDMI port in the default mode, also the Apple TV is sending subsampled limited range YCbCr so this isn't really a problem. However, madVR with 8 bit output and the GPU converting to 8 bit YCbCr 4:4:4 is higher quality.

Finally, why would I set madvr to full if I’m using limited and have my TV set to low hdmi black level?

Because limited in the GPU drivers means "convert the full range RGB into limited YCbCr." If you set madVR to limited range too you get double limited because the GPU always converts, it has no way to know madVR is sending limited range.

The reason madVR has a setting for limited range is because if you only care about madVR and don't mind if everything else in Windows is wrong you can set madVR to limited and the GPU to full range. This results in the same image but without the GPU converting ranges. I care about everything else too, and the drivers still need to convert the RGB to YCbCr anyway, so I use limited range in the GPU and full in madVR.

Also, what is ideal in principle and what is ideal in real life with an LG 2019 OLED is not the same thing. :(

tyguy
23rd November 2019, 11:43
It is easy to test for yourself. With ChromaRes.png (https://www.mediafire.com/view/40a9jrk3q03s7gk/ChromaRes.png/file) you can test which modes use 4:2:2 or 4:4:4. View this image at 100% scaling, i.e. in a window on a 4K screen, and switch between hdmi and pc modes. With the gradient test patterns I linked above you can verify all of what I have said. :)

Windows will always render in 8 bit RGB but if you set the GPU to YCbCr it converts everything to YCbCr. madVR always outputs RGB too.



Because you have your HDMI port in the default mode, also the Apple TV is sending subsampled limited range YCbCr so this isn't really a problem. However, madVR with 8 bit output and the GPU converting to 8 bit YCbCr 4:4:4 is higher quality.



Because limited in the GPU drivers means "convert the full range RGB into limited YCbCr." If you set madVR to limited range too you get double limited because the GPU always converts, it has no way to know madVR is sending limited range.

The reason madVR has a setting for limited range is because if you only care about madVR and don't mind if everything else in Windows is wrong you can set madVR to limited and the GPU to full range. This results in the same image but without the GPU converting ranges. I care about everything else too, and the drivers still need to convert the RGB to YCbCr anyway, so I use limited range in the GPU and full in madVR.

Also, what is ideal in principle and what is ideal in real life with an LG 2019 OLED is not the same thing. :(

I actually don’t have my Apple set in default mode. It’s hooked into my receiver which I have labeled “home theatre” in the input section. Maybe that’s the same as default hdmi, but I can always just label that game console or pc as well and see if I can notice banding.

I don’t think you can get wide color gamut from a console or Apple TV without sending the tv 10 bit because they don’t do dithering.

If Windows is converting ycbcr to rgb and madvr only outputs rgb....Why not just use rgb 8 bit limited instead of ycbcr 422?

el Filou
23rd November 2019, 12:06
Because the LG's processing of RGB input is of lower quality.

DMU
23rd November 2019, 13:32
Because the LG's processing of RGB input is of lower quality.
@Asmodian
And the output at 60Hz@RGB@PCMode does not solve the issue's on LG OLED?

mclingo
23rd November 2019, 16:42
It is easy to test for yourself. :(


hi, this issue with LG OLEDS, its quite confusing,, there is a lot to take on here and some conflicting information to what ive been given in the past. Firstl, does it extend to older models, i have gen 1.0 EF950v, i've never noticed any banding to be honest, my current setup is as follows:

HDMI 1 selected, lleft it named HDMI 1
Expert 1 profile set to HIGH colour space
AMD RX 580 running at 4:4:4 FULL RGB set to 8 bit in graphica settings
MADVR set to 0-255

everything looks fine to me, however I do have an issue if I use the actual "PC" HDMI input setting, SDR is fine but no matter what I do HDR is massively washed out and gamma is all messed up, nothing i do corrects this, I dont use PC mode anyway though as I use a tiny bit of smooth motion which greatly improves bright panning shots without any artefact or soap opera effects.

Are you suggesting I should be runniing my panel in PC mode and at YBCR limted mode, what should I actually see on that chroma res pattern, I see 442 clearly but I can also see 444 albeit fiently.

I dont see any banding in either of those movies, gradients and pretty smooth.

Stef2
23rd November 2019, 17:38
I would like to hear from madvr users with a projector and an anamorphic lens.

I just bought such a lens and when I enable the anamorphic option in madvr (4/3 vertical stretch in my case) the rendering time goes up quite a lot, increasing from 36ms average to 55+ms average after the stretch...

Of course, that makes my 4K HDR 24p movie unwatchable :(

The only way I gan get the rendering time back to below 40ms is by disabling completely any HDR processing in madvr, but that deteriorates the projected image a lot, of course. Decreasing luma and chroma upsampling quality by a lot is not enough. Decreasing dithering quality is not enough. Enabling every "trade quality for performance" option over all that that is not enough...

My GPU is a GTX 1070. I do not mind upgrading it to a RTX 2080 if this is what I will need.

Is there any anamorphic lens user around here? what do you observe when enabling this option? Any RTX 2080 user can help me by observing the difference in rendering time between no stretch and anamorphic stretch enabled in madvr.

Any input is welcome!
Thank you.

Asmodian
23rd November 2019, 22:19
I actually don’t have my Apple set in default mode. It’s hooked into my receiver which I have labeled “home theatre” in the input section.

Yes, Home Theatre is the same as the default, it subsamples the chroma.

If Windows is converting ycbcr to rgb and madvr only outputs rgb....Why not just use rgb 8 bit limited instead of ycbcr 422?

Windows is not converting YCbCr to RGB. :confused:

The GPU driver is converting the RGB from both Windows and madVR to YCbCr. Do NOT use YCbCr 422! That would be subsampling the chroma in the GPU driver instead of the TV. :p

If you are asking why the TV uses YCbCr 422 internally it is because TV manufactures are too cheap to get decent video processing chips. YCbCr 422 only takes 2/3 of the bandwidth of YCbCr 444 so they do not need as capable of hardware.

In the Nvidia drivers I cannot set limited range RGB anymore so I did not test limited range RGB (that isn't really a standard either). Better to use YCbCr as always limited and RGB as always full range. The TV is expecting YCbCr limited range input because that is what Apple TV, bluray players, etc. will send it. LG got it working reasonably well for that but they seem to not care about the quality of full range RGB input.

@Asmodian
And the output at 60Hz@RGB@PCMode does not solve the issue's on LG OLED?

The refresh rate does not change the banding with RGB input in PC/Game mode in anyway but it does solve the issue with judder with any non-60Hz input while in PC mode. I always use 60 Hz with smooth motion now. Once in PC mode (so we get full resolution color) these TVs are pretty finicky and only seem to handle 8 bit YCbCr 444 limited range 60 Hz input well. :(

Asmodian
23rd November 2019, 22:31
the problem is someone has to write the code for this and how do you even say the GPU this frame 0.5 ms later plz?


Yes, of course it is work for madshi that does not improve the quality in any ideal scenarios. This is the best reason for it not to exist.

But it isn't that hard to decide what to do (coding it is another issue), simply wait 0.5 ms and then present the frame. I probably cannot tell if a frame is 0.5 ms early or late anyway and the even smaller inaccuracies due to Windows scheduling are even less important. As long as the player is presenting the frames close to when it should audio sync is a non-issue. If this would be better than smooth motion at 60 Hz I don't know, I am pretty happy with smooth motion already so I am not sure it is worth the effort. However, as it is now I need to manually turn off VRR when I switch from gaming to watching video. :p

HDMI 1 selected, lleft it named HDMI 1

Nothing I said applies if you let the TV subsample chroma (e.g. do not use the PC HDMI setting).

Also, use the banding test patterns to judge banding. I do not see obvious banding with normal content except very rarely. I also don't know about models that old, I have only tested the C7 and C9 myself.

HDR tone mapping is obviously worse quality on my display when in PC/Game mode, I really wish LG did not subsample chroma in their video processor. According to my calibration software the gamut is much smaller, which results in less saturated/washed out video but the gamma is still reasonable, not as good, but reasonable. I do switch to Home Theater when watching HDR (rare for me).

DMU
23rd November 2019, 23:11
The refresh rate does not change the banding with RGB input in PC/Game mode in anyway
On my Samsung I notice only 1 issue in PC mode: if the frequency of the HDMI input is not 29/30/59/60Hz, then the TV switches to 422 mode.