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

Asmodian
14th September 2018, 18:07
I am simply mildly annoyed that they call RGB "RGB 4:4:4", as if there could be something like "RGB 4:2:2". Describing the chroma sampling pattern for RGB formats makes no sense. :p

But nothing is wrong with the image, and it does have full resolution "chroma".

huhn
14th September 2018, 18:10
AMD always did this.

and yes you can subsample RGB it simply doesn't make any sense.

nevcairiel
14th September 2018, 18:49
and yes you can subsample RGB it simply doesn't make any sense.

Not with HDMI you can't.

Razoola
14th September 2018, 19:15
In relation to the new Nvidia RTX graphic cards and the video decoding they support I read the following for those intrsted (from guru3d)...

The video processor also has had a bit of an update and offers an improved video and hardware en/decoder. HEVC 8K30 HDR real-time sees 25% bitrate savings. H.264 up to 15% bitrate savings. Turing GPUs can drive two 8K displays at 60 Hz with one cable for each display. Turing’s new display engine supports HDR processing natively in the display pipeline. Tone mapping has also been added to the HDR pipeline. Tone mapping is a technique used to approximate the look of high dynamic range images on standard dynamic range displays. Turing supports the tone mapping formula defined by the ITU-R Recommendation BT.2100 standard to avoid color shift on different HDR displays. Turing GPUs also ship with an enhanced NVENC encoder unit that adds support for H.265 (HEVC) 8K encode at 30 fps. The new NVENC encoder provides up to 25% bitrate savings for HEVC and up to 15% bitrate savings for H.264. Turing’s new NVDEC decoder has also been updated to support decoding of HEVC YUV444 10/12b HDR at 30 fps, H.264 8K, and VP9 10/12b HDR.

huhn
14th September 2018, 20:15
Not with HDMI you can't.

why should anyone sane add this.

YGPMOLE
15th September 2018, 01:52
Hi guys!

I didn't want to start a flame, just understand and learn a little bit more from who knows really more than I do!

That's my situation now: after checking every option in LAV, the output is NV12 for SD and HD 8 Bit (MPeg2 DVDs, and H264 .mkv) and P010 for HEVC 10 Bit UHD; with the same settings of before, madVR produces dropped frames: I suppose because colorspace conversion and chroma upsampling are on his shoulder, and I have to re-optimize.

If I simply enable SVP to do frame rate conversion for SD and HD, LAV changes automatically his output to YV12: I suppose to "talk" with FFDshow input, am I right?

In this situation, FFDShow output at NV12: wouldn't be better to force his output at YV12 (to avoid the YV12 - > NV12 conversion), and let madVR do directly the YV12 - > RGB conversion?

huhn
15th September 2018, 02:18
That's my situation now: after checking every option in LAV, the output is NV12 for SD and HD 8 Bit (MPeg2 DVDs, and H264 .mkv) and P010 for HEVC 10 Bit UHD; with the same settings of before, madVR produces dropped frames: I suppose because colorspace conversion and chroma upsampling are on his shoulder, and I have to re-optimize.

yes chroma scaling cost a little bit.

If I simply enable SVP to do frame rate conversion for SD and HD, LAV changes automatically his output to YV12: I suppose to "talk" with FFDshow input, am I right?

nv12 and yv12 are pretty much the same thing a conversation between them is very fast and lossless.

In this situation, FFDShow output at NV12: wouldn't be better to force his output at YV12 (to avoid the YV12 - > NV12 conversion), and let madVR do directly the YV12 - > RGB conversion?

madVR can convert pretty much everything that lavfilter outputs directly to RGB.

kostik
15th September 2018, 19:22
In relation to the new Nvidia RTX graphic cards and the video decoding they support I read the following for those intrsted (from guru3d)...

The video processor also has had a bit of an update and offers an improved video and hardware en/decoder. HEVC 8K30 HDR real-time sees 25% bitrate savings. H.264 up to 15% bitrate savings. Turing GPUs can drive two 8K displays at 60 Hz with one cable for each display. Turing’s new display engine supports HDR processing natively in the display pipeline. Tone mapping has also been added to the HDR pipeline. Tone mapping is a technique used to approximate the look of high dynamic range images on standard dynamic range displays. Turing supports the tone mapping formula defined by the ITU-R Recommendation BT.2100 standard to avoid color shift on different HDR displays. Turing GPUs also ship with an enhanced NVENC encoder unit that adds support for H.265 (HEVC) 8K encode at 30 fps. The new NVENC encoder provides up to 25% bitrate savings for HEVC and up to 15% bitrate savings for H.264. Turing’s new NVDEC decoder has also been updated to support decoding of HEVC YUV444 10/12b HDR at 30 fps, H.264 8K, and VP9 10/12b HDR.

