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

e-t172
2nd April 2014, 23:25
It's not that easy. The same settings may work on monitor 1 but not on monitor 2, if the two monitors are driven by different GPUs. So I can't just make things red in the settings dialog. However, madVR could show some sort of OSD complaint, I guess, if an enabled setting doesn't work.

Why not show it on CTRL+J stats?

madshi
2nd April 2014, 23:34
In latest build (0.87.9) nod32 detect madHcCtrl.exe as a threat.
That looks like a false positive to me. At least Malwarebytes claims that my PC is clean. Please complain to nod32, thanks.

It's an Asus P6T Deluxe V2, so PCI-E 2.0.

Yes, I was using a 720x576i/25 file.
Using DXVA deinterlacing? Which would make it 50p. Try film mode, at least, to half the required GPU power.

Why not show it on CTRL+J stats?
Because different users want different things in there. If I added "everything" there it would have 20 pages you'd have to scroll through.

Werewolfy
2nd April 2014, 23:34
I didn't read it as rude at all, no harm done. I just felt sympathy for your lost weekends...


FWIW, the improvements were the tries to fix the problem, which didn't really work in the end (already tested). But I left the improvements in there, in the hope that it might help some people.
Would it be useful to create an entry in the bug tracker? I know it will be very difficult to fix this problem without being able to reproduce it but it can be a sort of reminder if one day you have another idea to fix this and maybe some other users that have the same problem on Windows 8 will manifest too.

madshi
2nd April 2014, 23:36
Would it be useful to create an entry in the bug tracker? I know it will be very difficult to fix this problem without being able to reproduce it but it can be a sort of reminder if one day you have another idea to fix this and maybe some other users that have the same problem on Windows 8 will manifest too.
It's already there:

http://bugs.madshi.net/view.php?id=90

DragonQ
2nd April 2014, 23:39
It's an Asus P6T Deluxe V2, so PCI-E 2.0.


Yes, I was using a 720x576i/25 file.

I'll try 0.87.9 in a minute.

Still happens with 0.87.9.

Using DXVA deinterlacing? Which would make it 50p. Try film mode, at least, to half the required GPU power.

