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

QBhd
17th April 2020, 00:15
Yeah that's odd... somehow CRU was reset or set back to default. You should be okay if you just delete those standard resolutions again, okay out of CRU, Reboot, and all should be back. No need to redo everything. I just tested this today for $hit$ and giggles.

QB

EDIT: there was a Windows update this week... I am willong to bet that might be your culprit.

mclingo
17th April 2020, 00:22
Thanks but I wiped it all and re did it, will try that if it recurs.

SirMaster
17th April 2020, 04:31
Play a 23 Hz file for at least 10 minutes and create with CRU a custom resolution using a calculated one in madvr

I am not sure what to do here when I try entering the numbers that madVR calculated it wont let me save it.

https://imgur.com/2rfIL6m

Klaus1189
17th April 2020, 07:17
Never had issues with it. Are you probably using the resolution you want to do custom timings with? It is the only thing I can think of for now.

Cowboydude99
17th April 2020, 12:37
Thanks for the info on upscaling.

My gpu is Gtx 1080.

I’m running my gpu at 60hz. If I drop it to 24, I get horribly visible stutter/judder.

I can’t use RGB full at 60hz

How do you get hdr with wcg? 4:2:2 limited?

My projector has an Extended option.

I’m shooting for best image in movies. HDR WCG BT2020

mclingo
17th April 2020, 13:32
I am not sure what to do here when I try entering the numbers that madVR calculated it wont let me save it.

https://imgur.com/2rfIL6m

should you not be creating your custom resolution in your GPU contol panel not in CRU utility?, I just looked at mine and there are no 4k resolution in there now which is correct, I just used that to delete out all the 4k resolutions.

mclingo
17th April 2020, 14:22
to be honest thought mate i'm close to giving up on this myself, best I can get is about 1.55 hours no matter what I do, I thought it was several hours but once it settled it was stuck on that:

https://1drv.ms/u/s!AgvFafeelEBik6hBuPVDU9z4um3VEw?e=9rngJw

If I try optimize and select one of the others and click apply nothing changes even if I reboot, measured always says 1.55 hours. However i'm trying something different now. I'm trying this.

1. Delete custom res in MADVR
2. Open CRU utility and delete all 2160p resolutions in both TV resolutions and HDMI support in the extension blocks section
3. Reboot
4. create brand new custom res in MADVR using some of the timings you gathered from previous attemp, i'm going to use those in my screen shot that clock at 4.71 days.
5. Reboot
6. play movie for 30 mins.

Will report back shortly, if this works i'll probs write up some proper instructions, if it doesnt I'm probably going to dump this card at some point and re purchase my trusty MSI nitro x RX580.

SirMaster
17th April 2020, 14:31
Yeah I really do wish there were better instructions to follow.

I can't figure this out at all for some reason.

I just tried following all the instructions. I just created the custom res in nVidia control panel with the timings from madVR after optimize and it isn't making any change to my dropped frames. I am still at the same 4.40 minutes per dropped frame.

I don't want to give up on this but I can't see what I am missing.

SirMaster
17th April 2020, 14:37
Never had issues with it. Are you probably using the resolution you want to do custom timings with? It is the only thing I can think of for now.

I just tried switching resolutions to make sure I am not in the resolution I am trying to create and still the horizontal front porch value is red preventing me from clicking OK.

mclingo
17th April 2020, 14:46
I tried my method as stated, no joy so I tried putting those exact figures into AMD control panel, stated my display would was not compatible.

@Sirmaster - are you adding this to your TV resolutions or HDMI Support in the CRU utility?

SirMaster
17th April 2020, 14:56
I tried my method as stated, no joy so I tried putting those exact figures into AMD control panel, stated my display would was not compatible.

@Sirmaster - are you adding this to your TV resolutions or HDMI Support in the CRU utility?

I am clicking this Add button.

https://imgur.com/pAh5CT0

mclingo
17th April 2020, 15:32
i'm starting to think nobody really knows exactly whats going on with these issues, everyone knows a little bit, some a lot more than others but I think there must be a fundamental misunderstanding about how MADVR and windows works with custom modes as nothing seems to work as it should beyond those initial figures I was given here which gives me 1.55 hours, If change the totals even by one point it drops to something horrible like one frame drop every 6 seconds or 1.5 mins.

