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
5th July 2013, 22:28
CRU is an easy way to do EDID overrides....
So if he can change the product ID with CRU, the monitors don't have an EDID block...
Or they have an EDID block with identical product ID?

Can you try encoding a source
No. I have no experience with and no time for encoding.

wait, I've seen my fps go to 23.976 fps on telecined content without using madVR's film mode.
Where did you see that? Fraps? Reclock? There are different kinds of 60i sources out there. Some are hard telecined, others soft telecined, and many are a funny mix of hard and soft telecine. Soft telecined content can look like 23.976fps, even with DXVA deinterlacing. But that's not because DXVA can do decimating, but just due to the nature of the encoding. You won't see 23.976fps with hard telecined content, when using DXVA deinterlacing.

Moragg
5th July 2013, 22:43
Ok, will have to check whether I can isolate the problem with the FSE switch delay somehow.


Well, by turning "Present Several Frames in Advance" off you're practically going back to a rather old logic which madVR had used a long time ago. Some people are still using it because for some reason it works better for them. But as you found out yourself, having "Present Several Frames in Advance" turned on with a reasonably high number of frames produces better results for most users - especially on OSs newer than XP.

I'm guessing this logic doesn't work normally (for whatever reason) or you'd have implemented it, but would it be possible is it possible to "trick" madvr into presenting the frames later or something so audio and video are perfectly in sync?


Well, there you have it: FSE simply is the most reliable playback method. There's a reason why I have it enabled by default in the madVR settings - even though it comes with a number of usability disadvantages.

If your GPU supported Overlay mode, that would have been another thing worth trying. But if normal windowed mode simply doesn't run well on your PC (for whatever reason) you may have no other choice than to use FSE mode.

Windowed works fine, it's just these high framerate files I'm getting problems with.

Anyway, :thanks:

turbojet
5th July 2013, 22:51
No. I have no experience with and no time for encoding.

Does a log help then?

mindbomb
6th July 2013, 00:53
Where did you see that? Fraps? Reclock? There are different kinds of 60i sources out there. Some are hard telecined, others soft telecined, and many are a funny mix of hard and soft telecine. Soft telecined content can look like 23.976fps, even with DXVA deinterlacing. But that's not because DXVA can do decimating, but just due to the nature of the encoding. You won't see 23.976fps with hard telecined content, when using DXVA deinterlacing.

Oh, okay, i see. This clears up why when watch something that is a mix of hard and soft telecine that the frame rate will bounce around when not using film mode.
I was using reclock and double checked with evr cp. The content must have been soft telecined.

khanmein
6th July 2013, 04:26
guys, please kindly i need help cos whether i play .mkv it shown lav splitter (internal) low merit !!

http://i42.tinypic.com/2rdubub.png

druneau
6th July 2013, 05:54
guys, please kindly i need help cos whether i play .mkv it shown lav splitter (internal) low merit !!

I updated my MPC-HC today and noticed it came with its own copy of LAV.

