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 August 2010, 13:35
I also noticed the rendering time issue. In fullscreen windowed mode I usually have an average rendering time of 5ms with 1080p video on 1080p display resoultion.
When switching to exclusive mode it goes up to about 40ms, which is almost the movie frame intervall.
Try "flush & wait (loop)" after the backbuffer. That brings the rendering stats down quite nicely on my PC. I've no idea why it helps. And I've actually no idea if it's just cosmetical or if it really improves anything.

Also the rendering and upload queue don't fill up beyond 4-5/8 in exclusive mode whereas it was always full in fullscreen windowed mode.
Yes, I've also seen this. Don't know why the queues don't fully fill up, right now.

Luv
4th August 2010, 14:29
Madshi,I've found this workaround (?).Is it how you acesss to fullscreen mode on your test machine with ZP? It works superbly again this way.I haven't tried to go to FS immediately,though.I start windowed and then proceed like described in the link below to go FS:

http://forum.doom9.org/showthread.php?p=1423139#post1423139

sneaker_ger
4th August 2010, 14:32
My queues all fill up. (7-8/8 , 2-3/3) :confused:

Luv
4th August 2010, 14:35
About the rendering time mentioned by fps,it's multiplied by 3 from 6 to 18 ms when in FS mode on my system (With 1080p also).So everything is fine here.

namaiki
4th August 2010, 14:42
edit: my mistake... reclock was active, and the worst thing is I made the same mistake twice when testing and 'confirming'

fps
4th August 2010, 14:45
Try "flush & wait (loop)" after the backbuffer. That brings the rendering stats down quite nicely on my PC. I've no idea why it helps. And I've actually no idea if it's just cosmetical or if it really improves anything.

This doesn't help on my end, unfortunately. Rendering times actually increase very very slightly :confused:.

leeperry
4th August 2010, 15:15
I've not worked on subtitles yet. That's on my to do list for a future version.
Alright, told him. I thought "callback" meant something else.
The purpose of madHcNet.dll is a secret at this point
Ah, you're so full of mysteries! It seems that it's got to do w/ distributed calibration or so? possibly using a database running the default RBG xy coordinates of many displays?

The only reason I could think of for a VR to connect to the LAN would be to synchronize this kind of "wall of image" set ups: http://www.hellopro.fr/images/produit-2/9/6/6/mur-d-images-1227669.jpg

Otherwise, maybe you plan on running your own madtube.com website? it's a mad mad mad world, that's for sure :p

pie1394
4th August 2010, 15:23
One step at a time, mate, one step at a time... :)

As I said earlier:

"FWIW, the final solution will be to let madVR handle the refresh rates, instead of using the MPC HC autochanger."

In my system, the MPC-HC auto-refresh rate changer works fine with marVR 0.25 on various video clips. For example

Desktop : 23.976 fps (1920x1080 32bpp , MSI Lightning GTX260+ , Forceware 257.21, Win7 32-bit)

[madVR settings]
Luma : Lanczos4
Chroma : Spline64
No of backbuffers: 3
After render steps: flush --> don't flush
others as default settings

[MPV-HC Video playback started in Full-screen mode]
23.976 fps (in 23.976 Hz) OK
29.97 fps (in 59.94 Hz) OK
25 fps (in 50Hz) OK
30 fps (in 60 Hz) OK
50 fps (in 50 Hz) OK --> Need to use "other" setting in MPC-HC
--> MPC-HC lacks indivudual 50 / 60 fps video clip settings

To be honest, I never get this function work with VMR9 / EVR.
madVR 0.25 is the only one that I feel "STABLE" for it.

About the madVR's Full-screen Exclusive implemention, I only can describe it in one word ... GREAT WORK!!! :thanks:

Now there is no tearing issue any more on all video clips that happen to older madVR versions.

nlnl
4th August 2010, 15:46
pie1394
In my system, the MPC-HC auto-refresh rate changer works fine with marVR 0.25 on various video clips.
Did you try click right button once and again (see my post #3892 above)?

fastplayer
4th August 2010, 17:10
When UAC kicks in during playback, it stops and outputs the following message:
madVR reports:

resetting Direct3D device failed (88760868)
creating Direct3D device failed

buletti
4th August 2010, 18:04
My queues all fill up. (7-8/8 , 2-3/3) :confused:

same here.

[w7 x64, Aero off, ATI Radeon 5770, Catalyst 10.7, src: 720p24 tgt: 1920x1200/60 w/ Y: Spline64 UV: SoftCubic100]

mark0077
4th August 2010, 19:28
Hi madshi. Thanks for the new versions. Initially running into problems with my setup. Win 7 64bit , GTX 295, Core i7 920.

1) Initially I couldn't get any video output at all, only audio. It was because I have reclock calling a vbs script to auto refresh rate in certain scenarios. Disabling this allows me to see video output so madVR can't currently handle refresh rate changes with this new fullscreen mode. Can madVR be made to react to changes of resolution / refresh rate? In this scenario I wasn't able to get out of the black screen though using ESC or ALT-Enter.... can these keys be made to bring the user out of this fullscreen mode?