Will the new GPUs output RGB 12/10bit@60Hz via HDMI? or is it still limited to RGB 8Bit@60Hz\12BIT@30Hz-23Hz since the HDMI connecter is the same 'old' HDMI 2.0b?

huhn
15th September 2018, 19:47
on paper they have HDMI 2.0. so no.
but the fact they can send 8k 60hz means they may be able to patch it in.

el Filou
15th September 2018, 20:10
They can't claim they're HDMI 2.1 yet even if the hardware has been designed to be, because they have to wait for the official certification test spec: https://www.hdmi.org/manufacturer/hdmi_2_1/ (section 'Testing and Certification FAQs')
Samsung just announced a 8K TV but when asked if it had HDMI 2.1 inputs they said they had to wait for the certification to say anything:
https://www.cnet.com/reviews/samsung-85q900fn-preview/ (search page for HDMI 2.1)

So if you absolutely want 4K 60 Hz 10/12-bit RGB, the best is to specifically ask NVIDIA if the cards support that, but not ask them if the cards will be HDMI 2.1.

kostik
15th September 2018, 20:16
They can't claim they're HDMI 2.1 yet even if the hardware has been designed to be, because they have to wait for the official certification test spec: https://www.hdmi.org/manufacturer/hdmi_2_1/ (section 'Testing and Certification FAQs')
Samsung just announced a 8K TV but when asked if it had HDMI 2.1 inputs they said they had to wait for the certification to say anything:
https://www.cnet.com/reviews/samsung-85q900fn-preview/ (search page for HDMI 2.1)

So if you absolutely want 4K 60 Hz 10/12-bit RGB, the best is to specifically ask NVIDIA if the cards support that, but not ask them if the cards will be HDMI 2.1.

The new GPUs have HDMI 2.0b ports so they don't claim to have HDMI 2.1 . I guess it is possible to use 4k 10/12bit@60HZ using DisplayPort. Or do you mean that the new GPUs have actually HDMI 2.1 ports but hdmi 2.0b is mentioned in specs because they are waiting for official cert?

huhn
15th September 2018, 20:30
GPU just have HDMI ports end of story. what type of signal it can send depends on there display engine. if there display engine can produce a signal that is HDMI 2.1 complain they can update the driver to do that.

that's why all kepler cards can do HDMI 2.0 with the HDMI 1.4 bandwidth the a b c was always meaningless for GPUs the display engine matters and well HDCP which can't be updated.

nevcairiel
15th September 2018, 20:34
that's why all kepler cards can do HDMI 2.0 with the HDMI 1.4 bandwidth

Adding features like that is just software though, what we're really after with HDMI 2.1 is increased bandwidth. Now they may have planned ahead for that, but its a different situation entirely, since it needs stronger hardware to be able to do the increased bandwidth.

huhn
15th September 2018, 20:38
according to the source the hardware to create a signal "like" that is present.

as said before you should never believe in such a thing and never buy hardware in hope they add it until they confirm it and/or it is added.

SamuriHL
15th September 2018, 21:11
Which is great and all but everything in your chain has to support it. Meaning you need a TV that can receive it even if the GPU is capable. And if you pass it through a receiver, the receiver must also be compliant. That's why Nev is waiting to upgrade all his stuff. LOL I got impatient and bit the bullet this summer so I'm stuck on HDMI 2.0 equipment. But if you want full bandwidth, remember that it's more than just a GPU upgrade.

jmone
16th September 2018, 07:56
The good news is when Madshi's HDR->SDR is done, we can just run everything in 8-Bit and there is plenty of Bandwidth with HDMI 2.0 even with UHD @ 60p. I'll not need to upgrade to 2.1 till 8K content comes out... and that is going to be awhile anyway.

Betroz
16th September 2018, 09:24
Have Madshi stopped development of MadVr? There hasn't been any new release since late April as far as I can see.

kostik
16th September 2018, 09:27
Have Madshi stopped development of MadVr? There hasn't been any new release since late April as far as I can see.

No. The next final build is coming soon.

Betroz
16th September 2018, 09:29
No. The next final build is coming soon.

Ok thanks :)

madjock
16th September 2018, 12:34
No, I just recreated my custom resolution yesterday. I had also used the clean install option when installing the newest driver (399.07). Also running win10 1803.

