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

HauteTension
5th April 2020, 02:20
1) I suppose he himself is in serious throwings.
Therefore, so far has not given a direct answer.
However, we see the facts.
They are such that the development of MadVR in its usual form has long been stopped.
Algorithms do not develop. There is no support for new formats.
It is not known how long the code will work until the next update of WIN or video drivers
turn it into a useless set of zeros and ones.

You can call it a “project frozen” or something else.
But the facts remains.


2) Actually for MadShi personally, it`t not so bad "businessplan".
As I understand, he got some sort of venture funding for "Envy project" and some share in "madVR Labs, LLC".

It brought enough money so that for about two years not to engage in any other work.
At the same time, without releasing any finished product to the market :)

Are there any real market prospects for this device?
Why, in an era when high-end projectors will rapidly die out under the onslaught of WALL`s, capable of showing real HDR,
someone in this market will need a video processor sharpened for HDR to SDR conversion?
And with a single HDMI-input?
Will they be able to sell more than one or two dozens of these devices?

Who cares?

3) Suppose, after another year or two, it will become obvious that the Envy project has suffered a complete commercial failure.
Everyone in "madVR Labs, LLC" had a good time, but sooner or later the funds will run out.

Will this be a reason to suddenly resume work on MadVR ?
In the free version, after all, it is unlikely.

Perhaps madVR will return as paid software?
But even here the prospects are misty.
Selling "millions copies" and earning 50-100 million euros will definitely not work here :)
On his own site, madshi talks about "hundreds of thousands of madVR users world-wide."
Suppose there are 500 thousand . But these are those who use the program for free.
Usually, only 1-2% of the user base are ready to switch to the paid version.
This is only 5000 people :)
Theoretically, even this tiny base is enough to feed one developer, although this will not turn him into a millionaire.

mykillk
5th April 2020, 02:45
So back in the realm of actual MadVR questions. For "10-bit" displays that are actually 8-bit + 2-bit FRC, what should I set the native display bitdepth to in the properties section? EDID info shows 8-bit for bitdepth but I'm wondering if I should force it to 10-bit (particularly for HDR content) because it is capable of displaying more colors with FRC tricks.

Asmodian
5th April 2020, 03:33
No, 10 bit is not important, even for HDR. Keep using 8 bit to save yourself from extra complications for no benefit.

tp4tissue
5th April 2020, 13:11
So back in the realm of actual MadVR questions. For "10-bit" displays that are actually 8-bit + 2-bit FRC, what should I set the native display bitdepth to in the properties section? EDID info shows 8-bit for bitdepth but I'm wondering if I should force it to 10-bit (particularly for HDR content) because it is capable of displaying more colors with FRC tricks.

There's no such thing as 2 bit frc, it's either 8 bit or 10 bit.

the 10 bit can be achieved by 8 bit + frc or 8bit+ High-frc

You don't need to worry about this. Madvr output looks like 10bit even on 8bit.

the 10bit engine on the TV usually doesn't work well or works poorly, while 8-bit support is typically ubiquitous and stable.

Owyn
5th April 2020, 14:07
Just watched a video news about Nvidia's DLSS 2.0 https://www.youtube.com/watch?v=YWIKzRhYZm4
And I've been very wondering - can it be used to play old low-res 480p videos in mediaplayer? If in games it's a matter of fps - here it's a moon landing of upscaling (if I understand this right)

huhn
5th April 2020, 14:56
it seems to be hilariously bad:

https://i.imgsli.com/images/3f4bc0c7-b215-4f88-ac28-a131d0013c45.png
https://i.imgsli.com/images/f5ee702b-e17c-475f-b395-a1ee0cda82cb.png

littleD
5th April 2020, 21:22
Usually most of quite new games are playable on low end gpus. Its enough to turn off vsynch, antialiasing (especially MSAA and variations) and start with all quality on medium which is enough visual quality in today's game engines.
DLSS and Variable Rate Shading are teqniques for reducing quality. That is buisness move. Instead making games even faster on low end gpu, make them look worse, hah.

