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

huhn
31st May 2020, 14:14
noise from speaker under load.

Klaus1189
31st May 2020, 14:30
That should be easy to determine, press mute on remote of AVR. If the whine sound is still there, it is coilwhine, right? Do you know what is causing this noise from speaker under load, I think there was something here in the past already, but I can't really remember.

tp4tissue
31st May 2020, 16:02
Coil whine unfortunately can be ALOT of things rolled into one.

It could be a coil/ capacitor/ chock/ resistor/ inductor, etc etc, anything that creates friction(resistance) for electricity can exhibit the piezoelectric effect.

Plugging in different components _TOGETHER_ often changes the situation of how the electricity drains through the device, so it can cause whine that wasn't there if those components were seperate.

This is primarily why OPTICAL is still the cleanest option for PC sound output as it's a form of galvanic isolation.

GPUs/CPUs are resistors, therefore, given the right circumstances, they screech as well.

BetA13
31st May 2020, 22:16
Thank you for all the informative Answers.

@tp4tissue

yes, i did recently change my Hardware.. (upgraded)


@Asmodian

madVR is more likely to cause coil whine. It is a very spiky load, once the queues are full the GPU renders one frame and then idles until it needs to render the next frame. At a 70% load with 24 fps video this means the GPU is using a lot of power for 29 ms then very little power for 13 ms, and repeat forever.

This!!! is exactly what i saw in my GPU stats(afterburner) Its only happening when teh GPU is running with Full Clock speeds, as soonest it clocks down the noise is gone. But its the Speed of the VRAM´s from what i could found out in my testings, GPU clocks do not matter so much in my Case. As soonest the VRAM clocks down, the noise is gone... So its the buffering of teh prerendered frames? Or something like that... Dont know if i sayd that right...

---

Also, i know what Coil WHine is and its coming form the GPU.. NOT the speakers.
Like i sayd, when downclocking the Card, the Coil whine is allmost gone and cant be heard under 40cm...

---

i know what you guys mean about the speakers. i checked them and they are all grounded and do not touch metal with metal, etc etc..
Its only when the GPU is used.. And Coil whine is still present when i unpluged my sound system completly. (also in Hardware Manager disabled)..

I have another GTX980 here, but i need an 6 to 8 pin adapter first before i can Test this Card also..
If it does not have coil whine im gonna keep the GTX980 instead of teh GTX970 STRIX (wich from looking on the Webz, coil whine is kinda common, teh whoel 9series from what i was reading).

@clsid

Maybe madshi could add an option to adjust the queue refill strategy. That could perhaps reduce these kind of side-effects. The queue doesn't strictly need to be nearly full all the time. With a queue of size 8, refill will now happen when it drops to 7. Instead you could wait until it drops to 6 or even 4.

That sounds interessting, is there a way i can test this here? Is that whats causing those "loads" on teh GPU?
I allways thought that the NGU scaler would be one thing that is causing it, and shure enough, when i tested it, NGU did make more noise then Jinc, superXBR did.. So i also settled for SuperXBR for the moment and do not quadruple anymore, since this also caused more noise..


---
But yes, in teh End it looks like thats just the way it is and how a coil/ capacitor/ chock/ resistor/ inductor, etc etc. work...
What i found out, at least for my GPU, is that lowering teh GPU RAM Speed did really help.. So i edited my GPU BIOS a bit, i do not need an OCed Card, so no Biggy for me..

Thanks for all teh Answers here, some good information.....

Best Regards

wasper
1st June 2020, 02:43
Hello,

My display (Sony) calibration was set do "disabled display calibration". When looking HDR content with MADVR the display (Auto detect settings) correctly switched to Bt.2020 and HDR.

But, I recently watched a video that is Bt.2020 non HDR. The Tv Color Space stayed at BT.709. I never noticed that my tv color space didn't switch automatically to the correct color space as 99% of my content is Bt.709. Is it normal that Madvr doesn't sent color space metadata unless HDR. Had to change my calibration to "diaplay is calibrated to BT.709". Doing so, MADVR translate the color space from BT.2020 to BT.709 loosing precious colors during the process but at least the display show accurate color.

Could switch the tv manually to BT.2020 but nobody wants to do that, right?

Asmodian
1st June 2020, 14:06
SDR does not have metadata, so there is nothing for madVR to send. You can keep your display in DCI-P3 and set madVR so it coverts BT.709.