2) When I right click the video in fullscreen mode, the image flickers for a second or two and I see no menu, and then sometimes either nothing happens, playback continues but now I right clicked again and video and audio output stopped for about 10 seconds.... and then continued.

Octo-puss
4th August 2010, 19:46
http://thumbnails32.imagebam.com/9143/cf166891422363.jpg (http://www.imagebam.com/image/cf166891422363)
What does this do? Or rather, do I need this for anything when I already set madVR as output in the options?


Btw. The progress bar I talked about earlier sometimes stays on the screen even after switching back to windowed mode. Unfortunately I cannot give any details as it seems random so far.

mueslibrown
4th August 2010, 20:07
OK stupid question ... how do I get exclusive mode to start? I'm currently in windowed mode according to the OSD. Maybe I missed this in the thread ...

MB

mueslibrown
4th August 2010, 20:12
Found it ... nevermind ...

Spoke to fast I'm still in windowed mode according to the OSD. What am I doing wrong? D3D is not checked in the output tab in MPC-HC. In the external filters I have reclock and madVR (is this correct?). I'm on Win7 Home x64 with ATI 10.7

LoRd_MuldeR
4th August 2010, 21:06
OK stupid question ... how do I get exclusive mode to start? I'm currently in windowed mode according to the OSD. Maybe I missed this in the thread ...

MB

As soon as you go fullscreen in MPC-HC MadVR will switch to "fullscreen exclusive mode" automatically. Or at least it should ;)

However note that if you right-click in fullscreen mode in order to make MPC-HC's popup menu appear, then MadVR will switch back to "fullscreen windowed mode" temporarily.

(Of course "enable automatic fullscreen exclusive mode" must be checked in MadVR's option window)

pie1394
4th August 2010, 21:35
pie1394

Did you try click right button once and again (see my post #3892 above)?

I don't notice such detailed thing like you. The OSD text is too small when I watch it from 3 meters away. :p

Under the full-screen mode, I cannot see the sub-menu of madVR. Have to go back to regular Window mode to make it displayed. It is the same with EVR sync + D3D Exclusive mode.

The rendering time indeed becomes higher with my settings. Most of time it is equal to the refresh rate regardless the scaling mode of Lanczos3 / Lanczos4 / Spline36 / Spline64. But I don't observe any playback smothness issue yet.

Most of time I watch the FILM type contents. That is why I choose desktop refresh rate 23.976 Hz as the default. Another reason is that my Hitachi PDP's HDMI input sometimes takes longer time to be locked at 1080p24 stably when it is switched from 1080p50 or 1080p60.

About the madVR 0.25, it does still have some issues with some extra operations during the playback. I think most of them have been reported by other people. Fortunately they don't have big impact on normal playback.

My setup is always to start the video in Full-screen mode. Just have some minor issues:

1. Time Seeking bar does not appear until I click the mouse. It is ok with EVR. But it looks greater with madVR 0.25 since it is semi-transparent. If it is thicker (just like EVR mode's size), I think it will be better under HTPC + TV usage.

2. Press the [Windows] key, the MPC-HC sometimes gets hung or crashed.

cyberlolo
4th August 2010, 22:51
It doesn't. Or at least it shouldn't. It doesn't for me.

You were right and I was wrong. I can see OSD in exclusive mode too. Thanks again!

iSunrise
4th August 2010, 22:56
I really have to say that I´m extremely impressed with the stable state that madVR 0.25 already is in, even though you just introduced fullscreen exclusive mode with madVR 0.24.

The idea of having the renderer autmatically switch between fullscreen windowed and fullscreen exclusive is great, I´ve never even thought that something like this could work as flawless as this. Thanks not only for your commitment for giving us madVR for free, but also for your fresh new ideas which really deserve at least one post of respect.

I did some tests in Potplayer with various media files and a lot of different refresh rates and what I can already report is this:

1) Performance is even better than before (compared to 0.23), when exclusive mode comes into play. My rendering and present times went down a lot, which means that e.g. when playing a 1080p or 2304p (4K) resolution media file, I now get rendering times like 0.05ms and present times like 0.01ms, while with windowed mode I get 0.13ms and 0.05ms, respectively. This is absolutely awesome, because that means for future madVR releases, there easily seems to be enough headroom for e.g. image manipulation or some other stuff (which needs more processing or shader power) you have planned for the future.

2) After testing media files with 23.976fps at 23.982Hz, 24fps at 24.024Hz, 25fps at 25.026Hz, 29.970fps at 29.975Hz, 30fps at 30.031Hz, 50fps at 50.051Hz and 60fps at 59.951Hz on my EIZO, I am absolutely sure I did not detect one single glitch. I even tried all of the above at 59.951Hz (60Hz, which is my standard windows refresh rate). No dropped frames, nothing. Now, when keeping in mind that performance has also improved a lot, exclusive mode really seems the way to go. I am simply speechless.

One question though:

Is it possible that the involved switch (screen goes black, comes back again) that happens when the renderer switches from fullscreen windowed to fullscreen exclusive can somehow be made a little more "less noticable"? Or is that a side-effect of the automatic switching, because you kind of need to "initialize" the exclusive mode every time and so it´s completely out of your control? This is not a major problem at all, but it takes about 0.5-1 seconds, even on my GTX260.

Other than that, I´m gonna further test 0.25 and look out for bugs, but it seems you already did your homework, again... :)