There must be a better way to do this apart from guess what these figures should be but I also think MADVR custom modes doesnt work properly either as whenever I create on in there is does nothing at all and i cant get optimize to work at all.


i'll have one last go how you are doing it to see if that gets me the timings I want.

oldpainlesskodi
17th April 2020, 16:27
Sorry that I can't offer any further assistance on this mate - I'm still baffled why you need custom timings with AMD (with the 5700xt) , as I and others have said, it's rock solid stable.

mrmojo666
17th April 2020, 16:52
Sorry that I can't offer any further assistance on this mate - I'm still baffled why you need custom timings with AMD (with the 5700xt) , as I and others have said, it's rock solid stable.

i would say the same here with old rx460. in the past i had some timing problems, but they was becasue i was using two hdmis: one 2.0 to the tv for the video e one 1.3 to the AVr for the audio..... the day i bought my marantz hdmi2.0 AVR and started to use single hdmi all timing issues have gone

hannes69
17th April 2020, 16:55
Ok, some general ideas concerning custom resolutions:
Normally, madVRīs solution should work. But: Some time has passed since madshi released a new madVR version (beside the HDR betas), so in the meantime there could have developed some problems either with GPU drivers or at OS level.
MadVR calculates custom resolutions based on given timings (either EDID ones or your personally entered ones in the driverīs custom resolution section or in CRU.
If the madVR routine doesnīt work, either the driver is rejecting the suggested resolution or the display doesnīt accept/work with the given resolution or there are unsolved problems with the different GPU communication interfaces between madVR and the GPU drivers.
So: if madVRīs routine doesnīt work, the next attempt is to use the driver routine fpr custom resolutions. I personally only know the one in AMD drivers, but they all should work in a similar way.
You have simply to enter the give numbers of madVR in the custom resolution section of your GPU driver.
There you should have feedback (error, warning) when your entered numbers arenīt accepted.
If this way doesnīt work, then as a last resort you can try CRU.
There you can delete all the given resolutions and implement new ones with the numbers of madVR.

The normal behaviour is like that: You connect a display device to your computer and the device tells by EDID to the computer, which resolutions are supported and the according timings.
The driver GPU driver now knows them and implements the according resolutions and framerates at OS level.
Now youīre using this resolution and madVR measures it. Then madVR uses a interface to the GPU driver by which new custom resolutions are implemented. Thatīs the same way like entering numbers in the custom resolution section in your GPU driver, itīs only a sort of automation so you donīt have to do that manually. These interfaces can be broken or madVRīs code could have to be updated.
You can create new custom resolutions this way or you can use an already given resolution by EDID (combination of resolution + refresh rate). If using an already given set, this one gets an override by your custom one. So when everything is working as expected, there is no need to remove the EDID ones.
If these two ways donīt work, then I would say there is a problem on the OS side or a driver failure. Either a defective setup or errors in the driver or OS implementation.

CRU as last way overrides the given EDID of your display devices so it simulates that your display device is asking for the custom resolutions you want and not the given EDID standard ones.
If this doesnīt work out as well, then you maybe you are a victim of faulty drivers or some OS quirk. You can try to make a fresh install of OS or remove updates or try older drivers or... Maybe you should then accept the different approach of smoothmotion with a samll loss in image quality (most of the people wonīt even notice).

I would say: Sometimes OS or GPU drivers are faulty, often teh display devices are picky with custom resolutions, very often the end user is incapable for the given task.
But homecinema is a matter of tinkering, learning, big efforts, investing bigger parts of your freetime, so it should be possible in the end.

I wonīt deliver step by step instructions or even a youtube video. All the info is there in the net, madshi wrote a small guide, link given above, everything was explained many times. In the internet you find the necessary info.
There is no need to copy 1000 times always the same info and block server space with nothing new.
Many here expect personal assistance and are incapable or not willing to answer the most simple questions.
In very rare cases someone runs into a very special setup and a special problem. Most of the time we have standard cases with standard solutions. You have to take your time and have to work in structured manner. And rule out one error or possibility after another until the solution rests.
Most of the time there are reports and whinings like "I tried everything. Iīve done the same procedure now 10 times, always the same result. Iīll soon give up, please help me." Then some people chime in and are willing to help. Thereīs assistance and there are often specific questions. All of that is very often completely ignored. What do some people expect from a forum? Personal training and that other people offer solutions for personal problems and during the way no cooperation? No. You canīt expect help in a forum while not taking part in the process in a useful manner and in a manner demanded by the ones that help.

E.g. I gave the hint that you can prove if a custom resolution of madVR is applicated and where you can lookup the info. In the meantime there are more reports in the manner "Always the same drop time, regardless of what Iīm doing". You have to narrow down the problem. We all now know that you always have the same drop time, nothing new, even when 1000 more times reported. Is the madVR custom resolution accepted in the GPU driver - YES/NO. Then you can move on to the next step.
I am willing to help out, definetely, but not in this unstructured manner and when Iīm really mad I would say in this ignorant manner.
Sorry for being harsh, itīs not intended to be rude, but sometimes, you know, itīs time to say some 'truth'.

I just tried switching resolutions to make sure I am not in the resolution I am trying to create and still the horizontal front porch value is red preventing me from clicking OK.
Seems like CRU thinks that a limit is exceeded so it is colored red.
You can try to balance the porches. Leave the sync width alone, substract an amount from front porch (e.g -200) and add the same amount (+200 here) to back porch. The total number must stay the same.

QBhd
17th April 2020, 16:59
With the Optimize in madVR you select one of the "no frame drops/repeats" timings... hit apply... and reboot. Now sometimes it maybe rejected, so just move to another until you find one that is accepted. Most of the time this is linked to the pixel clock, if one has too high of a pixel clock it will more than likely be rejected (much higher than 300 MHz is usually the ceiling I found, sometimes I could go a little over, but not by much). And if none of the "optimized pixel clocks" work, use the best "same pixel clock" and try again.

Also know this... As you get closer and closer to the goal, you need longer and longer playback times to see the difference. Also be very sure that you have not paused or skipped playback. I find the best is to sit and watch a movie from beginning to end without touching the remote.

QB

mclingo
17th April 2020, 17:15
ok, so i followed the advice to the letter and got everything dialled in. I wasnt getting 3 hours as I first thought but more like 1.55 hours. Do i tried to tweak some of the totals in AMD control panel custom res but this just resulted in either black screen or much worse timings so I gave up on that.

the the next bit of advice was to create a custom res using the timings MADVR had already worked out, so I did, matched it exactly and guess what I got instead of 4.71 days.

30 mins.

https://1drv.ms/u/s!AgvFafeelEBik6hCmOie-2txaBfikQ?e=dbPjCB

Could be MADVR being very old just isnt optimised for the RX5700 series cards and those who arent having issues are just lucky, or i'm just unlucky.


Whats worse is I cant now get back to 1.55 hours at all, where's my hammer...

mclingo
17th April 2020, 17:24
And just to really do my head in I decided to wipe all customs and then reset using CRU so my card was back to default driver and res settings,.. I'm now showing hors /days without drops like I normally do. Either this is another fluke or my card from the beginning had a corrupt set of resolutions setup.

Now down to 12 hours after 19 mins of playback. I'll give it 39 mins, reboot and see if this was a fluke.

nussman
17th April 2020, 17:42
For AMD users default settings without CRU or custom timings should be fine.
I am pretty sure you dont even recognize some random frame drops while watching a movie. Reset madVR stats after starting your film, relax and recheck after the movie how many frames are actually dropped.

mclingo
17th April 2020, 17:58
we wouldnt be bothering to discuss this if we didnt care about frame drops mate, anything above zero per movie is unacceptable to me, yes they do actually drop.

I'm now getting 11 hours with default settings and i havent a clue why :)

https://1drv.ms/u/s!AgvFafeelEBik6hECHVa1BfmWYvZgQ?e=dog7ss

el Filou
17th April 2020, 18:12
I am pretty sure you dont even recognize some random frame drops while watching a movie. Reset madVR stats after starting your film, relax and recheck after the movie how many frames are actually dropped.It really depends on the sort of movie/scene. If a drop happens during a static scene where a character is just talking you might miss it by chance, but if it's when the camera or a character is moving it's really noticeable.

SirMaster
17th April 2020, 19:14
Seems like CRU thinks that a limit is exceeded so it is colored red.
You can try to balance the porches. Leave the sync width alone, substract an amount from front porch (e.g -200) and add the same amount (+200 here) to back porch. The total number must stay the same.

Thanks.

I was able to subtract 300 from the front and add to the back and it let me create it. I rebooted and switched to it, but I am still seeing the same 4.40 minutes per frame drop. This is the drop time I have always seen no matter if I do the custom mode through madVR, or nVidia control panel, or now CRU.


Is the madVR custom resolution accepted in the GPU driver - YES/NO.

I feel like I am not sure how to know the answer to this question. When I press the Test Mode button on madVR custom res it says that the mode was accepted, so I think the answer is yes.

But then I reboot to make sure it's applied, and I switch to the mode and then check the playback stats in the overlay and the dropped frames still goes right to 4.40 minutes same as before the optimization.

It says my current timings have no frame drops / repeats expected and all the timing numbers match the optimized pixel clock #1 but yet it seems to make no change to my actual dropped frames.

I made sure to leave a movie playing for over 30 minutes without interruption, and I reset everything (deleted all the resolutions) and tried again with the same results after a 30+ min measurement period.

https://imgur.com/tRfPXCT

QBhd
17th April 2020, 20:09
Again this sounds like "standard timings" overriding any custom timings. The EDID is sometimes a real pain in the butt. First thing I would do, delete all custom resolutions in the driver, run the reset-all.exe in the CRU folder, and reboot... then in madVR delete any display "identification" that is greyed out (these get created when you make changes to the EDID with CRU)… this should revert everything back to default/out of the box settings.

QB

Cowboydude99
17th April 2020, 20:35
Hi everyone,
I've been trying to get my set up to work properly, but not having much luck.

Hoping you can help me a bit further, but maybe in a different way.

My goal is to get smooth video with HDR BT2020.

24hz refresh rate plays 24p terribly. I have to increase it to 60hz and use MadVR's smooth motion.

Can I use RGB 8bit Full in Windows, and have something done in MadVR to output 10bit properly?

When I try to output 4K/60 at 4:2:2 10 bit, I get some very weird green lines running on the screen. This doesn't happen every time, but often enough that if I stop a movie, it happens, or if I play a movie where the system changes to HDR. It's not always HDR, but it looks like when the system tries to set color using 4:2:0, 4:2:2 or 4:4:4...

So I'm hoping that I can set RGB 8bit, and have MadVR output 10bit. This goes against what I'm thinking, but someone pointed out maybe that is an option.

This would give me smooth video at 60hz (24p).

PS- I tried the studio drivers and the same things happen (green and magenta screens).

mrmojo666
17th April 2020, 20:55
we wouldnt be bothering to discuss this if we didnt care about frame drops mate, anything above zero per movie is unacceptable to me, yes they do actually drop.

I'm now getting 11 hours with default settings and i havent a clue why :)

https://1drv.ms/u/s!AgvFafeelEBik6hECHVa1BfmWYvZgQ?e=dog7ss

i do not have a 5700, but on my system as repoted before, no famedrops at all , never feel to have to use cru or other thing like that.

QBhd
17th April 2020, 20:58
If you have read just a little bit of this, you would know that not even setups with very similar hardware behave the same. So talk like above is actually less than helpful.

QB

nussman
17th April 2020, 21:15
anything above zero per movie is unacceptable to me, yes they do actually drop.

Then use reclock or a player/audiorender with similar technic.
Without "on the fly sync" you can get close but it wont get perfect anyway (imho no videoplayer with bitstream audio output can do that).

On all AMD systems (default driver settings) I have seen the frame drop/repeat stats in madVR always vary a little bit at the beginning and then growing to hours or even days.

If you get 1-2 framedrop every 1,5h movie you have a good chance to miss it. I know it depends on scene/movie etc. but I would like to see a blind test for this. ;)

