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

Betroz
31st August 2016, 09:04
This is the solution to x64 playback WITHOUT ReClock:

http://forum.doom9.org/showthread.php?t=173571

QB

Thank you for the link :)
That seemed complicated and very time consuming...

Q-the-STORM
31st August 2016, 09:17
Thanks, I got 23.976Hz working (one frame repeat every 2 hours, which is fine) but if I let madVR swtich to it automatically, the custom resolution disappears and madVR switches to 24hz. So now I'd have to set resolution manually every time I watch something and set it back when I'm done...

and is there a way to do slowdown without reclock? got a bunch of 25fps stuff that needs slowdown on playback...

AntonP
31st August 2016, 18:33
Thanks, I got 23.976Hz working (one frame repeat every 2 hours, which is fine) but if I let madVR swtich to it automatically, the custom resolution disappears and madVR switches to 24hz. So now I'd have to set resolution manually every time I watch something and set it back when I'm done...

and is there a way to do slowdown without reclock? got a bunch of 25fps stuff that needs slowdown on playback...

+ 1
custom resolution is good, but what to do with display modes in madvr?
i need 23.976 for movies only and 60Hz for general use of htpc....

Uoppi
31st August 2016, 23:26
I just switched to exclusive mode to get lower present times BUT

a) are custom resolutions not supposed to work in exclusive mode?

or

b) is madVR reporting the tv's refresh rate incorrectly when in exclusive mode?

In other words, custom resolutions don't have any effect unless I'm in windowed mode. :(

(I'm on Windows 10 64bit Anniversary & GTX 960, all drivers and software up-to-date.)

Asmodian
1st September 2016, 04:18
quick sidenote, how is the new Titan X with madVR? do you use a 2160p screen?
I'm thinking about upgrading, but I don't know if I should go for the new Titan X or wait for the 1080 ti

The new Titan X is, of course, quite good for madVR. The price is not worth it but at stock I can double 1080p24 using NNEDI3 256 for luma. :D

That is pretty much maxed out though, only super-XBR for chroma upscaling, ED dithering, and a 3DLUT. This Titan is very temperature and power limited and throttles down as it heats up with madVR, you need very good cooling. NNEDI3 128 luma doubling with room for other settings is preferred.

I just switched to exclusive mode to get lower present times BUT

a) are custom resolutions not supposed to work in exclusive mode?

or

b) is madVR reporting the tv's refresh rate incorrectly when in exclusive mode?