Keeping to game technologies, I would rather look at something called DSR. Upsample first, then downsample to native screen resolution leaving all aliasing away. Watching 4k movies (samples :) ) on my screen i get aliased power lines and fences and any other thin long lines. I am still about to find fast 4K to HD good quality image scaler.

claw
5th April 2020, 22:07
madshi has made available for download and testing more than 100 builds of MadVR since September 2018 and since the last official release.

huhn
5th April 2020, 22:15
a cheap downscaler is bicubic 150.
madVR doesn't seem to be using convolution(or what's called) that'S why it can go terrible wrong but it's super cheap even with convolution.

you can try it with convolution in mpcVR.

littleD
5th April 2020, 23:06
a cheap downscaler is bicubic 150.
madVR doesn't seem to be using convolution(or what's called) that'S why it can go terrible wrong but it's super cheap even with convolution.

you can try it with convolution in mpcVR.Yes, thanks, madvr bc150 is nice even from 8k to hd :) But on intel frame droppping starts from 4k60fps to hd.
Mpcvr bicubic/sharp does not antialias.

@claw
I am on laptop with igpu and dgpu nvidia. I have to use igpu dxva hw acceleration decoding. Then i cannot use nvidia card for madvr, have to use intel gpu for scaling.

HauteTension
6th April 2020, 09:30
madshi has made available for download and testing more than 100 builds of MadVR since September 2018 and since the last official release.

- He could do even 1000 releases per year. Or at least 100 releases per day.
What's the use? Is it at least 1%, somehow improved the "classic" MadVR?

Likely the speech about "Advanced HDR tone mapping" addition?
Well, madshi himself really needs this because he wants free beta testers for the Envy Project.
But hardly more than 5% of those who communicate in this thread really need this option.

QBhd
6th April 2020, 09:44
Again... 7 posts from a lurker and we have an expert of this thread? How very interesting...

Also it is never a good sign when people with "beliefs" start spouting numbers... Usually means there is no reasoning with those people since they see their belief as fact.

QB

HauteTension
6th April 2020, 09:51
I am not saying that madshi does nothing.
On the contrary, it may work in this area much more than usual.
But what do we care about this job now?
When I say that madVR is DeadVR, I mean the demise of the project in the classic version "for the masses."
This work is for some very wealthy guys who are willing to pay $10K for admission :)

For him promised a lot of delicious new options.
For instance:

1) New, much better CNN algorithms.
True, they are not yet available, while open CNN solutions are developing with might and main and have surpassed any NGU in quality. (http://web.archive.org/web/20191105030230/https://artoriuz.github.io/mpv_upscaling.html)

2) Special algo implemented which has a similar effect as "genlock".

3) Envy has a database of which algorithm costs how much rendering time at which quality level with which input & output resolutions. Using this database, Envy decides automatically which algorithms can be run in which quality without causing the GPU to run out of steam ... Envy does all this automatically, so the GPU is always running at about 85% of its power.

4) More performance with the same hardware.
"Since Envy only uses Nvidia GPUs, I can use CUDA for new algos, or for optimizing existing algos. The HTPC software also has to support AMD and Intel, so using CUDA there isn't really a good option."

5) And - even more.
"In the future, Envy will use Tensor cores for AI processing."

Here is the complete list of sweets (https://www.avsforum.com/forum/37-video-processors/3053602-madvr-envy-anticipation-thread-72.html#post59346350) that are served in a $ 10K pack.
All this could have appeared in the classic MadVR for a long time.
But now it will not appear, because its existence fundamentally contradicts new, commercial interests.

So, what do we care about all these goodies now?

Manni
6th April 2020, 10:07
Stop feeding the troll ;)

nevcairiel
6th April 2020, 10:21
@HauteTension
If you think you could do better, you should actually do so and show us. If you can't, then there is really nothing else to say.

zapatista
6th April 2020, 17:52
Hi Madshi,