alexantr
2nd June 2020, 11:56
Who know anything about future of madvr? Will tonemapping be fixed in future? I can't uncheck "compromise on tone & gamut mapping accuracy" to activate two disabled options in "hdr" section. With unchecked "compromise on tone & gamut mapping accuracy" picture is reddish and unrealistic (I can not imagine who like it).

What I mean:
https://imgur.com/a/dMvYNJI
https://imgur.com/a/3gUvLj0

wasper
2nd June 2020, 12:31
SDR does not have metadata, so there is nothing for madVR to send. You can keep your display in DCI-P3 and set madVR so it coverts BT.709.

Thank you. I suppose then that when watching tv sd content the tv will switch to smtpe according to resolution. Isn't important, just trying to figure out...

Alexkral
2nd June 2020, 15:37
Who know anything about future of madvr? Will tonemapping be fixed in future? I can't uncheck "compromise on tone & gamut mapping accuracy" to activate two disabled options in "hdr" section. With unchecked "compromise on tone & gamut mapping accuracy" picture is reddish and unrealistic (I can not imagine who like it).

Yeah, that's the problem of using ICtCp the way it's done, but checking "Compromise in ..." causes other problems that are more evident. Actually I do think this can be fixed, in fact I've been using my own solution for tone mapping for some time now, if you could post the raw BT.2020 screenshot I'd like to check the result. EDIT: Forget it, it would be SDR.

And yes, I think most people would choose the second one.

Alexkral
2nd June 2020, 16:26
Well, this is my result for the second:

https://drive.google.com/file/d/19ObPdihoTNNxouUn5o4I6xoda5BPrkkC/view?usp=sharing

nevcairiel
2nd June 2020, 16:33
Who know anything about future of madvr? Will tonemapping be fixed in future? I can't uncheck "compromise on tone & gamut mapping accuracy" to activate two disabled options in "hdr" section. With unchecked "compromise on tone & gamut mapping accuracy" picture is reddish and unrealistic (I can not imagine who like it).


Tone Mapping has already been substantially reworked in the madVR beta versions with much better results, just need to be patient until its released - or use the betas like many here do if you watch a lot of HDR. But beware, it has many more options to find the proper balance, so its not necessarily fire-and-forget quite yet (hence still beta).

alexantr
2nd June 2020, 19:29
Well, this is my result for the second:

https://drive.google.com/file/d/19ObPdihoTNNxouUn5o4I6xoda5BPrkkC/view?usp=sharing

It looks like my monitor in HDR mode shows.

HillieSan
2nd June 2020, 22:17
Hi, where can I download the beta version?

huhn
3rd June 2020, 06:23
it's in this thread sorry i don't know the page.

https://www.avsforum.com/forum/24-digital-hi-end-projectors-3-000-usd-msrp/2954506-improving-madvr-hdr-sdr-mapping-projector.html

chros
3rd June 2020, 11:16
I can't uncheck "compromise on tone & gamut mapping accuracy" to activate two disabled options in "hdr" section. With unchecked "compromise on tone & gamut mapping accuracy" picture is reddish and unrealistic (I can not imagine who like it).

Yeah, that's the problem of using ICtCp the way it's done, but checking "Compromise in ..." causes other problems that are more evident. Actually I do think this can be fixed, in fact I've been using my own solution for tone mapping for some time now...
Interesting, is it publicly available?