And if you get 30-50 framedrops every movie there might be different problem with your system, videofile, videoplayer or directshow filter?

On the other site, setting up custom timings is not an easy task and there is a good chance to make things even worse (i.e. like you did before reset to driver defaults).

Back in the old days these problems were much bigger.
No madVR, no hdmi, but WinXP with VMR7/9 videorenderer and spdif output with frame drops/repeats every minute (and thats really annoying because you are waiting then for the next jitter).

Afaik on Intel/Nvidia the default timings are a little bit worse. So custom timings are might worth it.

SirMaster
17th April 2020, 21:56
Afaik on Intel/Nvidia the default timings are a little bit worse. So custom timings are might worth it.

I think that's an understatement. Stock nVida timings are a frame drop every 4-5 min and very noticeable.

I am not giving up bistream for this as I would lose Atmos and DTS:X on the 7.1.4 system. Like 80%+ of UHD movies are Atmos/DTS:X these days and pretty much every new release.

lazostat
17th April 2020, 22:01
Guys i have a question about duplicate screen and Madvr. Why force switch display mode doesn't work when i use duplicate screen? (Pc and TV). It works only if i make my Tv main monitor. Otherwise it goes on 60Hz, like my Pc monitor is. So everytime before i watch a movie, i have to change display shown only on TV. Then when i open the movie with WMPC and go full screen, it auto-changes the Hz according to the movie's.

