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

Sparktank
12th October 2018, 11:16
+1 for "add grain" as separate feature instead of being "upscale refinement".

When I use SVP, I don't know how to hack the scripts to include AddGrain for FFDShow. And FFDShow's own filter is nowhere near nice enough as AVS AddGrain.

Even at 4, it doesn't seem to do as much as what AddGrain AVS can do.

SamuriHL
12th October 2018, 16:30
HDR is working again with nVidia 416.34 drivers

Indeed it is. To clarify this means in windowed mode not just FSE.

brazen1
12th October 2018, 16:48
I can confirm nVidia 416.34 are switching HDR in FSW and FSE again. Same with 3D which is a first for my system.

ajp_anton
12th October 2018, 19:54
100% view is the screen as it appear in the media player. The encoded video size is the original pixel count of the source. I haven't tried the second option, but I think that is what it means.Nope, for me xxx% view always creates a screenshot that is xxx% of the encoded video, no matter how much I've zoomed. So "100% view" is always identical to "encoded video size".

huhn
12th October 2018, 21:39
did you try an anamorphic video. the view and encoded size should be different on these.

famasfilms
13th October 2018, 00:07
Latest Nvidia drivers have fixed HDR, but now the madvr display mode switching doesn't toggle my LG OLED from "PC" mode to "Home Theatre" and my calibrated picture settings.

Ever since I got the TV and the calibration done it's been set to PC mode (because I use it for other stuff), and madvr has been setup to switch display modes - the change of display mode would automatically change the TV to "home theatre" which is where the calibrated "night" setting was

mkohman
13th October 2018, 02:41
Hey guys thanks to @Onkyoman, I have now created two profiles for HDR and SDR within madVR for slight saturation boost for HDR content..

On my JVC projector I have also created 2 profiles.. First one is HDR to SDR and the second one is just SDR..

Is there anyway that when I am playing a bluray (1080p) upscaled to 4K via madVR using REC709 on the JVC's SDR custom setting I created, is there any way to get madVR to get the projector to detect that it's playing an SDR movie and to change it to the SDR profile on the JVC and visa versa? rather than me doing it via the projectors remote control? Thank you guys in advance..

Sent from my moto g(6) using Tapatalk

huhn
13th October 2018, 03:28
try the send bt 2020 option under calibration.
not sure how your device exsactly handles this but if you have it by default in bt 709 mode and add this bt 2020 option to the HDR profile it should switch if it understand this setting.

blaubart
13th October 2018, 07:45
Wow Nvidia was listening to my laments! :) 416.34 (still in W10 1809) and madVR switching HDR again. AND switching it to correct black/white clipping, yeah!

During all my posts I had to switch HDR manually through Windows Display settings -> aha and if I do that now madVR still shows wrong black/white clipping. So seems to be a Windows>Display settings>HDR bug or bad YCbCr cooperation with madVR.

pantagruel68
13th October 2018, 11:56
Hey Guys.
Can someone explain me why when I watch a movie when chosing 1080p resolution I get very close To 23.976 ( about 23.9758) with my gtx 1060 but when selecting 2160p I get 23.978?
Thanks

mytbyte
13th October 2018, 12:05
try the send bt 2020 option under calibration.
not sure how your device exsactly handles this but if you have it by default in bt 709 mode and add this bt 2020 option to the HDR profile it should switch if it understand this setting.

Actually, he may not even need the profiles in the PJ. Here's what I do for Panasonic UHD SDR TV:

In calibration section, I set colorspace to BT.2020 and select "report BT.2020 to display. MadVR should remap BT.709 HD bluray to BT.2020 , and the switch should put the PJ into BT.2020 mode automatically. With HDR content, if set to "tone map HDR", the passthorugh of BT2020 should also be automatic.

zapatista
13th October 2018, 16:26
HI Madshi,

i just replaced my old ati 5770 with a gtx 1060 (3gb) , but i have major dropped frames in madvr when playing video since i installed this card (about 10/sec). this is even with default madvr settings, and using mpc-hc (64 bit).
pc = i7-4770k cpu, 32 gb ram, ssd 500 gb, and new 1060 3gb gfx card on a win7 64 bit system

