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

tp4tissue
29th May 2021, 13:34
https://i.ibb.co/56DtdQ2/1.png (https://ibb.co/s2SkhTt)
https://i.ibb.co/sP4mhtz/2.png (https://ibb.co/BPJzmwF)

You may need to select the OTHER display hardware for your display device. where it says GTX xxxxxx

note that the gpu is listed xxxx for each connected xxxxx

https://i.ibb.co/F6hvR7X/3.png (https://ibb.co/kKGnNcJ)

el Filou
29th May 2021, 13:58
I don't think which GPU is used for decoding matters for black bar detection, as long as madVR gets the image back on the CPU (i.e. any decoding mode and config except 'native' hardware decode).
Sometimes with some madVR options it's difficult to find out why they don't work when they should...

huhn
29th May 2021, 14:16
correct.

try this add a folder with this name in the madVR folder: ShowBlackBars

this will active a mode where madVR will show what the black bar detection thinks. if it doesn't do than it's not active.

mclingo
29th May 2021, 20:45
I just never update, still going 1806 HTPC is HTPC :D

i rolled back to 1909, no issues with MADVR but youtube was a mess, audio dropouts all over the place even with latest and AMD driver, no issues with 1909 and for once rolling back was seemless, took 5 mins.

Aceman21
30th May 2021, 01:37
Today I went to watch a movie and I noticed that hdr wasn’t enabled. I checked the osd and I noticed these that I’ve never seen and have no idea what they are or how they got there. First is the panavision one and second is the hlg thing. I have no idea how to fix this and I really want to watch a movie https://uploads.tapatalk-cdn.com/20210530/b2c121e4b1d21fa13cdcc04f8f80d6e5.jpg

jmone
30th May 2021, 02:31
HLG is Hybrid Log Gamma which is a combined std SDR curve for the first part and an aggressive Log curve for the highlights that makes a HLG file playable on both a SDR Display (with slightly washed out highlights) and a HLG compatible HDR TV. HLG is being pushed by both the BBC and NHK as a broadcast format that will work OK on both SDR and HDR(HLG) compatible sets. Think of it as a compromise of SDR and HDR together. Unless something recently changed, madVR does not support tone mapping HLG, and if your TV does not support HLG then it will display as SDR.

Aceman21
30th May 2021, 02:33
HLG is Hybrid Log Gamma which is a combined std SDR curve for the first part and an aggressive Log curve for the highlights that makes a HLG file playable on both a SDR Display (with slightly washed out highlights) and a HLG compatible HDR TV. HLG is being pushed by both the BBC and NHK as a broadcast format that will work OK on both SDR and HDR(HLG) compatible sets. Think of it as a compromise of SDR and HDR together. Unless something recently changed, madVR does not support tone mapping HLG, and if your TV does not support HLG then it will display as SDR.


Ok but why is it all of the sudden doing this ? This have never shown up like this before. My movies have always played in hdr not this hlg

Asmodian
30th May 2021, 04:04
It is because of the metadata attached to that file, it says it is BT.2020 and HLG.

Aceman21
30th May 2021, 04:05
It is because of the metadata attached to that file, it says it is BT.2020 and HLG.


But if it’s never done it before why would it be doing it now ? That doesn’t make sense

huhn
30th May 2021, 07:10
we can't answer you why this file is HLG you have to ask the creator.

beware older madVR version where buggy with HLG misunderstanding the metadata and apply wrong HDR to it this has been fixed for a while.

nevcairiel
30th May 2021, 10:41
This might also happen if you use an old version of LAV Filters (pre-0.74) and madVR has dropped its previously accepted values for PQ HDR in recent development versions.
Some time ago, madVR introduced a custom value for PQ HDR signaling, but that value then collided with the official value for HLG when it was introduced, so you need to make sure all parts are up to date.

fireattack
30th May 2021, 10:43
Hi, a quick question.