1) for the use of MadVR in win 8.1 (sending 10 bit video over hdmi to a 2e display in full screen mode) does it matter if i use Aero (light), a high contrast theme, or use a default (classic) theme for my desktop ?
i vaguely remember there might be some reasons not to use Aero modes with madvr, but it seems to work better for me atm (when i right click on the video screen playing in FSE mode to alter subtitle settings etc, it seems to disrupt the playing video less)

2) is there any external usb "digital tv receiver" unit that you recommend for use with madvr ? (eg USB DTV dongle type unit)

thank you for your great madvr program, it makes a Big difference in video quality on a good display with HTPC use :)

tp4tissue
6th April 2020, 19:14
Again... 7 posts from a lurker and we have an expert of this thread? How very interesting...

Also it is never a good sign when people with "beliefs" start spouting numbers... Usually means there is no reasoning with those people since they see their belief as fact.

QB

Many people have mental illness, be nice.

DigitalLF
6th April 2020, 19:58
Sorry guys, terribly busy atm. Just to let you know: My Nvidia driver contact just informed me that the HDR passthrough problems (not always engaging, and incorrect metadata) should be fixed in the next bigger driver release.


TODAY it has been ONE YEAR since MadShi wrote here.. Hope hes doing well and not working to hard on Envy!

huhn
6th April 2020, 20:11
this is not the first time this happens just move on and wait until he returns.

if madVR gets scraped, disconnected, returning to the old days or what ever fantasy someone wants to come up with nothing discussed here will change that.

if you want to add your input on this topic do it where is is active now and even talks about it and add your thoughts on it this may have an effect unlike this useless doom saying.

the current stated fact is madVR will continue and the details are unknown most likely even for madshi.

HauteTension
7th April 2020, 19:04
Many people have mental illness, be nice.

It seems to me that mental illness is more likely when some people are so blind that they stubbornly believe in the continuation of free gifts
from the good Weihnachtsmann (german Santa Claus :)
Although they are no longer five years old.
And for two years now, Santa stopped harness his deers and sent them to stand as a window of Hi-End AV-salon :)
In addition, even Santa himself directly told them that the distribution of gifts "went sales through the floor" (https://www.avsforum.com/forum/37-video-processors/3053602-madvr-envy-anticipation-thread-73.html#post59405260)
and he "can't just brush off my business partner and all the distributors and dealers."

The situation is absolutely transparent.

But this does not prevent some peoples from believing that they need just have to wait a little longer
and free gifts will soon begin to pour in their mouths :)

mclingo
7th April 2020, 20:50
I)

Out of interest, how useful do you really think your comments are, do you really think you are contributing positively to this thread?

Manni
7th April 2020, 23:33
Stop feeding the troll ;)

wasper
8th April 2020, 04:11
Hello everyone,

I need some helps. I have an Intel card GPU is able to do HEVC decoding at 4K 10 bits. I have a video that is HDR 59fpf at 4k. This video play just fine n VLC. I can't play it in MADVR. The problem is probably related to the use of the GPU for decoding.

LAV at 0.74.1

The left pane is the use of the GPU by VLC, the right pane by MADVR. Any idea why isn't using gpu like VLC?

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


Hello,

Just in case it could help a dummy like me, the problem was that lav filter were using copyback. Even with gpu decode, the bus or cpu can't manage copyback for such framerate and resolution. I use MadvR through Jriver and I have some user exit that make possible for me to switch from built-in lav filter with copy back setting and an installed version using native dxva to play really high rate files. However, I'm wondering if there is some script that could change the lav setting dynamically?

nsnhd
8th April 2020, 04:57
So, the real problem is Jriver not allowing native dxva ?
How is Intel Iris Plus 655 doing with madVR ? Can it do tone mapping without problems ?

nevcairiel
8th April 2020, 08:14
Just in case it could help a dummy like me, the problem was that lav filter were using copyback. Even with gpu decode, the bus or cpu can't manage copyback for such framerate and resolution. I use MadvR through Jriver and I have some user exit that make possible for me to switch from built-in lav filter with copy back setting and an installed version using native dxva to play really high rate files. However, I'm wondering if there is some script that could change the lav setting dynamically?

