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

madshi
4th September 2017, 16:02
Ctrl+Alt+Shift+Break/Pause does unfortunately not work (not in Win10 nor in Win81)
Then please try running this exe and pointing it to the media player process:

http://madshi.net/madTraceProcess32.zip

for the judder Problem I have made two Screen shots. one for 2D (both on Win81)
The stats look ok, except for the frame drops. Do those frames drops all occur when the movie starts or when you switch from windowed to fullscreen mode? Or do they pile up during playback in fullscreen mode? What kind of judder is it? E.g. is it juddering all the time? Or once every couple of seconds or minutes?

You misread my post. D3D DXVA is active, the problem is that when in native mode the video freezes each time for 3 seconds after refresh rate is switched.

It does not have this problem in D3D11 CB mode.
Ok, thanks, I think I know what this problem is. Please let me know if they next madVR build has still not fixed this.

i just remembered a problem with AMD cards where windows things 4096x2160 is the native resolution of normal UHD TV screens.
madshi did you checked the EDID with your polaris card to see if AMD is doing some none sense to it or that the EDID doesn't match with windows recommended resolution?
I'm not sure if Windows interprets the EDID on its own or if Windows relies on the GPU driver to interpret the EDID. In any case, it doesn't matter to me, I interpret the EDID myself, so it's not a problem to me if either the OS or the GPU driver does it incorrectly.

That explains why reducing the back porch (which reduces the blanking interval) gives me almost perfect 23.976 refresh. But in order to do this, I have to lower the total pixels on my TV to 1123, and that results in weird lines either at the top or bottom of the screen, which must be a result of the missing pixels. There doesn't seem to be any way to both get close to the exact refresh rate and avoid this problem. Is there something about plasma TVs that might cause this?
The modes with higher "compatability" rating in the madVR custom modes optimization should have even total pixels, and still have nicely optimized refresh rates. Did you try those? Maybe they show fine on your TV without those weird lines?

Ah, that explains things. While it's smoother now, it's not like the immersive experience of smooth motion. I don't think my monitor is doing 71.928 hz for real.:devil:
That's quite possible. My LCD computer monitor doesn't do it for real.

Thanks for your support.
Now I try to optimize the custom mode 23p.
Select 23p, edit and then apply the EDID info. Now I can press the Optimize Button.
Start a video with 23.976 fps and then I have this screen:
https://ibb.co/goRmgk

The i press Optimize and select the Optimize Pixel Clock #1
https://ibb.co/hiFe1k

I select this profile, reboot the PC but when i start the video with 23.976 fps, I have always 1 frame repeat every 4.40 min.
why?

This is my setting
https://ibb.co/jtxWE5

Where is my error?
I have a nVidia 1070GTX GPU
It seems that 1 frame repeat every 4.40 minutes is also what you had before starting the whole process, is that correct? In that case it seems that the custom timings are not activated by the GPU at all, for some reason. I'm not sure what the exact reason is, unfortunately. I'd suggest that you try either with fullscreen exclusive mode turned on or off, and with the "use D3D11 for presentation" option turned on or off, to see if any of that makes a difference. It's possible that the GPU driver doesn't use our custom modes in some situations.

I am giving custom timings a try but it's not working with 59hz. I tried all the optimizations but it won't let me apply after testing. Says "gpu rejected this mode for unknown reasons".

23hz optimized timings works fine. Unfortunately I'm getting a frame drop every ~25 minutes on the default settings for 59hz.
It's a known Nvidia driver issue that it rejects some custom modes without even saying why. You can try manually changing the pixel clock by 0.01 to see if that makes the Nvidia driver accept a mode. In any case, maybe there's hope to have this fixed in a future driver version. However, my Nvidia contact hasn't replied in the last 2-3 weeks. So I'm not sure I'll hear from him again... :(

I cant play 3D MVC properly when windows in on 4k Resolution. The output seems be so stretched and only shows the magnified upper left part of the video. Any suggestions?
What does the Ctrl+J OSD say? Maybe the media player didn't tell madVR to zoom the image up properly? madVR obeys to the media player commands.

I am not sure which timings are best when it comes to optimization...

A. Current/measured timings Compat. is 100 with 1 frame repeat every 12.35 minutes
B. Same pixel clock #1 Compat. is 60, with 1 frame repeat every 3.90 hours
C. Optimized pixel clock #1 Compat. is 80 with no frame drops/repeats
The best is one is the one which 1) works and 2) produces the best drops/repeats stats. The compatability rating is just madVR's guess at which of the modes has the highest chance of working. But all the modes might be working, or none. Just try them out.

I am using Windows 10 Enterprise, and Windows Update brings all kinds of updates except for the upgrade to Creator's Update (not sure why). Also, I haven’t bothered to do a fresh install for upgrading to the Creator's Update. I will probably do that now.
If you do decide to upgrade to Creator's Update, it would be interesting to hear if FSE mode is still more reliable for you than fullscreen mode.

Recently switched to Windows 10 from 7 (clean install). Having a couple issues now.
And another user who ignored my advice. Your fault... :p

I don't think windows 8.1 is even recommended for anything.
Wrong. I've been recommending win8.1 for a long time now as the best HTPC OS atm. The only reasons to use win10 on an HTPC is if you need it for D3D12 games.

