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

chrisssj2
2nd May 2019, 14:26
Did you try both passthrough HDR to display and tone map HDR using pixel shaders with output video in HDR format checked?

Those are your two best options for HDR with an LG OLED display. There is no magic.

If you are talking about chroma upscaling or dithering, try NGU Anti-Alias or NGU Sharp combined with Error Diffusion option 1 or 2.

That should give you the "best quality" HDR.

Also, set the GPU to RGB rather YCbCr. That will actually lower image quality on a PC.

I use default settings. So upon checking this:
---HDR: "where left to decide by madvr" So changed it like you said to "passthrough to display" but you say use passthrough or HDR using pixelshaders..? which one to choose?
Or did you mean just put the HDR option on pixelshader? If so. what to put @Target peak nits? and tone mapping curve?
---Put error Diffusion on Option 2.
---Put chroma on NGU sharp very high. What about image downscale and image upscale?
---And what about the trade quality for performance tab?
---Tried changing ycbr to rgb but nvidia only allows me to choose 8 bit RGB. So can't choose 10 bit.. I think personally I found ycbr 10/12 bit to look better then 8 bit RGB..? The blacks were more black and colours more vibrant?

Warner306
2nd May 2019, 16:24
I use default settings. So upon checking this:
---HDR: "where left to decide by madvr" So changed it like you said to "passthrough to display" but you say use passthrough or HDR using pixelshaders..? which one to choose?

Try pixel shaders with HDR output checked. You may or may not prefer it to passthrough. To send the correct metadata to the display, however, the latest Nvidia driver is needed. So playback may stutter with an RTX 2080 due to conflicts with that driver. In that case, go back to 418.91 and stick with passthrough.

Set the target peak nits to 700-1,000 nits;
Tone mapping curve to BT.2390;
Leave color tweaks for fire & explosions at balanced;
Set highlight recovery strength to medium-high.

---Put chroma on NGU sharp very high. What about image downscale and image upscale?

high is a better choice, as very high is a waste of resources for chroma upscaling.


What about image downscale and image upscale?

Neither is required with 4K output.


---And what about the trade quality for performance tab?

Leave them all unchecked.


---Tried changing ycbr to rgb but nvidia only allows me to choose 8 bit RGB. So can't choose 10 bit.. I think personally I found ycbr 10/12 bit to look better then 8 bit RGB..? The blacks were more black and colours more vibrant?

See here:

https://forum.kodi.tv/showthread.php?tid=223175&pid=2739438#pid2739438

tp4tissue
2nd May 2019, 17:29
the i1d3 is notable faster which pretty important for 3D LUT creation.

The speed increases the accuracy by getting more samples in the stability window, but in this case, because TVs and non-Pro monitors are highly unstable to begin with, it's not going to make much of a difference.

For example, my samsung tv's white point algorithm doesn't always arrive at precisely the same gains between backlight setting changes.

The room temperature also greatly affects LED temperature, and white led has +/- 10-20% luminance difference between operable temps

Things like this will add to the delta E far greater than what the meter can improve with measurement speed.

If you catch the i1d3 at sale price, then that's one thing, but facing non-sale prices, There's no reason not to choose Cmunki instead.

$140? if I had known that I would've got one.. Uhh.. Someone should've posted here. T_T

Yea, it was sold by adorama camera on Rakuten during rakuten's 20% off black friday promotion. So, $165 (sale price) * 0.8 = $132 + Tax ~$140

SirMaster
2nd May 2019, 17:57
What do you guys think about this?

https://www.amazon.com/Wacom-EODIS3-DCWA-Color-Manager/dp/B01B96L2QE

It's just a i1d3 right?

Any reason to get the official brand over this? I'm only going to use it with open source software and drivers anyways like ArgyllCMS, DisplayCal, HCFR, madVR.

tp4tissue
2nd May 2019, 21:13
At the difference of $15 , y risk it ? if it was the difference of $50, yea, I'd give it a go.

SirMaster
2nd May 2019, 21:15
At the difference of $15 , y risk it ?

Becasue the x-rite was $259 earlier when I just looked for these :P

All the websites are starting to sync the current $201 price now. First Amazon, now B&H.

tp4tissue
2nd May 2019, 21:21
u could wait for Bk Fri, should be $165 ish

huhn
2nd May 2019, 22:24
how can you make sure the room temperature doesn't change to much in a measurement with speed even through it doesn't matter anyway heating the screen(and meter) by simply running has far more effects on temperature and is a default calibration part anyway. the number of patches is just defined by the time you are willing to spend on it and the speed of the meter.