I rechecked "option --> Internal Filters", some were now checked (they weren't before the update).

ryrynz
6th July 2013, 07:03
guys, please kindly i need help cos whether i play .mkv it shown lav splitter (internal) low merit


Internal filters: always try LAV Filters in low merit mode.
05abb83107 - Underground78 authored 2 days ago


Also, this is not the place to be posting about LAV or MPC-HC.

madshi
6th July 2013, 07:11
I'm guessing this logic doesn't work normally (for whatever reason) or you'd have implemented it, but would it be possible is it possible to "trick" madvr into presenting the frames later or something so audio and video are perfectly in sync?
Are you saying audio and video are not in sync? They should be. If they're not, it's likely something else in your playback chain and not madVR - unless you get constant frame drops reported. In that case I can't guarantee perfect audio/video sync.

Does a log help then?
I'll quote myself:

> I can only do anything (if at all) if I can reproduce
> it, though. So do your best to create a good
> step-by-step guide that allows me to reproduce
> the problem on my PC.

guys, please kindly i need help cos whether i play .mkv it shown lav splitter (internal) low merit !!
Please don't post the same question in multiple threads. That's considered rude. Also, this doesn't really have anything to do with madVR.

madshi
6th July 2013, 11:13
Here's a test build:

http://madshi.net/madVRfseTest.rar

Can those of you who have FSE delay with v0.86.7 please check whether this test build fixes the issue?

pankov
6th July 2013, 11:19
madshi,
this test build fixed the FSE issue that I had on my bedroom PC (Intel HD4000) with 0.86.7.
As far as I can tell it was always switching resolutions/refresh rates when going into FSE mode even though it was already at the correct one.
Is this what you actually changed in the test build?

ryrynz
6th July 2013, 11:30
please check whether this test build fixes the issue

Fixed!

madshi
6th July 2013, 12:59
Good to hear! So the problem was caused by my hacking around to fix the win8 wrong refresh rates when entering FSE mode. I've modified the hack a bit in the test build to apply it only if really necessary, and that seems to fix the FSE delay. However, for users who're on win8 and who need the hack, the FSE delay might still be there - but at least afterwards the correct refresh rate should be used.

THEAST
6th July 2013, 17:13
Edit: Scratch that, was a false-positive...

andybkma
6th July 2013, 17:39
Here's a test build:

http://madshi.net/madVRfseTest.rar

Can those of you who have FSE delay with v0.86.7 please check whether this test build fixes the issue?

Worked for me too :-)

turbojet
6th July 2013, 21:43
madshi: I'll make a batch file that starts an x264 encode using lavfilters as source but will need you to do a few changes with lavfilters but nothing needs to be installed. Might get it done today otherwise early next week. You might be able to move the player to another screen and with osd on switch, create new tabs in chrome or firefox and see some dropped frames but it's not consistent.

There's a lot of crashes (almost every time) in 86.7 going to next file in mpc-be. Doesn't happen with 86.6.

EDIT: added backbuffer issue to bugtracker.

madshi
6th July 2013, 22:55
There's a lot of crashes (almost every time) in 86.7 going to next file in mpc-be. Doesn't happen with 86.6.
Crashes in madVR? Does madVR show a bug report window? Or does MPC-BE itself crash?

turbojet
6th July 2013, 23:19
MPC-BE stable 1.2.0.3 crashes but latest nightly works fine. Seems like madvr 86.7 triggered an mpc-be bug that's since been fixed. MPC-HC stable and latest nightly work fine.

Soukyuu
6th July 2013, 23:29
What is the advantage of using the overlay mode vs. not using it? So far disabling it didn't seem to change anything except for no more glitches while resizing the window and the preview actually showing the video when hovering over a tab.

truexfan81
7th July 2013, 02:45
What is the advantage of using the overlay mode vs. not using it? So far disabling it didn't seem to change anything except for no more glitches while resizing the window and the preview actually showing the video when hovering over a tab.

when in windowed mode or non FSE, using overlay allows for smooth playback even with higher gpu usage, without it i think it starts getting choppy at about 60%, with overlay you can go upwards of 80% before it starts getting choppy

6233638
7th July 2013, 03:18
What is the advantage of using the overlay mode vs. not using it? So far disabling it didn't seem to change anything except for no more glitches while resizing the window and the preview actually showing the video when hovering over a tab.Better performance in windowed mode, but the trade-off is the problems that you describe. (just like FSE gives you even better performance, but also impacts usability)

Here's a test build:

http://madshi.net/madVRfseTest.rar

Can those of you who have FSE delay with v0.86.7 please check whether this test build fixes the issue?0.86.7 is switching to 24/59Hz in FSE for me, and this test build is switching to 23/59 again. (madVR is set for 24/60)

Windowed mode is still working correctly.

turbojet
7th July 2013, 07:41
Another limitation of overlay is it doesn't work with multiple instances. MadVR currently allows this but it could probably work around it by checking for another madvr overlay instance and automatically disables overlay if it finds one.