I did not need to restart or anything, it all worked in a nearly ideal fashion and I got down to ~1day between drops or repeats.

Just downloaded 399.24 and as per so many versions since 390.xx I cannot get it to keep a Custom Res I would like.

All I need to do is change 1 number, and it either does not save, it saves what I don't want, and it does its own thing at a seemingly locked nVidia framerate.

How did you get it to keep a custom res you actually needed, or how does it read it as whenever I have something in there it ignores it anyway ?

Manni
16th September 2018, 13:08
Just downloaded 399.24 and as per so many versions since 390.xx I cannot get it to keep a Custom Res I would like.

All I need to do is change 1 number, and it either does not save, it saves what I don't want, and it does its own thing at a seemingly locked nVidia framerate.

How did you get it to keep a custom res you actually needed, or how does it read it as whenever I have something in there it ignores it anyway ?

You need to use CRU with any recent version of the drivers, and it will only stick to 12bits if your default mode is 4K23p. If your default mode is 4K60p, it will revert to 8bits.

Both MadVR custom res and Nvidia custom res don't work with recent drivers.

madjock
16th September 2018, 13:17
You need to use CRU with any recent version of the drivers, and it will only stick to 12bits if your default mode is 4K23p. If your default mode is 4K60p, it will revert to 8bits.

Both MadVR custom res and Nvidia custom res don't work with recent drivers.

I agree as it has been for a lot of us for a long time, I don't seem to have much luck with CRU either, too many numbers and all I have to do with earlier drivers is change total pixels from 1125 to 1124 when nVidias custom res does work.

Hey ho, back to 390.xx again I guess :)

Darkimmortal
16th September 2018, 13:34
Is there an option in madVR to control which GPU it uses?

I have recently setup a multi-gpu system with one powerful GPU and a secondary weak GPU used only to drive an extra monitor. Every application seems to use whatever black magic is done in Windows 10 for the rendering to happen on the powerful GPU and the final image to be sent over PCI-E to the weak GPU.

The only exception to this is madVR - when more than exactly half of the player window is moved on to the monitor connected to the weak GPU, madVR performance falls off a cliff as it starts using the weak GPU for rendering.

Is there an option to disable this behaviour and have it work like other apps/games?

mrmarioman
16th September 2018, 13:56
No. The next final build is coming soon.

final build?

Manni
16th September 2018, 13:57
final build?

Public / non test build, not final :)

Asmodian
16th September 2018, 21:06
Just downloaded 399.24 and as per so many versions since 390.xx I cannot get it to keep a Custom Res I would like.

All I need to do is change 1 number, and it either does not save, it saves what I don't want, and it does its own thing at a seemingly locked nVidia framerate.

How did you get it to keep a custom res you actually needed, or how does it read it as whenever I have something in there it ignores it anyway ?

Make sure that when you make any changes it is not the current active resolution. I simply use madVR's custom resolution page to both create the custom mode and optimize it. Everything worked perfectly the first try, this is only 8 bit video modes as I don't like 10 bit with my TV.

The only thing I needed to pay attention to was making sure my 23 Hz resolution was not active when applying the optimize.

xabregas
17th September 2018, 01:24
Is the FSE mode on windows 10 new update corrected or should i still keep my windows 10 before falls creator untouched? Because before 1709 everything is ok on FSE. Works like a charm as in W8 or W7.

khanmein
17th September 2018, 07:49
Is the FSE mode on windows 10 new update corrected or should i still keep my windows 10 before falls creator untouched? Because before 1709 everything is ok on FSE. Works like a charm as in W8 or W7.

The FSE is not working with W10 + Nvidia 399.24

madjock
17th September 2018, 07:53
Make sure that when you make any changes it is not the current active resolution. I simply use madVR's custom resolution page to both create the custom mode and optimize it. Everything worked perfectly the first try, this is only 8 bit video modes as I don't like 10 bit with my TV.

The only thing I needed to pay attention to was making sure my 23 Hz resolution was not active when applying the optimize.

Thanks for the reply. Well a lot of us do not seem to get the same joy.

TBH I struggled with madVRs custom even with old drivers, as in the ones that promised no frame repeats never seemed to work (probably my fault), but creating a custom one always did.

With the latest drivers (last good few, even the ones with the seemingly locked 23.976), I cant get any joy at all. Same as Manni01 and others.

Strange how some have success, wonder where the difference lies ?

Back to 390.77 and all is well again anyway.

oldpainlesskodi
17th September 2018, 07:55
The FSE is not working with W10 + Nvidia 399.24