I'm trying to play a 2880x2880 file on a 4k LG OLED, but I'm getting a black screen instead when going fullscreen on the TV. Sound plays, no image though, but if I move the mouse over the lower part of the screen, the MPC-BE playback bar appears fine.
What does the madVR OSD (Ctrl+J) say?

During play my CPU is on 100% utilization, however I am using DXVA2 for hardware decoding.
"native DXVA2" or "DXVA2 copyback"?

Hello to all fans of custom resolutions!
I have made a package of test videos (https://www.sendspace.com/file/rkwcqh) for testing the accuracy of / optimizing your custom resolutions.
The package includes test videos for all common video frame rates (23.976, 24.000, 25.000, 29.970, 30.000, 48.000, 50.000, 59.940, 60.000, 120.000).
The format is MP4, resolution 640x360, simple black video, with silent audio track.
The length is 4 hours for each test video.

I made this package because it offers some advantages for testing purposes:
- all common frame rates in one package
- 4 hours long, should be sufficient for necessary accuracy
- tested timestamps and frame rate accuracy (common video material can have all sort of timestamp quirks, there are videos out there with "wrong" 23.9760000 fps etc.)
- comparable bitrate etc because of black video, so constant GPU load
- the whole package has 7 MB file size because of black video, silent audio and RAR compression

Some hints for testing / optimizing custom resolutions:
- test at least the time for a normal movie, so something like 2 hours
- leave the computer alone while measuring (no mouse and keyboard actions)
- the involved computer clocks are influenced by temperature to a certain degree, so for accurate results you should aim for constant and "real-life" temperatures (warm up your computer and generate a GPU load similar when watching normal videos by using different madvr settings).

Happy testing and optimizing ! :cool:
Nice! :)

Please I need help, no matter what I do I never get the optimized resolutions, every time I push the button there is only the window with the instructions, even after waiting 30 minutes... what exacly I have to do? because I think I'm missing something.
FWIW, I have the same
Did you create the custom modes with the madVR "custom mode" functionality? Or did you create them with the Nvidia custom mode tool (or some other tool)? There's a bug in the current madVR build which doesn't record measurements if you didn't create the custom modes with madVR.

which is the best OS for a HTPC and obviously to be used with MAdVR, windows 8.1 or windows 10 and why?
win8.1 because it can do everything win10 can (except 10bit output in windowed fullscreen), and is more stable at the same time.

I have encountered some kind of freeze with madVR FSE mode, it happened before keep skipping video (immature buffer I guess), and it can always be repeated if skipping enough times.

The configure of madVR are with NGU Soft, the freezes seems less prone to happen when there's no need to do scaling, e.g., playing back 1080p content with 1080p resolution.

Anyone suffer the same?

Edit: When the freeze happened, I'll have to use Ctrl-Alt-Del to switch to administrator account to kill the player using Task Manager.
Do you use native D3D11 decoding in LAV? If so, this is a known bug which should be fixed in the next build. Otherwise it's not a known bug.

am now getting no playback whatsoever. I really have no idea what is happening here
What does the madVR OSD (Ctrl+J) say?

i come for an feedback about a crash on madHcCtrl.exe on last madvr release.

this issue appear on 2 computer, with different hardware but with last Win10 public version.

the crash appear when edit and apply the setting in the displaymode-refreshrate section.

using madvr 0.92.2
Attaching things to this forum doesn't work, they never get approved. For a madHcCtrl.exe crash I need the full crash report. Please upload it somewhere else and link to it here, thanks.

I am experiencing a weird issue with the Test Patter Generator (TPG). I ran a calibration using DisplayCAL yesterday and all was good. It didn't look right so I tried running a verification but when I put the TPG to full screen there is no output - black screen with a mouse cursor. It worked fine in full screen the first time I calibrated.
I tried several times and indeed the TPG just refuses to show any content when in full screen. All seems ok when running in a window. MadVR works fine in Exclusive mode when using MPC-HC.
This is a freshly install system, Ryzen based, GTX 1050Ti with latest drivers.

Something I am not sure I am doing right: when selecting "fullscreen" the TPG window does not really go full screen so I usually force it by pressing ALT-ENTER. Am I doing that right, have I "broken" something by doing that?

I cannot run this in a window as this is a projector and the reflected light from the status bars etc would spoil the low level readings.
Pressing the "fullscreen" button doesn't show immediate effect, but it will switch madTPG into fullscreen mode automatically when measurements are starting. Anyway, using ALT-ENTER is fine, of course.

Does the mouse cursor show in fullscreen mode? Is it possible your display doesn't even sync to the GPU, for some reason?

Sorry to disturbing again. Just noticed.
MPC-HC
PIN INFO
PIN:OUT VIDEO
.
.
VIDEOINFOHEADER:
rcSource: (0,0)-(1920,1080)
rcTarget: (0,0)-(1920,1080)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 400000

MPC-BE
PIN INFO
PIN:OUT VIDEO
.
.
VIDEOINFOHEADER:
rcSource: (0,148)-(1920,932)
rcTarget: (0,148)-(1920,932)
dwBitRate: 0
dwBitErrorRate: 0
AvgTimePerFrame: 400000 (25.000 fps)