I wonder how vlc gets around all these overlay limitations, it runs nice and smooth near 100% gpu.

Trib
7th July 2013, 07:55
Ive been wondering does my panasonic st30 plasma expects tv or full range as unlike my previous sony lcd this one doesnt have any black levels switch or otherwise any calibration settings on the tv except contrast and brightness thats about it. With my sony I also got 16-235 in madvr with whole chain 0-255 which I assume was the correct behaviour.

Using the AVS HD 709 black and white patters and True Cinema preset from tv I get and whole chain until madvr set to 0-255 (used madnvtweak for gfx card)
1) MadVr set to 16-235 -> black clips at 16 white goes to 255 on white pattern test
2) MadVr set to 0-255 -> black doesnt show at all compared to 1) white clips at 235

With my sony I got 16-235 in madvr with whole chain 0-255 so Im not sure tho measuring with spyder 4 hcfr says the gamma deltas are <4E(overall around ~2.2avg gamma) and color too with option 1) so I assume its correct? (with 2) delta avg >18E and gamma ~2.6) If this is the case why does it still show 235-255 and is this a bad thing?

6233638
7th July 2013, 10:57
Ive been wondering does my panasonic st30 plasma expects tv or full range as unlike my previous sony lcd this one doesnt have any black levels switch or otherwise any calibration settings on the tv except contrast and brightness thats about it.The manual indicates that you should have this option:

http://www.abload.de/img/hdmiiasxc.png

There is also a "Black Level: Dark/Light" option, which is presumably for YCC signals.


Using the AVS HD 709 black and white patters and True Cinema preset from tv I get and whole chain until madvr set to 0-255 (used madnvtweak for gfx card)
1) MadVr set to 16-235 -> black clips at 16 white goes to 255 on white pattern test
2) MadVr set to 0-255 -> black doesnt show at all compared to 1) white clips at 235That indicates your display is set to 16-235, but doesn't clip above 235. (presumably contrast isn't high enough to clip)

makakam
7th July 2013, 11:25
Has anyone seen "The Place Beyond the Pines" and can confirm that blacks are washed out? When switching between tv and pc levels in madvr I can see that pc levels look better (though I think some details might be crushed then) but tv levels is what works best for me in every other movie (of course it works with calibration patterns as well). Thanks.

ryrynz
7th July 2013, 11:45
The manual indicates that you should have this option:


Have the same TV, it doesn't have this option.

6233638
7th July 2013, 12:03
Have the same TV, it doesn't have this option.It must be a regional difference - unfortunately Panasonic have a track record of doing that. It looks like the manual I checked was for the US model (http://service.us.panasonic.com/OPERMANPDF/TCP42ST30.PDF).

Qaq
7th July 2013, 13:24
For panny TVs I'd use YCC 4:4:4 in video driver and TV anyway. Panny TVs are known to screw RGB 444 down to YCC 422. YCC 444 should be safe.

kasper93
7th July 2013, 13:46
Has anyone seen "The Place Beyond the Pines" and can confirm that blacks are washed out? When switching between tv and pc levels in madvr I can see that pc levels look better (though I think some details might be crushed then) but tv levels is what works best for me in every other movie (of course it works with calibration patterns as well). Thanks.

Yes, I can confirm that. But this is shitty Russian version and I think it's just broken. Wait and buy proper version when they release it. According to blu-ray.com official premiere is on Aug 06, 2013.

Ps. This is wrong place to discuss such things...