Also, sometimes when i have duplicate screen, i have lags, and i don't know why. My system is good with 3600+2070 super combo.Can someone help me pls?

nussman
17th April 2020, 23:34
Maybe because your PC Monitor does not support 24p?

Asmodian
18th April 2020, 00:23
When using the duplicate option you can only use modes both displays support.

hannes69
18th April 2020, 01:13
I feel like I am not sure how to know the answer to this question. When I press the Test Mode button on madVR custom res it says that the mode was accepted, so I think the answer is yes.
Ok.
Iīm on AMD and I donīt know the according section in nvidia control panel - if it exists.
In AMD Radeon settings there is a section where you can lookup the current timings being used - all porches, refresh rate, pixel clock, polarity and so on like in CRU or in madVR.
I mentioned this approach to rule out some possible problems on madVRīs side.
The second possibility to check this is madVR itself of course.
MadVR has the line "current timings". So you let madVR optimize your refresh rate, apply it, note it (screenshot or pen+paper), reboot, enter madVR and check now the "current timings".
In my case the behaviour is like expected: I use a certain custom resolution. I look up the current timings in madVR and in the AMD Radeon section - they are the same. Then I edit this custom resolution within AMD Radeon settings. The corresponding values in Radeon settings showing the current applied timings are updated without reboot and show the values from the custom resolution (which is applied instantly without reboot as well). When now opening madVR the line "current timings" now corresponds to the custom resolutionīs change, so everything is lined up correctly.
MadVR interacts with the driver in both directions: One possibility is to send custom resolution timing parameters to the driver which implements it (or rejects it if the mode is not accepted by the driver or the display). The other way round, madVR requests from the driver the currently used timings and shows them.
This communication is realized by specific interfaces with AMD nvidia and intel. They may be broken in the context of driver updates. As a consequence madVR may sometimes not be able to apply custom resolutions or request the current timings.