I'm using an old SDR monitor, so when playing HDR BT.2020 content the color is off.
Based on some tutorials I learned from here, I enabled the option calibration and set the option "the display is calibrated to BT.709":

https://i.imgur.com/EBGej2R.png

Now MadVR will convert HDR content to SDR so they look good on my screen.

However, I found out later if I enable this option, BT.601 (smpte170m) content will not playback correctly: the color will be converted too so the red colors no longer have the correct RGB values.

Is there anyway to have both work? I tried MPV and they all work fine (BT.2020 got converted to SDR, BT.601/BT.709 content plays as-is.)

Thanks.


Edit: never mind. It looks like the video I got just has the wrong color primaries tagged: it's actually BT709 but tagged as BT601. MPV "works" because it ignores color primaries.

jmone
30th May 2021, 10:56
But if it’s never done it before why would it be doing it now ? That doesn’t make sense

Use MediaInfo (under View --> Text) to check what the meta data of the file is. See if it is reporting as PQ/HDR10 or HLG

Aceman21
30th May 2021, 12:57
we can't answer you why this file is HLG you have to ask the creator.

beware older madVR version where buggy with HLG misunderstanding the metadata and apply wrong HDR to it this has been fixed for a while.


The file isn’t tho, if I watched the same movie last week and it didn’t do how would it all of the sudden change ?

Aceman21
30th May 2021, 14:49
Use MediaInfo (under View --> Text) to check what the meta data of the file is. See if it is reporting as PQ/HDR10 or HLG


Where do I do this ?

NDUS
30th May 2021, 17:20
Custom timings can damage a monitor, I saw it once (before madVR had the option). I believe is very rare today, but it is possible.

That said, have you tried deleting all your displays with CRU? This is the only way I have found to really reset them, sort of reinstalling Windows.

I gave this a few tries, and nope...

It seems that MadVR's custom modes menu has permanently damaged my monitor. The program really should include some kind of disclaimer that this can happen.

hannes69
30th May 2021, 19:14
It seems that MadVR's custom modes menu has permanently damaged my monitor.
Are you absolutely sure that you are using the default EDID timings of your monitor and nothing else?
Beside that it could be coincidence of another problem.
When e.g. electrolytic capacitors of the monitor are older, they can loose capacity and similar effects like showing black picture, going on and off can occur.
Normally, if you exceed the capabilities of your monitor´s input range, the monitor shows an error message by OSD and you have a permanent black 'image' then until you change the timings to the allowed range.
When sending a 'wrong' signal, a monitor simply doesn´t show an image or a corrupted one or an error message, but nothing gets defective on the hardware side.

It could be coincidence or maybe something in your monitor was already a little bit out of spec and there was only missing a small deviation to produce a permanent damage.
But such a case is VERY unlikely.

huhn
30th May 2021, 19:57
there is a reason all GPU manufacture are showing a damage warning with custom resolution.

it doesn't matter how rare it is.

tp4tissue
30th May 2021, 20:14
I gave this a few tries, and nope...

It seems that MadVR's custom modes menu has permanently damaged my monitor. The program really should include some kind of disclaimer that this can happen.

Did you try a different computer ?

This is extremely rare.

tp4tissue
30th May 2021, 20:18
Hi, a quick question.

I'm using an old SDR monitor, so when playing HDR BT.2020 content the color is off.
Based on some tutorials I learned from here, I enabled the option calibration and set the option "the display is calibrated to BT.709":

I thought madvr already assumed 709 during sdr conversion and gamma 2.2

In this case, by telling madvr that your monitor is 2.2g and has 709 primaries isn't exactly right, because your monitor almost certainly does not fit those descriptions by default without real calibration.

If the image looks Better to you , it's likely just the effect of lowering gamma which makes everything more saturated.

An OLD monitor usually means its gamma tracking is really out of wack.

What monitor are you using.