Trib
7th July 2013, 14:29
It must be a regional difference - unfortunately Panasonic have a track record of doing that. It looks like the manual I checked was for the US model (http://service.us.panasonic.com/OPERMANPDF/TCP42ST30.PDF).

Yup my EU, specifically Nordic/Finnish model doesnt have that option atleast.

madshi
7th July 2013, 18:11
madVR v0.86.8 released

http://madshi.net/madVR.zip

* fixed: entering FSE mode sometimes caused a delay (introduced in v0.86.7)
* added support for specifying a separate external 3dlut for each source gamut
* gamut conversion is now skipped if the 3dlut gamut matches the source gamut
* madTPG: screensaver is blocked (except if it is passworded!)
* madTPG: screen is prevented from going to sleep
* madTPG: added "stay on top" button
* madTPG: changed the way the "fullscreen" button works
* madTPG: window size/state and all settings are auto saved now
* madTPG: now works without requiring madVR to be installed
* madTPG: fixed: crash when madVR was not installed

rack04
7th July 2013, 18:35
madVR v0.86.8 creates a log file on the desktop. Is this intentional?

antonyfrn
7th July 2013, 18:55
madVR v0.86.8 creates a log file on the desktop. Is this intentional?

Confirmed here is there away to disable it as I don't want unneeded writes to my SSD just under 500meg log file for 5min of video being played.

Also noticed madTPG full screen doesn't work. But did work in 0.86.6

Warlock
7th July 2013, 19:08
You can disable this log file? Just watched a video of 24min, he created +-2GB log file.

DragonQ
7th July 2013, 19:15
Have the same TV, it doesn't have this option.

My Panasonic TX-P50ST50B also has differing menus to what most claim on the internet. Definitely a regional thing. It accepts both 0-255 and 16-235 and adjusts automatically though.

madshi
7th July 2013, 19:16
Sorry, my fault. I've accidently compiled the release build as debug build. I've fixed it now, please re-download.

@antonyfrn, the "use fullscreen" button works differently now. It doesn't go fullscreen immediately. It will go fullscreen in the moment when ArgyllCMS/HCFR start measuring. The purpose of this change is that you can activate fullscreen mode while running ArgyllCMS/HCFR on the same PC. That wasn't possible before. If you prefer going fullscreen immediately, you can still do so by pressing Alt+Return.

Nui
8th July 2013, 00:42
@ madshi
In the last few days I tried generating 3dluts myself.

I noticed, that madvr requires the parametersData field in the .3dlut file. This and what it expects is not clear from the the file specification :)
So I copied a "minimal" parametersData from a madvr-ycms generated 3dlut to create my own. Again I dont know how relevant this is. Especially now when you load a 3dlut for a specific target.

I dont know if im doing something wrong, but I noticed some odd behaviour.
All input values from 0 to 15 are disregarded, at least in my tests. The same goes for output, black is 16*256. White is a 255 and 255*256 respectively.
Isnt this behaviour just wrong?

Once I knew that, I successfully created useful luts, so im happy :)
So thanks again for your awesome renderer! :D

ryrynz
8th July 2013, 07:38
Hey Madshi, can ya improve a little on the icon for madHcCtrl.exe?

madshi
8th July 2013, 07:39
I noticed, that madvr requires the parametersData field in the .3dlut file. This and what it expects is not clear from the the file specification :)
Yeah, unfortunately when we specified the 3dlut file format, we failed to add proper fields to the header which define which gamut the 3dlut expects the input data to be in. Because of that madVR checks "parametersData" to find that information. Copying that minimal parametersData from a madVR-yCMS generated 3dlut should do the trick, but please also make sure you set "Input_Primaries" to the correct coordinates, because madVR will convert the source gamut to those Input_Primaries.

All input values from 0 to 15 are disregarded, at least in my tests. The same goes for output, black is 16*256. White is a 255 and 255*256 respectively.
Isnt this behaviour just wrong?
The 3dlut format used by madVR uses video levels. So 0-15 are BTB, 236-255 are WTW, black is 16 and white is 235. The BTB and WTW areas should not be clipped by the 3dlut processing itself, but depending on your settings, they might be clipped somewhere in the processing chain.

madshi
8th July 2013, 07:40
Hey Madshi, can ya improve a little on the icon for madHcCtrl.exe?
What do you mean? It clearly reads "mad", doesn't it? Isn't that clear enough?

cyberbeing
8th July 2013, 07:55
Only the tray icon reads "mad". The actual exe is now a music note...