other video players work fine, eg cyberlink powerdvd, vlc, mplayer without madvr is also ok, etc
i have tried several gfx drivers (latest whql, version on the install dvd, best recommended by other users for similar video card etc..), all no solution. also checked for mb driver & bios updates etc (all are up to date). gfx card has no alternative bios release to try.
i did search for other users w madvr reporting similar problems but the main suggestions (from yourself earlier in this thread for ex) was to turn flux off and not use gpu-z, didnt seem to help in my case

https://ibb.co/eQ0VZU
https://ibb.co/eQ0VZU

when i first installed the new 1060 gfx card i thought it was working correctly, even was able to play some 4k HEVC files smoothly(downscaled to my 1080 tv over hdmi) and was really impressed with the quality of the video image (as i was expecting from madvr from my old ati card use in previous yrs), but then further testing with 1080p and 720p files (mp4 and HEVC) over the following days all started to have similar severe dropped frames (tried lots of settings in madvr options, but now even default settings with all enhancements off now cause dropped frames 10/sec approx)

i have reset madvr to defaults, uninstalled and reinstalled mpc-ht etc, sadly no solution found so far. cpu usage stays low @ 30% approx, and gpu load is also low @ approx 30% with only 900 mb of the 3 gb vram used (as reported by gpu-z)

any idea what i should look at ?

your presentation times are terrible try windows 7 overlay.

i have tried the win7 overlay you suggested, no real improvement regretfully

thx for pointing to the poor "presentation time" as an indication of my poor video play, i can monitor that variable also now when searching for solutions

when i switch users on my win 7 install to admin user and play the same video files everything seems to run fine (using default mpc-ht and default madvr settings) see image
https://ibb.co/fFq7m9 this would at least suggest there is no hardware issues (ram etc ) or bios setup problems etc, also the current win7 install works ok when run from another user account to.

anybody know what else i can look at to find the cause of my high frame drops and poor render times? (as seen here https://ibb.co/eQ0VZU)

to me the current poor video play seems to behave as if some crumbs from a previous madvr installation might still be interfering somehow with my fresh madvr and mpc-ht re-install and their default setup

chros
13th October 2018, 16:48
http://thumbs2.imagebam.com/d0/9e/10/641fe9995220124.jpg (http://www.imagebam.com/image/641fe9995220124) http://thumbs2.imagebam.com/55/38/4d/82a011995220164.jpg (http://www.imagebam.com/image/82a011995220164)

any ideas why the picture changes to black and white for me as soon as I set "highlight recovery strength" to anything else than 'none'?

Same here,, happens with 92.15 too.
GTX660, software decoding.

Probably DirectCompute related.

Exactly same problem here !

MPC-HC 1.7.13 (x86&x64)
MADVR 0.92.17
Geforce 650Ti
DL580G5 (4xXeonX7460)
Win10 1803

it worked fine before (DirectCompute ?)
And it possible to be able to choose the old algo ?

Guys, who doesn't have laptop (Optimus)? I do, unfortunately.
It's definitely DirectCompute related.

Edit: it's fixed in madVRhdrMeasure10, just wait for the new release. (Although my laptop doesn't have enough juice to use both "compromise tone & gamut mapping ..." unchecked and "highlight recovery" at the same time :) )

Khaled1323
13th October 2018, 19:04
https://i.imgur.com/yRBEFvJ.png

any idea why it says windows 8 bit even thou my monitor is 10 bit?

mclingo
13th October 2018, 19:06
have you set your panel to 10 bit or higher in MADVR?

In devices / properties at the top.

Khaled1323
13th October 2018, 19:10
https://i.gyazo.com/ae6a5825e847898896c761433aaf45a6.png
yes

SirSwede
13th October 2018, 19:56
Hello!

I am soon to be an owner of a Inno3D GeForce GTX 1050 Ti 1-Slot Edition HDMI DP 4GB. How do I want to be scaling 540p, 720p and 1080p, respectively, to a LG OLED55C8?

:thanks:

brazen1
13th October 2018, 20:14
Khaled, use FSE Full Screen Exclusive.

ryrynz
13th October 2018, 21:12
How do I want to be scaling 540p, 720p and 1080p, respectively, to a LG OLED55C8?


The answer is, however you want. Most would use NGU (any variant) for their luma/chroma upscaling and SSIM 1D/2D for downscaling.

Crimson Wolf
13th October 2018, 21:25
Khaled, if you have anything open like right-click mouse and menu, it will be 8-bit until that menu is closed. If nothing is open, and it's still 8-bit, try rebooting. If you still have issues, try reinstalling the video drivers.