There was a discussion about this recently in the beta thread started by @Javs, for about from here (https://www.avsforum.com/forum/24-digital-hi-end-projectors-3-000-usd-msrp/2954506-improving-madvr-hdr-sdr-mapping-projector-298.html#post59546710) (and it goes through 10 pages).

Alexkral
3rd June 2020, 17:27
Interesting, is it publicly available?

Currently not, it's a pixel shader with BT.2390 tone mapping (original roll-off), saturation correction and gamut mapping. I'd like to share it at some point but I don't think it's completely finished, it needs some more work and testing, and right now I'm trying to finish another project completely unrelated.

There was a discussion about this recently in the beta thread started by @Javs, for about from here (https://www.avsforum.com/forum/24-digital-hi-end-projectors-3-000-usd-msrp/2954506-improving-madvr-hdr-sdr-mapping-projector-298.html#post59546710) (and it goes through 10 pages).

I took a look at that until madhi's answer, I'll try to summarize what I think. They are two different concepts. With "Compromise ..." Off, tone mapping and saturation correction are done in ICtCp in two separate steps, resulting in oversaturation and (theoretically) correct hue. With "Compromise ..." On, tone mapping is applied separately to the RGB channels, which directly desaturates them, but although for normal scenes this desaturation is more or less normal, for bright scenes it is clearly too much, to the point that highlights can end up completely white. And it also produces hue shifts, which, as incorrect as they may be, we are used to seeing because they are already present in the SDR.

So in terms of the saturation correction, it would be about finding a middle point, but there is no middle concept, so you have to start from one of the two. Since madhi is not willing to tolerate any hue shift and madVR is completely based on the first concept, I imagine he will try to modify the saturation correction step, and I wish him luck because I consider it extremely complicated. I think that the fact that desaturation is sometimes clearly exaggerated with the second concept, should not make us forget the fact that RGB channels are desaturated in a more natural way in the same tone mapping step, so it's just a matter of avoiding that excess. This can be done even while avoiding any hue shift with some conversions, but honestly, I am used to seeing the fire between yellow and red, also in real life, so maybe the shift is only wrong because we don't know enough about the changes in hue perception related to changes in intensity (see Bezold-Brucke effect), and perhaps the "very bad and un-scientific math" has surprisingly a correct side effect. So of course I understand madhi's point, but instead of adding options to artificially modify it, I think it would be better to allow it naturally up to a limit. But maybe we should ask a firefighter. :D

el Filou
3rd June 2020, 18:43
SDR does not have metadata, so there is nothing for madVR to send. You can keep your display in DCI-P3 and set madVR so it coverts BT.709.IMHO that's a display bug/inconsistency. Even if there's no metadata, when receiving UHD the display should switch to BT.2020 colour space as it does with 601/709 when receiving SD/HD. @wasper Are you sure the display colour gamut mode is on 'auto'?

huhn
3rd June 2020, 21:45
there is even in practice meta data for the color space and you can even set it with nvidia cards to bt 2020.

tp4tissue
4th June 2020, 05:48
IMHO that's a display bug/inconsistency. Even if there's no metadata, when receiving UHD the display should switch to BT.2020 colour space as it does with 601/709 when receiving SD/HD. @wasper Are you sure the display colour gamut mode is on 'auto'?


Headscratch.. why would it do this automatically for 4k. What if someone wants 4K SDR gamut emulation like on PC.

jkauff
4th June 2020, 15:38
Headscratch.. why would it do this automatically for 4k. What if someone wants 4K SDR gamut emulation like on PC.
Some of us have 4K monitors on our PCs.

huhn
4th June 2020, 15:44
what has this to do with a monitor or TV?

shaolin95
4th June 2020, 23:16
Hello guys...two questions..

1. If I am using the madvr Tone Mapping, does it mean when doing a 3Dlut with DisplayCal I must select 2.2 Gamma or can I use 2.4? I ask because of a comment I read recently someone saying he was forced to use 2.2 gamma because he uses the tone mapping feature of madvr.
2. Any suggestions on settings when upconverting 1080p blurays to 4K? I am on beta 112.

Like maybe this
Medium:

Chroma: NGU Anti-Alias (low)

Downscaling: SSIM 1D 100% + LL + AR
Image upscaling: Off
Image doubling: NGU Sharp
<-- Luma doubling: high
<-- Luma quadrupling: let madVR decide (direct quadruple - NGU Sharp (high))
<-- Chroma: let madVR decide (Bicubic60 + AR)
<-- Doubling: let madVR decide (scaling factor 1.2x (or bigger))
<-- Quadrupling: let madVR decide (scaling factor 2.4x (or bigger))
<-- Upscaling algo: let madVR decide (Bicubic60 + AR)
<-- Downscaling algo: let madVR decide (Bicubic150 + LL + AR)
Upscaling refinement: Off
Artifact removal - Debanding: low/medium
Artifact removal - Deringing: Off
Artifact removal - Deblocking: Off
Artifact removal - Denoising: Off
Image enhancements: Off
Dithering: Error Diffusion 2

High:

Chroma: NGU Anti-Alias (medium)

Downscaling: SSIM 1D 100% + LL + AR
Image upscaling: Off
Image doubling: NGU Sharp
<-- Luma doubling: very high
<-- Luma quadrupling: let madVR decide (direct quadruple - NGU Sharp (very high))
<-- Chroma: let madVR decide (NGU medium)
<-- Doubling: let madVR decide (scaling factor 1.2x (or bigger))
<-- Quadrupling: let madVR decide (scaling factor 2.4x (or bigger))
<-- Upscaling algo: let madVR decide (Jinc + AR)
<-- Downscaling algo: let madVR decide (SSIM 1D 100% + LL + AR)
Upscaling refinement: Off
Artifact removal - Debanding: low/medium
Artifact removal - Deringing: Off
Artifact removal - Deblocking: Off
Artifact removal - Denoising: Off
Image enhancements: Off
Dithering: Error Diffusion 2

Thank you!!

Manni
5th June 2020, 00:09
Re 3D LUT yes the target has to be 2.2 when using tonemapping. It doesn’t make any difference as PQ is absolute, so it will look the same as if 2.4 was possible. It can be whatever you want for sdr rec-709.

shaolin95
5th June 2020, 00:38
Re 3D LUT yes the target has to be 2.2 when using tonemapping. It doesn’t make any difference as PQ is absolute, so it will look the same as if 2.4 was possible. It can be whatever you want for sdr rec-709.
I just tried a 2.4 3Dlut with my projector as 2.4 and things were a bit too oddly dark so I guess 2.2 it is.

Ok but since you mentioned SDR, from my understanding, since i have my projector to 2020 and madvr with the 3Dlut on the 2020 slot of the calibration page, then madvr will be taking care of mapping any SDR non 2020 content to 2020 space so I only need that one 3Dlut. Right?
Thanks again

huhn
5th June 2020, 04:56
yes this one is enough.

but you could just add a bt 709 gamma 2.4 3D LUT for SDR as an example and you don't need new readings for this.

HillieSan
5th June 2020, 10:39
it's in this thread sorry i don't know the page.

https://www.avsforum.com/forum/24-digital-hi-end-projectors-3-000-usd-msrp/2954506-improving-madvr-hdr-sdr-mapping-projector.html

Thanks. I have found it. Phew, lots of stuff to read.

tp4tissue
5th June 2020, 10:48
Hello guys...two questions..

1. If I am using the madvr Tone Mapping, does it mean when doing a 3Dlut with DisplayCal I must select 2.2 Gamma or can I use 2.4? I ask because of a comment I read recently someone saying he was forced to use 2.2 gamma because he uses the tone mapping feature of madvr.
2. Any suggestions on settings when upconverting 1080p blurays to 4K? I am on beta 112.


You craete a 2.4 lut for SDR
For the HDR, you create a 2.2 SDR Lut

In both cases, you want to use the Native gamut mode of your TV, whichever mode gives you the widest gamut.

magnusr
5th June 2020, 13:15
HDR Question. Just upgraded to a LG C9 Oled. In madvr under hdr should I just use passthough (with hdr metadata) and have dynamic tone mapping enabled on the tv? Or should I set the target peak nits to 700 in madvr and disable dynamic tone mapping on the tv?

Manni
5th June 2020, 17:55
I just tried a 2.4 3Dlut with my projector as 2.4 and things were a bit too oddly dark so I guess 2.2 it is.

Ok but since you mentioned SDR, from my understanding, since i have my projector to 2020 and madvr with the 3Dlut on the 2020 slot of the calibration page, then madvr will be taking care of mapping any SDR non 2020 content to 2020 space so I only need that one 3Dlut. Right?
Thanks again

Yes sure if it's a panel and if you don't need a separate LUT for SDR to get better contrast/black levels/lower peak white in a dedicated room, a single BT2020 LUT should do and madVR can convert as needed.

2.2 is the only possible choice for the target if you want to use the LUT for madVR tonemapping, but you can set the display to whatever you want, as it will be corrected by the LUT. It just makes sense to make the baseline calibration as close to the target as possible if you don't need to use the same calibration fro non-madVR sources.

Asmodian
5th June 2020, 18:17
HDR Question. Just upgraded to a LG C9 Oled. In madvr under hdr should I just use passthough (with hdr metadata) and have dynamic tone mapping enabled on the tv? Or should I set the target peak nits to 700 in madvr and disable dynamic tone mapping on the tv?

I use passthrough on my C9 but others prefer madVR's tone mapping.

magnusr
5th June 2020, 18:24
I use passthrough on my C9 but others prefer madVR's tone mapping.

Thanks. Ill stick with passthrough then :)

magnusr
5th June 2020, 18:28
Also got a questions about chroma and image upscaling. 1080p>2160p. While keeping the picture as the filmmaker intended (more like film maker mode). Using 1050Ti with 3600x ryzen cpu to my LG C9 oled tv.

Chroma upscaling: NGU Anti--Alias, medium quality
Image upscaling: NGH Sharp High

Is this good or a bad setting?

VBB
5th June 2020, 20:52
If your 1050Ti can handle "High" for luma, sure. I also use AA for chroma, but on "low" with my 960. The general rule here is luma > chroma. Asmodian didn't mention it, but you probably want to turn off Dynamic Tone Mapping on your C9. It messes with the picture too much. There's also a dedicated OLED thread here, if you have more questions.

sam0t
5th June 2020, 22:06
Hello fellow MadVRs, tl;dr warning!

Been experiencing almost daily BSOD’s with with MPC-HC + MadVR 0.9.17 for the past +2 months or so, and thought it prudent to share the solution for this particularly tricky issue. First of all must say that my AMD Ryzen setup has been rock stable with MadVR ever since I put it together back in 2017 and later upgraded the CPU from Ryzen 5 1600x >> 3600 in Sep 2019.

So when I started getting these BSODs back in April I thought that they surely it must be due to some usual suspects such as old driver/BIOS, overheating, faulty memory, a buggy Windows 10 update
or faulty hardware, but the system kept on passing all of the hardware stress tests I kept throwing at it (CPU/MEM/GFX), and it was stable through few hours of 3D gaming easily too, but as soon as video playback began there would be a random BSOD within 15-45 minutes sure as day.

What made this issue so much harder to pinpoint was the fact that the BSODs error codes kept changing constantly, with the following ones however being most numerous: DRIVER_OVERRAN_STACK_BUFFER, IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA. And then there was the fact that the BSODs were always pointing to the ntoskrnl.exe, and not any driver which might have given clue to the origin of the issue.

After some 60 BSODs and countless hours of fruitless troubleshooting later I stumbled upon a forum thread about some Windows 10 update removing AMD's Power Plan from Windows, and surely that was the case with my OS as well. The tricky part was that for some reason the AMD Power Plan would not appear in Windows when installing the latest AMD chipset drivers (a common issue according to various forums) and to get it to show, had to extract and install the RyzenPPM.msi file manually from an older older Chipset driver package from Gigabyte for Windows 10 1903. After installing the old AMD Power Plan there has been no BSODs for 7 days now, so I think it is safe to say this was the root cause for these issues. I can only speculate as to why these issues started couple months back (Probably it was some of the more recent Windows 10 updates that did away the AMD power profile from my OS, or it changed the Windows default Power Profiles in some way), but my working theory is that perhaps the latest Windows Default Balanced Power Plan does not work well with my older X370 motherboard chipset and the newer AMD Ryzen 3600 CPU combo.

Long rant, but perhaps this helps somebody else struggling with similar issues.

edit:

In case anybody stumbles across this post, my issue was "officially"resolved by AMD chipset drivers 2.04.28.626 which finally installed successfully AMD power plan 5.0.0.0 for my Windows, and also by starting to use the AMD Ryzen Power Profile "High Performance" as default power plan instead of the Balanced.

Can't say for sure, but my hunch is that the Balanced power profile's constant adjustment of the CPU clock speed somehow causes the BSODs with hardware accelerated video playback with my system.

Asmodian
6th June 2020, 00:09
If your 1050Ti can handle "High" for luma, sure. I also use AA for chroma, but on "low" with my 960. The general rule here is luma > chroma. Asmodian didn't mention it, but you probably want to turn off Dynamic Tone Mapping on your C9. It messes with the picture too much. There's also a dedicated OLED thread here, if you have more questions.

Thanks, I do have that off.

magnusr
6th June 2020, 07:14
Thanks, I do have that off.

Thanks. But what happens to everything above around 700 nits if dynamic tone mapping is off and madvr is sett to passthrough?

VBB
6th June 2020, 20:03
You're confusing LG's dynamic tone mapping with normal tone mapping, which cannot be disabled (unfortunately). The TV will never clip, even with DTM turned off.

magnusr
6th June 2020, 20:38
You're confusing LG's dynamic tone mapping with normal tone mapping, which cannot be disabled (unfortunately). The TV will never clip, even with DTM turned off.

Ok thx :) madvr with passthrough and disable dtm on the c9 then.