Specs:
(1) Geforce GTX 260-216 [Nvidia Quadro 258.49 WHQL]
(2) Windows Vista x64
(3) Aero on
(4) 1920x1200@59.951Hz (normal use)
(5) PotPlayer, KMPlayer or MPC-HC
(6) ffdshow video and audio decoder
(7) Haali Media splitter

madVR settings:
(1) Use 3DLUT
(2) Bicubic75, Spline64, Bicubic75
(3) don´t flush for everything

pankov
5th August 2010, 00:19
Is this really v0.25? I'm asking because v0.24 had this issue and it was supposed to be fixed in v0.25. The fix was also confirmed by at least 2 people. With MPC HC, though.
Yes, in the changelog it says 0.25. Btw is there a reason not to put madVR version as a general file version?

In what way is it inconsistent?
Points 2 and 3 in my post - the ones with ZP's popup menu and seekbar.

Does not happen for me. Does it only happen on secondary screen or also on primary?
Since my problems with playback on the secondary monitor I've switched to single monitor usage - so I'm currently reporting problems that happen on my Primary monitor.

Ok, will have a look at that.

Thank you very much

That's weird. Haven't actually looked at rendering times myself yet.
I tried the advice you gave to someone else - to change to flush & wait (loop) but this didn't help.

madshi,
I really like your idea of implementing automatic exclusive mode
Thank you very much for thinking about us ZoomPlayer users.
In the devinfo.txt I noticed that you've implemented an interface for OSD text messages and I was wondering if it's possible to bring this to the next level - to have interface for drawing graphics not only text in exclusive mode? (Some kind of virtual window/Device Context that madVR will overlay over the rendered image).
This will allow with very little work from the developers of the player to have their original OSD/Media Library/Navigation ... or at least I think/hope so.
Another thought that popped into my mind is about controlling which windows should bring madVR out from exclusive mode. It will be great if you can add support for black/white listing window names/executables that should be ignored/considered when checking if madVR needs to get out of fullscreen exclusive mode.

cyberlolo
5th August 2010, 00:34
.i really have to say that i´m extremely impressed with the stable state that madvr 0.25 already is in, even though you just introduced fullscreen exclusive mode with madvr 0.24.

The idea of having the renderer autmatically switch between fullscreen windowed and fullscreen exclusive is great, i´ve never even thought that something like this could work as flawless as this. Thanks not only for your commitment for giving us madvr for free, but also for your fresh new ideas which really deserve at least one post of respect.

+1

Anima123
5th August 2010, 05:20
Madvr is so great that I'd even like to pay for it if I will have to.

BeNooL
5th August 2010, 07:20
Tested 0.25 yesterday and here is what I noticed.

- while generally smooth the fullscreen exclusive mode has sometimes severe dropped frames: it plays fine for a while, severe dropped frame and smooth again for another long time.
- having the video paused in MPC-HC with fullscreen exclusive seems to sometime steal focus from other application.

That is with ATI 4550, XP SP3 and Catalyst 10.6. Multi display with video being played on 2nd screen (TV).

andybkma
5th August 2010, 09:13
Hope one of you fine video experts can help me out with this problem I'm having ever since any version of madVR past .19