huhn
13th October 2018, 21:31
i have tried the win7 overlay you suggested, no real improvement regretfully
that's odd
thx for pointing to the poor "presentation time" as an indication of my poor video play, i can monitor that variable also now when searching for solutions

when i switch users on my win 7 install to admin user and play the same video files everything seems to run fine (using default mpc-ht and default madvr settings) see image
https://ibb.co/fFq7m9 this would at least suggest there is no hardware issues (ram etc ) or bios setup problems etc, also the current win7 install works ok when run from another user account to.

anybody know what else i can look at to find the cause of my high frame drops and poor render times? (as seen here https://ibb.co/eQ0VZU)

to me the current poor video play seems to behave as if some crumbs from a previous madvr installation might still be interfering somehow with my fresh madvr and mpc-ht re-install and their default setup

on your first screen did you disable aero?

huhn
13th October 2018, 21:41
Actually, he may not even need the profiles in the PJ. Here's what I do for Panasonic UHD SDR TV:

In calibration section, I set colorspace to BT.2020 and select "report BT.2020 to display. MadVR should remap BT.709 HD bluray to BT.2020 , and the switch should put the PJ into BT.2020 mode automatically. With HDR content, if set to "tone map HDR", the passthorugh of BT2020 should also be automatic.

while you may not need that.
sending bt 2020 to a screen that is not bt 2020 is not ideal in my book. the screen needs to do heavy processing.

this is totally different if you run a screen in native mode and 3D LUT correct the image.

on projector it's an even bigger problem.

SirSwede
13th October 2018, 22:01
The answer is, however you want. Most would use NGU (any variant) for their luma/chroma upscaling and SSIM 1D/2D for downscaling.

Okay. Does it matter that it is an old processor and old ram? All that Madvr needs is a good graphics card, right?

Also, someone told me that the TV is better at scaling these resolutions to 4K, than Madvr, which is not the case, right?

:thanks:

blu3wh0
13th October 2018, 22:33
So I spent some time testing the dynamic tone mapping on my LG B7 OLED and the latest pixel shaders for HDR in the test version 9 (with saturation boost +15, peak 750 nits, output in HDR, and measure peak). Overall, both the dynamic tone mapping and the pixel shader attempt to do the same thing, except for one key difference. The dynamic tone mapping appears to affect the whole image, while the shaders mostly impact only the highlights or sources of peak brightness. I'm not sure if this is the way it's supposed to work, but it's what I see. This is even more effective where working with a 4000 nit master, which the dynamic tone mapping helps with, but no where near as accurately as the shaders. An example of this is the bright green spear cut that is one of the test shots. For 1000 nit masters, the impact on the highlights between the two is very similar. I did see some instances of color tone changes with the shaders, but again I can't tell what was supposed to be correct in the image. Regardless, either would look normal if you didn't switch between passthough and shaders. I've only tested a few movies, but so far this is very promising and enough for now to try using the HDR pixel shaders for general usage.

Anima123
13th October 2018, 23:04
Do you guys know since when madVR requires DirectX 11 for advanced dithering method? As I remembered, it does not have that requirement during the testing of Diffusion methods.

ryrynz
13th October 2018, 23:06
Okay. Does it matter that it is an old processor and old ram?


If you're using a dedicated gpu then that can matter for file decoding performance but not for madVR but it can depend on age and core count.


All that Madvr needs is a good graphics card, right?


I used a gtx 960 for a good long time and it did well. I'd recommend anything similar or greater performance to get the most out of MadVR.


Also, someone told me that the TV is better at scaling these resolutions to 4K, than Madvr


There are good quality scalers used today on the latest 4k tvs but nothing that can match madVR's NGU in real time built in to any consumer display or readily available device.

mytbyte
13th October 2018, 23:19
while you may not need that.
sending bt 2020 to a screen that is not bt 2020 is not ideal in my book. the screen needs to do heavy processing.

this is totally different if you run a screen in native mode and 3D LUT correct the image.

on projector it's an even bigger problem.

Hmm...my line of thinking is this: no display is natively BT.2020, even the ones with the widest of gamuts need to remap from native gamut to a stabdard gamut ...even plasmas were not strictly rec.709, they had wider gamuts than rec.709 natively, there is always a 3D LUT or some other processing involved to get the colors in place (especially if a display has user-accessible CMS system) and these things should be optimized to run without hickups in all circumstances...

blaubart
13th October 2018, 23:31
Also, someone told me that the TV is better at scaling these resolutions to 4K, than Madvr, which is not the case, right?

"the TV", there are 1000 different TVs with 100 different scaling abilities. And which answer do you expect if you ask true madVR Fan's if any TV on ths world scales better then madVR :p

HDR
14th October 2018, 00:40
So I spent some time testing the dynamic tone mapping on my LG B7 OLED and the latest pixel shaders for HDR in the test version 9 (with saturation boost +15, peak 750 nits, output in HDR, and measure peak). Overall, both the dynamic tone mapping and the pixel shader attempt to do the same thing, except for one key difference. The dynamic tone mapping appears to affect the whole image, while the shaders mostly impact only the highlights or sources of peak brightness. I'm not sure if this is the way it's supposed to work, but it's what I see. This is even more effective where working with a 4000 nit master, which the dynamic tone mapping helps with, but no where near as accurately as the shaders. An example of this is the bright green spear cut that is one of the test shots. For 1000 nit masters, the impact on the highlights between the two is very similar. I did see some instances of color tone changes with the shaders, but again I can't tell what was supposed to be correct in the image. Regardless, either would look normal if you didn't switch between passthough and shaders. I've only tested a few movies, but so far this is very promising and enough for now to try using the HDR pixel shaders for general usage.
I can't live without LG's "active HDR". It tries to mimic HDR10+/Dolby Vision by analyzing the whole scene and adjusting brightness and tone mapping per frame. I don't know if this is something madshi is working on or is even possible with madVR, but until/if this happens I'm sticking with LG's implementation.

It really helps with shadow detail in dark scenes. Often times madVR is simply too dark compared to LG with active HDR turned on.

You can use madVR for tone mapping and still turn on LG active HDR, but then you've got kind of a double tonemapping situation where the tv is trying to dynamically adjust brightness and highlights after madVR has already tone mapped. It doesn't quite look right IMO. Often times it will just make the highlights even darker.

blaubart
14th October 2018, 00:55
It really helps with shadow detail in dark scenes. Often times madVR is simply too dark compared to LG with active HDR turned on.

Switching HDR through Windows Display settings results here in madVR too dark black clipping. Since NV 416.34 madVR is able to switch HDR by himself again (Windows>Display settings>HDR off) - black/white clipping ok now.

blu3wh0
14th October 2018, 02:33
I can't live without LG's "active HDR". It tries to mimic HDR10+/Dolby Vision by analyzing the whole scene and adjusting brightness and tone mapping per frame. I don't know if this is something madshi is working on or is even possible with madVR, but until/if this happens I'm sticking with LG's implementation.

It really helps with shadow detail in dark scenes. Often times madVR is simply too dark compared to LG with active HDR turned on.

You can use madVR for tone mapping and still turn on LG active HDR, but then you've got kind of a double tone mapping situation where the tv is trying to dynamically adjust brightness and highlights after madVR has already tone mapped. It doesn't quite look right IMO. Often times it will just make the highlights even darker.

I agree, however I can also clearly see the benefit of the pixel shaders in reeling in the highlights into the brightness range of the TV. The dynamic tone mapping on my LG clearly fails to do this accurately enough to recover the details, especially in the extreme regions. I've been testing out a higher peak nit value of 1000 to bring in the highlights more accurately towards something that dynamic tone mapping won't over darken or screw up.

I thought that madVR does do dynamic tone mapping to adjust brightness to the whole image, but I think this only seems to work in SDR. It should be able to do this since it does know peak brightness of each scene. However, for most of the range when output in HDR, brightness seems to be unchanged. Is this due to the static metadata that is sent for HDR? Are our TVs only relying on the HDR nits mastering in the metadata to scale brightness? Maybe if the metadata can be manipulated to send peak brightness of the scene as mastering metadata, it may change the brightness range dynamically. I don't know.

HDR
14th October 2018, 04:34
Switching HDR through Windows Display settings results here in madVR too dark black clipping. Since NV 416.34 madVR is able to switch HDR by himself again (Windows>Display settings>HDR off) - black/white clipping ok now.
That's not the issue. I'm using NV for HDR output.

LG's active HDR dynamically adjusts the brightness of the entire image per frame. madVR does not. Because of this the madVR image appears too dark on most low/mid lit scenes compared to LG's implementation.

Anyone who has an oled can clearly see the difference between the two.

https://media.flixcar.com/f360cdn/LG_Electronics-2407895202-Calibration_Notes_for_2017_LG_OLED_TVs.pdf

*LG’s ‘Active HDR’ function analyses content on a frame by frame basis in real time, to
determine metadata for the scene. This information is then used to adjust the HDR tone-curve
to match the content, on a frame by frame basis.
Control of the ‘Active HDR’ feature is found in the ‘Dynamic Contrast’ setting in the Expert
Picture Settings menu. In HDR mode, the Dynamic Contrast settings are defined as follows:

Off - Active HDR Disabled / Contrast Enhancement Disabled

Low - Active HDR Enabled / Contrast Enhancement Disabled

Medium - Active HDR Enabled / Contrast Enhancement Low

High - Active HDR Enabled / Contrast Enhancement High
The default setting of ‘Low’ is recommended for accurate content reproduction.

I agree, however I can also clearly see the benefit of the pixel shaders in reeling in the highlights into the brightness range of the TV. The dynamic tone mapping on my LG clearly fails to do this accurately enough to recover the details, especially in the extreme regions. I've been testing out a higher peak nit value of 1000 to bring in the highlights more accurately towards something that dynamic tone mapping won't over darken or screw up.
Ya, madVR is clearly better at restoring detail in extremely bright regions than the tv, but only if "highlight recovery" is turned on, and the higher setting the better, (are you insane?) is my preference.

ryrynz
14th October 2018, 06:30
It's 'are you nuts!?' considering this is madVR, maybe this should be expected?

I'd like to put forward some new setting names.
None - remove
low - Pretty mad
medium, Right mad
High - Extremely mad
Very high - Super mad
Are you nuts!? - Chris Brown mad.

j82k
14th October 2018, 07:26
LG's dynamic tonemapping will literally brighten up any scene that isn't super bright already. I guess they implemented it for those watching in a bright room or for those that always complain about HDR being too dark. Personally I don't like it, it's like compressing the dynamic range of an audio track so that every scene has the same volume. With madVR dark scenes will stay dark unless you use a very low target nit peaks value.
Brighter isn't always better even if a lot of people seem to think that way...

blaubart
14th October 2018, 07:49
That's not the issue. I'm using NV for HDR output.

?? Also Windows is using NV (Nvidia) for HDR output. To bypass the GPU you had to stream the video to the TV (or per USB). I do that often to see what Windows/madVR actually are doing wrong.. :)