FSE working here.

Sparktank
17th September 2018, 09:21
@madshi, we can get "transfer=2048" for file name tags?
even without meta data for the HDR, it will just have to guess what the tonemapping should be.

khanmein
17th September 2018, 09:35
FSE working here.

Are you sure that you enable automatic fullscreen exclusive mode under madVR settings?

oldpainlesskodi
17th September 2018, 09:46
Are you sure that you enable automatic fullscreen exclusive mode under madVR settings?

Yep, OSD showing D3D11 Exclusive 10 bit.

Sunset1982
17th September 2018, 11:39
Since I changed my GPU from GTX1070 to AMD's RX480, my tv show a "no signal" message, when the gpu switches tv mode from 60hz to 23/24hz mode or hdr mode. Seems like the amd needs a bit more time to change modes. The GTX1070 chenged a bit faster and no message was shown.

Is there any option within madvr to reduce switching time ? (maybe I will try Windowed and FSE modes...

Anyone with a LG Oled and AMD gpu got the same problem using madvr's auto display changing?

Klaus1189
17th September 2018, 11:52
I use also an AMD RX480 but I have a Samsung HDR screen and I don't get a "no singal" message.

xabregas
17th September 2018, 12:47
Yep, OSD showing D3D11 Exclusive 10 bit.

Some people can. Some people dont. Im not risking it. I need windows 10 on this mini pc because support for previous windows doesnt exist. 7th generation SOB. Windows 10 previous fall update is OK with madvr FSE mode. It works like a charm on intel uhd 600. So im not risking updating for getting some unknown security updates losing FSE in the process.

They keep telling me you have to update. For WHAT?? I use it as htpc ONLY.

madjock
17th September 2018, 12:53
They keep telling me you have to update. For WHAT?? I use it as htpc ONLY.

To be fair they don't know that ?

Excuse my ignorance but what is the point in FSE, I never use it, if its for stopping notifications and it is only used for HTPC, what would you get notifications from.

I don't use it myself and don't think I'm any worse for it, sure I saw Warner write somewhere that it is fake FSE in Windows 10 anyway, but could be wrong.

mrmojo666
17th September 2018, 13:08
AMD did break this quite recently but fixed it again with 18.8.1, i havent tried 18.8.2 yet as I never update drivers unless there is a good reason too these days.

Other than that you may still have something setup wrong.

other than general settings these are the only other prerequisites I am aware of with AMD cards.

- is you OLED setup in MADVR as 10bit or higher?
- do you have use Direct3D 11 for presentation (windows 7 and new) ticked - this is required.

Mine also stops working if either of these are not applied.

I'm going mad..... I'm quite sure after your post I've updated to 18.8.1 and tested ..but again yesterday night i got no hdr switch...i went back to 18.2.1 and working as expected..... without any changes in madvr config.....

there is any log that i can look at, to try to understand what's going on ?

thank you

xabregas
17th September 2018, 13:20
To be fair they don't know that ?

Excuse my ignorance but what is the point in FSE, I never use it, if its for stopping notifications and it is only used for HTPC, what would you get notifications from.

I don't use it myself and don't think I'm any worse for it, sure I saw Warner write somewhere that it is fake FSE in Windows 10 anyway, but could be wrong.

You arent a FSE believer. You need to see it to understand that some people without it get all kind of banding and blurring you wont get with fullscreen exclusive mode because it will disable anykind of postprocessing stuff your screen is doing. For me FSE mode almost like cleanup the image. The PQ seems more detailed and smooth. Yeah, my eyes can detect that stuff. Windows 10 and probably all windows enable certain feautures than simply arent disabled when you watch a movie in fullscreen windowed mode.

mclingo
17th September 2018, 14:11
I'm going mad.......

thats happened to me a few times and is always been either, my TV needed a hard reboot, which it doesnt get very often as you are supposed to leave an OLED on permanently so it can do its nighly pixel cylces or something had switched in my settings and I hadnt noticed, like MADVR had switched to auto or 8 bit, DIRECT3D11 had become unticked, something like that.

I did have a similar issue though, I could have swarn 18.3.4 was working with HDR but when I tried it a while back it wasnt. i'm still on 18.8.1 as I now never change my drivers unless I need to.

mrmojo666
17th September 2018, 14:20
thats happened to me a few times and is always been either, my TV needed a hard reboot, which it doesnt get very often as you are supposed to leave an OLED on permanently so it can do its nighly pixel cylces or something had switched in my settings and I hadnt noticed, like MADVR had switched to auto or 8 bit, DIRECT3D11 had become unticked, something like that.

I did have a similar issue though, I could have swarn 18.3.4 was working with HDR but when I tried it a while back it wasnt. i'm still on 18.8.1 as I now never change my drivers unless I need to.

I'm going to check again tonight, at least for tv madvr settings, i'm sure that dx11 is checked because i saw it today..... It's really annoying.
Also i have an lcd so i'm used to cut off powerto all my stuff during the night. so everyday there is a tv reboot.

I'm a bit sad because 18.8.1 are very good drivers for games.....


thank you

huhn
17th September 2018, 14:20
FSE is a lie on windows 10.
it obviously can't disable processing at your screen.
notifications and stuff like xbox app, nvidia experience and stuff like this can show "infos" over it because the exclusive part is not true anymore it's just a simulation that been the case for a lot of windows version not only the newest.

i'm not saying you shouldn't use FSE but there is stuff it clearly doesn't do.

Klaus1189
17th September 2018, 14:56
For me all optional and normal drivers of AMD worked flawlessly (tried the last 6 ... 8 months) and these also did HDR. I can not reproduce HDR problems.

GCRaistlin
17th September 2018, 15:03
madshi
If software deinterlacing mode in LAV Video is Weston Three Field then madVR ignores "treat 25p movies as 24p" setting state and always behaves as it is off.. Sample 25fps video: https://mir.cr/0TFWKUVY
MPC-HC 1.8.1 x86, LAV 0.72.13, madVR 0.92.14

mrmojo666
17th September 2018, 15:08
For me all optional and normal drivers of AMD worked flawlessly (tried the last 6 ... 8 months) and these also did HDR. I can not reproduce HDR problems.

It's possible to know which card ? do you refer to HDR autoswitch that is always working ?

thank you

Klaus1189
17th September 2018, 15:13
I have an AMD RX480 8GB and use MPC-BE (always latest nightly) with madVR and LAV Filters, HDR is automatically switching -> AMD HDR is visible on first line in madVR stats.

xabregas
17th September 2018, 15:24
FSE is a lie on windows 10.
it obviously can't disable processing at your screen.
notifications and stuff like xbox app, nvidia experience and stuff like this can show "infos" over it because the exclusive part is not true anymore it's just a simulation that been the case for a lot of windows version not only the newest.

i'm not saying you shouldn't use FSE but there is stuff it clearly doesn't do.

Xbox app? I disabled all notifications and i have intel HD. Was never interrupted by notifications even on windowed. Idk what you are talking about. On my end if i compare FSE and FSW i see big differences in PQ on windows 10 previous Fall Update.

But i still agree with you that windows 10 overall is shit and that it was kinda better on old windows 8.1 and 7. But i cant install it. I can but the performance will be worst. Because 7th generation cpus u know. CRAP.

huhn
17th September 2018, 15:51
madshi
If software deinterlacing mode in LAV Video is Weston Three Field then madVR ignores "treat 25p movies as 24p" setting state and always behaves as it is off.. Sample 25fps video: https://mir.cr/0TFWKUVY
MPC-HC 1.8.1 x86, LAV 0.72.13, madVR 0.92.14

it is able to treat 25p as 24p not 50p as 24p or 48p.

working as intended

Manni
17th September 2018, 19:18
To be fair they don't know that ?

Excuse my ignorance but what is the point in FSE, I never use it, if its for stopping notifications and it is only used for HTPC, what would you get notifications from.

I don't use it myself and don't think I'm any worse for it, sure I saw Warner write somewhere that it is fake FSE in Windows 10 anyway, but could be wrong.

FSE is a lie on windows 10.
it obviously can't disable processing at your screen.
notifications and stuff like xbox app, nvidia experience and stuff like this can show "infos" over it because the exclusive part is not true anymore it's just a simulation that been the case for a lot of windows version not only the newest.

i'm not saying you shouldn't use FSE but there is stuff it clearly doesn't do.

For me FSE is still the only way to get 3D to work, although I haven’t checked on 98.24 if I could use windowed. I know some people with nVidia can, but it never worked for me.

Otherwise I hate FSE. I see no PQ improvement with it, and it takes ages to sync HDMI everytime you try to select an audio or subtitle track on my JVC, so I only use it if I can’t do otherwise.

The day 3D works here without FSE, I’ll gladly never use it again.

huhn
17th September 2018, 21:05
the system wide 3d may make it work in windowed.

you know you can workaround the resync with hotkeys or something like the MPC-HC web UI.