chros
6th June 2020, 22:42
You're confusing LG's dynamic tone mapping with normal tone mapping, which cannot be disabled (unfortunately). The TV will never clip, even with DTM turned off.
C9 and newer models can be set to clip, but there is always tonemapping with HDR10 mode.

VBB
6th June 2020, 23:55
You mean in game mode by turning on HGIG and/or by calibrating the LUT a certain way?

I didn't want to get into anything too complicated here ;)

TripleH
9th June 2020, 18:33
Hi All,

I'm building a new HTPC to run madVR and I am trying to understand which GPU I should go with.

My goals are:
- Upscaling 1080p to 2160p
- Dynamic tone mapping
- Other image enhancements on 2160p content
- 3D Lut calibration

I planned to use a GTX 1080 (non Ti) for this task.

Will I get any benefit for the above tasks if I go with RTX 2080 Ti instead?

Thanks in advance,

chros
9th June 2020, 19:53
If you can use d3d11 native in Lav then 1080 will be more than enough, maybe a 1070 as well. There will be really powerful new GPUs next year, so there's no point spending lot of money on it now.

huhn
10th June 2020, 02:34
the new GPUs will pretty sure release all this year including AMD and nvidia maybe even bad intel GPUs.

it very likely that madVR will make use of tensor cores getting a pascal GPU is not a great idea.