NDUS
30th May 2021, 20:45
Are you absolutely sure that you are using the default EDID timings of your monitor and nothing else?
Beside that it could be coincidence of another problem.
When e.g. electrolytic capacitors of the monitor are older, they can loose capacity and similar effects like showing black picture, going on and off can occur.

Here's the readout from MadVR's optimize page after I've taken all of the aforementioned steps (deleting MadVR custom mode, reinstalling GPU drivers including with DDU, reinstalling monitor drivers, deleting all displays with CRU a few times across multiple reboots in safe mode just to be sure)

https://i.imgur.com/bOZjwa8.jpg

It seems there is a small discrepancy between the "EDID" and "measured timings." Dunno if that's normal.

This is a pretty new monitor, only had it for about a month or two and it had zero issues before using MadVR custom modes.
Every 8~35 minutes it goes black for about 1-2 seconds. It does not appear to exhibit this issue outside of the 59.94hz mode (the one I tried custom modes on)

Did you try a different computer ?

I don't own another machine.

fireattack
30th May 2021, 21:02
I thought madvr already assumed 709 during sdr conversion and gamma 2.2

In this case, by telling madvr that your monitor is 2.2g and has 709 primaries isn't exactly right, because your monitor almost certainly does not fit those descriptions by default without real calibration.

If the image looks Better to you , it's likely just the effect of lowering gamma which makes everything more saturated.

An OLD monitor usually means its gamma tracking is really out of wack.

What monitor are you using.

I'm using a Dell u2312hm.

It's not about gamma, but the HDR to SDR tone-mapping (?).
Without setting this (the default setting is "disable"), the BT2020's matrix/primaries is played as-is, which is pretty pale/dull.
I have to set this to let MadVR to map it to a SDR which looks much better.

Here is a comparison:

https://i.imgur.com/QFr9Vmo.png

(I tried to play with the options under "hdr" too, but none of them seem to have any effect.)

I agree with you that without calibration the gamma/transfer function setting won't be exactly correct,
but that doesn't seem to have much (if at all?) effect on playback from my testing, so I just leave it as the default 2.20.


Anyway, I knew very little about HDR content and the techniques around it, so feel free to correct me.

Aceman21
30th May 2021, 22:13
Use MediaInfo (under View --> Text) to check what the meta data of the file is. See if it is reporting as PQ/HDR10 or HLG


https://uploads.tapatalk-cdn.com/20210530/4b74a9720641980add1e528be164c89a.jpg
https://uploads.tapatalk-cdn.com/20210530/494204cd5e614bc7958192509b7ab2bc.jpg
https://uploads.tapatalk-cdn.com/20210530/af394123847012987b7a3163022adb9e.jpg

hannes69
31st May 2021, 00:13
It seems there is a small discrepancy between the "EDID" and "measured timings."
Some monitors only work correctly if the EDID timings are used, so they aren't ready for custom resolutions.
They maybe 'accept' it obviously, but it doesn´t work as intended.
You shouldn't have a difference between 'EDID timings' and 'current timings' now to test if the custom resolutions are the problem.
You should use now really exactly the EDID timings in order to see if the problem persists or not.
A complete EDID timing consists of the porches and an exact value of the pixel clock.
I don't know what exactly in your setup is responsible for the difference in the pixel clock.
Try using the EDID mode, either by the help of madvr if that works (select the EDID one) or by using the display driver's settings.


This is a pretty new monitor, only had it for about a month or two and it had zero issues before using MadVR custom modes.
Every 8~35 minutes it goes black for about 1-2 seconds. It does not appear to exhibit this issue outside of the 59.94hz mode (the one I tried custom modes on)
New monitor - then there shouldn't be hardware aging effects.
If the other refresh rates still work then there shouldn't be a hardware defect. Normally...