huhn
14th October 2018, 08:05
windows is not using nvidia API to accept an HDR image from software.

we currently have 3 different HDR APIs.
windows own API.
nvidias API
and AMD API.

but you are just making conclusion without even known this.

Hmm...my line of thinking is this: no display is natively BT.2020, even the ones with the widest of gamuts need to remap from native gamut to a stabdard gamut ...even plasmas were not strictly rec.709, they had wider gamuts than rec.709 natively, there is always a 3D LUT or some other processing involved to get the colors in place (especially if a display has user-accessible CMS system) and these things should be optimized to run without hickups in all circumstances...
you can not use an Tvs CMs change red to red -1 and it will create a new 3D LUT. and that'S not the point with bt2020 you send the display a ton of useless data or a lot of data that can be corrected beforehand .sending DCI P3 would be far better for the time been.

blaubart
14th October 2018, 09:19
..angry huhn again - do you feel better now? My above conclusions in the end were right. Having wrong black/white clipping is in the end as easy as having a buggy driver version. No theories needed for that.

huhn
14th October 2018, 09:29
do i really have to quote your ycbcr stuff?

just read the FAQ: https://forum.doom9.org/showpost.php?p=1271416&postcount=2

SirSwede
14th October 2018, 10:11
"the TV", there are 1000 different TVs with 100 different scaling abilities. And which answer do you expect if you ask true madVR Fan's if any TV on ths world scales better then madVR :p

