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

Neet009
5th January 2015, 11:39
madVR v0.87.12 released



Thank you for releasing the new version. Now it works well with HCFR.
:thanks:

shaolin95
5th January 2015, 19:27
Hello guys!
Is it normal for the Nvidia Control Panel settings like deinterlace etc to have no effect on the image when using madvr? I have a GTX750ti and Windows 8.1

Thanks

leeperry
5th January 2015, 20:50
Is it normal for the Nvidia Control Panel settings like deinterlace etc to have no effect on the image when using madvr?
yep, but you can always try DXVA and CUVID:

features: (..)
- bypasses graphics card's video (damage) algorithms

dbcooper
5th January 2015, 21:27
Hi Madshi, the problem seemed to start with 0.87.11 - it was not present in 0.87.10.

The problem is when I am using a second display (e.g. my Samsung UE40H6400 TV, via HDMI, and an AMD HD7790 GPU). I can force film mode on the primary display, but not when the MPC-HC window is on the secondary display. When I toggle through modes, it just goes through auto and video, and skips film.

shaolin95
6th January 2015, 01:53
yep, but you can always try DXVA and CUVID:

But that is odd because on LAV Video filter I see CUVID selected. I guess is not a big deal since we are shooting for best IQ and that is what I understand madvr is doing after all. :)

huhn
6th January 2015, 03:49
DXVA and CUVID decoding (it's the same any way) doesn't have an effect on this.

these settings effect madVR when DXVA scaling is used.

next thing is deinterlacing. madVR uses DXVA deinterlacing with a interlaced input stream. and again there is no difference between CUVID or DXVA deinterlacing (CUVID HQ is deinterlacing with inverse telecine checked in the driver). you can change the type of deinterlacing at least with AMD but the sharpening settings and so on doesn't have an effect on this (just tested with amd).

there is "nothing" to gain from CUVID any more it only forces your GPU in a high powerstate. and with active deinterlacing you can't use madVR IVTC for telecine streams any more. which can be easily trigger with a hot key.

mandarinka
6th January 2015, 15:51
http://www.pcper.com/news/Displays/CES-2015-AMD-Announces-Worlds-First-Shipping-Freesync-Monitors

FreeSync monitors finally out (almost). It appears that at least some will hit the shelves this month?

Asmodian
6th January 2015, 21:56
That is very good news but not relevant for madVR as it is currently. It would be interesting to have madVR be G-sync (or FreeSync) aware, it seems like it would be possible to have the audio and video sync be very exact without smooth motion, basically like Reclock but adjusting the video frame timing instead of re-sampling the audio. This would also be great for bit-streaming without smooth motion.

I have been playing with G-sync (PG278Q) and madVR. If madVR goes into full screen exclusive mode G-sync activates but the image flickers quite often which does not happen in games. Also, as expected, it does not refresh at the move frame rate but at 143.5 Hz (I have "use fastest mode available" enabled). If I don't have g-sync enabled or don't use FSE madVR reports a refresh rate of 144 Hz. I believe madVR would need to not present frames in advance but instead only present new a frame when it should be displayed.

As it is now I cannot use full screen exclusive with G-sync enabled but this is not a problem.

DragonQ
7th January 2015, 00:10
Without looking it up, I'm assuming G-Sync and Freesync have fluid refresh rates where you can update the screen at any time (with a minimum time between updates of course, which'd translate to a maximum refresh rate). If so, that is pretty damned cool and I'm surprised it's taken so long to happen. I came up with the idea about a decade ago. :p

In terms of video playback, it's probably most useful for mixed telecined/interlaced content in 60 Hz regions.