So EVR custom preset in MPC-HC crop is ignored, but in MPC-BE is propertly displayed. But MadVR in MPC-BE has same issue as in Potplayer. See http://forum.doom9.org/showthread.php?p=1816256#post1816256
Bernix
Ok, I can reproduce it, will see what I can do.

Anima123
4th September 2017, 16:07
madVR wrote: Do you use native D3D11 decoding in LAV?

No, the native D3D11 decoding is not activated during the tests. I more prefer software decoding.

madshi
4th September 2017, 16:11
Then please try Ctrl+Alt+Shift+Pause/Break to create a freeze report. If that doesn't work, try running http://madshi.net/madTraceProcess32.zip and point it to your media player in the moment when it's frozen.

Anima123
4th September 2017, 16:16
Does the freeze report shortcut work under 64-bit version? Or I need to do it with 32-bit version only?

madshi
4th September 2017, 16:18
Oh, it requires you to use a 32bit media player, but the OS doesn't matter.

Anima123
4th September 2017, 16:28
The real challenge is that I cannot get back to the desktop since the freeze is with FSE mode. The shortcut doesn't seem to work.

aufkrawall
4th September 2017, 16:31
win8.1 because it can do everything win10 can (except 10bit output in windowed fullscreen), and is more stable at the same time.

I don't think there is VP9 DXVA decoding on Windows 8.