There is an option under the checkbox that enables hardware decoding in JRiver, named "Optimize hardware decoding for performance", if you enable that it'll use DXVA2 Native.

chros
8th April 2020, 12:01
1) New, much better CNN algorithms.
True, they are not yet available, while open CNN solutions are developing with might and main and have surpassed any NGU in quality. (http://web.archive.org/web/20191105030230/https://artoriuz.github.io/mpv_upscaling.html)
Thanks, that was an interesting read!
The first time I saw proper measurements about different scaling algos.

Unfortunately only madVR NGU Very High was tested, not the much faster variants (High, Med, Low).
It's indeed interesting to see that FSRCNNX is in the same ballpark as NGU algos. FSRCNNX-16-0-4-1 luma is about the same performance here as NGU Sharp High, while FSRCNNX-8-0-4-1 is way faster.

Do you know how exactly (which tools) the actual measurements (PSNR, SSIM, IW-SSIM, PSNR-HMA, PSNR-HA) were created to be able to replicate them? I'd like to try it out here.

And lastly, why was the whole github repo deleted? :)
Edit: it was renamed then renamed again, it's here (https://artoriuz.github.io/mpv_upscaling.html) now

tp4tissue
8th April 2020, 17:13
So, the real problem is Jriver not allowing native dxva ?
How is Intel Iris Plus 655 doing with madVR ? Can it do tone mapping without problems ?

I don't think anything below a 1050ti / 1060 can do tonemapping reliably.

Alexkral
8th April 2020, 19:11
Thanks, that was an interesting read!
The first time I saw proper measurements about different scaling algos.

Unfortunately only madVR NGU Very High was tested, not the much faster variants (High, Med, Low).
It's indeed interesting to see that FSRCNNX is in the same ballpark as NGU algos. FSRCNNX-16-0-4-1 luma is about the same performance here as NGU Sharp High, while FSRCNNX-8-0-4-1 is way faster.

Do you know how exactly (which tools) the actual measurements (PSNR, SSIM, IW-SSIM, PSNR-HMA, PSNR-HA) were created to be able to replicate them? I'd like to try it out here.