XP SP3, Using Zoom Player 7 Pro, 2 different laptops with 1) Nvidia 8600M-GT and 2) Nvidia 8600M-GS. And using a 20" external monitor with resolution 1600x900.

Basically my problem is that whenever I play a higher rez video such as 1280x720 or 960x540 on my 1600x900 external monitor in fullscreen mode, I drop frames like crazy and have severe video stuttering. The same video plays fine in window mode, it's just in fullscreen that I get this severe stuttering. If I change the resolution of my external monitor to let's say 1280x720 (or 1280x800) or use my projector with its native rez of 1280x720 the videos play fine. It's only in resolution 1600x900 that I have this problem. I tried both the VGA and DVI inputs of my external monitor and same same problem.

Like I mentioned, .19 madVR does not have this problem for me so it's something in the code past .19 that is causing this for me. Does anyone have any ideas? How can I get these newer madVR versions to play nice nice with monitor resolution 1600x900 with 1280x720 videos? Thanks for any tips or advice...

lych_necross
5th August 2010, 10:35
Alright, told him. I thought "callback" meant something else.

Ah, you're so full of mysteries! It seems that it's got to do w/ distributed calibration or so? possibly using a database running the default RBG xy coordinates of many displays?

The only reason I could think of for a VR to connect to the LAN would be to synchronize this kind of "wall of image" set ups: http://www.hellopro.fr/images/produit-2/9/6/6/mur-d-images-1227669.jpg

Otherwise, maybe you plan on running your own madtube.com website? it's a mad mad mad world, that's for sure :p
I ran strings on that file. Interesting output. I came across a line called "mad* home cinema network". My guess is that it allows the user to stream a video from one computer to another on a lan. It maybe something like a Windows Media Center Extender. Very interesting... :D

madshi
5th August 2010, 11:41
Madshi,I've found this workaround (?).Is it how you acesss to fullscreen mode on your test machine with ZP?
You shouldn't have to change the AR to make madVR go fullscreen exclusive mode. Don't know why you have to do that. I'll add more information to the OSD in the next version to find out why it's not going into fullscreen mode with the default AR mode for you.

This doesn't help on my end, unfortunately. Rendering times actually increase very very slightly :confused:.
Weird. But I'm not sure if it has anything to say, though...

When UAC kicks in during playback, it stops and outputs the following message:
Why would UAC kick in during video playback? :confused:

1) Initially I couldn't get any video output at all, only audio. It was because I have reclock calling a vbs script to auto refresh rate in certain scenarios. Disabling this allows me to see video output so madVR can't currently handle refresh rate changes with this new fullscreen mode. Can madVR be made to react to changes of resolution / refresh rate?
As I said before, the final solution will be to let madVR handle refresh rates. I don't believe in letting ReClock pull the strings behind madVR's back. ReClock should leave madVR's rendering logic alone, thank you very much.

In this scenario I wasn't able to get out of the black screen though using ESC or ALT-Enter.... can these keys be made to bring the user out of this fullscreen mode?
Should work, unless the media player and/or madVR were frozen/crashed.

2) When I right click the video in fullscreen mode, the image flickers for a second or two and I see no menu, and then sometimes either nothing happens, playback continues but now I right clicked again and video and audio output stopped for about 10 seconds.... and then continued.
You're playing video back on secondary monitor, right? Seems that v0.25 doesn't handle that well yet. Should be fixed in the next build.

What does this do? Or rather, do I need this for anything when I already set madVR as output in the options?
You can ignore that. All DirectShow filters are listed there, including renderers.

I'm still in windowed mode according to the OSD. What am I doing wrong?
I'll add more info to the OSD in the next build to find out why it's not switching to fullscreen exclusive mode on your PC.

1. Time Seeking bar does not appear until I click the mouse.
Will be fixed in the next build.

2. Press the [Windows] key, the MPC-HC sometimes gets hung or crashed.
Will check if I can reproduce that problem.

I really have to say that I´m extremely impressed with the stable state that madVR 0.25 already is in, even though you just introduced fullscreen exclusive mode with madVR 0.24.

The idea of having the renderer autmatically switch between fullscreen windowed and fullscreen exclusive is great, I´ve never even thought that something like this could work as flawless as this. Thanks not only for your commitment for giving us madVR for free, but also for your fresh new ideas which really deserve at least one post of respect.
Thanks!