You can test this interface by e.g. implementing a new refresh rate through madVR. E.g. create a custom resolution through madVR for a refresh rate you havenīt implemented yet and which doesnīt exist on the OS side.
Implement it. When it shows up (maybe after reboot) in the OS, the interface is intact, if it doesnīt show up you know itīs broken. You can choose e.g. 26 Hz (a normally not used one) and by this way you can rule out the possibility that it is maybe overwritten by the driver or OS (EDID quirks).

The crucial point is to find out, which timings are actually used.
The driver has control over that and at least AMD shows them. Would be a pity if nvidia or intel donīt offer this info.
On the other side I would say, normally I would trust madshi. When he delivers numbers for "current timings" then it is to assume that these values are actually requested from the drivers, and if this fails, that there is not shown anything else but a message like "couldnīt request current timings". I donīt know that because in my setup this was never the case.

I hope you understand what Iīm trying to say.
When the drop/repeat time doesnīt change (and the time is real, so you really get drops/repeats in the given time) and you havenīt changed your audio output or there is a massive change in hardware temperatures (which influences the clocks slightly) you have to assume that the actual used resolution is always the same. But this should show up in madVR and/or in the GPU driver settings.

This is the next step.
If it is the case that all the time the same timings are used then the next step would be to find up why this is the case.
But first find out IF this is the case.