Anima123
4th September 2017, 16:35
Please download the freeze report from Freeze Report (https://www.dropbox.com/s/db9d4a7ltflci1e/madVR_FreezeReport-2017-09-04.zip?dl=0)

Dorohedoro
4th September 2017, 16:42
Madshi, thanks for your reply.

I've deleted every custom resolution in the nvidia panel and also created the custom 1080p23hz in the madvr options.

Btw, Ive created a bunch of custom resolutions with the Custom Resolution Utility (CRU) a long time ago, maybe that app is the cause of my problems? (btw, none of the custom resolutions are active in the CRU right now).

SamuriHL
4th September 2017, 16:51
What does the madVR OSD (Ctrl+J) say?


It was in that post just not formatted very well....cause you know, why would I make it easier for people to help me. LOL Sorry about that.

Display is set to 23.97113Hz
composition rate is 23.970Hz
smooth motion is off (settings)
D3D11 fullscreen windowed mode (10 bit)
NV12, 8 bit, 4:2:0 (DXVA11)
movie is 23.976 fps
movie 1920x1080, 16:9
draw 0,0,1920,1080
touch window from inside
chroma->NGU AA (med)
vsync 41.72ms
frame 41.71ms
matrix BT.709 (says upstream)
primaries BT.709 (says upstream)
limited range (says upstream)
deinterlacing off (dxva11)
decoder queue 16
upload queue 8
render queue 8
present queue 1
dropped frames 0
repeated frames 0
delayed frames 0
presentation glitches 0
rendering 12.12ms
present 0.14ms

nevcairiel
4th September 2017, 16:51
I don't think there is VP9 DXVA decoding on Windows 8.

The OS really doesn't matter to DXVA. The same codecs are supported from 7 to 10. D3D11VA is not available on 7, but thats not the one we were talking about anyway. :)

mparade
4th September 2017, 17:18
12-bit is not supported through DXVA, no matter what the hardware claims to support.

I was succeeded in decoding my main12 HDR (HDR10 source reencoded using main12 profile) movie to madVR without dropping frames using DXVA with my EVGA Nvidia GTX 1060 6GB and the latest LAV filters integrated in Kodi Kripton 64 bit version. 32 bit decoding was failed, there was continuous frame drops with 100% CPU utilization.

azzuro
4th September 2017, 17:37
Quote:
Originally Posted by azzuro View Post
i come for an feedback about a crash on madHcCtrl.exe on last madvr release.

this issue appear on 2 computer, with different hardware but with last Win10 public version.

the crash appear when edit and apply the setting in the displaymode-refreshrate section.

using madvr 0.92.2
Attaching things to this forum doesn't work, they never get approved. For a madHcCtrl.exe crash I need the full crash report. Please upload it somewhere else and link to it here, thanks.

what full crash do you need ?
i have only the popup from windows, who say than madHcCtrl.exe stopped to work.

https://image.noelshack.com/minis/2017/36/1/1504542904-madvrcrash2.png (https://www.noelshack.com/2017-36-1-1504542904-madvrcrash2.jpg)

aufkrawall
4th September 2017, 17:40
The OS really doesn't matter to DXVA. The same codecs are supported from 7 to 10. D3D11VA is not available on 7, but thats not the one we were talking about anyway. :)
So the changes with Redstone 1 update were only concerning Edge? I somehow recall this differently.

Could someone with Windows 7 + sufficient GPU please test if VP9 hardware decoding does work there?

VHT
4th September 2017, 18:13
Madshi, thanks for your reply.

I've deleted every custom resolution in the nvidia panel and also created the custom 1080p23hz in the madvr options.

Btw, Ive created a bunch of custom resolutions with the Custom Resolution Utility (CRU) a long time ago, maybe that app is the cause of my problems? (btw, none of the custom resolutions are active in the CRU right now).

Go to the "change resolution" tab from nvidia drivers and use NVIDIA color setting instead of your displays default settings. That should do the trick.

madshi
4th September 2017, 18:26
Please download the freeze report from Freeze Report (https://www.dropbox.com/s/db9d4a7ltflci1e/madVR_FreezeReport-2017-09-04.zip?dl=0)
Ok, thanks, this will probably be fixed in the next build.

I've deleted every custom resolution in the nvidia panel and also created the custom 1080p23hz in the madvr options.
And did it help?

Btw, Ive created a bunch of custom resolutions with the Custom Resolution Utility (CRU) a long time ago, maybe that app is the cause of my problems? (btw, none of the custom resolutions are active in the CRU right now).
I thought CRU would do EDID overrides? EDID overrides should be totally different things and probably not affect custom modes.

It was in that post just not formatted very well....cause you know, why would I make it easier for people to help me. LOL Sorry about that.

decoder queue 16
upload queue 8
render queue 8
present queue 1
This information is not complete. The queue information consists of 2 numbers each.

I was succeeded in decoding my main12 HDR (HDR10 source reencoded using main12 profile) movie to madVR without dropping frames using DXVA with my EVGA Nvidia GTX 1060 6GB and the latest LAV filters integrated in Kodi Kripton 64 bit version. 32 bit decoding was failed, there was continuous frame drops with 100% CPU utilization.
How's CPU utilization in 64bit?

what full crash do you need ?
i have only the popup from windows, who say than madHcCtrl.exe stopped to work.
Does this one fix it?

http://madshi.net/madHcCtrl922.zip

Sorry to disturbing again. Just noticed.

So EVR custom preset in MPC-HC crop is ignored, but in MPC-BE is propertly displayed. But MadVR in MPC-BE has same issue as in Potplayer. See http://forum.doom9.org/showthread.php?p=1816256#post1816256
Ok, the next madVR build behave somewhat differently now in this situation. However, only for software (or copyback) decoding, and only with specific FOURCCs (e.g. NV12). Furthermore, at least MPC-BE's pin information is IMHO incorrect. It does provide cropping information, but it didn't update the aspect ratio information, which means that the cropped video area will be stretched by madVR to cover the original aspect ratio. MPC-BE must update the "VIDEOINFOHEADER2.dwPictAspectRatioX/Y" information in the pin connection info to reflect the aspect ratio of the *cropped* video.

azzuro
4th September 2017, 18:32
Does this one fix it?

http://madshi.net/madHcCtrl922.zip


no, same popup.

Dorohedoro
4th September 2017, 18:34
No Madshi It did not. I did that on my first try yesterday because I saw the similar issues other user had on this thread.

VHT I will try that as soon I get home.

Thank you so much to both of you.

madshi
4th September 2017, 18:39
no, same popup.
Argh, too bad. Can you try to point tool at madHcCtrl.exe while the error box is still open?

http://madshi.net/madTraceProcess32.zip

Maybe I can get a proper bug report this way. Please upload the bug report elsewhere (don't attach to this forum) and link to it here. Thanks.

No Madshi It did not. I did that on my first try yesterday because I saw the similar issues other user had on this thread.
Ok, in your registry in "HKEY_CURRENT_USER\Software\madshi\madVR", is there a subfolder called "DisplayModeMeasurements"? If so, does one of the subfolders is named like the custom mode that you want to measure? Does it have a "LatestMode" value?

azzuro
4th September 2017, 19:30
this is the trace report https : //forum.doom9.org/showthread.php?p=1817445&posted=1#post1817445

thread $0:
>> stack not accessible, exception location:
00000000 +ffbde2c0 madTraceProcess32.exe madStackTrace +0 StackAddrToStr

main thread ($1e50): <priority:15>
>> internal error in GetThreadStack:
004586e7 +29f madTraceProcess32.exe madExcept +0 GetThreadStack

thread $2dec:
>> internal error in GetThreadStack:
004586e7 +29f madTraceProcess32.exe madExcept +0 GetThreadStack

thread $122c:
>> internal error in GetThreadStack:
004586e7 +29f madTraceProcess32.exe madExcept +0 GetThreadStack

thread $31c4:
>> internal error in GetThreadStack:
004586e7 +29f madTraceProcess32.exe madExcept +0 GetThreadStack

thread $3240:
>> internal error in GetThreadStack:
004586e7 +29f madTraceProcess32.exe madExcept +0 GetThreadStack

thread $2cb8:
>> internal error in GetThreadStack:
004586e7 +29f madTraceProcess32.exe madExcept +0 GetThreadStack

disassembling:
>> will be calculated soon

mparade
4th September 2017, 19:39
@madshi

How's CPU utilization in 64bit?

between 34% and 60% during play of the entire video on my

Windows 10 64 bit OS
Nvidia Geforce GTX 1060 6GB
i3-6100@3.7GHz

system. Kodi reports "HVC1 (FFMpeg) (HW)" as the decoder...I thought it is executed via DXVA because I have set it in LAV Video settings...but I realized afterwards that any settings (even Nvidia CUVID) are used in LAV Video for decoding "HVC1 (FFMpeg) (HW)" is reported by Kodi as the decoder. But at least not my weak CPU is used to it's maximum for decoding in case of main12 source.

Bernix
4th September 2017, 20:01
@Madshi
Yes, you are right. I thought it croped from top same as from bottom, but I did some primitive test, and it croped video propertly in MHC-BE. I made picture (videos) There are black bars on top and bottom with height of 80px each other bars are see clearly. Sorry, i am not very clever so the picture is wrong as it could only be. But it is only demonstration. So I think no problem.
Each bar is cca 80 pixel height. There are 9 bars. resolution is 1280x720. The videos are long enought. There is source picture too. Sorry, for such primitive test, I hope it helps to see croping in EVR custom preset is properly in MPC-BE even pin info say something different.
Here is series of videos with selfexplaining croping sizes.
http://leteckaposta.cz/941169353
Thank you very much for your interest.
Bernix

tony359
4th September 2017, 20:16
Originally Posted by tony359
I am experiencing a weird issue with the Test Patter Generator (TPG). I ran a calibration using DisplayCAL yesterday and all was good. It didn't look right so I tried running a verification but when I put the TPG to full screen there is no output - black screen with a mouse cursor. It worked fine in full screen the first time I calibrated.
I tried several times and indeed the TPG just refuses to show any content when in full screen. All seems ok when running in a window. MadVR works fine in Exclusive mode when using MPC-HC.
This is a freshly install system, Ryzen based, GTX 1050Ti with latest drivers.

Something I am not sure I am doing right: when selecting "fullscreen" the TPG window does not really go full screen so I usually force it by pressing ALT-ENTER. Am I doing that right, have I "broken" something by doing that?

I cannot run this in a window as this is a projector and the reflected light from the status bars etc would spoil the low level readings.


Originally Posted by madshi
Pressing the "fullscreen" button doesn't show immediate effect, but it will switch madTPG into fullscreen mode automatically when measurements are starting. Anyway, using ALT-ENTER is fine, of course.

Does the mouse cursor show in fullscreen mode? Is it possible your display doesn't even sync to the GPU, for some reason?

Thanks a lot for your reply.
Yes, I can see the cursor and I hear DisplayCAL working in the background (taking black readings!). The moment I switch back to the window I can immediately see the pattern I was supposed to see fullscreen.
Thanks for confirming ALT-ENTER is ok. It's just that when I select FULL-SCREEN it does not seem to work and it starts taking readings not full-screen.

I'll try again tonight, is there anything I can do for you or logs to send you to help identifying the problem?

Cheers
Tony

Dorohedoro
4th September 2017, 20:46
Ok, in your registry in "HKEY_CURRENT_USER\Software\madshi\madVR", is there a subfolder called "DisplayModeMeasurements"? If so, does one of the subfolders is named like the custom mode that you want to measure? Does it have a "LatestMode" value?

Yeah there is that folder and also there are measurements for the custom 1080p23hz mode with the "LatestMode" value (REG_BINARY and a bunch of numbers in "data").

I did what VHT and Asmodian told me to do with no luck (the color option change on the nvidia settings and the resolution swiching on madvr).

Thank you so much to all of you for the help.

madshi
4th September 2017, 21:10
this is the trace report
Hmmm... Unfortunately it's not really helpful. Can you repeat the procedure multiple times? Maybe with a bit of luck you'll get one report without those "stack not accessible" and "internal error" problems? Otherwise it won't help... :(

between 34% and 60% during play of the entire video on my
That's still quite a lot, though. Are you using "native DXVA" or "DXVA copyback"? Do you have the "zoom control" options activated in madVR?

Yes, I can see the cursor and I hear DisplayCAL working in the background (taking black readings!). The moment I switch back to the window I can immediately see the pattern I was supposed to see fullscreen.
Thanks for confirming ALT-ENTER is ok. It's just that when I select FULL-SCREEN it does not seem to work and it starts taking readings not full-screen.

I'll try again tonight, is there anything I can do for you or logs to send you to help identifying the problem?
Do you have the same problems when playing a video with madVR? Also a black screen in fullscreen?

Yeah there is that folder and also there are measurements for the custom 1080p23hz mode with the "LatestMode" value (REG_BINARY and a bunch of numbers in "data").
1) Are you sure there's only one madVR installation on your PC? E.g. if you use J.River MC, that one comes with its own madVR installation etc.

2) Are you sure that your media player runs under the same user account as madHcCtrl.exe? Of course HKEY_CURRENT_USER only works if it's the same user for both processes.

3) Are you sure that 1080p23 is the actual active mode while you play a video? And you let the video play for at least 11 minutes without touching it in any way?