RXP
10th June 2020, 06:56
Is there a reason people don't use CUDA in LAV? I seem to get the best performance out of that for tone mapping.

curael
10th June 2020, 07:47
Just checking in to say that I'm now on Windows 10 Pro build 2004 and on the newest nvidia driver as of today - on an RTX 2080 and everything is working as it should. Woowee. In case anyone is considering making the plundge. :p HDR switching still works as it should and there are no stutters as were the case in previous versions of Windows 10 on newer nvidia cards. Don't know when they fixed it but I just wanted to mention that it at least works great now. :)

Mike-uk
10th June 2020, 13:11
hmm ok madvr is causing mpc-be to close upon a file being played, using another render solves the problem, so ive used the uninstall.bat with admin rights, got a fresh copy of madvr install, but i still have all the old config ?? remder profiles and resolutions ?? where is it storing this info ?? Thanks Mike

el Filou
10th June 2020, 18:52
Is there a reason people don't use CUDA in LAV? I seem to get the best performance out of that for tone mapping.This is surprising, CUVID being copy-back you would not expect it to have better performance than D3D11 native.
Do you mean better performance compared to DXVA copyback?
Also I seem to remember nevcairiel saying something about CUVID clipping to 8-bit on decode and therefore being unfit for HDR, not sure if it's still the case.hmm ok madvr is causing mpc-be to close upon a file being played, using another render solves the problem, so ive used the uninstall.bat with admin rights, got a fresh copy of madvr install, but i still have all the old config ?? remder profiles and resolutions ?? where is it storing this info ?? Thanks MikeIf you install in a folder with no write access like Program Files under a normal user then it stores settings in the registry.