toki
2nd May 2019, 22:28
I do it for quality. I don't care how long it takes. I always go for the most amount of patches. With that said, this is where the rabbit hole part comes in, if you're anything like me you'll always be looking at it thinking you can squeeze just that little bit more out of your display.

huhn
2nd May 2019, 22:31
you know there is no real limited to the number of patches. there are theoretically enough patches to measurer for over 10 years or was it 100?

tp4tissue
2nd May 2019, 22:57
You guys are overthinking this. The TV and Sensor are unstable over 1.5-2 hours.

Measurements you take exceeding 1.5 to 2 hours (has a probability) of being NON relevant to the data within that 2 hours.

A very good human eye on a person who's trained to know precisely what to look for can discern quality up to ~2-3000 patches. Any more than that is purely academic. again, if anything more patches will increase the average error.

The only time where EXCESSIVELY many patches may outperform fewer is if the monitor has some really weird behavior. The error will still be higher than fewer patches, but it may fix the busted spot.

el Filou
3rd May 2019, 01:28
What do you mean "the TV [...] is unstable over 1.5-2 hours"?
Is this only valid for LCDs with local dimming as the LEDs can vary in temperature depending on content displayed?
Once a display is warmed up it should be stable in its responses.

tp4tissue
3rd May 2019, 01:32
No it absolutely is not. Daily temperature can vary quite alot. even 2 degrees difference changes the backlight characteristics.

The meter also heats up as the photons hit the sensor surface.

There's a very specific reason you should not calibrate for more than 1-2 hours.

Even 2 hours is asking a bit much.

Y'all can relax on this , cuz the outcome colors are Interpolated, it's not a 1:1 matching game where the accuracy increases linearly with ever more patches.

It just needs to define the general shape of the monitor's behavior.