4) Does the OSD (Ctrl+J) report a frame repeat/drop estimation during those 11 minutes?

Yes, you are right. I thought it croped from top same as from bottom, but I did some primitive test, and it croped video propertly in MHC-BE.
I'm not sure what you mean. I'm right with what exactly?

tony359
4th September 2017, 21:13
Quote:
Originally Posted by tony359
Yes, I can see the cursor and I hear DisplayCAL working in the background (taking black readings!). The moment I switch back to the window I can immediately see the pattern I was supposed to see fullscreen.
Thanks for confirming ALT-ENTER is ok. It's just that when I select FULL-SCREEN it does not seem to work and it starts taking readings not full-screen.

I'll try again tonight, is there anything I can do for you or logs to send you to help identifying the problem?

Quote:
Originally Posted by madshi

Do you have the same problems when playing a video with madVR? Also a black screen in fullscreen?

no, fullscreen - exclusive or windowed - works fine when playing back from MPC-HC and MadVR

Bernix
4th September 2017, 21:14
I meant you are correct about wrong pin info in MPH-BE Furthermore, at least MPC-BE's pin information is IMHO incorrect.

Bernix

madshi
4th September 2017, 21:19
no, fullscreen - exclusive or windowed - works fine when playing back from MPC-HC and MadVR