Is it possible that the involved switch (screen goes black, comes back again) that happens when the renderer switches from fullscreen windowed to fullscreen exclusive can somehow be made a little more "less noticable"? Or is that a side-effect of the automatic switching, because you kind of need to "initialize" the exclusive mode every time and so it´s completely out of your control? This is not a major problem at all, but it takes about 0.5-1 seconds, even on my GTX260.
I have to "reset" the Direct3D device to switch between windowed <-> exclusive mode, there's nothing I can do about that. I don't think it can be made less noticeable. It seems it's more noticeably for some people than others. It's much less noticeably on my dev PC compared to my HTPC. Don't know where the difference comes from. Maybe OS. Maybe GPU. Maybe something else...

in the changelog it says 0.25. Btw is there a reason not to put madVR version as a general file version?
Would have to change the install bat every time. In the long run I'll probably not ship all those various versions, anymore, but just the latest one. I'm shipping so many versions now because it's still so early in development and sometimes older versions may work better than newer versions.

In the devinfo.txt I noticed that you've implemented an interface for OSD text messages and I was wondering if it's possible to bring this to the next level - to have interface for drawing graphics not only text in exclusive mode? (Some kind of virtual window/Device Context that madVR will overlay over the rendered image).
This will allow with very little work from the developers of the player to have their original OSD/Media Library/Navigation ... or at least I think/hope so.
VMR9 already has an interface which allows that, but ZoomPlayer isn't using it (AFAIK). ZoomPlayer seems to be using standard Delphi GUI elements to draw the GUI, and I don't think it's easy to draw these GUI elements into a device context.

Another thought that popped into my mind is about controlling which windows should bring madVR out from exclusive mode. It will be great if you can add support for black/white listing window names/executables that should be ignored/considered when checking if madVR needs to get out of fullscreen exclusive mode.
Not sure if that makes sense. If madVR does not switch out of exclusive mode when it's covered by other windows then there may be nasty flickering between madVR window and the other window.

- while generally smooth the fullscreen exclusive mode has sometimes severe dropped frames: it plays fine for a while, severe dropped frame and smooth again for another long time.
Don't see that on my PC. Do you have the same problem in windowed mode?

- having the video paused in MPC-HC with fullscreen exclusive seems to sometime steal focus from other application.
Do you see the same behaviour with EVR/VMR exclusive mode? Or is this specific to madVR?

XP SP3, Using Zoom Player 7 Pro, 2 different laptops with 1) Nvidia 8600M-GT and 2) Nvidia 8600M-GS. And using a 20" external monitor with resolution 1600x900.

Basically my problem is that whenever I play a higher rez video such as 1280x720 or 960x540 on my 1600x900 external monitor in fullscreen mode, I drop frames like crazy and have severe video stuttering.
Try playing with the windowed mode tweak options. Generally, v0.19 should not perform better than newer versions, if you set the tweak options "right". If you search back through the thread, I once explained which tweak options make newer madVR versions behave similar to v0.19.

I ran strings on that file. Interesting output. I came across a line called "mad* home cinema network".
In what way does that surprise you?

mad* home cinema network -> madHcNet.dll

I thought that much was obvious! Let me state again that madHcNet.dll does *NOT* contact the internet, or "dial home" or anything of that sort. I've seen speculation about that in another forum. So in order to put that fear to rest, let me say that much, that madHcNet.dll allows madVR instances on the local LAN to see and communicate with each other. This functionality is not actually used yet, though. And I won't say (yet) which purpose it will be used for.

fastplayer
5th August 2010, 11:43
Why would UAC kick in during video playback? :confused:
When you invoke it manually, I mean.

neb1236
5th August 2010, 12:32
Hi,

Firstly I confirm the problem on full-screen on secondary monitor that jump back to the main monitor on my configuration.
btw at the moment madVR switch to full-screen on primary, the second monitor also blink at the same time as the primary, is it needed?
May I propose an option to use the exclusive mode immediately when going to full-screen? It will virtually reduce the impression of the black blink since it will be mixed with the changing of windowed to full-screen?

Last question, is it possible to see no improvement compared to windowed, Meaning that windowed mode is (for me) is already perfectly smooth? Or am I tolerant to bad playback?

Config:
ATI HD5770 last catalyst drivers, all catalyst software deactivated at startup
2 screens in DVI : 1600x1200+1920x1200 both at 60hz
Madvr 2.4 setting to default, except lanczos4 moved to lanczos3
Window 7 x64 aero on
All=ffdshow, H264=coreAVC through ffdshow, vsfilter, haali, mpcHC (build 2099)

Speed of the full-screen exclusive mode: low for the first time (about 1/2sec) and then too fast to quantify it