Asmodian
3rd May 2019, 02:42
madVR, not calibration in general. We do have a good Calibration Thread (https://forum.doom9.org/showthread.php?t=172783).

chrisssj2
3rd May 2019, 11:34
Try pixel shaders with HDR output checked. You may or may not prefer it to passthrough. To send the correct metadata to the display, however, the latest Nvidia driver is needed. So playback may stutter with an RTX 2080 due to conflicts with that driver. In that case, go back to 418.91 and stick with passthrough.

Set the target peak nits to 700-1,000 nits;
Tone mapping curve to BT.2390;
Leave color tweaks for fire & explosions at balanced;
Set highlight recovery strength to medium-high.


high is a better choice, as very high is a waste of resources for chroma upscaling.



Neither is required with 4K output.



Leave them all unchecked.



See here:

https://forum.kodi.tv/showthread.php?tid=223175&pid=2739438#pid2739438

Done checked them all.
As for the link it says recommended:
(madVR) PC levels (0-255) -> (GPU) Full Range RGB 0-255 -> (Display) Output as RGB 0-255

I understand MadVR part, And the GPU is set in Nvidia control panel. but as for the display part I don't remember seeing a 0-255 option.

As to why I can't select RGB 10 bit is because I need to put it at 30 hz.. lol ok so I need to switch this manually each time i watch a movie.. Got it.

I created an nvidia profile for kodi with anisoptric filtering off etc. everything as close to nvidia defaults. And "adaptive power" and "Vsync" on. Pre-render frames @default (3) Did the same for MPC-BE.

Will report back on how it runs!

el Filou
3rd May 2019, 13:45
In displays, the RGB range setting is sometimes called "HDMI black level" and sometimes the values are called Low/High or Standard/Extended.

You could also just leave the graphics card output on 8-bit for all refresh rates and trust madVR's dithering, it's that good.

svengun
3rd May 2019, 13:56
If you catch the i1d3 at sale price, then that's one thing, but facing non-sale prices, There's no reason not to choose Cmunki instead.

yeah, I should have opted for that one too, didn't know it existed, would have saved me 120 euro's

any suggestions for which software to use, I have the softw that came with it and SpectraCal Ultimate for Business v 5.6.1

Warner306
3rd May 2019, 16:30
In displays, the RGB range setting is sometimes called "HDMI black level" and sometimes the values are called Low/High or Standard/Extended.

You could also just leave the graphics card output on 8-bit for all refresh rates and trust madVR's dithering, it's that good.

I think that is joke. It is spelled out in the link provided above, "LG: Black Level - High."

hotripper
3rd May 2019, 19:11
yeah, I should have opted for that one too, didn't know it existed, would have saved me 120 euro's

any suggestions for which software to use, I have the softw that came with it and SpectraCal Ultimate for Business v 5.6.1

https://forum.doom9.org/showthread.php?t=172783

tp4tissue
3rd May 2019, 23:09
In displays, the RGB range setting is sometimes called "HDMI black level" and sometimes the values are called Low/High or Standard/Extended.

You could also just leave the graphics card output on 8-bit for all refresh rates and trust madVR's dithering, it's that good.

You gotta double check this setting. Not super sure on LG

But on Samsung, it's either Normal or Low.

On PC mode, normal is 0-255, on low it's 16-235

On OTHER inputs, normal is 16-235, low is 0-255

WTH righ?

HelmedHorror
4th May 2019, 03:47
How will Ultra HD Blu-ray content be handled by a monitor like the LG 34GK950F (https://www.tftcentral.co.uk/reviews/lg_34gk950f.htm), which supports up DisplayHDR 400 (https://displayhdr.org/performance-criteria/) and uses 8-bit+FRC (as I understand it , it's 8-bit plus dithering to simulate 10-bit)?

My gut tells me that it will be handled similarly to how SDR monitors handle it. That is, poorly.

Unsurprisingly, I found it impossible to Google this question because I think very few people watch Blu-ray content (i.e., literally Blu-ray discs or rips thereof, not merely Netflix) on a computer monitor. Buuuut I knew just the place to ask! :)

huhn
4th May 2019, 04:17
pretty much the same as a TV with 400 nits.

HelmedHorror
4th May 2019, 04:48
pretty much the same as a TV with 400 nits.

I don't have a TV and haven't watched a movie on one in over a decade, so I'm not sure what that means :(

tp4tissue
4th May 2019, 05:37
@ HelmedHorror

Well, the main issue to work around is that it's ips with a contrast ratio of 1000:1

So , @ the peak 400cd, the black lvl is 0.4cd.

Before worrying about peak brightness, what you need to understand is that the image loses alot of depth without at least a VA-panel. VA has ~2000-3000:1 contrast on pc monitors. On va-Televisions, it goes from 4000:1 to 6000:1

The 10bit SHOULD give you smoother gradient than on 8bit.

But in most cases, Madvr does just as well with 8bit, because it has its own dithering capability.


You may even consider using 144hz w/ LG's Motion blur reduction turned ON.

The MBR cuts the brightness to 234.53cd, but that might actually be better depending on your room stimulus light.

Overall, in a bright room, it should look pretty decent. the high black lvl will however eat most of the dark details.

If you're using this monitor Long term for HDR movies, I recommend getting a colorimeter, so you can adjust blackoutput offset to tease out a just little more black detail, while still maintaining the more contrasty look.

Boo @ 75%
https://imgur.com/XAdPuib

Boo @ 100% (more contrast, but too black for IPS)
https://imgur.com/fjmHt4t

huhn
4th May 2019, 09:45
you don't lose dark details with a low CR displays. they just get less dark...

the screen simply has a similar if not better HDR as an entry level LG IPS UHD TV the total majority they sell but this is a gaming screen on top of it.

el Filou
4th May 2019, 15:17
@HelmedHorror the last paragraph from the TFTCentral article you linked tells all you need to know about that monitor's HDR mode: basically, it's even worse than in SDR mode.
Setting madVR to tone map using 400 as peak nits and outputting SDR with the display backlight at maximum would give you the best quality IMO.
The monitor still has a larger colour gamut than most SDR screens so you'll still benefit from that.

tp4tissue
4th May 2019, 15:19
If by similar HDR you mean lacking contrast. then Yes. hahaha.

IPS blk lvl is too high.

If the image has any dark noise, it can grey cast and fade the entire image.

Had they graded the film FOR IPS, things would be different.

Having high blk lvl is the same as having Missing gamut. Director intent is lost to some degree.

tp4tissue
4th May 2019, 15:21
Setting madVR to tone map using 400 as peak nits and outputting SDR with the display backlight at maximum would give you the best quality IMO.


He should try out the 10bit too. Might look nice.

I really don't think 400cd is a good idea here, but yea, try it, keep the room very bright to offset blacks. For 0.4cd to look black or even 0.2 cd, the room basically needs to be as bright as morning sunlight.

chrisssj2
4th May 2019, 16:53
Try pixel shaders with HDR output checked. You may or may not prefer it to passthrough. To send the correct metadata to the display, however, the latest Nvidia driver is needed. So playback may stutter with an RTX 2080 due to conflicts with that driver. In that case, go back to 418.91 and stick with passthrough.

Set the target peak nits to 700-1,000 nits;
Tone mapping curve to BT.2390;
Leave color tweaks for fire & explosions at balanced;
Set highlight recovery strength to medium-high.


high is a better choice, as very high is a waste of resources for chroma upscaling.



Neither is required with 4K output.



Leave them all unchecked.



See here:

https://forum.kodi.tv/showthread.php?tid=223175&pid=2739438#pid2739438

Just tried your settings. The movie played back fine.
First I was afraid of micro stutters. But I don't think I have any.
Perhaps only when starting the movie/pausing/resuming it.

http://prntscr.com/nkcq5v

Image of the stats on kodi.
Using 12 RGB BIT here.. Don't rly see difference at first glance to ybcr

Tried putting the TV on low blacks during mission impossible 2015 movie. And it looked better in my own personal opinion.
With blacks on high it looked too bright and grey IMO. The blacks low make the blacks rly nice.

Also RTings guide suggest to use Low black levels for my tv.

EDIT:
Just put up the mission impossible 2018 movie.
And im getting stutters all over the place. Whereas 2015 mission impossible was fine today!

http://prntscr.com/nkdc6g

Lots of occasional glitches and frame drops. Any idea?
Most of it is watchable but every minute or so something happens. sometimes a second only and sometimes several seconds.

leeperry
4th May 2019, 18:44
Long shot or not but if I want to zoom a 1080p60 video by 30%, why does mVR still does all its processing even on portions of the video that aren't shown? Wouldn't it be possible to only post-process(SSIM/NGU/etc) what's visible after zoom is applied? It's a waste of ressources and I might get away with higher quality picture if that was doable.

hotripper
4th May 2019, 19:21
EDIT:
Just put up the mission impossible 2018 movie.
And im getting stutters all over the place. Whereas 2015 mission impossible was fine today!

http://prntscr.com/nkdc6g

Lots of occasional glitches and frame drops. Any idea?
Most of it is watchable but every minute or so something happens. sometimes a second only and sometimes several seconds.

Yeah thats high and high renders and cues arent filling. What driver are you on? Latest or 418.91? You aren,t display matching...? Check Task Manager see if you have anything hogging resources. Maybe you have the high cpu bug for nvidia.

chrisssj2
4th May 2019, 20:17
Yeah thats high and high renders and cues arent filling. What driver are you on? Latest or 418.91? You aren,t display matching...? Check Task Manager see if you have anything hogging resources. Maybe you have the high cpu bug for nvidia.

No idea what that means what you just said but im on latest nvidia drivers. Nothing running on the computer. And I can't exactly pullup task manager while playing exlusive fulscreen movie.

Anyway I undid the suggested changed in the "Trade quality for performance" tab and set them to default. also changed back from RGB to YBCR.
I don't actually know what caused it.
But after changing those things the movie playbackked flawlessly.

Asmodian
4th May 2019, 20:27
Wouldn't it be possible to only post-process(SSIM/NGU/etc) what's visible after zoom is applied?

No, the player is doing the zoom and it does it by telling madVR to render to a larger size, madVR does not know exactly what part of the image is off the screen. That is also a pretty rare use case for a dedicated feature but a simple manual crop could do it (with more work) and be useful in other ways too.

leeperry
4th May 2019, 20:33
No, the player is doing the zoom and it does it by telling madVR to render to a larger size, madVR does not know exactly what part of the image is off the screen. That is also a pretty rare use case for a dedicated feature but a simple manual crop could do it (with more work) and be useful in other ways too.
mVR is told by the player what portion to zoom in, I don't see why invisible portions are being processed at all....especially with 4K content for instance.

Manual crop? With Avisynth in ffdshow in 8bit? No thanks :D

Asmodian
4th May 2019, 20:54
I meant a new feature for madVR, a manual crop, not resurrecting ffdshow. :p
I used to think that madVR would never have those kind of features but we got denoising, deblocking, sharpening, etc. A crop does not seem inappropriate.

Is madVR told by the player what portion to zoom into or is it simply told to render to a specific rectangle? I am pretty sure madVR simply gets told a target rectangle. It could assume (0,0) is the top left most visible pixel, and the display is a specific resolution, but I am not sure that would be true in all situations.

Siso
4th May 2019, 20:58
I meant a new feature for madVR, a manual crop, not resurrecting ffdshow. :p
I used to think that madVR would never have those kind of features but we got denoising, deblocking, sharpening, etc. A crop does not seem inappropriate.

Is madVR told by the player what portion to zoom into or is it simply told to render to a specific rectangle? I am pretty sure madVR simply gets told a target rectangle, it could assume (0,0) is the top left most visible pixel pixel and a specific aspect ratio but I am not sure that would be true in all situations.

Manual crop or crop via AR, would be a very cool feature in madvr, just my two cents ;)