What happens if you play with the "image area" slider and the "disable OSD" button. If you modify the image area so you don't get a full black screen, and then enable the OSD, so you see the progress bar at the bottom, does all this go away if you go fullscreen with ALT-ENTER (before starting the measurements!)?

One thing you could is change the madVR settings. E.g. enable/disable fullscreen exclusive mode. Enable/disable "use D3D11 for presentation". Enable/disable overlay mode etc.

I meant you are correct about wrong pin info in MPH-BE. Furthermore, at least MPC-BE's pin information is IMHO incorrect.
Ok, so let's wait for the next madVR build, then you test with that and complain to the MPC-BE devs. Then let's go from there, ok?

Bernix
4th September 2017, 21:23
O.K.
Thank you
Bernix

tony359
4th September 2017, 22:02
Quote:
Originally Posted by tony359
no, fullscreen - exclusive or windowed - works fine when playing back from MPC-HC and MadVR
What happens if you play with the "image area" slider and the "disable OSD" button. If you modify the image area so you don't get a full black screen, and then enable the OSD, so you see the progress bar at the bottom, does all this go away if you go fullscreen with ALT-ENTER (before starting the measurements!)?

One thing you could is change the madVR settings. E.g. enable/disable fullscreen exclusive mode. Enable/disable "use D3D11 for presentation". Enable/disable overlay mode etc.

No OSD at all, just black screen - and the cursor. No different colour frame when "image area" is not maxed out. But I can see that as expected when windowed.

I believe I have found a "workaround": leave the TPG to NON full screen and switch to full screen by double-clicking on the screen, not by pressing ALT-ENTER.

That seems to work ok. Does it make any sense at all?

Dorohedoro
4th September 2017, 22:06
1) Are you sure there's only one madVR installation on your PC? E.g. if you use J.River MC, that one comes with its own madVR installation etc.

2) Are you sure that your media player runs under the same user account as madHcCtrl.exe? Of course HKEY_CURRENT_USER only works if it's the same user for both processes.

3) Are you sure that 1080p23 is the actual active mode while you play a video? And you let the video play for at least 11 minutes without touching it in any way?

4) Does the OSD (Ctrl+J) report a frame repeat/drop estimation during those 11 minutes?


1.- yes, I only have pot player and the lav filters and none of those comes with madvr... also, I dont know if this is messing with the config, but I'm using ffdshow raw with denoise options turned on.

2.- not really, I'm not sure, I have two users, I will check playing a video on the other user and see if I get a result

3.- yeah 100% sure

4.- yeah, 1 frame drop every hour (is not that bad, but I want to improve it)

Thank you very much!

Dorohedoro
4th September 2017, 22:29
Ok, I didnt get any result on the other user, maybe it has something to do with the videocard, or the driver?

mparade
4th September 2017, 22:42
@madshi

That's still quite a lot, though. Are you using "native DXVA" or "DXVA copyback"? Do you have the "zoom control" options activated in madVR?

In LAV Video I have tried both with main12 source. Both resulted in nearly the same CPU utilization. But I do not really think decoding is being accomplished via DXVA (as also stated by Nevcairiel, however I selected DXVA in LAV Video settings dialog). Kodi reports "HVC1 (DXVA Native) (HW) only if I change to a main10 source. Every time changing back to a main12 source the reported decoder becomes again HVC1 (FFMpeg) (HW). During play of a main10 source using DXVA Native the CPU average utilization is only 40% compared to that when playing a main12 source.

All zoom control options is deactivated excluding "move subtitles". It is on by default.

mitchmalibu
4th September 2017, 22:57
What it boils down to is that when FSE activates, it calls the custom mode. Then, while the file is playing, I am able to use that custom mode in non-fullscreen windowed or fullscreen windowed (if I disable FSE in the settings).
I am 100% sure that the mode summoned by FSE is the custom one (vastly improved frame drop frequency).

The custom modes in the nvidia control panel were created by madvr. Once I check the checkbox in front of them, they are available to select through the nvidia selection box, in the custom section. So if I changed the display using the nvidia control panel to that custom mode and launch a 23p file without triggering a display mode change, it is correctly using the new custom mode. Otherwise, switching to 23p either by using the standard windows display settings or using the madvr display mode switcher uses the standard 23p mode.

So my two posts aren't contradictory, but complementary : the first one gives an example of how I was able to trigger the custom mode using the FSE trick (without fiddling in the nvidia cpl), and the second one shows that I can directly summon the same custom mode through the nvidia cpl, but that the same custom mode won't be called by the windows display settings or madvr display mode switcher. So I am able to use the custom mode, but not without using roundabout ways each time.

Also relevant, in response to cyber201 :

It seems that 1 frame repeat every 4.40 minutes is also what you had before starting the whole process, is that correct? In that case it seems that the custom timings are not activated by the GPU at all, for some reason. I'm not sure what the exact reason is, unfortunately. I'd suggest that you try either with fullscreen exclusive mode turned on or off, and with the "use D3D11 for presentation" option turned on or off, to see if any of that makes a difference. It's possible that the GPU driver doesn't use our custom modes in some situations.