Last word: Thank you so much, madVR is the only overlay that initiates that fast compared to other EVR base output

leeperry
5th August 2010, 13:00
@madshi: so do you think there's a chance you could retrieve the current refresh rate info from XP at all? some ppl complained that it also didn't work on Vista I think.

I can only confirm that windowed mode still works amazingly well, I said "it's a mad mad mad world" coz I had almost given up on my HTPC before mVR showed up, hah :D

And Reclock doesn't just "pull the strings behind mVR's back", it also does 23.976 and 25@24fps adaptations so anyone can enjoy his movies at the proper speed...and w/o any audible glitch at that. Some ppl seem to prefer a dropped frame from time to time over resampled audio...each to his own, personally dropped frames ruin the whole thing for me..just like gappy audio playback.
"mad* home cinema network". My guess is that it allows the user to stream a video from one computer to another on a lan.
That's the most logical explanation but I don't see the point to that..as most processing is done in the GPU anyway?

andybkma
5th August 2010, 13:02
Thanks, madshi for your input to my rendering 1280x720 material on a 1600x1900 monitor stuttering problem. I realized that I do indeed still have the same problem with version .19 so went back to .25 and played with the luma upscaling/downscaling and changed from the default Lanczos 4 to Softcubic 60 for both luma up & down scaling and that improved the stuttering somewhat. Not perfect but better than using Lanczos 4. Guess that means my 8600M-GT and GS are not powerful enough to display 720p material on a 1600x1900 monitor with Lanczos? strange.

Oh, and I want to also confirm I have the same problem as poster "Luv" with going into Exclusive Full Screen mode with Zoom Player requiring that I change the aspect ratio to Disable (Fit To Window). If I leave it at Derived (recommended) then it stays in windowed mode per the madVR OSD even though I am in fullscreen. Not every video but I would say at least 80% of my videos won't go into Exclusive Full Screen mode unless I change the aspect ration to Disabled. But then of course that messes up the AR so that solution is no good.

leeperry
5th August 2010, 13:05
BTW, you said: "If the PotPlayer coder wants to have an interface to ask madVR whether it's in fullscreen exclusive mode or not, I can add that"

He told me that he would need it, as he currently has no way to know whether mVR is running in FS. :thanks:

nlnl
5th August 2010, 13:13
madshi
Thanks again for that smooth playback!

And back to high rendering time...
FS Exl
Playing 1080p23 file at 1080p23 monitor aver rendering time is 32 dec queue 7-8/8 up queue 4-5/8 rend queue 3-4/8
Playing the same 1080p23 file at 1080p50 monitor aver rendering time is 17 dec queue 7-8/8 up queue 7-8/8 rend queue 7-8/8
Playing 1080p23 file at 1080p59 monitor aver rendering time is 13 dec queue 7-8/8 up queue 7-8/8 rend queue 7-8/8

And aver rendering time is slowly going up!

Is that OK ?

In FS Wind mode rendering time is always 7.1-7.4 and queues are 7-8/8

MPC, Vista, AMD 5400, 10.7 30bitRGB output

Fer
5th August 2010, 13:51
Brilliant work. Keep doing. Very grateful forever.

One minor petition. It would be posible to low the screen OSD vertical position in order that the text were inside a 2.35:1 screen?
http://a.imageshack.us/img828/5298/dibu.th.jpg (http://img828.imageshack.us/i/dibu.jpg/)
Now the information about the exclusive mode it is not seen in such kind of constant height screens.

:thanks:

Mark_A_W
5th August 2010, 14:35
madshi, the aspect ratio (Derived) is what has been preventing ZP going into exclusive on my system, if the resolution does not match the video.

With it set to "Disabled", ZP/madVR will go into exclusive on my primary monitor (1920x1200 at 85hz progressive). But of course the aspect ratio is now wrong. It was going into exclusive on my secondary monitor (1920x1080 at 96hz interlaced), but would then chuck the Direct3D error.


So I think I have found why the results appear inconsistent: It will only go into exclusive with the aspect ratio set to "Derived (recommended)", if the resolution matches the video res.


Also, it would be FANFRIGGINTASTIC if you could negotiate the madVR/Reclock interaction with James at Slysoft. He is still actively developing Reclock, and as madVR is the best video renderer, Reclock is the best audio renderer (even if you don't want resampling - it still has WASAPI and all sorts of good stuff).


Please consider setting up a Paypal donation account. I'm sure I'm not the only one who would like to buy you a beer :)

Mark