sam0t
10th June 2020, 19:31
Just checking in to say that I'm now on Windows 10 Pro build 2004 and on the newest nvidia driver as of today - on an RTX 2080 and everything is working as it should. Woowee. In case anyone is considering making the plundge. :p HDR switching still works as it should and there are no stutters as were the case in previous versions of Windows 10 on newer nvidia cards. Don't know when they fixed it but I just wanted to mention that it at least works great now. :)

Encouraging to hear. Earlier this year had W10 updates wreak havoc with my HTPC where an undetermined Windows update silently removed AMD Ryzen Power Profile from the system, which in turn introduced random BSODs with GPU assisted video playback. Just had W10 install the 2004 update with the HTPC that brought up bad memories. :D


hmm ok madvr is causing mpc-be to close upon a file being played, using another render solves the problem, so ive used the uninstall.bat with admin rights, got a fresh copy of madvr install, but i still have all the old config ?? remder profiles and resolutions ?? where is it storing this info ?? Thanks Mike

For me they are stored in the registry @ HKEY_CURRENT_USER\SOFTWARE\madshi\

Read somewhere that the settings.bin file at MadVR install folder would contain MadVR settings as well, but as el Filou suggested, this must be the case when MadVR is installed on a folder with write access.

shaolin95
10th June 2020, 20:00
Hi All,

I'm building a new HTPC to run madVR and I am trying to understand which GPU I should go with.

My goals are:
- Upscaling 1080p to 2160p
- Dynamic tone mapping
- Other image enhancements on 2160p content
- 3D Lut calibration

I planned to use a GTX 1080 (non Ti) for this task.

Will I get any benefit for the above tasks if I go with RTX 2080 Ti instead?

I am doing all that with my 1070 ..well except the 2160 enhancements so not sure what you are doing on that one.
No issues for me.

Thanks in advance,
I am doing all that with my 1070 ..well except the 2160 enhancements so not sure what you are doing on that one.
No issues for me.

Mike-uk
10th June 2020, 20:26
Thanks el Filou and sam0t, after deleting the reg entry madvr is working again with mpc-be