I finally managed to do a fresh windows install with the bare minimum (drivers, mpc-be x64, lav and madvr): the same behavior persists. The custom mode is only summoned when going into FSE mode. It is similar to the behavior described by cyber201 (same GPU). Looks like this is really tied with the way Nvidia handles the custom resolutions ...

SamuriHL
4th September 2017, 23:02
This information is not complete. The queue information consists of 2 numbers each.


Yea, that's what I get for typing it and being lazy LOL. The queues were all full so those numbers should be duplicated 16/16, etc. It's weird. I've never seen it do that before where the queues are all full but video is frozen. When I change LAV to copy back and/or change D3D11 to use copy back instead of native it works fine. Very strange.

cyber201
4th September 2017, 23:10
It seems that 1 frame repeat every 4.40 minutes is also what you had before starting the whole process, is that correct? In that case it seems that the custom timings are not activated by the GPU at all, for some reason. I'm not sure what the exact reason is, unfortunately. I'd suggest that you try either with fullscreen exclusive mode turned on or off, and with the "use D3D11 for presentation" option turned on or off, to see if any of that makes a difference. It's possible that the GPU driver doesn't use our custom modes in some situations.



Hi madshi, Yes, it's correct.
But if I disable D3D11 presentation, I will have a poor image quality?
Maybe a nvidia driver bug?

Thanks

Asmodian
5th September 2017, 02:00
But if I disable D3D11 presentation, I will have a poor image quality?


Unless you are using 10-bit or the new DX11 version of DXVA2 Native decoding turning off D3D11 will not harm image quality in anyway. 8-bit DX9 old path has the same image quality as 8-bit DX11 new path.

Maybe a nvidia driver bug?