namaiki
5th August 2010, 15:24
Guess that means my 8600M-GT and GS are not powerful enough to display 720p material on a 1600x1900 monitor with Lanczos?

Are you using CoreAVC's CUDA video offloading?

andybkma
5th August 2010, 15:39
Are you using CoreAVC's CUDA video offloading?

No, this is 1280x720 wmv material. Just can't figure out why it renders fine on any other resolution except for 1600x900. Very strange, still haven't quite solved this problem. The more I play with madVRs settings, the more problems I seem to create....

namaiki
5th August 2010, 15:45
andybkma, assuming single monitor, have you tried disabling Aero?

andybkma
5th August 2010, 16:11
andybkma, assuming single monitor, have you tried disabling Aero?

Yes, single monitor but am XP SP3. My original post (amended for current problem)

XP SP3, Using Zoom Player 7 Pro, 2 different laptops with 1) Nvidia 8600M-GT and 2) Nvidia 8600M-GS. And using a 20" external monitor with resolution 1600x900.

Basically my problem is that whenever I play a higher rez video such as 1280x720 or 960x540 on my 1600x900 external monitor in fullscreen mode, I drop frames like crazy and have severe video stuttering. The same video plays fine in window mode, it's just in fullscreen that I get this severe stuttering. If I change the resolution of my external monitor to let's say 1280x720 (or 1280x800) or use my projector with its native rez of 1280x720 the videos play fine. It even plays fine on my laptops' rez of 1280x800 in fullscreen. It's only in resolution 1600x900 and fullscreen that I have this problem. I tried both the VGA and DVI inputs of my external monitor but same same problem.

namaiki
5th August 2010, 16:18
Did it work before? How much video ram do the GPUs have?

andybkma
5th August 2010, 16:37
Did it work before? How much video ram do the GPUs have?

The 8600M GT has 512 MB and the 8600M GS has 256. Problem is on both laptops and has always been there. Earlier I had thought the problem went away with version .19 but I was mistaken. Changing the luma upscaling/downscaling values has minimal effect. It's only with resolution 1600x900 in fullscreen mode that I have this problem which unfortunately is my external monitor's native rez. The vids play fine in fullscreen on both my laptops internal displays which are 1280x800 rez. This is driving me nuts trying to figure out this problem...

More troubleshooting: Also have this same problem with H264 1280x720 material even when using CoreAVC and Cuda. It's as if madVR can't render 1280x720 material (wmv nor H264) smoothly in fullscreen on my monitor resolution 1600x900. I don't know how else to describe this...