mclingo
18th April 2020, 12:58
Hi, there is how i got mine fixed last night, still working today, no idea if it will hold or not but right now i have good times for both 2160p 2d and 1080p 3d.

https://1drv.ms/w/s!AgvFafeelEBik6hMzYAoEAPeWrMD8Q?e=21zFGM


EDIT - sadly 3D was a fluke, best I can get with any settings is 30 mins, acting just like NVIDIA cards now, very odd behviour for AMD, 2d holding solid however at no drops for 11 hours +

Cowboydude99
18th April 2020, 16:02
Is there any SDR to HDR conversion?

I’ve been testing how I like some image enhancements, and wondered about sdr to hdr.

SamuriHL
18th April 2020, 16:14
No, SDR to HDR is not something that can be done.

Cowboydude99
18th April 2020, 16:18
No, SDR to HDR is not something that can be done.

Thanks!

How have you all calibrated your projectors? I use my HTPC w/ MadVR for all of my movies.

Is there a specific software that would be recommended for MadVR using projection?

Any specific hardware/meters?

Asmodian
18th April 2020, 21:42
i1 Display Pro is a good meter, DisplayCal is good free software. I like Calman too, but it is expensive and DisplayCal is quite good.

hannes69
18th April 2020, 21:48
Colormunki Display (the same like i1 Display Pro, but cheaper + a little bit slower measurements) combined with DisplayCal.

Cowboydude99
18th April 2020, 21:52
Great! Thank you! I will look into both meters.

Do you have to make adjustments regularly, or is it a 1 time config? I'm using a PJ, so the bulbs lose their brightness over time.

tp4tissue
18th April 2020, 22:23
Great! Thank you! I will look into both meters.

Do you have to make adjustments regularly, or is it a 1 time config? I'm using a PJ, so the bulbs lose their brightness over time.

Every 200-300 hours of use, it's necessary to remeasure. That's how fast it begins to drift.

VERY FAST.

huhn
18th April 2020, 22:44
just run a verification every 1-3 months if it fails do a new calibration.

Cowboydude99
18th April 2020, 23:22
Cool! Anything else to consider?

Also- anywhere to donate for MADVR? Seems like for such great software, I should be paying something...

huhn
18th April 2020, 23:43
you could inform yourself about your projectors behaviour.
how fast does it drift in the first 1000 hours of the lamp is it relative stable after that these kind of things.

they may or may not be a paid version of madVR "soon" something like never to 1-36 months.

Cowboydude99
18th April 2020, 23:58
you could inform yourself about your projectors behaviour.
how fast does it drift in the first 1000 hours of the lamp is it relative stable after that these kind of things.

they may or may not be a paid version of madVR "soon" something like
never to 1-36 months.I'll see what happens over time I guess.

OK, I'll keep a look out.

Cowboydude99
19th April 2020, 01:45
95% if what I watch us HDR Blu-ray disks.

Would I still use one of these devices?

Edit: I found this on the X-rite site;
According to X-Rite, only the Rev.B OEM version of the meter (not the Retail) manufactured from January 2017 or later is certified to measure up to 2000 nits.

So I guess it is not suitable for hdr.

Asmodian
19th April 2020, 02:26
2000 nits is way above what any projector can do. Even most consumer displays cannot do 2000 nits. I do not know of a better meter you could buy, at least for <$1000 USD.

Also, you can calibrate at 75% IRE, or lower if you need to. This does make sense for HDR, since most of the screen is not very close to peak most of the time.

Cowboydude99
19th April 2020, 05:29
In order to get the nits output, I’d need a light meter too?

I don’t know the nits, but supposed to be 2000 likens, not sure what the actual light hitting the screen would measure though.

Do I need to know this for a good calibration?

Asmodian
19th April 2020, 06:12
Measuring it is part of the calibration, a colorimeter can measure it.

huhn
19th April 2020, 06:47
you are nearly sure not even close to 200 nits even below 100 nits is pretty normal for a good projector projecting on a big screen.

failax
19th April 2020, 10:44
It is possible to create a table of peak luminance of every frame before, instead of processing in real time, so less powerful video card could read it?