In other words, custom resolutions don't have any effect unless I'm in windowed mode. :(

(I'm on Windows 10 64bit Anniversary & GTX 960, all drivers and software up-to-date.)

Do not put too much stock in the reported present times, it is hard to measure these things very precisely between modes and you always need to leave some headroom anyway. Present times should be quite low even in windowed mode. With Nvidia I find the mode with the highest real performance is Windowed Overlay, but I use DX11 windowed myself for the improved responsiveness to window resizing, etc.

I find windowed mode to work at least as well as full screen exclusive without the mode change and other issues.

Light001
1st September 2016, 05:27
Looking for help Again

i5 3550 4.1ghz, Gtx 980, windows 10 pro 64bit and most recent nvidia driver. BenQXl2420T, i watch mostly 1080p Quality vidoes with some older shows 480p. My monitor only supports 60hz and 100hz and 120hz. I used Tft Centrals color calabration for my monitor. Watching things like game of thrones using madvr and Mpc-hc its abit dark unless i turn up brightness. Do i touch anything in the Nvidia Control Panel? under Video ? (Edge Enhance,Noise Reduc,Deinterlacing-unverse telecine)??
Under Devices I do not know what should be set, i assume the pc levels 0-255 is fine and 8 bit for native display? 3d format is auto. calibration is set to disable display modes is also unchecked color and gamma is left alone and hdr which is new, i selected the top option.

Processing All unchecked, Artifact removal unchecked,Image Enhance unchecked, and zoom, disable scaling if image size changes by only 25 lines or less. Scaling Algorithims are Chroma up- Jinc, Image Down-Jinc,Image doubling-off,image upscale-jinc with active anti ringing on all 3. Nothing in upscale refinement, Rendering has nothing checked off under general and the que for cpu is 16 and gpu is 8, Smooth Motion on, althought i do not know what to be looking for, just that in some movies when the scene is in motion from side to side i see visually its not very smooth, like a little judder or something, Dithering is Ordered and nothing checked in trade quality for preformance.

In Mpc Under lav Decored, top corner is all auto with the box checked 0-255 and ordered dithering, Dxva2 copyback with all boxes checked and software deinterlacing disabled.

Does anything stand out here that i would or should want to change? i would prefer to stay under 70% Gpu usage. Its been along time since i posted and i forgot alot of stuff :(. As i said most the stuff i watch is 1080 or 720 with the odd older show @ 480p. or worse. i find it dark watching game of thrones, unless i turn up brightness in mpc, which is kinda annoying. But i gave up trying to find a better set up for the monitors settings. Help me obi won kenobi, your my only hope <3

Sorry to toxic your thread, but if anyone can give me some input base on info provided or can inbox me id greatly appreciate it. if i find movie nirvana or epic results id glady paypal a few bucks for your time. TY!

Uoppi
1st September 2016, 09:09
Do not put too much stock in the reported present times, it is hard to measure these things very precisely between modes and you always need to leave some headroom anyway. Present times should be quite low even in windowed mode. With Nvidia I find the mode with the highest real performance is Windowed Overlay, but I use DX11 windowed myself for the improved responsiveness to window resizing, etc.

I thought windowed overlay and windowed mode are the same thing - or am I misunderstanding something? :scared:

Problem is, performance in .24 madVR is significantly worse. I already had to overclock my card by +100 MHz and even then I'm unable to use some of my previous profiles. I know madshi said quality will always come before performance in madVR builds but I can't find anything in the changelog that would explain my issues. And it doesn't appear to be a driver or Windows Anniversary issue either.

Switching to exclusive mode made a slight improvement that was sorely needed. But apparently custom resolutions are bypassed now. :(

I find windowed mode to work at least as well as full screen exclusive without the mode change and other issues.

"Mode change and other issues" = would custom res not supported be one of these "other issues"? Can't figure out why it's not working.

hannes69
1st September 2016, 16:42
Quote:
Originally Posted by huhn:
you should really read the link. 23.976 is pointless

Not really. Yes, you need a video signal that matches the audio rate. However, 23.976 is a whole lot closer than the 23.97 Nvidia cards start with. Further, the graphics card is the audio output in most cases nowadays, so they should both be derived from the same source clock. I have no idea why they can't just put the right circuitry on a $650 videocard to output 24/1.001 & 60/1.001 correctly. Instead they have some gimped clock generator that is limited to only 2 decimal places of pixel clock frequency accuracy which forces you to use a custom resolution rather then than the standard CEA-861 timings.

My R9 380 was much better in this regards.

In an ideal world the graphic and audio clock would be derived from the same clock. This is in reality not the case and it is very simple why not: E.g. MSI or Gigabyte or ... builds a graphic card. The guys there construct a circuitry and buy the necessary components out in the world, RAM, GPU, connectors, passive and active electronic standard components and so on. They buy maybe a video chip from nvidia and an audio chip from Realtek. nvidia has nothing to do with Realtek. MSI buys components that are "ready" and "as are". Then they implement the required oscillators that are needed for both of the chips according to the specifications from nvidia and Realtek. If one producer would produce a one chip solution with audio and video and doesnīt use third party components then it would be possible to have one common clock. I donīt know such a producer at the moment...
And this has nothing to do with the price segment, it is the same for a 10$ or a 1000$ graphic card.
The 2 decimal places pixel clock is a Windows and/or driver limitation, the clock is much more precise than these two decimal places. If it wouldnīt be you couldnīt do the trick with the custom resolutions.
If the R9 380 was better in this regards, than it was a kind of luck. The inaccuracy lies in the limitation of the 2 decimal places pixel clock.

are custom resolutions not supposed to work in exclusive mode?

I use exclusive mode and custom resolutions work perfectly in my case. I have Win 7 64 with AMD R7 250.

Stereodude
1st September 2016, 19:02
In an ideal world the graphic and audio clock would be derived from the same clock. This is in reality not the case and it is very simple why not: E.g. MSI or Gigabyte or ... builds a graphic card. The guys there construct a circuitry and buy the necessary components out in the world, RAM, GPU, connectors, passive and active electronic standard components and so on. They buy maybe a video chip from nvidia and an audio chip from Realtek. nvidia has nothing to do with Realtek. MSI buys components that are "ready" and "as are". Then they implement the required oscillators that are needed for both of the chips according to the specifications from nvidia and Realtek. If one producer would produce a one chip solution with audio and video and doesnīt use third party components then it would be possible to have one common clock. I donīt know such a producer at the moment...
And this has nothing to do with the price segment, it is the same for a 10$ or a 1000$ graphic card.
The 2 decimal places pixel clock is a Windows and/or driver limitation, the clock is much more precise than these two decimal places. If it wouldnīt be you couldnīt do the trick with the custom resolutions.
What the heck are you talking about? The HDMI signal containing both the audio and video is entirely generated by the graphics chipset. There is no Realtek chip on a graphics card handling the audio. I looked over a GTX 1080 card very closely and found no audio codec/processor on it. It would be trivial for them to make the card have proper 24/1.001 output.

There is no Windows limitation. It's not really a driver limitation either. It's a self inflicted hardware limitation. Only Nvidia gets 23.97 for 24/1.001. Intel and AMD both do 23.976. Custom resolutions work on Nvidia cards because you can find non-standard 1080p24 timings that give exact 24/1.001 output with a pixel clock generator that has only 2 decimal place pixel clock accuracy. With the right crystal and HW implementation it would have exact 24/1.001 output with the correct CEA-861 timings.

If the R9 380 was better in this regards, than it was a kind of luck. The inaccuracy lies in the limitation of the 2 decimal places pixel clock.
It had nothing to do with luck, but a better implementation by AMD.

hannes69
1st September 2016, 23:38
The HDMI signal containing both the audio and video is entirely generated by the graphics chipset. There is no Realtek chip on a graphics card handling the audio. I looked over a GTX 1080 card very closely and found no audio codec/processor on it.

It was a simple example to explain the problem. Maybe there is not a discrete chip on the board for audio, but it is something like "separated units" within the GPU. Thatīs more or less the same thing, maybe a GPU manufacturer uses predefined solutions for HDMI audio and connects that with the video part.
Maybe engineer team A realizes video, team B audio, team C this, team D that and team E combines that all...

There is no Windows limitation.
Ask the author of CRU utility, he knows for sure things like that, because he has made that tool to make custom resolutions for Windows. You canīt define a pixel clock in Windows more accurate than with 2 decimal places. That IS a Windows limitation.

I donīt see the described problem especially with nvidia. For me all resolutions with the according refresh rates arenīt accurate enough, so I have to use custom resolutions anyway. And thatīs the case with intel, nvidia, AMD. The nature of the problem are not perfect crystals, thermal effects and the fact of using 2 different clocks.
Of course you can use smoothmotion in madvr or reclock. I donīt use both of them and use custom resolutions instead. With perfect results. 23.976, 24.000 25.000 29.970 fps movies with NO drops/repeats (or within days to be accurate).
Problems have solutions and/or workarounds, such is life.
You can get perfect playback regardless of the manufacturer. Itīs simple as that. And you donīt get PERFECT playback out of the box regardless of the manufacturer (beside by chance of course). I personally see no plus or minus in this regard with nvidia.

XTrojan
1st September 2016, 23:54
This thread has too much OCD in it, is it only me who doesn't notice the frame repeat once every 5min?
I hope you're not confusing 24p issues with perfect 23.976 sync as I did the latter and eventually figured out it's just my TV being shit and decided to upgrade.

e-t172
1st September 2016, 23:59
It was a simple example to explain the problem. Maybe there is not a discrete chip on the board for audio, but it is something like "separated units" within the GPU. Thatīs more or less the same thing, maybe a GPU manufacturer uses predefined solutions for HDMI audio and connects that with the video part.

Using separate units for audio and video might make sense, but it would still be very strange if these units used different clocks. In fact, the GPU manufacturer would have to go out of its way to make this work; it's much simpler to just use the same clock for both.

This thread has too much OCD in it, is it only me who doesn't notice the frame repeat once every 5min?

At 24Hz, a single frame drop or frame repeat can be highly noticeable. At 60Hz and higher refresh rates, not so much.

ashlar42
2nd September 2016, 10:43
Using separate units for audio and video might make sense, but it would still be very strange if these units used different clocks. In fact, the GPU manufacturer would have to go out of its way to make this work; it's much simpler to just use the same clock for both.If that was the case (and I've been using HDMI video/output since GTX 460), we would always have 0 frames dropped/repeated, out of the box. The video would be presented with the same exact speed variation that audio is presented at. This is not happening.
In any case, I suggest that this discussion would be better on my thread with the guide to smooth playback. I wouldn't want to annoy people that don't feel the need for precise refresh rates, zero frames dropped/repeated, etc.
If madshi is happy in having this discussed here, then fine, obviously.

huhn
2nd September 2016, 11:23
madshi has a proper solution anyway it's smooth motion.

it is a sad fact that way to many screen can't do proper 23/24 and either your guide or reclock can fix this but smooth motion can fix this.

just to give you can idea:
http://www.rtings.com/tv/reviews/lg/ef9500

Update 1/25/2016: We installed new firmware (04.20.75) and no longer have judder via 24p or 24p via 60i, which means this TV is now equal to the LG EG9600 for judder-free playback. You can find the firmware and installation instructions here.

and my new screen can't do proper 24p in PC mode. this is a huge plague in the TV industry.

mueslibrown
2nd September 2016, 13:59
You seem to be disagreeing with yourself here. Why bother with 23.976 if we already know it may not be perfect? Why not set it up to be as perfect as possible? Which is what the thread elaborates in detail on how to get there.

I followed the thread and couldn't understand it - I'm fairly technical with 20 years in IT software so unless I'm actually incredibly dim I went back to the nVidia panel which gives me 1 frame repeated every 46mins according to madVR.

I think the guide would work better if there were step by step instructions (using an example) with screenshots. Too many assumptions on the user's understanding are made in the 'guide'.

Betroz
2nd September 2016, 14:06
I followed the thread and couldn't understand it - I'm fairly technical with 20 years in IT software so unless I'm actually incredibly dim I went back to the nVidia panel which gives me 1 frame repeated every 46mins according to madVR.

I think the guide would work better if there were step by step instructions (using an example) with screenshots. Too many assumptions on the user's understanding are made in the 'guide'.

My feelings about that guide too.

Stereodude
2nd September 2016, 14:08
Ask the author of CRU utility, he knows for sure things like that, because he has made that tool to make custom resolutions for Windows. You canīt define a pixel clock in Windows more accurate than with 2 decimal places. That IS a Windows limitation.
Well I can't speak to whether it is a Windows limitation or a limitation of the clock generator on the graphics card. Ultimately, the hardware can do what it wants. They could simply have a special mode where the driver tells the hardware to engage drop frame (/1.001) while Windows still thinks the clock rate is 74.25MHz.

I donīt see the described problem especially with nvidia. For me all resolutions with the according refresh rates aren't accurate enough, so I have to use custom resolutions anyway. And thatīs the case with intel, nvidia, AMD. The nature of the problem are not perfect crystals, thermal effects and the fact of using 2 different clocks.
Of course you can use smoothmotion in madvr or reclock. I donīt use both of them and use custom resolutions instead. With perfect results. 23.976, 24.000 25.000 29.970 fps movies with NO drops/repeats (or within days to be accurate).
Problems have solutions and/or workarounds, such is life.
You can get perfect playback regardless of the manufacturer. Itīs simple as that. And you donīt get PERFECT playback out of the box regardless of the manufacturer (beside by chance of course).
A $50 Blu-ray player has no problem locking and synchronizing the audio and video clocks together and outputting something very close to 24/1.001 with CEA-861 timings, but it's somehow it's unrealistic to expect a PC costing many times more to do the same? :confused: I don't think so.

With the graphics card doing both the audio and video side there's no hardware reason why the audio and video clock can't be locked and synchronized exactly even if it isn't 24/1.001 with 0 ppm. I'm sure stand alone Blu-ray players aren't 24/1.001 with 0ppm clock variance either, but the display synchronizes to them just fine.

I personally see no plus or minus in this regard with nvidia.
All I can say is Nvidia gives 23.97 with the standard drivers which has gross clock errors. AMD and Intel give 23.976 which are considerably closer. As to whether the 23.976 from AMD and Intel are good enough, well a secondary issue relating back to the first half of my post. They easily could be if the video and audio clocks were linked correctly.

Sunset1982
2nd September 2016, 16:17
Good news for all guys interested in AMD RX480:

My new Sapphire RX480 Nitro+ 4GB arrived today,

RX480's HEVC decoder is running good with newest crimson 16.8.3 drivers, LAV and MadVR! :cool:

fairchild
2nd September 2016, 16:17
My feelings about that guide too.

I tried to mess around a bit with it on my Sony 32" 1080p TV but gave up after a bit. I googled around a bit to see if there is a better guide out there regarding using CRU but can't seem to find anything. My Panasonic 55" VT60 plasma TV does a good enough job I think with 23.976 content and the standard AMD drivers.

hannes69
2nd September 2016, 16:24
A $50 Blu-ray player has no problem locking and synchronizing the audio and video clocks together and outputting something very close to 24/1.001 with CEA-861 timings, but it's somehow it's unrealistic to expect a PC costing many times more to do the same? I don't think so.

That reminds me of the old discussion of GPUs and game consoles. A game console has total inferior hardware capabilities compared to many PC components but can deliver very high performance. This is because it is specialized to only one purpose: games. The console canīt do anything more. A PC is a general purpose machine and NOT specialized to anything.
Now thatīs the same story with a cheap bluray player. This device can only playback blurays. It would be a shame if that device couldnīt do that in a somehow perfect manner.
A GPU is principally constructed for showing a normal desktop, office applications, browsers ... Thatīs the basic functionality everyone needs. Then we have the large community that wants power for games. GPU companies are focused on that demands. Then we have a smaller community that wants a GPU for HTPC usage. And a very small part of this community has an obsession for "perfect" video playback. The GPU manufacturer is concentrated on the need of the mass market and doesnīt obviously care for the needs of us 0.001% nerdy freaky perfect video junkies. So I would assume that 30% of their team works on basic functionality, 68% on gaming performance and 2% on video playback. The 2% guarantee that video playback is working for "normal" people, maybe one freak is in their team who knows and cares and has ressources for "special" video needs.
Donīt get me wrong - I am NOT satisfied with the situation, like you, but I donīt complain. I try to see the situation realistic and then Iīm focused on solutions/tricks/workarounds to realize my needs. Special needs lead to special requirements. Out of the view of a normal human being we are talking about special needs, yes.;)

Sunset1982
2nd September 2016, 16:25
Is there someone using Crimson drivers?!

The new crimson drivers are missing some options.

Can't change pixelmode to RGBfull (no options shown in drop down menu) and cant get 10 bit output (8bit is choosen and greyed out in crimson settings)

you can pm me, so we do not spam this thread...

e-t172
2nd September 2016, 20:57
Using separate units for audio and video might make sense, but it would still be very strange if these units used different clocks. In fact, the GPU manufacturer would have to go out of its way to make this work; it's much simpler to just use the same clock for both.

If that was the case (and I've been using HDMI video/output since GTX 460), we would always have 0 frames dropped/repeated, out of the box. The video would be presented with the same exact speed variation that audio is presented at. This is not happening.

I don't think that your reasoning is correct. Using the same clock for audio and video is a necessary requirement for perfect playback, but it's not sufficient. You also need to make sure the GPU sends the correct length of audio with each video frame.

For example, if you configure the GPU to display at 24Hz and output audio via HDMI at 48kHz, the GPU will send exactly 48000 / 24 = 2000 samples (44.67ms) of audio with each frame. It can guarantee this with perfect accuracy because it's using the same clock for both; in other words, "variation", as you call it, does not occur and is not a problem.

The problem is, if you play a video using this configuration, but the video is not actually 24 FPS but rather 24000/1001 FPS (23.976), one video frame does not correspond to 2000 samples of audio, but rather 2002 samples. But the GPU doesn't know that - it's still outputting 24.000 Hz with 2000 audio samples per frame. This means that, in practice, the audio plays faster than the video (even though the hardware clock is the same!) because every time a new frame is presented, the amount of audio the GPU sends is very slightly wrong, and doesn't match the amount of audio per frame that the video actually contains.

This in turn means that, other time, the audio timestamps will drift relative to the video timestamps, and at some point, when the drift exceeds some software-defined threshold, madVR will decide to repeat a frame to bring the timestamps back in sync - most likely, it will repeat a frame once the drift equals one full frame, which happens after 1001 frames (the amount of time it takes for the 2-additional-audio-samples-per-frame to accumulate to 2002 samples, i.e. a full frame duration), or roughly 42 seconds. Here's the not-so-obvious thing: this is an exact number. Since there is only one hardware clock, there is no variation. A frame repeat will happen every 1001 frames, no more, no less, period. This is quite different from the situation where you have two separate audio and video clocks (i.e. you're not sending the audio through HDMI), which can drift against each other somewhat randomly and unpredictably.

Obviously, the proper fix would be to tell the GPU to precisely lock itself to 24000/1001 Hz (23.976), so that it sends exactly 2002 audio samples per frame, which would exactly match the contents of the video, and there would be no frame drops or repeats whatsoever. However, if Windows itself limits the accuracy of the refresh rate configuration to only 2 decimal places, this is impossible. The only thing you can do is get closer to the 2002-audio-samples-per-frame ideal, but you will still miss it by at least 0.3 sample or so.

What would be great is if the GPU driver could detect that you're asking it to display a refresh rate that's very close to 23.976 (say, 23.98) and automatically "nudge" the refresh rate to the proper rate so that each frame really is 2002 audio samples, without telling Windows. That seems technically feasible (Windows doesn't really care what the actual refresh rate is, it can't even assume the audio and video clocks are the same anyway). However that would require GPU manufacturers to actually implement such a feature, which is probably never gonna happen because, as hannes69 just pointed out, not enough people care.

AngelGraves13
3rd September 2016, 01:04
All scaling with Jinc and Super Res at 3 passes looks great unlike the other sharper scalers.

ryrynz
3rd September 2016, 01:19
Good news for all guys interested in AMD RX480


Is everything running properly? NNEDI3, and post processing options?

CarlosCaco
3rd September 2016, 03:49
Acidentaly i discovered that if press v i active or disable v sync (appears on osd using mpc-be) i thougth that this was a hotkey only active for evr cp, should i turn on or off?

Betroz
3rd September 2016, 07:14
All scaling with Jinc and Super Res at 3 passes looks great unlike the other sharper scalers.

You prefer that over NNEDI3?

ryrynz
3rd September 2016, 08:25
You prefer that over NNEDI3?

To each their own, I think it's quite overboard. Trying firing that combo through some SD anime and you'll recoil. NNEDI3 reins supreme for most content, then enable some edge/detail sharpening or w/e.

Betroz
3rd September 2016, 08:49
To each their own, I think it's quite overboard. Trying firing that combo through some SD anime and you'll recoil. NNEDI3 reins supreme for most content, then enable some edge/detail sharpening or w/e.

Yeah well I use NNEDI3 for both Chroma Upscaling and Image Doubling settings, and I like the IQ - but I do notice more artifacts than I'd like. I'm not sure if NNEDI3 is the only reason for that, maybe the settings under Upscaling Refinement is the culpit. Is this something we must live with or can it be fixet? Or maybe the LAV filters is to blame? I have no clue...so please enlighten me :)

@Madshi : What's your response to this?

ryrynz
3rd September 2016, 09:38
Yeah well I use NNEDI3 for both Chroma Upscaling and Image Doubling settings, and I like the IQ - but I do notice more artifacts than I'd like.

I think his response would be to simply upload a screenshot of these artifacts.
Nobody else appears to have any issues, likely it's related to your setup.

Sunset1982
3rd September 2016, 15:15
Is everything running properly? NNEDI3, and post processing options?

yes, everything runs fine...

AngelGraves13
3rd September 2016, 20:44
Watching Futurama with my settings and it looks better than NNEDI3. Lines are sharp and no artifacts.

Asmodian
3rd September 2016, 21:43
Watching Futurama with my settings and it looks better than NNEDI3. Lines are sharp and no artifacts.

I like NNEDI3 a lot but Jinc+SR1-3 looks great too, you have to admit. ;)