leeperry
4th May 2019, 22:04
Is madVR told by the player what portion to zoom into or is it simply told to render to a specific rectangle? I am pretty sure madVR simply gets told a target rectangle. It could assume (0,0) is the top left most visible pixel, and the display is a specific resolution, but I am not sure that would be true in all situations.
mVR gets told what portion to zoom in, let it do the math and only process what's visible then: http://thumbs2.imagebam.com/e6/bd/a8/36b73b1214157884.jpg (http://www.imagebam.com/image/36b73b1214157884)

Code is kinda already there with black bars cropping and all so mostly a small change and we'd be good to go heh, sometimes I'd love to zoom in 1080p60 videos but it ends up in stutterland coz the 30/40% of picture that are invisible are being processed anyway.

madjock
4th May 2019, 23:15
No idea what that means what you just said but im on latest nvidia drivers. Nothing running on the computer. And I can't exactly pullup task manager while playing exlusive fulscreen movie.

Anyway I undid the suggested changed in the "Trade quality for performance" tab and set them to default. also changed back from RGB to YBCR.
I don't actually know what caused it.
But after changing those things the movie playbackked flawlessly.

Here is what I see from your OSD/s

Playing a 23.976 @30
You say you are 12 Bit, which you are with nVidia. but madVR is outputting in 8 Bit
you are at Limited should you be in Full ?
Looking at the 2nd screen the GPU cannot cope at all and the frame rates are still off ?