I actually mentioned which TV in a few of the previous posts. :)

HDR
14th October 2018, 11:03
LG's dynamic tonemapping will literally brighten up any scene that isn't super bright already. I guess they implemented it for those watching in a bright room or for those that always complain about HDR being too dark. Personally I don't like it, it's like compressing the dynamic range of an audio track so that every scene has the same volume. With madVR dark scenes will stay dark unless you use a very low target nit peaks value.
Brighter isn't always better even if a lot of people seem to think that way...
It accomplishes the same thing that HDR10+ and Dolby Vision does.

If you enjoy watching crushed blacks and a dim picture be my guest.

nevcairiel
14th October 2018, 11:35
It accomplishes the same thing that HDR10+ and Dolby Vision does.

Not really, its just "fake".

Actual dynamic HDR has mastering engineers controlling the parameters of every scene, so that intentional brightness differences are fully maintained, which can give a movie much more depth.
Those automatic algorithms have no clue about the creative intent of a movie and they just "unify" everything, which can take away a lot of depth.

For me, its in a similar boat to the extremely cranked up brightness and color vibrance, or those fake HDR encodes you can find online made from consumer SDR sources. It makes for good show floor presentation, but its far from the creative intent of a movie. If you are into that sort of thing, go nuts. But don't claim your subjective preference is the only valid way to watch anything, because thats just silly.