And lastly, why was the whole github repo deleted? :)
Edit: oh, I found the original here (https://joaochrisostomo.github.io/mpv_upscaling.html)

I've been doing some tests myself related to what I am working on, when I finish I'll post some results with the metrics that I consider most interesting. The performance of NGU sharp very high is usually comparable to FSRCNNX with any metric, the other settings (high, medium, and low) are always a bit below. The other NGU variants produce worse results, but still better than interpolation methods (except NGU soft).

Most of the metrics are implemented in Matlab, there are plenty to try:

http://www.ponomarenko.info/psnrhma.htm

senzaparole
8th April 2020, 19:20
hi guys,
if in Calibration I set disable calibration controls for this display, in Color & Gamma do I have to set enable gamma processing?

Asmodian
8th April 2020, 19:25
Gamma processing is only if you want to make adjustments, it is not part of calibration. You do not have to enable it, in fact I would not use it unless your screen's gamma is bad and you cannot fix it on the display itself.

Personally I would set your calibration to something, probably BT.709 - pure power 2.2, if disabled looks good for most content.

tp4tissue
8th April 2020, 22:35
hi guys,
if in Calibration I set disable calibration controls for this display, in Color & Gamma do I have to set enable gamma processing?

You need a colorimeter to really mess with the gamma, every display is different, and between the different tv modes, or monitor modes, the gamma and grey balance could change as well. So while you can tweak it until it looks good to you, that's a bad idea unless you've had alot of experience with reference images and know how it's suppose to look.

And catch 22 is, if you are such a person, you probably have a colorimeter.

amayra
8th April 2020, 22:46
admin or manager in this forum need to hire special mods for this thread only to keep it under control

videoh
8th April 2020, 22:51
keep it under control Ooh, a control freak. Watch out!

mykillk
9th April 2020, 01:04
No, 10 bit is not important, even for HDR. Keep using 8 bit to save yourself from extra complications for no benefit.

There's no such thing as 2 bit frc, it's either 8 bit or 10 bit.

the 10 bit can be achieved by 8 bit + frc or 8bit+ High-frc

You don't need to worry about this. Madvr output looks like 10bit even on 8bit.

the 10bit engine on the TV usually doesn't work well or works poorly, while 8-bit support is typically ubiquitous and stable.

Thanks for the info! Will stick with 8-bit.

Although HDR can look pretty amazing, I kind of miss the "old" days before it came out. HDR has made the world of video quite a lot more complicated and uncertain!

wasper
9th April 2020, 03:25
There is an option under the checkbox that enables hardware decoding in JRiver, named "Optimize hardware decoding for performance", if you enable that it'll use DXVA2 Native.

Coming from you, it must be right! Maybe, I should reinstall JRiver. I did replace the plugin folder for Lav filter with a more recent version and maybe the flag setting broke during the process. Just to be clear, using regular HQ setting the gpu is used but the decoder queue isn't filled fast enough. What I did, is to change a registry key to move from HQ to custom in function of a database tag. Using custom, it plays 4k 10bits easily at 59fps but without any enhancement! Doesn't need that much anyway for those kind of file.

Appreciate your answer and will definitely have a look how I could have broke this setting or why native isn't triggered, cause gpu is still used with copyback, right?

https://imagehost.imageupload.net/2020/04/09/Untitled2.png

wasper
9th April 2020, 03:43
So, the real problem is Jriver not allowing native dxva ?
How is Intel Iris Plus 655 doing with madVR ? Can it do tone mapping without problems ?

It should like nevcairiel said. I might missing something there and I'll try to figure out. Not too much time but I'll try to find a program that will tell me the real path from decoding to rendering.

One thing for sure, using custom settings you can use native DXVA with MADVR, so it shouldn't be something to worry. As for tone mapping, I don't use it as I dynamically switch the windows desktop between HDR and SDR in function of the movie content. Anyway, I don't have enough knowledge to give you an answer. Didn't play with windows setting but desktop looks awful in HDR with default settings. Iris is fine as it supports HEVC and VP9 decoding. Intel Nuc is small and pretty, Jriver needs tweaking and some programing skill if you want to customize the behavior exactly like you want(at least for my version but I thing it's fine in the late version). Like the quality of my HTPC. Not sure I answered your question though!

nevcairiel
9th April 2020, 09:02
Appreciate your answer and will definitely have a look how I could have broke this setting or why native isn't triggered, cause gpu is still used with copyback, right?


The checkbox is only visible if video is set to ROHQ, because in custom it can't really do anything, and in ROSTD its not needed.
It was added in MC24, the other explanation would be if you are on something earlier then that.

wasper
9th April 2020, 13:59
The checkbox is only visible if video is set to ROHQ, because in custom it can't really do anything, and in ROSTD its not needed.
It was added in MC24, the other explanation would be if you are on something earlier then that.

I was too tired yesterday and read too fast your answer about "Optimize hardware decoding for performance" and mixed up with "hardware accelerate video decoding when possible". I'm still on MC21, so everythings is explained! Everything is so fine tuned on 21 that I don't want to upgrade just in case my user exit wouldn't work as expected.

Since you are there, I got a video clip that is 4k HEVC (bitrate at 56312) that doesn't use gpu decoding. Using DXVAChecker, I got this:

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

The file: https://mega.nz/#!7hUGxQwb!nZknEB5dQaxgf5K_0ttBNrGRcTKH6fH7iowG8gadYYg

Normal behaviour? Once again, thanks for your time.

senzaparole
9th April 2020, 17:57
Gamma processing is only if you want to make adjustments, it is not part of calibration. You do not have to enable it, in fact I would not use it unless your screen's gamma is bad and you cannot fix it on the display itself.

Personally I would set your calibration to something, probably BT.709 - pure power 2.2, if disabled looks good for most content.

You need a colorimeter to really mess with the gamma, every display is different, and between the different tv modes, or monitor modes, the gamma and grey balance could change as well. So while you can tweak it until it looks good to you, that's a bad idea unless you've had alot of experience with reference images and know how it's suppose to look.


Thanks for your advice. I do not have a colorimeter or experience with images.
I am aware that I cannot achieve perfection but thanks to your help I would like to obtain a satisfactory result.

I set in "this display is already calibrated":
- BT.709 and pure power curve 2.20.
I disabled "enable gamma processing".


I take this opportunity to ask you another doubt.
I own a B9 OLED TV. After several tests I decided to use the conversion from HDR to SDR.
Did I have a good idea?
I use these settings:

https://i.ibb.co/ZBCB40d/hdr.png (https://ibb.co/Lxfxj3S)

https://i.ibb.co/0mbfdFQ/IMG-20200407-104022-1-ridotta-ok.jpg (https://ibb.co/tQrbWx3)

In "display peak luminance" I set 80. And in "dynamic target nits" : 50.
Are values ​​too low? Do I lose some details?
For example, to obtain adequate brightness, I could increase the value of the "display peak luminance" and in "this display is already calibrated" increase the value of pure power curve from 2.20 to 2.40. What do you think?
Thanks for your suggestions.

QBhd
9th April 2020, 18:55
Why have an HDR device and source and not use it... your settings make no sense to me.

QB

Cowboydude99
9th April 2020, 22:13
Hi there,
Can someone help me with my profile rules. I cannot seem to get this right...

If (scrWidth = 1920) "1080p"
Else If (scrWidth = 3840) and (fps > 30) "4K_24fps"
Else "4K_60fps"

The 4k 60 profile is never used, it always uses the settings in 4k 24fps. 1080p seems to work just fine.

senzaparole
9th April 2020, 22:32
Why have an HDR device and source and not use it... your settings make no sense to me.

QB

hi, thank you for your comment.
The conversion from HDR to SDR was not my initiative. I read that some users who own an OLED or LED TV have given up on converting HDR to HDR to switch to converting HDR to SDR.
At the beginning I was very skeptical too like you .. then I made several tests and I had to change my mind.

Asmodian
9th April 2020, 22:33
If (scrWidth <= 1920) "1080p"
Else If (scrWidth <= 3840) and (fps < 31) "4K_24fps"
Else "4K_60fps"

Cowboydude99
9th April 2020, 22:42
If (scrWidth <= 1920) "1080p"
Else If (scrWidth <= 3840) and (fps < 31) "4K_24fps"
Else "4K_60fps"

Hi there. Thanks, but having the same issue. I just copied and pasted what you entered...

It looks like the 1080p is OK and the 4k 24fps is ok.
4k 60 plays the 4k 24fps profile... so line 2 seems to be catching the 4k60 file...?

Cowboydude99
9th April 2020, 23:00
When setting up MadVR, I set the HDR to passthrough.
HDR profile does show up on my projector.

If I Control+J the video to see the details, it shows up BT.709 (Best Guess). I'm playing 4k UHD files. I believe they're all BT2020.

Is there a setting I need to adjust? I have the PJ showing in MADVR with calibration of BT.2020.

Also HDR shows "Unknown".

NVIDIA control panel shows 8Bit RGB Full

QBhd
10th April 2020, 00:01
if (srcHeight < 1081) and (deintFps < 25) "1080p23"
elseif (srcHeight < 2161) and (deintFps < 25) "2160p23"
elseif (srcHeight < 2161) and (deintFps < 61) "2160p59"



This is a very trimmed down version of mine:


if (srcHeight < 721) and (deintFps < 25) "720p23"
elseif (srcHeight < 1081) and (deintFps < 25) "1080p23"
elseif (srcHeight < 2161) and (deintFps < 25) "2160p23"
elseif (srcHeight < 721) and (deintFps < 26) "720p25"
elseif (srcHeight < 1081) and (deintFps < 26) "1080p25"
elseif (srcHeight < 721) and (deintFps < 31) "720p29"
elseif (srcHeight < 1081) and (deintFps < 31) "1080p29"
elseif (srcHeight < 2161) and (deintFps < 31) "2160p29"
elseif (srcHeight < 721) and (deintFps < 51) "720p50"
elseif (srcHeight < 1081) and (deintFps < 51) "1080p50"
elseif (srcHeight < 721) and (deintFps < 61) "720p59"
elseif (srcHeight < 1081) and (deintFps < 61) "1080p59"
elseif (srcHeight < 2161) and (deintFps < 61) "2160p59"


QB

mclingo
10th April 2020, 00:08
hi, thank you for your comment.
The conversion from HDR to SDR was not my initiative. I read that some users who own an OLED or LED TV have given up on converting HDR to HDR to switch to converting HDR to SDR.
At the beginning I was very skeptical too like you .. then I made several tests and I had to change my mind.


Hi, i've dabbled with this myself and i'm doing that at the moment for reasons I wont bore you with but my OLED is only 450 nits max so Its barely capable of HDR, I would say if you have a new OLED with 700+ nits you should probably output to HDR but also have a play with tone mapping in madvr to pull out a bit more highlight detail.

Asmodian
10th April 2020, 00:23
Hi there. Thanks, but having the same issue.

Ah, use deintfps instead of fps, like QBhd did above, perhaps also use 26 instead of 30:

If (scrWidth <= 1920) "1080p"
Else If (scrWidth <= 3840) and (deintfps < 26) "4K_24fps"
Else "4K_60fps"

Cowboydude99
10th April 2020, 00:39
if (srcHeight < 1081) and (deintFps < 25) "1080p23"
elseif (srcHeight < 2161) and (deintFps < 25) "2160p23"
elseif (srcHeight < 2161) and (deintFps < 61) "2160p59"



This is a very trimmed down version of mine:


if (srcHeight < 721) and (deintFps < 25) "720p23"
elseif (srcHeight < 1081) and (deintFps < 25) "1080p23"
elseif (srcHeight < 2161) and (deintFps < 25) "2160p23"
elseif (srcHeight < 721) and (deintFps < 26) "720p25"
elseif (srcHeight < 1081) and (deintFps < 26) "1080p25"
elseif (srcHeight < 721) and (deintFps < 31) "720p29"
elseif (srcHeight < 1081) and (deintFps < 31) "1080p29"
elseif (srcHeight < 2161) and (deintFps < 31) "2160p29"
elseif (srcHeight < 721) and (deintFps < 51) "720p50"
elseif (srcHeight < 1081) and (deintFps < 51) "1080p50"
elseif (srcHeight < 721) and (deintFps < 61) "720p59"
elseif (srcHeight < 1081) and (deintFps < 61) "1080p59"
elseif (srcHeight < 2161) and (deintFps < 61) "2160p59"


QB

Ah! That did the trick. I ended up using the following:

if (srcHeight <= 1080) and (FPS < 25) "1080_24fps"
elseif (srcHeight <= 2160) and (FPS < 25) "4K_24fps"
elseif (srcHeight <= 2160) and (FPS < 61) "4K_60fps"

Cowboydude99
10th April 2020, 00:47
Hi,
Here is a screenshot of the issue with BT.709 (Best Guess).

I have an HDR projector (JVC) and the chain is:

Jriver Media Center + MadVR + SVP4 Pro -- Denon AVR -- Projector.

The PJ turns on the HDR profile.

The files are BT.2020 UDH disks.

Any idea what needs to be changed to ensure BT.2020 color and that HDR is actually in use?

Also, NVIDIA Control Panel = RGB 8Bit Full. 422.74 drivers (Win 10). I am able to change it to YCC422 10bit.

Screenshot below shows RGB 8bit, but I can set it to 422/10bit. It will show in the OSD, but it continues to show BT709.

https://drive.google.com/open?id=1hw2uxKckNAIIQoP1W4puDwFyp9gNrSKk
https://drive.google.com/open?id=1hw2uxKckNAIIQoP1W4puDwFyp9gNrSKk