Unsure why you cannot see this, will it make a difference to the choppiness unsure. Ultimately madVR and nVidia are not in tune for the later cards, but the settings you are using will not help.

Read this this thread to understand what the OSD means etc...
https://forum.kodi.tv/showthread.php?tid=259188- 5. MEASURING PERFORMANCE & TROUBLESHOOTING

chrisssj2
5th May 2019, 13:29
Here is what I see from your OSD/s

Playing a 23.976 @30
You say you are 12 Bit, which you are with nVidia. but madVR is outputting in 8 Bit
you are at Limited should you be in Full ?
Looking at the 2nd screen the GPU cannot cope at all and the frame rates are still off ?

Unsure why you cannot see this, will it make a difference to the choppiness unsure. Ultimately madVR and nVidia are not in tune for the later cards, but the settings you are using will not help.

Read this this thread to understand what the OSD means etc...
https://forum.kodi.tv/showthread.php?tid=259188- 5. MEASURING PERFORMANCE & TROUBLESHOOTING

That maybe due to the fact I need to make it windowed to make a screenshot..? Unsure will check.
Yes like I said suddenly with that movie it was completely unwatchable. But with the other movie it was perfect. Sounds strange no?

So I should use nvidia's 24 hz setting? When playing RGB? or even if I choose to YCBR, always 24 hz rather then 60 hz?

Klaus1189
5th May 2019, 14:22
23 Hz for 23.976p
24 Hz for 24.000p
50 Hz for 25.000p, 50.000p and also interlaced 25.000i/50.000i (same thing)
59 Hz for 29.970p, 59.940p and also interlaced 29.970i/59.940i (again same thing)
60 Hz for 30.000p, 60.000p and also interlaced 30.000i/60.000i (and again same thing)

Please note:
23.976 is 24.000/1.001
29.970 is 30.000/1.001
59.940 is 60.000/1.001

Charky
5th May 2019, 14:50
Using 12 RGB BIT here.. Don't rly see difference at first glance to ybcr

Tried putting the TV on low blacks during mission impossible 2015 movie. And it looked better in my own personal opinion.
With blacks on high it looked too bright and grey IMO. The blacks low make the blacks rly nice.

Also RTings guide suggest to use Low black levels for my tv.
While many settings in madvr are about what looks nice to your eyes, black levels are NOT one of them : there are (several) right and (many) wrong settings.