e-t172
7th January 2015, 01:38
This article (http://www.hardware.fr/news/14025/ces-amd-freesync-presque-la-point.html), which unfortunately is in French, contains the following information, which I'm translating:

One should note that FreeSync is not usable on the Windows desktop and needs fullscreen exclusive mode to work, which makes it incompatible with most video players. That said, the video player bundled with Windows 8.1 and Windows 10 is FreeSync compatible and the refresh rate will adapt to the video format, thereby ensuring perfectly smooth playback.

The last bit about video playback is quite interesting, maybe it could apply to madVR as well if madshi decides to support it.

kalston
7th January 2015, 10:57
I think the old fullscreen exclusive mode should in theory work with G-Sync but I couldn't get the old FSE to work with my GTX 970 and latest drivers. Might give it another try when I get the chance.

Toco
7th January 2015, 14:54
How should I configure devices - calibration and devices - color & gamma settings if I am using Samsung S24D590PL display with color profile from this review (http://www.easycom.com.ua/disply/samsung_s24d590pl/?lang=ru) (direct link to .icm file (http://easycom.com.ua/data/disply/201410380-3086/img/samsung_s24d590pl.icm))?
http://ipic.su/img/img7/tn/madvr1.1420638088.png (http://ipic.su/img/img7/fs/madvr1.1420638088.png)http://ipic.su/img/img7/tn/madvr2.1420638107.png (http://ipic.su/img/img7/fs/madvr2.1420638107.png)

huhn
7th January 2015, 16:51
there are multiply ways to do this
option 1 (low quality):
load the icm in windows color management. (there is a well known bug in windows where calibrations are not loaded at all the work around is a different program or run the windows calibration program 1 time picture (http://abload.de/img/windowsbugqgu33.png)(just press next and down't change anything))
in madVR:
set calibration to: "this display is already calibrated"
don't check "disable GPU gamma ramps"
optional set color & gamma to pure power curve 2.4.

option 2 /high quality): create a 3d lut from the icm and load it with madVR.
set madVR to "calibrate this display by using external 3DLUT files"
load the file in bt 709.
check "disable GPU gamma ramps"

i crated two 3d lut from the icm file samsung_s24d590pl.icm for you: http://www.file-upload.net/download-10107027/3d-lut.7z.html

i can't check them because i don't have that screen.

one is bt 709 gamma 2.2 an old standard the other one is a bt 1886 3d LUT the new way to do it.

Warlock
7th January 2015, 17:50
there are multiply ways to do this
option 1 (low quality):
load the icm in windows color management. (there is a well known bug in windows where calibrations are not loaded at all the work around is a different program or run the windows calibration program 1 time picture (http://abload.de/img/windowsbugqgu33.png)(just press next and down't change anything))
in madVR:
set calibration to: "this display is already calibrated"
don't check "disable GPU gamma ramps"
optional set color & gamma to pure power curve 2.4.

option 2 /high quality): create a 3d lut from the icm and load it with madVR.
set madVR to "calibrate this display by using external 3DLUT files"
load the file in bt 709.
check "disable GPU gamma ramps"

i crated two 3d lut from the icm file samsung_s24d590pl.icm for you: http://www.file-upload.net/download-10107027/3d-lut.7z.html

i can't check them because i don't have that screen.

one is bt 709 gamma 2.2 an old standard the other one is a bt 1886 3d LUT the new way to do it.
huhn, this same process works in Benq XL2420T?

Toco
7th January 2015, 18:17
there are multiply ways to do this
option 1 (low quality):
load the icm in windows color management. (there is a well known bug in windows where calibrations are not loaded at all the work around is a different program or run the windows calibration program 1 time picture (http://abload.de/img/windowsbugqgu33.png)(just press next and down't change anything))
in madVR:
set calibration to: "this display is already calibrated"
don't check "disable GPU gamma ramps"
optional set color & gamma to pure power curve 2.4.

option 2 /high quality): create a 3d lut from the icm and load it with madVR.
set madVR to "calibrate this display by using external 3DLUT files"
load the file in bt 709.
check "disable GPU gamma ramps"

i crated two 3d lut from the icm file samsung_s24d590pl.icm for you: http://www.file-upload.net/download-10107027/3d-lut.7z.html

i can't check them because i don't have that screen.

one is bt 709 gamma 2.2 an old standard the other one is a bt 1886 3d LUT the new way to do it.

Thank you. I followed "option 2" instructions and it looks like everything is ok(at least, colors are not broken). Btw, how to use "bt 1886 3d LUT"?
http://ipic.su/img/img7/tn/madvr3.1420650615.png (http://ipic.su/img/img7/fs/madvr3.1420650615.png)

huhn
7th January 2015, 18:42
Thank you. I followed "option 2" instructions and it looks like everything is ok(at least, colors are not broken). Btw, how to use "bt 1886 3d LUT"?
http://ipic.su/img/img7/tn/madvr3.1420650615.png (http://ipic.su/img/img7/fs/madvr3.1420650615.png)
you load it like a bt 709 3d LUt

bt 1886 is a different gamma the gamut is still bt 709.

MysteryX
7th January 2015, 20:30
I'm jus thinking about something. Why do the video profiles have to be configured manually? Thinking about it, it could be auto-configured pretty easily.

Let's say I'm running with SVP and madVR has 16.6ms to render each frame. What I would manually do is open each resolution of video (288p, 360p, 480p, 720p, 1080p) in Widescreen, press CTRL+J and create a profile that brings the rendering time as close to 16.6ms as possible.

madVR could do these tests and build these profiles itself.

or... perhaps even better, it could try various settings until it gets close to its maximum allowed rendering time, and cache these results. If there are dropped frames, it would automatically lower the settings, if rendering time gets lower, it would automatically higher the settings.

Is something like this in the road-map?

ikarad
7th January 2015, 22:18
I think the old fullscreen exclusive mode should in theory work with G-Sync but I couldn't get the old FSE to work with my GTX 970 and latest drivers. Might give it another try when I get the chance.

Why old? It's the also the current fullscreen exclusive mode.

ikarad
7th January 2015, 22:21
This article (http://www.hardware.fr/news/14025/ces-amd-freesync-presque-la-point.html), which unfortunately is in French, contains the following information, which I'm translating:



The last bit about video playback is quite interesting, maybe it could apply to madVR as well if madshi decides to support it.

Madvr support since long time fullscreen exclusive mode, then gsync must be compatible.
http://img15.hostingpics.net/thumbs/mini_413262Sanstitre.jpg (http://www.hostingpics.net/viewer.php?id=413262Sanstitre.jpg)

e-t172
7th January 2015, 22:48
Why old? It's the also the current fullscreen exclusive mode.
Madvr support since long time fullscreen exclusive mode, then gsync must be compatible.

No. Fullscreen exclusive mode is a necessary condition, not a sufficient one. My understanding is that madVR's new presentation path cannot make use of G-Sync/FreeSync because it has no way of telling the display when to display a specific frame (the frames presented in advance are simply displayed at the display's nominal refresh rate). I guess maybe it could work with the old path, but since madVR relies on VSync information which is made meaningless in this scenario, I would be surprised if it did.

Most likely madVR needs to be made G-Sync/FreeSync aware for this to work. In the past madshi said he had no intention on working on this. Maybe he will change his mind considering that's where the PC monitor market seems to be heading full steam.

kalston
7th January 2015, 23:09
There are two fullscreen exclusive modes in madVR, just like there are two different windowed modes.

I recall the old fullscreen mode being like the regular windowed mode, so a 24fps film would send 24 fps to the display (as reported by fraps), regardless of your monitor refresh rate, while the new presentation mode will send a number of frames corresponding to whatever your refresh rate is - and thus g-sync can't really do anything but run at the max refresh rate.

That is what I was referring to. But yes I'm not entirely sure it would work either.

Zachs
7th January 2015, 23:13
Does anyone have any programming documentations in regards to G-sync / freesync? In particular, I'm looking for a way to automatically detect if it's enabled, and what its lower limit is (30Hz at the moment for both I was told, but I'd hate to hardcode that into a player).

Asmodian
8th January 2015, 04:33
There are two fullscreen exclusive modes in madVR, just like there are two different windowed modes.

I recall the old fullscreen mode being like the regular windowed mode, so a 24fps film would send 24 fps to the display (as reported by fraps), regardless of your monitor refresh rate, while the new presentation mode will send a number of frames corresponding to whatever your refresh rate is - and thus g-sync can't really do anything but run at the max refresh rate.

That is what I was referring to. But yes I'm not entirely sure it would work either.

Testing both FSE modes they seem to behave the same with regard to G-sync, lots of flickering and Fraps reports ~143.5 Hz not 24 Hz in both modes. 24 Hz is too slow for G-sync anyway, even if madVR did send it.

Interestingly MPDN does not flicker when using G-sync with any of its D3D modes (9, 10, or 11).

Vyral
8th January 2015, 09:40
there are multiply ways to do this
option 1 (low quality):
load the icm in windows color management. (there is a well known bug in windows where calibrations are not loaded at all the work around is a different program or run the windows calibration program 1 time picture (http://abload.de/img/windowsbugqgu33.png)(just press next and down't change anything))
in madVR:
set calibration to: "this display is already calibrated"
don't check "disable GPU gamma ramps"
optional set color & gamma to pure power curve 2.4.

option 2 /high quality): create a 3d lut from the icm and load it with madVR.
set madVR to "calibrate this display by using external 3DLUT files"
load the file in bt 709.
check "disable GPU gamma ramps"

i crated two 3d lut from the icm file samsung_s24d590pl.icm for you: http://www.file-upload.net/download-10107027/3d-lut.7z.html

i can't check them because i don't have that screen.

one is bt 709 gamma 2.2 an old standard the other one is a bt 1886 3d LUT the new way to do it.

I've the icm profile for my monitor thanks to the manufacturer's drivers. I think it's calibrated for BT.709.

I want to create a BT.1886 3D LUT, should I follow this tutorial (http://www.avsforum.com/forum/139-display-calibration/1471169-madvr-argyllcms.html) to create it ?
I just have to start from part 4 and change the source profile in part 5.2 for my icm profile, the output encoding to 0-255 and the gamma mapping to 2.25 absolute in part 5.5. Then load the new 3D LUT in BT.709 in madVR, right ?

Thanks for your help.

huhn
8th January 2015, 09:54
I've the icm profile for my monitor thanks to the manufacturer's drivers. I think it's calibrated for BT.709.

I want to create a BT.1886 3D LUT, should I follow this tutorial (http://www.avsforum.com/forum/139-display-calibration/1471169-madvr-argyllcms.html) to create it ?
I just have to start from part 4 and change the source profile in part 5.2 for my icm profile, the output encoding to 0-255 and the gamma mapping to 2.25 absolute in part 5.5. Then load the new 3D LUT in BT.709 in madVR, right ?

Thanks for your help.

you need to set your ICM file as target.

and you have to leave output at 16-235 madVR thinks every 3d lut is 16-235. dispcalgui 2.6 shouldn't even give you an option to change this any more.

if you want to use bt 1886 leave gamma at 2.4.

gamma should be changed based on your room lightning. "correct" is 2.2 and for dark rooms 2.4 is recommended. bt 1886 is very complicated just leave it at 2.4. not sure if your ICM has any information for your black point so not sure if it has any effect or just results in gamma 2.4.

and yes you add it in bt 709 and don't forget to check disable GPU gamma ramp.

madshi
8th January 2015, 13:10
I've had an issue for awhile now where I will play a video in FSE mode and the render time will settle down to say, 30ms for 720p->1080p NNEDI3 upscaling. Then I'll back out to windowed mode and back into FSE and the render time will drop down to a steady 25ms. I'm not sure what's happening but I can reproduce this consistently. I have my gpu overclocked and it's almost like madVR isn't accepting the overclock in FSE even though Afterburner says it's using 1050 core the entire time.
madVR is not even aware of whether the GPU is overclocked or not, let alone control it in any way. This is all outside of madVR's control.

Now it works well with HCFR.
Good to hear!

Is it normal for the Nvidia Control Panel settings like deinterlace etc to have no effect on the image when using madvr?
NVidia deinterlacing settings only have an effect if DXVA deinterlacing is used (maybe also for CUVID deinterlacing, I don't know). The other GPU control panel options may or may not have an affect if DXVA deinterlacing or DXVA scaling is used, but they won't have an effect otherwise.

Hi Madshi, the problem seemed to start with 0.87.11 - it was not present in 0.87.10.

The problem is when I am using a second display (e.g. my Samsung UE40H6400 TV, via HDMI, and an AMD HD7790 GPU). I can force film mode on the primary display, but not when the MPC-HC window is on the secondary display. When I toggle through modes, it just goes through auto and video, and skips film.
Could you please double check by going back to v0.87.10 that the problem was indeed introduced exactly by v0.87.11? The reason I'm asking you to do that is that none of the changes in v0.87.11 should affect film mode in any way. I rather think that the problem was introduced by some other change. Maybe you're using native DXVA decoding now? Film mode only works with software decoding (or DXVA copyback).

It would be interesting to have madVR be G-sync (or FreeSync) aware, it seems like it would be possible to have the audio and video sync be very exact without smooth motion, basically like Reclock but adjusting the video frame timing instead of re-sampling the audio. This would also be great for bit-streaming without smooth motion.
If only I could tell FreeSync in advance which frame to present when. But I don't think it works like that. Basically in order to use FreeSync, I would have to present each video frame exactly at the right time, which means fluidity would depend on how reliably madVR gets CPU time from the task scheduler. IMHO that would be a step backwards. Windows is not a real time OS.

madshi
8th January 2015, 13:16
madVR v0.87.13 released

http://madshi.net/madVR.zip

* madTPG: added "madVR_Find" API
* madTPG: fixed "madVR_GetVersion" API
* added OSD API stretch option
Once again only API changes. For your interest, all these recent changes are made to improve support for Calman, DVBViewer and one more application (not XBMC/Kodi, don't get your hopes up), which are all in the process of adding/improving support for madVR.

XinHong
8th January 2015, 21:27
I didn't know that DVBViewer was able to use madVR

Plutotype
8th January 2015, 22:39
Madshi, any chance to ask Light Illusion to include remote madtpg control as you have done with Calman please?

Thanks

mzso
8th January 2015, 22:57
I didn't know that DVBViewer was able to use madVR

Maybe not yet?

madshi
8th January 2015, 23:44
I didn't know that DVBViewer was able to use madVR
The official version doesn't support it yet, but it's currently being developed. The DVBViewer dev already posted in the forums that the next official version will support madVR.

Madshi, any chance to ask Light Illusion to include remote madtpg control as you have done with Calman please?
;)

StinDaWg
9th January 2015, 10:58
madVR is not even aware of whether the GPU is overclocked or not, let alone control it in any way. This is all outside of madVR's control.
So you can't replicate madVR lowering render time after exiting out of, and then back into fullscreen?

Mano
9th January 2015, 14:35
Is it just me or when i open a 1080p clip with bit rate higher than 3mbps there will be a 2s lag like this? https://www.youtube.com/watch?v=w_H2T6ZaJfo

I show up my madvr setting in the end of the clip. Is that problem with my pc spec or hdd or just madvr nature?

huhn
9th January 2015, 15:19
is EVR CP opening a file a lot faster for you?

could be your HDD, DXVA decoding (DXVA AMD is pretty slow...) or something else.

Mano
9th January 2015, 16:26
EVR CP improved it somehow but i still feel it is a bit slow. and yes i am using AMD card

https://www.youtube.com/watch?v=9qvweN_uFmU

huhn
9th January 2015, 16:35
the difference is about 0-3 frames.

try disabling DXVA decoding.

but this looks more like it has to do with your HDD. but is this really an issue?

Mano
9th January 2015, 16:49
how do i disable DXVA? did you see there is a noticeable jagging/lag/shutter at the beginning with madvr? i just got a bsod open that video the first time which i havent got for like a years.

also i just checked playing it on my ssd drive. the jagging/lag/shutter is still present.

huhn
9th January 2015, 18:33
this should do the trick: http://abload.de/img/dxva1mujm.png

i don't get problems opening a BD with 37+ mbit.
but i have more than decent hardware.

a8213711
9th January 2015, 19:12
i25 should be the same as i50, which most TVs do support. But I would stay away from anything interlaced unless oyu have no other choice.


Sorry, do you mean away from interlaced source or output?




Also I have a weird behaviour I just noticed:
I have in MadVR http://i58.tinypic.com/dqr89e.jpg and when I start a .wtv with 25fps I get display at 59.9Hz, then I press alt+tab to go on Windows Media Center (Win8.1) and then again alt+tab on MPC-HC and this time I get display at 50Hz and the image is more saturated.
What should I do?

Mano
9th January 2015, 19:27
thanks, seem like disable DXVA did the trick.

huhn
9th January 2015, 19:32
can you make a screen with the different saturations plus OSD?
are you using an intel IGPU ?

iSunrise
9th January 2015, 20:21
I'm jus thinking about something. Why do the video profiles have to be configured manually? Thinking about it, it could be auto-configured pretty easily.

Let's say I'm running with SVP and madVR has 16.6ms to render each frame. What I would manually do is open each resolution of video (288p, 360p, 480p, 720p, 1080p) in Widescreen, press CTRL+J and create a profile that brings the rendering time as close to 16.6ms as possible.

madVR could do these tests and build these profiles itself.

or... perhaps even better, it could try various settings until it gets close to its maximum allowed rendering time, and cache these results. If there are dropped frames, it would automatically lower the settings, if rendering time gets lower, it would automatically higher the settings.

Is something like this in the road-map?
Pretty cool idea, however, since there is not only resolution and refresh rate of the source that needs to be taken into account, but also your current refresh rate of your monitor, interlaced/progressive and finally your madVR settings, this can get a mess pretty fast, especially since madVR should work in realtime.

What would probably work is that the user had some kind of offline tool that replicates madVRs functionality and settings 100% and calculates a "automatic_profile.mvr", where the actual madVR renderer then can read that profile and you would have your perfect settings for your current config.

If you change the graphics card, output resolution or other stuff, you would just do that again, so you would have different automatic_profiles.

"Advanced mode" would enable you to access all power features manually, like it is right now.

That would certainly make some users happy, others would still prefer to have manual access at all time, so I'm not sure if the time invested in this is worth it. I guess that most people that use madVR are kinda advanced users and know what they are doing, but it would certainly make your first steps easier.

iSunrise
9th January 2015, 20:47
Does anyone have any programming documentations in regards to G-sync / freesync? In particular, I'm looking for a way to automatically detect if it's enabled, and what its lower limit is (30Hz at the moment for both I was told, but I'd hate to hardcode that into a player).
No programming guide, unfortunately.

However:
http://img.24liveblog.com/2014/11/20/1416475443498526.jpg

It seems that not only is FreeSync more flexible, but according to various CES articles, the first FreeSync monitors are limited to 40Hz at the minimum, or else they will flicker. Not sure if that's because of the pixel matrix / panel driver firmware that just isn't able to go lower, but that's the only info that I came across. More in-depth stuff seems to be still rare.

At least theoretically, 9-240Hz seems to be perfect for our needs.

e-t172
9th January 2015, 21:03
The problem madshi was referring to, I believe, is the lack of explicit G/FreeSync support in APIs (i.e. Direct3D). Frame presentation APIs were never designed with variable refresh rate in mind, and it's not clear how they can be used to achieve precise and arbitrary (custom) timing of frame presentation. It seems the only known way to do this right now is to "pretend to be slow", i.e. behave like a game that can't keep up, but madshi seems to be reluctant to go this way for various (valid) technical reasons.

In that way, I see the fact that recent Windows versions seem to explictly use G/FreeSync for video playback as a good sign, because that might mean that such APIs (or some form of clarifying documentation) are about to be released.

nevcairiel
9th January 2015, 22:14
However:
http://img.24liveblog.com/2014/11/20/1416475443498526.jpg

It seems that not only is FreeSync more flexible, but according to various CES articles, the first FreeSync monitors are limited to 40Hz at the minimum, or else they will flicker. Not sure if that's because of the pixel matrix / panel driver firmware that just isn't able to go lower, but that's the only info that I came across. More in-depth stuff seems to be still rare.


Its an AMD slide, what are you going to expect. :p

The reason for the minimal refresh rate is that the screen doesn't actually redraw a frame when no new frame comes in, and the old frame then "decays", which depending on screen allows a minimum of 30 to 40 fps.
Of course a theoretical upper limit of 240 fps is also just a paper stat, since we have no screens for that, and for higher resolutions we're also bandwidth limited on DP.

GSYNC has its own advantages over FreeSync that AMD is of course not going to mention. For video playback not necessarily important, but AMD doesn't have a framerate limiter when FreeSync is active, which causes tearing when your 3D application/game renders faster than the maximum screen refresh. Apparently this is even a design decision on AMDs side and not just a missing feature.

And the fact that its limited to like 2 AMD GPUs and no released screens .. well, we'll see. NVIDIA could always implement FreeSync if the market goes that way, but AMD will never implement GSYNC, so NVIDIA is somewhat in a better position here. ;)

6233638
10th January 2015, 07:23
While it has yet to be confirmed, I've seen talk that Adaptive Sync/FreeSync may have two frames of latency just like V-Sync, while G-Sync is polled at 1000Hz for a fixed overhead of 1ms.
And with G-Sync being separate hardware, it guarantees that you have the lowest latency possible. Being able to work with the display's existing processing seems detrimental from a gaming perspective.

But Adaptive Sync actually has a chance (though slim) of ending up in televisions rather than just being a thing for PC gaming monitors.
I'd prefer that NVIDIA gave us the choice of using G-Sync or Adaptive Sync displays. If G-Sync is better, surely that is what users will buy.
If Adaptive Sync is equally good at a lower price, that's good for everyone. It's not like NVIDIA is in the business of selling displays.

a8213711
10th January 2015, 13:27
can you make a screen with the different saturations plus OSD?
are you using an intel IGPU ?

I just realized that in screenshots I can't see any difference in saturation, therefore it must be my Samsung television's fault, and I don't know how to fix it.
I'm using an AMD APU.

huhn
10th January 2015, 14:05
I just realized that in screenshots I can't see any difference in saturation, therefore it must be my Samsung television's fault, and I don't know how to fix it.
I'm using an AMD APU.

did you used print screen?

and is your TV using PC mode there is a huge change your TV can't do PC mode in any other refresh rate than 60 hz (most samsung can't do this for what ever reason)so this may trigger the issue with the saturation. and if this is the case and you want to use PC mode think about 60 HZ only and smooth madVR motion.

James Freeman
10th January 2015, 14:06
NVIDIA news

Driver 347.09
Color Range has been fixed with HDMI/DP connections, RGB Mode and YCbCr444 mode as well as 16-255 Limited Range and 0-255 Full Range options is finally available.

Yes! there is an option in the "Adjust Desktop Color Setting" menu for Limited and Full ranges.

How cool is that?
Took'em 10 years but still.... thanks.

I'll test and return in a few moments.


EDIT:

IT WORKS!!!
No restarts, no registry hacks, no nothing! Just works in a second.
http://www.mediafire.com/convkey/0148/s9z8zm983xe7rnjzg.jpg

khanmein
10th January 2015, 14:09
anyone please kindly help how to fixed the error? thanks. guys did u noticed when open mpc got some delay? around 2-3 sec

http://www54.zippyshare.com/v/27530580/file.html