If I try to play a theoretically easier 640x480p/25 video full-screen (1600x1200) I get rendering times of 82 ms with NNEDI3 16 neurons and rendering times of 84 ms with NNEDI3 32 neurons. :(

If I disable banding reduction rendering times drop to 72 ms, hmm.

Werewolfy
2nd April 2014, 23:41
It's already there:

http://bugs.madshi.net/view.php?id=90

Ok sorry, I was the only one to have this problem on the forum so I didnt' check the bug tracker.

madshi
2nd April 2014, 23:47
If I try to play a theoretically easier 640x480p/25 video full-screen (1600x1200) I get rendering times of 82 ms with NNEDI3 16 neurons and rendering times of 84 ms with NNEDI3 32 neurons. :(
Ouch. And that's really the shiny new AMD? Are you sure it's not your old NVidia or maybe the mainboard's Intel GPU which is doing all the rendering? If it's really the AMD, then it seems that interop cost on your PC is sky high. You might be better off with a Maxwell then.

DragonQ
2nd April 2014, 23:52
Ouch. And that's really the shiny new AMD? Are you sure it's not your old NVidia or maybe the mainboard's Intel GPU which is doing all the rendering? If it's really the AMD, then it seems that interop cost on your PC is sky high. You might be better off with a Maxwell then.
This motherboard has no on-board GPU. The nVidia is no longer plugged in lol.

This post (http://forum.doom9.org/showthread.php?p=1666561#post1666561) suggests this GPU is easily capable of NNEDI3 (an R9 270 is essentially a rebranded HD 7870). :(

How do I know if OpenCL is working correctly? It's ticked in GPU-Z, which AFAIK means it's fine.

madshi
2nd April 2014, 23:54
Well, you can try this (http://madshi.net/OpenClSpeedTest.zip). But I'm pretty sure the problem is going to be the interop cost. If so, you may want to replace your AMD with a Maxwell, as mentioned earlier.

DragonQ
3rd April 2014, 00:05
http://www.aotplaza.com/Files/AMD%20R9%20270%20OpenCL%20Tests.png

I don't think I'll be changing my GPU again, especially to nVidia out of principle.

ryrynz
3rd April 2014, 00:09
Hey nevcairiel, any chance of that compute performance test of your 750?

madshi, is there still reason to keep the old FSE path?

Audionut
3rd April 2014, 00:29
Have you looked at the online Help in madVR? It also has a sample script.

Online help is page 3 of this thread. Where I suggested the screenshot should go :)

huhn
3rd April 2014, 01:23
http://www.aotplaza.com/Files/AMD%20R9%20270%20OpenCL%20Tests.png

I don't think I'll be changing my GPU again, especially to nVidia out of principle.

i have a r9 270 my self it normally gets over 440 fps with opencl copy interop and pci-e 3.0.

in a post above you said your mainboard got pci-e 2.0 please check if your board is using pci-e 2.0.
over 300 fps is normal for pci-e 2.0.

please check your pci-e speed with GPU-Z there is a blue question marker on the "graphics card" page on the right middle.

all other number of your r9 270 are way better then my numbers.

leeperry
3rd April 2014, 01:48
is there still reason to keep the old FSE path?
It's needed on XP, at least with nvidia as the new path constantly drops frames. mVR uses DX9 so I guess it makes sense to keep XP compatiblity intact.

DragonQ
3rd April 2014, 01:50
please check your pci-e speed with GPU-Z there is a blue question marker on the "graphics card" page on the right middle.
x16 1.1 when idle, x16 2.0 when running the graphics test.

x16 1.1 when using MadVR with Jinc3, x16 2.0 when using NNEDI3.

x16 2.0 during most of the OpenCLSpeedTest.

When using Jinc3, GPU usage is 0% most of the time, with random spikes. Same with GPU Memory Clock, it's 150 MHz most of the time and jumps to 1400 MHz every few seconds.

The other thing is that the Backbuffer Queue keeps dropping to 0 and I get dropped frames every few seconds, but this only happens when GPU-Z is open so it doesn't matter.

ryrynz
3rd April 2014, 02:10
It's needed on XP, at least with nvidia as the new path constantly drops frames. mVR uses DX9 so I guess it makes sense to keep XP compatiblity intact.

Can anyone else confirm constant frame drops when the old path is used with smooth motion enabled?

Mangix
3rd April 2014, 02:36
It's needed on XP, at least with nvidia as the new path constantly drops frames. mVR uses DX9 so I guess it makes sense to keep XP compatiblity intact.

Windows XP support ends on the 8th. I don't think it makes sense anymore.

Anime Viewer
3rd April 2014, 02:41
madVR v0.87.9 released

http://madshi.net/madVR.zip


There's one new (hidden) feature which may help Optimus users: You can now force madVR to use a specific GPU vendor for OpenCL rendering. You can do this by manually adding the following registry value:

HKEY_CURRENT_USER\Software\madshi\madVR\OpenCL\forceVendor REG_SZ "nVidia"

Alternatively you can also use "AMD" or "Intel", of course, which will force madVR to use the specified vendor for OpenCL rendering. Of course telling madVR to use a specific vendor does not guarantee that doing so will actually work, but madVR will try. If it fails, NNEDI3 will silently be disabled.

I downloaded, unzipped 87.9 to my madVR directory, and ran the install batch file. Went into MPC-HC, opened a video, went to filters -> madVR, and set chroma upscaling to NEEDI3, set 64 neurons, and the screen turned green and the video ran very poorly. I opened up regedit, went to HKEY_CURRENT_USER\Software\madshi\madVR\OpenCL and created a new key named forceVendor, and in that created a string key which I named nVidia (you didn't mention it, but I'm guessing it should also have a value of 1), but it made no difference. I tried changing the name to Intel, and nothing ran any different.
Should I also be copying madVR.ax from the previous b version, or the previously ineffective optimus, or optimus2 madVR.ax again to go with 87.9, or should I have been using the madVR.ax included with 87.9?

Edit: Well I tried copying all of the previously mentioned madVR.ax versions (b, optimus, and optimus2) over the 87.9 version, and nothing changed. b and optimus played with a green screen and high render times regardless of if I had the Nvidia or Intel as the registry key, and optimus2 ran as if NNEDI3 was silently disabled again.

Something else of note I noticed when I went in to add the forceVendor key and sting inside it I noticed there is a HKEY_CURRENT_USER\Software\madshi\madVR\OpenCL\Intel(R) HD Graphics 4000 key, but no sign of an Nvidia one.

Asmodian
3rd April 2014, 03:35
http://www.aotplaza.com/Files/AMD%20R9%20270%20OpenCL%20Tests.png

I don't think I'll be changing my GPU again, especially to nVidia out of principle.

Wow! look at that interop fps, not good. :(

Do you have something else on the PCI-E bus? It looks like it takes a really long time for a frame to make a round trip.

seiyafan
3rd April 2014, 03:51
Agreed, my 270x had OpenCL copy interop and kernel interop in the 400'ish fps, check your PCI-e

biggerpapi
3rd April 2014, 04:12
Something else of note I noticed when I went in to add the forceVendor key and sting inside it I noticed there is a HKEY_CURRENT_USER\Software\madshi\madVR\OpenCL\Intel(R) HD Graphics 4000 key, but no sign of an Nvidia one.

I noticed the same thing. It seems madVR is trying to use the HD4000 for openCL. I even tried deleting the HD4000 value and added a new value for my nVidia gpu but as soon as I started a video it added the HD4000 right back.

cyberbeing
3rd April 2014, 05:19
I opened up regedit, went to HKEY_CURRENT_USER\Software\madshi\madVR\OpenCL and created a new key named forceVendor, and in that created a string key which I named nVidia (you didn't mention it, but I'm guessing it should also have a value of 1), but it made no difference. I tried changing the name to Intel, and nothing ran any different.

I think you've misunderstood madshi's notation.
HKEY_CURRENT_USER\Software\madshi\madVR\OpenCL\forceVendor REG_SZ "nVidia"

This means to add a 'forceVendor' String (REG_SZ) with a value of 'nVidia' at HKEY_CURRENT_USER\Software\madshi\madVR\OpenCL , not a key.

Anime Viewer
3rd April 2014, 05:26
I think you've misunderstood madshi's notation.
HKEY_CURRENT_USER\Software\madshi\madVR\OpenCL\forceVendor REG_SZ "nVidia"

This means to add a 'forceVendor' String (REG_SZ) with a value of 'nVidia' at HKEY_CURRENT_USER\Software\madshi\madVR\OpenCL , not a key.

Thanks for clearing that up. That worked, and now it has created a HKEY_CURRENT_USER\Software\madshi\madVR\OpenCL\GeForce GTX 680M key in the registry. 32 neurons seems to be the best setting for an Nvidia GTX 680M gpu chroma upscaling setting.

Its interesting...if I force the Nvidia NEEDI3 runs correctly, but if I force the Intel the screen goes green again...

QBhd
3rd April 2014, 05:42
Agreed, my 270x had OpenCL copy interop and kernel interop in the 400'ish fps, check your PCI-e

What OS do you use?

My R9 270x is only getting 185'ish fps

QB

6233638
3rd April 2014, 05:42
Thanks for the fixes in this build - especially #097.
Now I can leave Smooth Motion enabled all the time. :D

truexfan81
3rd April 2014, 05:53
Just copy the settings.bin file. In order to go back to a stored settings.bin file, first run "restore default settings.bat", then copy the stored settings.bin file into the madVR folder. For any of this to work, madVR requires write access to its own folder. If you don't want to give madVR write access to its own folder, open regedit, browse to "HKCU\Software\madshi\madVR" and export to a reg file. Then when you later want to go back, again first run "restore default settings.bat", then double click the saved reg file.quite slow and results in very slow OpenCL <-> Direct3D9 interop performance.


good to know, thanks :D

huhn
3rd April 2014, 06:29
What OS do you use?

My R9 270x is only getting 185'ish fps

QB

this has a lot to do with the cpu and pci-e versions.

i get over 440 fps with haswell and pci-e 3.0 ivy bridge is slower with pci-e 3.0.

just have a look at this post:
http://www.avsforum.com/t/1477339/so-youve-built-your-htpc-now-what-is-next-how-to-get-the-ultimate-picture-and-sound-quality-from-your-htpc-madvr-svp-xbmc-mediabrowser-jriver/450#post_24514253

this is not 100 % reproduceable number can varies between two identical cards and that a lot.

nevcairiel
3rd April 2014, 09:13
D'ya still have a Maxwell? Would be interesting to hear how that fares compared to the 660, considering that Maxwell seems to have noticeably improved compute performance over Kepler.

Hey nevcairiel, any chance of that compute performance test of your 750?

Using the same settings as my GTX 660, it seems to produce similar performance - which is kinda impressive, considering its quite a bit slower in raw performance (~30%).

Chroma: Bicubic 75+AR
Image Up: Jinc3+AR
Image Down: CR+AR+LL

720->1080 with NNEDI 32N: 37ms with OD, 40ms with ED1. Stable and no dropped frames during a 24p movie.
If I step down image downscaling to CR without AR/LL, rendering goes down to ~32ms, or image upscaling down to lanczos3+AR to 35ms.

The hit from error diffusion is much lower than on the 660, but NNEDI does take a bit more performance out of it.
However, its quite usable with NNEDI for 24p content. A 750Ti, with around 20% more performance, should fare even better and beat the GTX 660 consistently. A "860" model based on Maxwell sounds like a good madVR card, but who knows when those will come out. To reach enough performance to run 60p with NNEDI, you'll need to wait for the new high end cards, though!

90% of all content I watch is 24p, 7% is 25p, and only the last 3% are anything higher, so for me it would probably even be enough.

John Carmack
3rd April 2014, 10:12
Try increasing the GPU queue size and the number of pre-presented frames for exclusive mode. Smooth motion FRC benefits from bigger queues.

I actually tried and noticed a lot of things:
-Disabling exclusive mode solves the stutter.
-When in exclusive mode, (even with a GPU queue of 24), the decoder queue is always something like 21-25/24 while the others are 20 or 21-24/24
-The mouse is stuttering a lot in exclusive mode (maybe a clue?)

DragonQ
3rd April 2014, 10:44
Wow! look at that interop fps, not good. :(

Do you have something else on the PCI-E bus? It looks like it takes a really long time for a frame to make a round trip.
Nope, no other PCI-E devices.

Agreed, my 270x had OpenCL copy interop and kernel interop in the 400'ish fps, check your PCI-e
The only option in the BIOS that I can remember which relates to PCI-E sets the speeds of the 2nd and 3rd PCI-E x16 slots, which I'm not using. :/

The only other setting I can think of is the Windows Power Settings for PCI-E power savings but that makes no difference.

Something else of note I noticed when I went in to add the forceVendor key and sting inside it I noticed there is a HKEY_CURRENT_USER\Software\madshi\madVR\OpenCL\Intel(R) HD Graphics 4000 key, but no sign of an Nvidia one.
Hmmmm, mine also only has a key for my old GTS 250 and "Pitcairn", whatever that is. There is no key for my R9 270...could this be the problem?

EDIT: Just realised Pitcairn is an AMD code name so that's probably fine.

madshi
3rd April 2014, 11:18
{benchmark image}

I don't think I'll be changing my GPU again, especially to nVidia out of principle.
Well, for whatever reason interop cost seems to be extremely high on your PC. How well does DXVA decoding with copyback work for you? I guess it'll probably be very slow, too. Many other users have better results. Could be a problem with your mainboard or your OS installation or something. Can't say for sure. At least it looks like you can forget about NNEDI3 with AMD on your mainboard or OS installation, unfortunately, unless AMD fixes the interop performance problem with a future driver.

madshi, is there still reason to keep the old FSE path?
Some users are still using it. I hope to be able to get rid of it some day, but it's not costing me much support work, so I'll leave it in for now. The big cleanup might come for v1.0. No need to rush cleanup now.

Thanks for clearing that up. That worked, and now it has created a HKEY_CURRENT_USER\Software\madshi\madVR\OpenCL\GeForce GTX 680M key in the registry. 32 neurons seems to be the best setting for an Nvidia GTX 680M gpu chroma upscaling setting.

Its interesting...if I force the Nvidia NEEDI3 runs correctly, but if I force the Intel the screen goes green again...
Ok, that's good to know. So NNEDI3 generally works on Optimus laptops. Now the big question is how I can automatically detect the situation, so that you don't have to create that registry tweak. I'll probably have to create a small test tool for you to run...

Thanks for the fixes in this build - especially #097.
Now I can leave Smooth Motion enabled all the time. :D
:)

Using the same settings as my GTX 660, it seems to produce similar performance - which is kinda impressive, considering its quite a bit slower in raw performance (~30%).

Chroma: Bicubic 75+AR
Image Up: Jinc3+AR
Image Down: CR+AR+LL

720->1080 with NNEDI 32N: 37ms with OD, 40ms with ED1. Stable and no dropped frames during a 24p movie.
If I step down image downscaling to CR without AR/LL, rendering goes down to ~32ms, or image upscaling down to lanczos3+AR to 35ms.

The hit from error diffusion is much lower than on the 660, but NNEDI does take a bit more performance out of it.
That's quite interesting, thanks for the tests! FWIW, looking at raw numbers it seems that the 750 has about 55% of the memory bandwidth of the 660 and also about 55% of the GLOPS shader power. So it's quite promising if it runs at about the same speed in madVR.

You're saying the 750 is faster with error diffusion but a bit slower with NNEDI compared to the 660? I think the 750Ti should be a great HTPC card, at least it's by far the greatest card which doesn't need an extra power plug. Can't wait for 860Ti or 960Ti in 20nm without an extra power plug... :D

I actually tried and noticed a lot of things:
-Disabling exclusive mode solves the stutter.
-When in exclusive mode, (even with a GPU queue of 24), the decoder queue is always something like 21-25/24 while the others are 20 or 21-24/24
-The mouse is stuttering a lot in exclusive mode (maybe a clue?)
The queues look just fine to me. Some questions:

(1) How's the presentation queue?
(2) Do you get frame drops? Or presentation glitches? Or both?
(3) Have you changed any other settings besides from the queue sizes?
(4) Hope you're using the default flush settings?
(5) Have you tried disabling desktop composition (if you're on win7)?

TheShadowRunner
3rd April 2014, 11:18
Windows XP support ends on the 8th. I don't think it makes sense anymore.
Yeah well, 30% of the world thinks otherwise.
Please don't drop XP support.
And thanks madshi for the new build with Vsfilter/black frame bug fixed!

DragonQ
3rd April 2014, 11:50
Well, for whatever reason interop cost seems to be extremely high on your PC. How well does DXVA decoding with copyback work for you? I guess it'll probably be very slow, too. Many other users have better results. Could be a problem with your mainboard or your OS installation or something. Can't say for sure. At least it looks like you can forget about NNEDI3 with AMD on your mainboard or OS installation, unfortunately, unless AMD fixes the interop performance problem with a future driver.
OS is Windows 8.1 x64, couple of months old. Naturally all motherboard drivers are installed. Latest BIOS too.

Can't think of any settings to change so I guess I'm stuck. My CPU is overclocked but Nehalem uses Base Clock rather than CPU Multiplier for overclocking, so the PCI-E bus is overclocked as well. My RAM has to be underclocked due to this but I can't imagine that would make such a huge difference; it's still over 1333 MHz.

EDIT: Just realised the PCI-E bus isn't overclocked since it's separate to the Base Clock. Been a while since I've checked BIOS settings on this machine! In any case, QPI should surely be fast enough...is anyone else here using an AMD GPU on a QPI-based motherboard? I think QPI was only used on first-generation Core i7s (Bloomfield), at least for desktop systems.

ryrynz
3rd April 2014, 12:49
Yeah well, 30% of the world thinks otherwise.


30% of the world won't upgrade unless made to :rolleyes: also I'm sure 29.9% of them aren't using madVR. Anyway the old path is sticking around at least until 1.0 so don't worry.

John Carmack
3rd April 2014, 12:51
The queues look just fine to me. Some questions:

(1) How's the presentation queue?
(2) Do you get frame drops? Or presentation glitches? Or both?
(3) Have you changed any other settings besides from the queue sizes?
(4) Hope you're using the default flush settings?
(5) Have you tried disabling desktop composition (if you're on win7)

First, thank you for helping me, even if I'm an isolated case.

1) Almost always empty (i.e. 0 or 1-8/8)
2) Both
3) I tried with the reseted settings and it's the same.
4) Yes, defaults
5) Tried it too

I must precise again that these errors only show up with High10.

Anime Viewer
3rd April 2014, 21:11
Ok, that's good to know. So NNEDI3 generally works on Optimus laptops. Now the big question is how I can automatically detect the situation, so that you don't have to create that registry tweak.

While experimenting around with different forms of combinations it looks like optimus (and manybe AMD's hybrid) may be able to run in a hybrid state. While using the force registry key to Nvidia, and selecting the Intel gpu for MPC-HC in Nvidia control panel it looks like it may have used a combination of the two gpu. The NNEDI3 continued to render using the Nvidia because the screen didn't turn green and render times didn't shoot up drastically (like when I force the Intel in the registry), but the render times did increase ~5-7ms over the times when run with Nvidia control panel and the registry set to Nvidia. Potentially if other things besides OpenCL could be forced (like DirectCompute) people with dual gpu systems could eliminate the weaker of the two gpu's when it comes to using certain features. People with hybrid amd/intel systems might be able to get around the OpenCL interop bug if they set their systems to force the Intel in the registry, but tell their system to use the AMD for MPC-HC (or whatever other video player - like POT - they may be using).

blu3wh0
3rd April 2014, 23:24
http://www.aotplaza.com/Files/AMD%20R9%20270%20OpenCL%20Tests.png

I don't think I'll be changing my GPU again, especially to nVidia out of principle.

I would like to note that I'm getting the same issue as DragonQ with AMD 7950 x2. At first I thought I was crazy since most other people with AMD video cards seem to be getting at least some respectable luma doubling, thinking it might be a problem with my setup. I have tried everything that I could think of to try to fix this to no avail.

My OpenCL copy and kernel fps drops from approximately 5250 fps to 130 fps with the interop. I'm on Windows 8.1 x64 and running the latest AMD beta driver. OpenCl error diffusion used to give me the same problem before madshi switched it to DirectCompute. The lowest frame time I can get with luma doubling at 16 neurons for a 720p 24 fps file is 48-50 ms with everything else either disabled or the lowest possible settings. My GPU runs at approximately 40% when I try to use my current settings with luma doubling.

Sorry if this is kind of abrupt, I have been following madVR and lurking here since madshi started developing it, to which I cannot express my gratitude enough in words (for now, thank you!), but I have been pulling my hair out due to this problem. Please let me know if I can provide any other kind of info.

flashmozzg
4th April 2014, 00:10
I would like to note that I'm getting the same issue as DragonQ with AMD 7950 x2. At first I thought I was crazy since most other people with AMD video cards seem to be getting at least some respectable luma doubling, thinking it might be a problem with my setup. I have tried everything that I could think of to try to fix this to no avail.

My OpenCL copy and kernel fps drops from approximately 5250 fps to 130 fps with the interop. I'm on Windows 8.1 x64 and running the latest AMD beta driver. OpenCl error diffusion used to give me the same problem before madshi switched it to DirectCompute. The lowest frame time I can get with luma doubling at 16 neurons for a 720p 24 fps file is 48-50 ms with everything else either disabled or the lowest possible settings. My GPU runs at approximately 40% when I try to use my current settings with luma doubling.

Sorry if this is kind of abrupt, I have been following madVR and lurking here since madshi started developing it, to which I cannot express my gratitude enough in words (for now, thank you!), but I have been pulling my hair out due to this problem. Please let me know if I can provide any other kind of info.
What cpu / pci-e do you have?

blu3wh0
4th April 2014, 01:12
I have an i5-2500k on an ASRock Z67 Extreme4 motherboard, with the video cards running on PCI Express 2.0 x8/x8. Disabling crossfire also provided no improvements.

huhn
4th April 2014, 01:49
pci-e 2.0 x8 is like using pci-e 1.1 and this is to slow for nnedi on amd. i hope amd fix this in the future.

leeperry
4th April 2014, 01:55
my GTX 660
I just experienced my first random white pixels veil due to overheating on my 7850 huh(the 20% fan speed cap apparently has its limits), all was well until I tried NNEDI 32x for chroma and things went bananas...2:30AM is way too late for me to compare it against J3AR anyway :D

All this said, your Asus 660 has become a benchmark when it comes to silence...can it do the following on 1280x720@24 please?

Chroma: J3AR(possible NNEDI 32x)
Image Up: J3AR
Image Down: CR+AR+LL
NNEDI 64x luma doubling
low debanding
A4 mono-static LL dithering
PS script on top of it

I realize that the 660 scores poorly in pure OCL benchmarks but the AMD interop lag divides the results in outrageous proportions and your 660's silence blew me away while I briefly owned it :)

trip_let
4th April 2014, 04:12
Just reporting in to say the OpenCL registry tweak does the trick for my HD 4000 / GT 650M.

Now I have the option for 480p23 -> 1080p to go Jinc3+AR or NNEDI3 16 neurons doubling+Lanczos3+AR. More intensive, and rendering times are too high. Hrms. Choices, choices. Both are good ones, fortunately.

James Freeman
4th April 2014, 04:40
madVR v0.87.9

Thank You !!!

SecurityBunny
4th April 2014, 10:46
I think I found a pretty serious bug.

Setup:
Windows 8.1
madVR 0.87.9
MPC-HC 1.7.3.185
Nvidia 335.23
ReClock 1.8.8.3
Xy-SubFilter 3.1.0.687

MadVR Settings:
Debanding low, NNEDI3 32 chroma, NNEDI3 32 luma doubling, Jinc 3 upscaling, CR AA LL downscaling
FSE, Seperate device for presentation, queues 24/20/16, SM FRC 'only if judder'
ED option 2, colored noise, change every frame
No trade for quality options checked.

Issue:
Playing back content not in native aspect ratio of monitor plays content outside monitor resolution. In other words, rendering / upscaling larger than monitor supports, cutting subtitles and picture detail. Not fully fitting the image inside the resolution. I have a 2560x1440 (16:9 aspect ratio) monitor.

Examples playing SD content. (4:3 and other, not natively 16:9) Had to disable FSE mode to take screenshots.
http://i.imgur.com/DrQBioR.pnghttp://i.imgur.com/xoQiG4d.pnghttp://i.imgur.com/C2cvhzj.png

Native 16:9 content upscales fine and doesn't have this issue. Here are two examples with 720p and 1080p images to 1440p.
http://i.imgur.com/rFRCJai.pnghttp://i.imgur.com/eKZokNO.png

I apologize, I do not know when this bug began to occur, as I only recently began watching older SD content. I do know I never use to have this issue about 8 months back.

Is there a way to force target rectangle to monitor's resolution so content can maintain aspect ratio inside display's aspect ratio to avoid stretching and displaying 'out of bounds', losing detail?

nevcairiel
4th April 2014, 11:10
Are you sure you didn't mess with your player settings to cause this?
For example, MPC-HC should be set to Video Frame -> "Touch from inside" and "Keep Aspect Ratio", as well as Pan&Scan should be off (use "Reset" to clear any settings).
Sounds to me like you have it set to "Touch from outside" instead.

octal9
4th April 2014, 11:36
madshi, is there still reason to keep the old FSE path?for people like me with crap gpu's and not much (or any) expendable income (i.e.: me). fse provides much more stable performance with far less frame drops/presentation glitches (at least on my rig) - currently running an ancient geforce 8400gs on windows 7 64bit and can play back even high bitrate blu ray encodes beautifully (albeit with mostly the lowest settings). thanks a trillion times over to madshi!

toniash
4th April 2014, 11:42
Is it possible with Madvr?
If possible how?

nevcairiel
4th April 2014, 11:55
Is it possible with Madvr?
If possible how?

Only DXVA2 is supported by madVR, which generally requires Windows Vista or newer.

DragonQ
4th April 2014, 12:16
I would like to note that I'm getting the same issue as DragonQ with AMD 7950 x2. At first I thought I was crazy since most other people with AMD video cards seem to be getting at least some respectable luma doubling, thinking it might be a problem with my setup. I have tried everything that I could think of to try to fix this to no avail.

My OpenCL copy and kernel fps drops from approximately 5250 fps to 130 fps with the interop. I'm on Windows 8.1 x64 and running the latest AMD beta driver. OpenCl error diffusion used to give me the same problem before madshi switched it to DirectCompute. The lowest frame time I can get with luma doubling at 16 neurons for a 720p 24 fps file is 48-50 ms with everything else either disabled or the lowest possible settings. My GPU runs at approximately 40% when I try to use my current settings with luma doubling.

Sorry if this is kind of abrupt, I have been following madVR and lurking here since madshi started developing it, to which I cannot express my gratitude enough in words (for now, thank you!), but I have been pulling my hair out due to this problem. Please let me know if I can provide any other kind of info.

pci-e 2.0 x8 is like using pci-e 1.1 and this is to slow for nnedi on amd. i hope amd fix this in the future.

At least in your case it looks like there's an explanation!

blu3wh0
4th April 2014, 12:48
I still can't get my head around how 4 GB/s is limiting the performance of the video card when using NNEDI. It must be a very poor/slow implementation on AMD's part for the OpenCL/Direct3D interop, an issue they apparently don't have when it is DirectCompute/Direct3D. At least I can still watch DVD/480p content using luma doubling/quadrupling, where it makes a bigger difference. Since my computer is relatively modern and high spec, I never thought I would run into an issue like this :( I just don't see AMD fixing this any time soon, if ever.