Best advice (and madshi's own recommandation : https://forum.doom9.org/showthread.php?p=1271416#post1271416) is generally to set the whole chain (madvr + GPU driver + display) to Full, and check with a pattern to make sure your near blacks and near whites are correct.

This wiki page explains it all : https://kodi.wiki/view/Video_levels_and_color_space

jorsan
5th May 2019, 17:29
Maybe you could help: some of my music concerts are in 480. When the camera is moving (showing the uadice for example), I can see intervals of clear and blur images. how can I solve this issue?. I use Jriver/MAdvr/2070 gpu/i5/Windows 10. Thanks in advance

el Filou
5th May 2019, 18:27
We need more info:
- is it 480i (from a TV feed or a DVD for example) or 480p? If 480i, is deinterlacing active? What fps? Can you post the Video info section from MediaInfo?
- Are you sure it's not in the source? If you frame-step like with Ctrl+Right in MPC-HC, are the frames blurry?

hotripper
5th May 2019, 19:09
That maybe due to the fact I need to make it windowed to make a screenshot..? Unsure will check.
Yes like I said suddenly with that movie it was completely unwatchable. But with the other movie it was perfect. Sounds strange no?

So I should use nvidia's 24 hz setting? When playing RGB? or even if I choose to YCBR, always 24 hz rather then 60 hz?

You should be able to take a screenshot in FSE or windowed, use madvr settings f5 not windows prnt scrn, but both work for me I just prefer madvr screenshots.

No it does not sound strange as the new turing cards are giving completely random issues for video playback.

Go to nvidia cp set 24hz full rgb save, then you can repeat as necessary and finally go back to 60hz 8 full rgb if you want. Use madvr diplay matching and it will automatically switch to 12bit full rgb 24hz and back and forth as you change from desktop to fullscreen with madvr.

chrisssj2
5th May 2019, 22:56
You should be able to take a screenshot in FSE or windowed, use madvr settings f5 not windows prnt scrn, but both work for me I just prefer madvr screenshots.

No it does not sound strange as the new turing cards are giving completely random issues for video playback.

Go to nvidia cp set 24hz full rgb save, then you can repeat as necessary and finally go back to 60hz 8 full rgb if you want. Use madvr diplay matching and it will automatically switch to 12bit full rgb 24hz and back and forth as you change from desktop to fullscreen with madvr.

The post above says I should use 23hz for movies..?
Anyway I see forgot to put RGB limited to full. OSD shows full now with 10 bits. Not sure if it suppose to show 12 bits since that is what nvidia is set on. BUt that is what it shows.

where is this display matching setting located?

jorsan
5th May 2019, 23:37
thanks El Filou. Let mw get the info and let you know. Thanks again for your input

hotripper
6th May 2019, 02:40
The post above says I should use 23hz for movies..?
Anyway I see forgot to put RGB limited to full. OSD shows full now with 10 bits. Not sure if it suppose to show 12 bits since that is what nvidia is set on. BUt that is what it shows.

where is this display matching setting located?

Madvr>devices>display mode

Enable switch to matching and paste this in the box for 4k tv if 1080p tv then sub 1080:
2160p23, 2160p24, 2160p25, 2160p29, 2160p30, 2160p50, 2160p59, 2160p60

And go to display properties in windows, monitor tab, and make sure your display supports those values.

Charky
6th May 2019, 14:16
The post above says I should use 23hz for movies..?
Well, that depends too ;)

Some of us (Asmodian among them I believe) prefer to stick with a 60 Hz display and trust madvr frame blending (aka "smooth motion") to handle 3:2 judder.

Display matching comes with drawbacks, most notably the fact that, out of the box, most display can't perfectly reproduce 23,976 Hz and you will most likely experience frame drops/repeats (micro stutters) every few minutes, unless you create a custom resolution with madvr's integrated utility or another tool such as CRU. When they work, custom resolution are great, but if you're unlucky they can be excessively tricky to get right, depending on your GPU manufacturer, display brand, driver version, or a combination of these :D

huhn
6th May 2019, 14:30
you are mixing to different problems here.

a display that has a problem with 3:2 judder at 23p can't be fixed CRU and alike these displays are very common and just work with 60 hz internally.

the repeated dropped frame every couple mins comes from audio video clock deviations and the display has nothing with this.

Charky
6th May 2019, 18:12
you are mixing to different problems here.

a display that has a problem with 3:2 judder at 23p can't be fixed CRU and alike these displays are very common and just work with 60 hz internally.

the repeated dropped frame every couple mins comes from audio video clock deviations and the display has nothing with this.

My bad :o

Anyway, using 60 Hz + frame blending fixes both these issues, right ? :)