namaiki
5th August 2010, 17:07
Try on the 8600M GT first. Make sure you have the latest ForceWare (if you can't update for some reason, you can still try download GPU-z), download the latest GPU-z. Open GPU-z, go to the sensors tab. There should be load readings for GPU, RAM, RAM usage. Tick 'continue refreshing this screen while GPU-z is in the background'. Open madVR, and play a video in full screen as usual and check the load readings.

If they look high, you can try set flushes as follows (I haven't bothered recommending these in a while):
After render: flush and wait(sleep)
After last step: flush
After backbuffer: don't flush
After present: don't flush

Also, make sure that your PC is set to portable/laptop or a power profile where it will not throttle the CPU.


These are all blind information, but I really hope you can get this working.

Lastly, are these all standard videos like 23.976 or 29.970 fps, or is this the interlaced thing?

andybkma
5th August 2010, 17:54
Try on the 8600M GT first. Make sure you have the latest ForceWare (if you can't update for some reason, you can still try download GPU-z), download the latest GPU-z. Open GPU-z, go to the sensors tab. There should be load readings for GPU, RAM, RAM usage. Tick 'continue refreshing this screen while GPU-z is in the background'. Open madVR, and play a video in full screen as usual and check the load readings.

If they look high, you can try set flushes as follows (I haven't bothered recommending these in a while):
After render: flush and wait(sleep)
After last step: flush
After backbuffer: don't flush
After present: don't flush

Also, make sure that your PC is set to portable/laptop or a power profile where it will not throttle the CPU.


These are all blind information, but I really hope you can get this working.

Lastly, are these all standard videos like 23.976 or 29.970 fps, or is this the interlaced thing?

Thanks, namaiki, for trying to help me out. Ya, these videos are just regular 23.970 or 23.976 fps per MediaInfo. Both laptops' power profiles have always been at portable/laptop. Tried your settings, unfortunately no help. Newest GPU-Z version sensors tab only shows me GPU Core Clock, Memory Clock & Shader Clock readings which I'm sure are not the load readings you were referring to for me to monitor. Thanks again but still at a loss...

Edit: After further research the problem seems to be mostly with 1280x720 material with fps of 29.970 and higher (30.000). 1280x720 vids with 23.976 and 25.000 fps don't play too badly. Is this a hint to finally solving this problem?

BeNooL
5th August 2010, 18:42
Don't see that on my PC. Do you have the same problem in windowed mode?
I don't watch videos in windowed mode...
This is new to 0.25 build. Previous version were very smooth from beginning to end.

Do you see the same behaviour with EVR/VMR exclusive mode? Or is this specific to madVR?

I don't think I ever used EVR/VMR exclusive mode before.
Saying that I realize my contribution to helping the developpement starts to grow thin :p

TinTime
5th August 2010, 18:45
madshi, the aspect ratio (Derived) is what has been preventing ZP going into exclusive on my system, if the resolution does not match the video.

madshi, I've found similar results with Zoom Player. The key is whether the display AR of the the video matches the display AR of the screen or not.

I'm using a 1920x1080 TV so 16x9 video triggers exclusive mode but anything else doesn't (although MPC HC seems to work as expected with non-16x9 material).

I should say that flipping in and out of exclusive mode is fast on my PC. Not quite instant but not far off - certainly a small fraction of a second. I'm running Windows 7 32bit with an Nvidia 8600GT 512MB, and using CoreAVC in CUDA mode to decode.

But aside from ZP not always switching to exclusive it's looking very good - thanks for the new version!

Razoola
5th August 2010, 19:40
I don't watch videos in windowed mode...

I think I'm right in saying with older versions of madvr (before 024) you were in windows mode even when in full screen unless you were testing the AERO mode which was in a couple of builds.

THX-UltraII
5th August 2010, 20:40
What does the new fullscreen exclusive mode do?

BeNooL
5th August 2010, 20:59
I think I'm right in saying with older versions of madvr (before 024) you were in windows mode even when in full screen unless you were testing the AERO mode which was in a couple of builds.

Oh ok. Then yes, there is no such issue in previous version.

Just finished watching a movie with 0.25 FS Exclusive disabled and no hiccups all along.

So for me, FS exclusive mode is worse than normal/windowed mode.:confused:

leeperry
5th August 2010, 21:03
Having more thoughts about it, Reclock simply asks GDI for the current resolution...if D3D is clueless, GDI's got to know :)

Mangix
5th August 2010, 21:16
Thanks, namaiki, for trying to help me out. Ya, these videos are just regular 23.970 or 23.976 fps per MediaInfo. Both laptops' power profiles have always been at portable/laptop. Tried your settings, unfortunately no help. Newest GPU-Z version sensors tab only shows me GPU Core Clock, Memory Clock & Shader Clock readings which I'm sure are not the load readings you were referring to for me to monitor. Thanks again but still at a loss...

Edit: After further research the problem seems to be mostly with 1280x720 material with fps of 29.970 and higher (30.000). 1280x720 vids with 23.976 and 25.000 fps don't play too badly. Is this a hint to finally solving this problem?
your GPU is most likely not fast enough. i have an 8500 GT(16 vs your 32 shader cores). And it drops frames like crazy if i enable resizers like lanczos or spline. Softcubic, Bicubic, and those work just fine.

Best tip i can give you is to overclock your GPU. Programs such as EVGA Precision or RivaTuner will let you do that. note that only shader clock actually makes any difference. The rest can be left alone.

pankov
5th August 2010, 22:19
Would have to change the install bat every time. In the long run I'll probably not ship all those various versions, anymore, but just the latest one. I'm shipping so many versions now because it's still so early in development and sometimes older versions may work better than newer versions.
madshi, I think you missed my point. I'm not talking about changing the name of the .ax file - I'm talking about the file version (http://msdn.microsoft.com/en-us/library/ms646981%28VS.85%29.aspx) (right click - properties - Details in Win7 or right click - properties - Version in WinXP)
VMR9 already has an interface which allows that, but ZoomPlayer isn't using it (AFAIK). ZoomPlayer seems to be using standard Delphi GUI elements to draw the GUI, and I don't think it's easy to draw these GUI elements into a device context.
I suppose you are right :(
Not sure if that makes sense. If madVR does not switch out of exclusive mode when it's covered by other windows then there may be nasty flickering between madVR window and the other window.
I'm not sure why do you think there will be flickering. DVBViewer is using fullscreen exclusive mode and there is no flickering at all. But I suppose you know better. I was just trying to find a way to prevent unnecessary switching between exclusive and windowed modes.