vanden
14th October 2018, 11:40
Edit: it's fixed in madVRhdrMeasure10, just wait for the new release. (Although my laptop doesn't have enough juice to use both "compromise tone & gamut mapping ..." unchecked and "highlight recovery" at the same time :) )
Yes it works properly with "madVRhdrMeasure10"

el Filou
14th October 2018, 12:03
I am personally suspicious of someone whose account name is 'HDR' and whose very first actions on this forum consist of coming to madVR's thread just after the release of the best HDR processing featureset in a renderer, to say LG's TVs are doing a better job. :rolleyes:

Manni
14th October 2018, 12:36
Actual dynamic HDR has mastering engineers controlling the parameters of every scene, so that intentional brightness differences are fully maintained, which can give a movie much more depth.
Those automatic algorithms have no clue about the creative intent of a movie and they just "unify" everything, which can take away a lot of depth.


Exactly :)

zapatista
14th October 2018, 12:36
a general question for the video experten here:

is it possible with madvr to use the GPU (for ex from a gtx 1060) to play mp4 video files instead of it being processed by the cpu ?

my haswell i7 cpu seems to do most of the work , and i am hoping to offload it to the more modern GPU that might be more efficient (fine for mp4 @ 2k, but the cpu maxes out on 4k mp4 files while the GPU is only @ 10% load). with HEVC files of same resolution, the GPU does most of the work and the cpu stays @ 20 % for ex, this is much more hardware cpu/gpu efficient (i know hevc is a much more efficient file format, but am hoping the gpu can be used more for mp4 decoding now to)

sneaker_ger
14th October 2018, 13:05
Madvr doesn't do video decoding by itself, other components need to handle that. Usually, players/decoders that allow HEVC hardware decoding also allow H.264/AVC hardware decoding (H.264/AVC is the most common codec in mp4 files, but there are others). For example LAV Video/MPC-HC can do that.

kostik
14th October 2018, 13:06
Anyone else have a pinkish-magentish screen if you choose YCbCr 4:2:0 when watching HDR content (MADVR shows NV HDR...) ?

Switching to HDR mode using windows display settings , works fine.

driver version : 416.34 , latest madvr build

blaubart
14th October 2018, 13:16
do i really have to quote your ycbcr stuff?

just read the FAQ: https://forum.doom9.org/showpost.php?p=1271416&postcount=2

If you knew how deep I doubt in internet being the right place to discuss tiny differences in video playback... One is telling what he sees another is telling what he sees.. then wrapped into some convenient theory (including 'I am right') that's it.

Nobody can see into the ohters screen so no true comparision at all - so no truth at all - so happy dicussion till the end of all days.. :o

huhn
14th October 2018, 13:24
so you still didn't read it and understand that madVR has nothing todo with how a GPU is turning the RGB data from madVR to yCbCr...

Anyone else have a pinkish-magentish screen if you choose YCbCr 4:2:0 when watching HDR content (MADVR shows NV HDR...) ?

Switching to HDR mode using windows display settings , works fine.

driver version : 416.34 , latest madvr build
i take from this it is working fine with RGB?

kostik
14th October 2018, 13:32
so you still didn't read it and understand that madVR has nothing todo with how a GPU is turning the RGB data from madVR to yCbCr...


i take from this it is working fine with RGB?

Working fine with ycbcr 4:2:2/4:4:4 and RGB … only happens with ycbcr 4:2:0 when the screen switches to HDR mode (NV HDR not Windows HDR which works fine)…