Probably, there have been a lot of driver oddities around applying and enabling custom resolutions. :(

SamuriHL
5th September 2017, 03:09
Probably, there have been a lot of driver oddities around applying and enabling custom resolutions. :(

No kidding. It seems like every driver release either fixes something (yey) or breaks 10 things (boo) LOL

Ava Pug
5th September 2017, 05:50
Also relevant, in response to cyber201 :



I finally managed to do a fresh windows install with the bare minimum (drivers, mpc-be x64, lav and madvr): the same behavior persists. The custom mode is only summoned when going into FSE mode. It is similar to the behavior described by cyber201 (same GPU). Looks like this is really tied with the way Nvidia handles the custom resolutions ...

Have you tried enabling "Use NVIDIA color settings" in Display -> Change resolution? That fixed my custom resolution issue.

madshi
5th September 2017, 09:05
With that, my screen should change to 29.97Hz (which is supported, I just tested with another video), but it remains at 23.97Hz.
In case is any useful, I have: Win8.1, AMD A6-4455M, smooth motion off, D3D11 exclusive.
One possible reason for the problems is that madVR isn't sure whether deinterlacing will be needed or not. So madVR ideally wants to activate 59.940Hz, but that mode doesn't seem to be available. However, I guess if the only choices available are 23.976 and 29.970, then I suppose madVR should switch to 29.970. I've tried to reproduce on my PC, but my PC properly switches to 29.970, if only 23 and 29 are available.

Which is the exact list of display modes to switch to in your display's "display modes" tab in the madVR settings? And please create a debug log, zip it, upload it somewhere else (don't attach to this forum) and then link to it here.

No OSD at all, just black screen - and the cursor. No different colour frame when "image area" is not maxed out. But I can see that as expected when windowed.

I believe I have found a "workaround": leave the TPG to NON full screen and switch to full screen by double-clicking on the screen, not by pressing ALT-ENTER.

That seems to work ok. Does it make any sense at all?
No, it doesn't make any sense to me because the code to handle double clicking and ALT-ENTER is pretty much identical! I've made a tiny change to the ALT-ENTER handling for the next build now, but I don't have much hope that will change anything.

1.- yes, I only have pot player and the lav filters and none of those comes with madvr... also, I dont know if this is messing with the config, but I'm using ffdshow raw with denoise options turned on.

2.- not really, I'm not sure, I have two users, I will check playing a video on the other user and see if I get a result

3.- yeah 100% sure

4.- yeah, 1 frame drop every hour (is not that bad, but I want to improve it)
Can you double check in the task manager ("details" tab) with user name the madHcCtrl.exe process is running as, and which user name your media player is running as?

In LAV Video I have tried both with main12 source. Both resulted in nearly the same CPU utilization. But I do not really think decoding is being accomplished via DXVA (as also stated by Nevcairiel, however I selected DXVA in LAV Video settings dialog). Kodi reports "HVC1 (DXVA Native) (HW) only if I change to a main10 source. Every time changing back to a main12 source the reported decoder becomes again HVC1 (FFMpeg) (HW). During play of a main10 source using DXVA Native the CPU average utilization is only 40% compared to that when playing a main12 source.

All zoom control options is deactivated excluding "move subtitles". It is on by default.
Even 40% is much too high to make sense. I'd expect something like 5% or so. Something is weird there. Do you have MPC-HC/BE installed? If so, can you please right click on the video then choose "Filters -> LAV Video Decoder", then check what the "Active Decoder" says? Also what does the madVR OSD (Ctrl+J) say about the incoming video format? E.g. does it say "NV12, 8 bit, 4:2:0" or something similar? I need the exact full text of this one OSD line.

Yea, that's what I get for typing it and being lazy LOL. The queues were all full so those numbers should be duplicated 16/16, etc. It's weird. I've never seen it do that before where the queues are all full but video is frozen. When I change LAV to copy back and/or change D3D11 to use copy back instead of native it works fine. Very strange.
Does the OSD update at all? E.g. the refresh rate measurement should fluctuate to some extend. Or is the OSD completely frozen, too?

But if I disable D3D11 presentation, I will have a poor image quality?
Please see Asmodian's and Ava Pug's replies.

tony359
5th September 2017, 09:13
Quote:
Originally Posted by tony359 View Post
No OSD at all, just black screen - and the cursor. No different colour frame when "image area" is not maxed out. But I can see that as expected when windowed.

I believe I have found a "workaround": leave the TPG to NON full screen and switch to full screen by double-clicking on the screen, not by pressing ALT-ENTER.

That seems to work ok. Does it make any sense at all?
No, it doesn't make any sense to me because the code to handle double clicking and ALT-ENTER is pretty much identical! I've made a tiny change to the ALT-ENTER handling for the next build now, but I don't have much hope that will change anything.


ahah! Thank you. I'll test and report back. To be honest I am not totally sure I tested ALT-ENTER when FULLSCREEN is disabled. Maybe the key is the fullscreen button and not the way you go into fullscreen. I'll test and report back.

mitchmalibu
5th September 2017, 10:25
Have you tried enabling "Use NVIDIA color settings" in Display -> Change resolution? That fixed my custom resolution issue.

Yep, I'm using 422 10bit atm, still no luck :(

cyber201
5th September 2017, 13:00
Have you tried enabling "Use NVIDIA color settings" in Display -> Change resolution? That fixed my custom resolution issue.


Thanks, but all my videos are playing in FSE mode end the custom resolution don't work

leandronb
5th September 2017, 13:39
Hi guys. I was wondering which option is better, using TV at 60hz and smooth motion on, or make it go to 23/24hz with smooth motion off?
I kinda like smooth motion on because there is no flashing on screen because there is no refresh rate change.
Also I really don't know if my tv can actually handle 24p content, is a Samsung Eh6030, maybe 120hz because of 3D and accept various refresh rates.
My brother's TV can change to 24hz too but is not a 120hz tv so I think is a waste making it change to 24hz everytime.
So what do you guys think about this?

SamuriHL
5th September 2017, 15:27
Does the OSD update at all? E.g. the refresh rate measurement should fluctuate to some extend. Or is the OSD completely frozen, too?


Well I give up. I went and changed it back to d3d11 native to check on the OSD and for whatever reason playback is working. I've not, to my knowledge, changed anything since I last tried so I have NO idea what happened. Sorry to have troubled you with this one.

SamuriHL
5th September 2017, 15:37
HEYYYY there we go! I got it to freeze again and maybe this'll shed a little light on the subject. Can someone with a 1060 try this and see what they get for results? With D3D11 Native mode enabled, watch a 3D movie for a couple minutes. Stop playback and then try to watch a 2D movie. It's now frozen for me. The average and max stats do seem to be changing in the OSD, but, the queues are full and no video is playing. That's...weird right?

Ok, I think I got this one figured out finally. If I exit out of JRiver MC23, go to display properties and toggle 3d off, then back on, I'm able to play the 2D movie again. So I have a feeling something's not getting reset on playback of a 3D movie.

mparade
5th September 2017, 18:50
@madshi

can you please right click on the video then choose "Filters -> LAV Video Decoder", then check what the "Active Decoder" says? Also what does the madVR OSD (Ctrl+J) say about the incoming video format? E.g. does it say "NV12, 8 bit, 4:2:0" or something similar? I need the exact full text of this one OSD line.

Active Decoder says: avcodec
madVR OSD says: P016, 16bit 4:2:0.

mogli
5th September 2017, 19:24
I was playing around with the hdr to sdr conversion. Why is the default display's peak nits set to 400?
I read sdr content is usually intentionally limited to 100 nits for compatibililty with older devices. I understand that newer devices allow for more nits but that's not exactly sdr anymore. So when conversion to sdr is needed wouldn't 100 nits (less than madVR even allows to be set) be the most sensible default?

@mparade
Your cpu utilization seems normal considering software decoding such a file.

mparade
5th September 2017, 20:13
It seems, even these days there is no GPU assisted decoding method for main12 HEVC sources. After reading the specs of my card I was pretty sure it could be done at least via CUVID or DXVA. I was wrong, or just not having enough info.

Grimsdyke
5th September 2017, 20:26
Hi Madshi, would it be possible to add something like a 'lock-buttom' for a custom mode once a perfect setting was found ? I am asking because last weekend I spent hours trying to find a setting for a refresh rate but with each new measurement it got worse, e.g. dropped frames down to minutes until I remembered that I had already found a p.s. for that frequency.
But unfortunately that remark was changed to 'optimization available' after playing another file not long enough or with interruptions or whatever ...
So after, say, a driver update it can get unlocked - tested - and locked again.