NDUS
31st May 2021, 04:56
Some monitors only work correctly if the EDID timings are used, so they aren't ready for custom resolutions.
They maybe 'accept' it obviously, but it doesn´t work as intended.
You shouldn't have a difference between 'EDID timings' and 'current timings' now to test if the custom resolutions are the problem.
You should use now really exactly the EDID timings in order to see if the problem persists or not.
A complete EDID timing consists of the porches and an exact value of the pixel clock.
I don't know what exactly in your setup is responsible for the difference in the pixel clock.
Try using the EDID mode, either by the help of madvr if that works (select the EDID one) or by using the display driver's settings.



New monitor - then there shouldn't be hardware aging effects.
If the other refresh rates still work then there shouldn't be a hardware defect. Normally...

Tried manually altering it to match the EDID. oddly, applying the "EDID" mode in MadVR would not give precisely the same pixel clock as indicated on the custom modes panel, but manually changing the pixel clock of the active mode to create a new custom mode did.

The custom mode is now identical to the reported EDID mode, and the problem continues (when the monitor is set to 59.94hz, anyway)

hannes69
31st May 2021, 14:40
@NDUS
Can you check what timings are actually used?
I don't know what GPU you have.
I have an AMD GPU and I can look up the currently used timings in Catalyst Control Center under Display -> Display Specifications (I don't know if you can look up this info with nvidia or intel).

If the 59.94 Hz setting is really broken and you want to use the monitor furthermore:
Is it a 120Hz model, then you could use 120Hz instead of 60Hz.
If you don't watch 59.94 fps videos but only 29.97fps, maybe you could use this refresh rate.
If everything else fails, you could use the highest correct working refresh rate of the monitor and use smoothmotion in madvr.

Or if you consider the monitor as broken, you could now tinker with it and try other custom resolutions for 59.94 Hz with different porches and pixelclock settings.

You can buy a new monitor and give this to someone who doesn't need different refresh rates and uses always the same rate for a normal desktop computer.

clsid
31st May 2021, 15:11
It could be a driver problem, where the driver doesn't like having two screens with big difference in refreshrate. AMD even has something related to that in its know issues list. So not unlikely that NVIDIA could have issues as well. Occasional screen blackouts are usually driver related.

So test with just one monitor connected.

And also test with driver changed to "Microsoft Basic Display Driver".

Klaus1189
31st May 2021, 17:09
So not unlikely that NVIDIA could have issues as well. Occasional screen blackouts are usually driver related.

I have still occasional display dropouts with my RTX30 card. Very rare but still the case. After longer periods on running time. But these are shorter than the dropouts on my RX 5700 XT. There the signal took 2 or 3 seconds to be back, on the RTX 30 card only for max 1 second on only when on idle like desktop usage or web browsing. During gaming never had one in 6 months on the RTX30 card. I thought would be getting a quality product but, meh .... But the thing is AMD Radeon driver issues on RDNA 1 and later (HTPC related)!, meh meh ...

@NDUS:
What monitor is it exactly?

NDUS
31st May 2021, 17:47
I have still occasional display dropouts with my RTX30 card. Very rare but still the case. After longer periods on running time. But these are shorter than the dropouts on my RX 5700 XT. There the signal took 2 or 3 seconds to be back, on the RTX 30 card only for max 1 second on only when on idle like desktop usage or web browsing. During gaming never had one in 6 months on the RTX30 card. I thought would be getting a quality product but, meh .... But the thing is AMD Radeon driver issues on RDNA 1 and later (HTPC related)!, meh meh ...

@NDUS:
What monitor is it exactly?


Dell S2721QS


It appears the "automatic" timings reported in NVCP are different from the "EDID" in MadVR, this is what they look like:
https://i.imgur.com/OAhhIs9.png

I will try manually creating a custom resolution in NVCP using the "EDID" timings from MadVR and see if this fixes it.
However, in NVCP there is no field to enter the "back porch" numbers used in MadVR..
I know that this problem isn't caused by the refresh rate discrepancy between the primary and secondary monitors, because I ran this setup like this for around 1.5 months without this issue happening, then after testing MadVR custom modes it began.

Edit:

So far, this solution (making a custom resolution in NVCP with the EDID timings from MadVR) seems to work.

Edit 2:

Or not... it is still happening... maybe less frequently?
I dunno what to do at this point. Shit's fucked.

0xothik
31st May 2021, 20:53
I think it's just a bug report now, but still :)

I've got the lastest K-Lite CP, MPC-HC and madVR from it.
And there is the problem — subtitles doesn't always switches. I paused the video, change the subtitles via hotkeys, and 1 of 7 times — player shows, that subtitle track was switches, but the subtitles on screen remains the same. If I unpause in that moment — subtitles would changes immediately.
Other 6 times — everything is fine. EVR custom renderer — everything is fine. Subtitles are external ASS files. Subtitles renderer — "internal"

With the help from Reddit (https://www.reddit.com/r/htpc/comments/nkz3me/mpchcmadvr_subtitles_problem_doesnt_always/gzt3za3/?utm_source=reddit&utm_medium=web2x&context=3) I've managed to get rid of this, so — it's just a bug report, I think :)

(In case you are wondering — i've got an app for dynamic bilingual subtitles, and it works through switching subs via hotkeys, that's why this is the case for me, unfortunately)

hannes69
31st May 2021, 20:55
Dell S2721QS
Maybe it has something to do with that monitor being a freesync one?

in NVCP there is no field to enter the "back porch" numbers used in MadVR
Not necessary because redundant.
Total = active + front + sync + back ;)

So far, this solution (making a custom resolution in NVCP with the EDID timings from MadVR) seems to work.
So nothing 'permanently damaged' :cool:

Matias
2nd June 2021, 10:45
Do anyone have a problem with playing this video with Beta 132 and MPC-BE?
https://file-examples-com.github.io/uploads/2018/04/file_example_AVI_1280_1_5MG.avi

NoTechi
2nd June 2021, 20:40
Do anyone have a problem with playing this video with Beta 132 and MPC-BE?

No problem here

NoTechi

Matias
2nd June 2021, 22:22
Ok, I found problem, not working with external avi splitter only internal in mpc-be

ashlar42
3rd June 2021, 21:55
Just to get the pulse of the situation, trying to understand what upgrading my HTPC for 4K would cost me: what would be the minimum specced card needed to decently upscale SD, 720p and 1080p to 4K? Say with NGU High quality for 24fps material and NGU Medium for higher framerates.

huhn
3rd June 2021, 22:18
really basic but even these cards shouldn't be available.
even a 1060 should have a lot of headroom so it depends more on what you can get used.

rfpm
3rd June 2021, 23:46
I started facing the same issue with the latest beta too, why is this happening?

tp4tissue
4th June 2021, 01:05
Just to get the pulse of the situation, trying to understand what upgrading my HTPC for 4K would cost me: what would be the minimum specced card needed to decently upscale SD, 720p and 1080p to 4K? Say with NGU High quality for 24fps material and NGU Medium for higher framerates.

NGU is not worth upgrading your GPU for.

If your GPU can handle HDR to SDR, (1060,6gb), then wait it out unless you need it to play games.

NGU is a huge waste of electricity for what it does. At real viewing distances you can't really even tell the difference vs lanczos.


If you want to improve image quality, a COLORIMETER is the Best investment you could ever make. Better than any amount of money spent on GPU.

i1display pro, or i1display studio, Madvr's most powerful and useful feature is 3DLUT integration, :D

nsnhd
4th June 2021, 04:56
NGU is a huge waste of electricity for what it does. At real viewing distances you can't really even tell the difference vs lanczos.

What viewing distance are you talking about ?
I always keep mine within that rule:
https://photos.smugmug.com/AVSFORUM-2/i-9MVJNTS/0/f90eecbf/O/8K%20RESOLUTION%20DISPLAYS%20WORTH%20IT%20CHART%20%28hi-res%29.jpg

Aceman21
4th June 2021, 10:40
I’m running a rx580 8gb in my htpc, I mostly watch 4Khdr movies and 1080p tv shows upscaled to 4K on my 65” tv. What would be the most important madvr setting to be trying to get as high as possible and what ones not to waste time on ? I have a feeling that I’m wasting resources and things what aren’t benefiting my performance.

ashlar42
4th June 2021, 12:44
NGU is not worth upgrading your GPU for.

If your GPU can handle HDR to SDR, (1060,6gb), then wait it out unless you need it to play games.

NGU is a huge waste of electricity for what it does. At real viewing distances you can't really even tell the difference vs lanczos.


If you want to improve image quality, a COLORIMETER is the Best investment you could ever make. Better than any amount of money spent on GPU.

i1display pro, or i1display studio, Madvr's most powerful and useful feature is 3DLUT integration, :DThanks for you reply. I already own and use a colorimeter (even got ISF training some years ago).

So your position is that for "real" use, madVR upscaling is of little use? This comes as quite the surprise. Not contesting your opinion, I am all for objective measurements. So you might be onto something. But still surprising.

I don't get what you mean by this "If your GPU can handle HDR to SDR". You mean for projectors? I plan on getting an OLED TV, so that would be of no significant use to me, I suppose.

Also, considering LG OLEDs have 3DLUT accessible at panel level, with Calman... would this mean that madVR is of no practical use in that scenario?

huhn
4th June 2021, 14:34
madVR 3d LUT have a higher resolution if this really matter is something different.

obviously depending on the relative distant to the screen a scaler is utterly useless to day night different.

generalising with something like "real viewing distance" what ever that even is does not help here you have to figure out if you have a chance to gain anything from UHD. to gain the most out of UHD the distance is about 3x screen hight(this takes 21/9 and 16/9 difference out of the equation) the image posted by nsnhd is a good starting point.

there are also recommendation for relative distance the dolby one is really really close. maybe to give 8K anything to grab to...

mclingo
4th June 2021, 14:40
I’m running a rx580 8gb in my htpc, I mostly watch 4Khdr movies and 1080p tv shows upscaled to 4K on my 65” tv. What would be the most important madvr setting to be trying to get as high as possible and what ones not to waste time on ? I have a feeling that I’m wasting resources and things what aren’t benefiting my performance.

too many variables really, it depends of the quality of your sources, the size of your TV, where you are sitting, how good your TV is at HDR / nits range etc etc.

If everything you watch is bluray quality or close and you are not tone mapping to SDR or downscaling, then you dont really need anything set high, arguably.

I now just push upscaling and chroma as high as I can to prevent my GPU fans getting noisy, I now use NGU LOW for everything and my PC is silent, on HIGH I can just hear the fans but not over the movie but I prefer silence for the silent parts of movies.

el Filou
4th June 2021, 15:44
What viewing distance are you talking about ?
I always keep mine within that rule:
https://photos.smugmug.com/AVSFORUM-2/i-9MVJNTS/0/f90eecbf/O/8K%20RESOLUTION%20DISPLAYS%20WORTH%20IT%20CHART%20%28hi-res%29.jpgThat chart seems strange to me seeing I can easily see the difference between 720 and 1080 on my 50" when sitting 3 meters away, and it's a plasma which is not the cleanest display technology. IMHO it's pessimistic for 720/1080, and a bit optimistic for 4K/8K.

I guess tp4tissue meant at your usual viewing distance with your own display and eyes.
I would suggest buying the display first, then taking the time to do tests to see if you can actually see a difference between the various upscaling algos (you can do this on pause and don't actually need your current GPU to be able to handle all the algos at playback speed).

mclingo
4th June 2021, 15:58
3 meters is right on the edge so you should be able to tell the difference between 1080p and 720p but only just?

mclingo
4th June 2021, 16:00
thing is though, do you not find that film grain tends to be supressed when something is compressed to 720p so you might be seeing that more as the difference than an actual obvious difference in resolution clarity in general.

huhn
4th June 2021, 16:24
the chart clearly aggress with you that you should be able to see the difference and you do. sounds perfect to me?

edit: the chart is bias distance and resolution should be linear it isn't in the chart.
simple example is a 32 TV with 1080 is replaced with 64 with 2160 the pixel have 100% the same size.

SirMaster
4th June 2021, 16:46
NGU is not worth upgrading your GPU for.

NGU is a huge waste of electricity for what it does. At real viewing distances you can't really even tell the difference vs lanczos.


For 2D animation (cartoons) NGU makes a big difference over lanczos.

Upscaling older 480p animation like early seasons of The Simpsons or Futurama to 4K, or even just normal 1080p cartoons to 4K.

chros
4th June 2021, 16:49
I’m running a rx580 8gb in my htpc, I mostly watch 4Khdr movies and 1080p tv shows upscaled to 4K on my 65” tv. What would be the most important madvr setting to be trying to get as high as possible and what ones not to waste time on ? I have a feeling that I’m wasting resources and things what aren’t benefiting my performance.

So your position is that for "real" use, madVR upscaling is of little use? This comes as quite the surprise. Not contesting your opinion, I am all for objective measurements. So you might be onto something. But still surprising.

I don't get what you mean by this "If your GPU can handle HDR to SDR". You mean for projectors? I plan on getting an OLED TV, so that would be of no significant use to me, I suppose.

Also, considering LG OLEDs have 3DLUT accessible at panel level, with Calman... would this mean that madVR is of no practical use in that scenario?
In short, get a used 1060 6GB with a TV and you are done. Take a look at the link in my signature to see what settings it can handle with different content.

But lot of things have changed in the past couple of years, especially with HDR, importance of madvr is decreasing:
- lot of content only availabe via streaming, already in 4k DoVi HDR
- HDR just look better than any SDR and with HDR TVs madvr doesn't do much (maybe 5% of the content)
- different TVs deal with HDR10 content differently, introducing color issues, hence DoVi looks better on most of them (not without isuues either)
- e. g. Oppo can upconvert 1080p SDR into DoVi and it looks just better than anything you do with madvr in sdr

tp4tissue
4th June 2021, 23:22
So your position is that for "real" use, madVR upscaling is of little use? This comes as quite the surprise.

I don't get what you mean by this "If your GPU can handle HDR to SDR". You mean for projectors? I plan on getting an OLED TV, so that would be of no significant use to me, I suppose.

Also, considering LG OLEDs have 3DLUT accessible at panel level, with Calman... would this mean that madVR is of no practical use in that scenario?


Real use, meaning somewhere around 30 to 40 degrees FOV angle.

You can put your face arbitrarily close to the screen, and claim you can see the difference for NGU,

What I've found through my own testing with still images at 30-40 FOV, I would get it wrong between NGU and Lanczos ~50% of the time. I took screen shots and randomized the order.

Then when watching action content, moving pictures, it's was IMPOSSIBLE for me to tell the difference even a bit closer than that.

If the difference was 10-20watts , I'd say, hell go for it, but we're talking upwards of 100-200 watt difference if you push it all the way (depending on gpu), it's plainly NOT worth the expense and we're killing the earth damn it. :scared:


HDR to SDR is madvr's tonemapping for use with PC oriented monitors/ TVs. It does a better job than a TV's tonemapping, not better than the premium LG/Sonys, but many of the middling brands/models.


LG 3DLut support is only on their OLED and highest end models, and all that goes through their own abl / tonemapper. If you like their engine you don't absolutely need Madvr's 3dlut features or its HDR to SDR engine.

I'd still recommend using madvr 3dlut for SDR content though, because it's higher resolution correction 65x65x65. It can also correct in the TV's native color space. That may provide fewer potential for math errors.

Overall, Using Madvr's 3DLut is an end to end solution, with LG's internal lut, it operates under the assumption that the system is bit perfect without measuring the whole system.