I use NNEDI3 doubling and it looks great IMO, no artifacts to speak of, and good at removing or reducing aliasing present in the source. Somehow aliasing seems to bother me more than most artifacts.

However, I can do a lot of damage when using the same Upscaling Refinement settings between different sources. I like very low strengths on these too, they can cause a lot of artifacts when turned way up.

Betroz
3rd September 2016, 22:17
I found out that if I removed/unticked my settings under Upscaling Refinement, I saw a reduction in artifacts. The only option I would use there from now on, is Super Resolution.
I too like Jinc AR + SR3, a good alternative to NNEDI3 128 with 720p content upscaled to 1080p!

ryrynz
3rd September 2016, 22:38
I saw a reduction in artifacts.

Nobody knows what you're talking about, screeeenshots.

Betroz
3rd September 2016, 23:00
Nobody knows what you're talking about, screeeenshots.

Kind of pixelation at the edge of someones nose f.eks. Pixels that are not supposed to be there. Hard to take a screenshot of something that is there for maybe 1-2 seconds and then gone.

huhn
3rd September 2016, 23:01
puase the video and use control + arrow left right.

Asmodian
4th September 2016, 06:42
I thought windowed overlay and windowed mode are the same thing - or am I misunderstanding something? :scared:

No, Windowed Overlay and Windowed DX9 or DX11 are not the same. Windowed Overlay (the option is in rendering -> general settings -> "enabled windowed overlay (Windows 7 and newer)". I think it still only works with Nvidia and Intel GPUs. Overlay only works in D3D9 so enabling Direct3D 11 disables Overlay.

There are 5 main modes available, D3D9 Overlay, D3D9 Windowed, D3D11 Windowed, D3D9 Exclusive, and D3D11 Exclusive. The D3D9 Windowed and Exclusive modes also have an old path available (which uses backbuffers instead of present queues).

The Overlay mode uses overlay hardware that skips much of the OS, it is the highest performance mode on my system.

"Mode change and other issues" = would custom res not supported be one of these "other issues"? Can't figure out why it's not working.

I get odd refresh rate issues with FSE (the refresh rate isn't the same as in a windowed mode), I had assumed it was due to G-sync, but I do not really know why it happens. I do not use custom resolutions anymore but they used to work with FSE for me.

Siso
4th September 2016, 08:09
No, Windowed Overlay and Windowed DX9 or DX11 are not the same. Windowed Overlay (the option is in rendering -> general settings -> "enabled windowed overlay (Windows 7 and newer)". I think it still only works with Nvidia and Intel GPUs. Overlay only works in D3D9 so enabling Direct3D 11 disables Overlay.

There are 5 main modes available, D3D9 Overlay, D3D9 Windowed, D3D11 Windowed, D3D9 Exclusive, and D3D11 Exclusive. The D3D9 Windowed and Exclusive modes also have an old path available (which uses backbuffers instead of present queues).

The Overlay mode uses overlay hardware that skips much of the OS, it is the highest performance mode on my system.

Is overlay mode messing up with the 3dlut?

huhn
4th September 2016, 08:20
no it isn't.

Sunset1982
4th September 2016, 09:12
guys, which pixel mode ist recommendet for madvr with amd card?


1. UHD, 60hz, RGB 4:4:4, 8 bit

or

2. UHD, 60hz, YCbCr 4:2:0, 10 bit


I have a LG 55E6 4K OLED tv, which has a 10 bit Panel. Would like to use the 10bit mode in madvr...

Siso
4th September 2016, 10:51
no it isn't.

No out of gamut colors or color clipping?

huhn
4th September 2016, 11:00
nothing specified to a 3D LUT.
overlay mode is handling ICM calibrations differently.

Siso
4th September 2016, 11:34
nothing specified to a 3D LUT.
overlay mode is handling ICM calibrations differently.

I see, so it is OK to use it with 3dlut, even for madvr 0.90.21?

huhn
4th September 2016, 11:44
yes it is.

Siso
4th September 2016, 12:19
yes it is.

Thank you, dude :D

tony359
4th September 2016, 13:01
Hi there.
My little media player is a little slow (Intel Cherry Trail), it works fine most of the time but sometimes it struggles a little. I noticed that all the cores were running at minimum speed when a video is playing so I investigated and found a way to force all the cores at maximum speed. Now when in Windows - or when using different renderers - the cores are maxed out.

However, when MadVR is used, the cores go back to minimum speed - with core utilisation up to 100%!

This is only happening when MadVR is running. If I default back to the default renderer, cores are maxed out.

Any reasons why this should happen??

Thanks
Tony

huhn
4th September 2016, 13:14
sounds like thermal throttling.
have a look at the temps.

for what do you need the max core speed in the first place?

tony359
4th September 2016, 13:28
Hi huhn,

Temperatures are well within thermal throttling. I used to have this problem until I installed a fan. I can run prime95 and still the CPU does not throttle.
Any change the GPU is throttling instead maybe?

I can disable thermal throttling from the bios though, I could give it a go to see what happens.

I'm trying to find out why picture is stuttering every now and then and sometimes sound is crackling too. The first think I noticed was the cores maxed out at 100% and the frequency at minimum. That's why I wanted to try boosting the cores manually - in case the Speedstep is somehow not working as it should.

huhn
4th September 2016, 13:35
these CPU have a power target that is shared with the GPU.
if the GPU is taking to much power "resources" is could throttle the CPU.

with hardware decoding the CPU clock shouldn't matter.

you could make a screen shoot from the OSD(control + j) when the problems is accruing.

tony359
4th September 2016, 13:59
Hi huhn

You are right. I have run furmark and when the GPU is maxed out, the CPU slows down. The default renderer does not show this issue as it does not use the GPU, I reckon. Nothing to do with madVR then.
I will investigate whether anything could be done - or I'll look into a proper HTPC ;)

If you happen to know how to disable/improve this setting, I'm all ears ;)

Thanks for your help!
Tony