http://imageshack.us/a/img708/6341/w8qq.png

kopija
8th July 2013, 07:56
Madshi, how come using linear light for smooth motion FRC is disabled by default? I just turned it on and saw no impact on GPU load.

madshi
8th July 2013, 07:59
Only the tray icon reads "mad". The actual exe is now a music note...
Oooops. Seems the Windows icon cache fooled me here. It still shows the "mad" icon. Only when I move madHcCtrl to a new folder, I can see the music note.

Madshi, how come using linear light for smooth motion FRC is disabled by default? I just turned it on and saw no impact on GPU load.
You probably have a somewhat faster GPU? I think for really old GPUs there could be a noticable difference in performance?

Can anybody with a slow GPU double check? Should I enable linear light for smooth motion FRC by default?

cyberbeing
8th July 2013, 08:25
Can anybody with a slow GPU double check? Should I enable linear light for smooth motion FRC by default?

Increases GPU load by ~3% if I upscale from 1280x720 23.976fps to 1600x900 @85Hz.

Increases GPU load by ~10% if I upscale from 1280x720 23.976fps to 2048x1152 @85Hz.

Increases GPU load by ~10% playing 1920x1080 deinterlaced 60fps with 1920x1080 @85Hz.

ryrynz
8th July 2013, 08:48
I would say that's a reasonable compromise, might as well enable it by default. What GPU was that BTW Cyberbeing?

cyberbeing
8th July 2013, 08:55
I would say that's a reasonable compromise, might as well enable it by default. What GPU was that BTW Cyberbeing?

A GPU I would disable this option on, even if it were enabled by default. ;)

GT440 1GB DDR5

madshi
8th July 2013, 09:09
Need Feedback:

The recent versions (v0.86.7 and v0.86.8) are supposed to fix refresh rate switching in Windows 8, when entering fullscreen exclusive mode. Without that fix, switching to 60.000Hz resulted in 59.940Hz being used, and switching to 24.000Hz resulted in 23.976Hz being used by Direct3D in FSE mode. The fix works for me with my Intel HD4000, resulting in 60.000Hz and 24.000Hz being used in FSE mode. However, I've received a report that it doesn't work in the madVR bug tracker.

So all you Windows 8 users: Could you please check whether you can get 60.000Hz and 24.000Hz to work with v0.86.8 in FSE mode, when using the madVR display mode switcher? Please mention whether your OS is x86 or x64, and which GPU you're using.

Thanks!!

kopija
8th July 2013, 09:31
You probably have a somewhat faster GPU? I think for really old GPUs there could be a noticable difference in performance?

Can anybody with a slow GPU double check? Should I enable linear light for smooth motion FRC by default?

Intel HD 3000 here, when upscaling SD content to 720p plasma, no noticable increase in GPU load.

ryrynz
8th July 2013, 09:57
Yeah that's why I enable it, it's jack all of anything. I don't think many people at all are upscaling to beyond 1920x1080 or running 60fps content or displays higher than 60hz either
so that 10% GPU usage really is in the more extreme situations. Reckon Cyberbeing should just upgrade already :)

mark0077
8th July 2013, 11:42
madshi, does madVR simply switching from desktop to FSE (by making the player go fullscreen, rather than using the display mode switcher) also need to be tested? I still have an issue when going from 60.000hz desktop mode to FSE, it goes into 59.9hz mode, but thats the same for games I believe, probably nothing to do with madVR right?

madshi
8th July 2013, 11:49
madshi, does madVR simply switching from desktop to FSE (by making the player go fullscreen, rather than using the display mode switcher) also need to be tested? I still have an issue when going from 60.000hz desktop mode to FSE, it goes into 59.9hz mode, but thats the same for games I believe, probably nothing to do with madVR right?
If you disable the display mode switcher then madVR is not responsible for the refresh rate. You could try enabling the display mode switcher and only enter one resolution: 1080p60, if that's what you want to achieve. If you do that, madVR is supposed to make sure this also works in FSE mode.