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

DragonQ
12th January 2013, 00:48
Interestingly, although the "Aggressive Deinterlacing" workaround works for the ~hour of interlaced video after the progressive title sequence, it doesn't work for the pre-titles section, which is definitely interlaced video but not being detected as such. Tis possible the metadata is wrong in this section. Sample here. (http://www.mediafire.com/?yb995bwznf8ney7)

pei
12th January 2013, 01:45
IRC channel anyone? Maybe we could start one on NewNet? irc.virtual-dope.com #madvr (irc://irc.virtual-dope.com/madvr) if anyone is interested...

chuuey
12th January 2013, 01:51
hey guys, just wondering if I will get frame drops no matter what I do unless i get reclock? I managed to get my display refresh to a 23.976xx something - madVR displays that, but still I get a 1 frame repeat every 12-13 minutes - or so the OSD shows. Unless I configured something in madVR badly? Cheers :)

dansrfe
12th January 2013, 02:37
I think this would be a right time to make use of IRC for discussions related to madVR since the response time may be quicker for simple questions.

And to keep doom9 updated we can log the channel and maybe madshi could add a link to the log in the first post?

mark0077
12th January 2013, 02:52
hey guys, just wondering if I will get frame drops no matter what I do unless i get reclock? I managed to get my display refresh to a 23.976xx something - madVR displays that, but still I get a 1 frame repeat every 12-13 minutes - or so the OSD shows. Unless I configured something in madVR badly? Cheers :)

I honestly don't think matching rates can stop frame drops repeats. I was able to match my playback rate to my display rate reported by madvr down to like 0.0001hz using svp interpolation.

I still get drops. Madshi suggested it could be due to the clock deviation so your display will never exactly be 23.976. For those brief moments I guess you could drop a frame. That's my understanding
I actually made adjustments to my playback rate upwards in tiny increments using svp until I got 0 frame drops but can't really be sure that im not getting frame repeats. I think there's always a need for some software solution to sort out this type of problem I guess. Matching rates is good but not enough.

Gelatinous
12th January 2013, 02:58
IRC channel anyone? Maybe we could start one on NewNet? irc.virtual-dope.com #madvr (irc://irc.virtual-dope.com/madvr) if anyone is interested...

madshi has been asked before and wasnt interested in creating an IRC channel.

dansrfe
12th January 2013, 07:20
For some reason when I drag MPC-HC to my second screen MPC-HC freezes and creates a dump file. This just started happening out of the blue... :(

kthxbye
12th January 2013, 08:56
For some reason when I drag MPC-HC to my second screen MPC-HC freezes and creates a dump file. This just started happening out of the blue... :(

I have the exact same problem! Good to see it probably isn't my set-up.

--dump file attached--

chuuey
12th January 2013, 12:49
I honestly don't think matching rates can stop frame drops repeats. I was able to match my playback rate to my display rate reported by madvr down to like 0.0001hz using svp interpolation.

I still get drops. Madshi suggested it could be due to the clock deviation so your display will never exactly be 23.976. For those brief moments I guess you could drop a frame. That's my understanding
I actually made adjustments to my playback rate upwards in tiny increments using svp until I got 0 frame drops but can't really be sure that im not getting frame repeats. I think there's always a need for some software solution to sort out this type of problem I guess. Matching rates is good but not enough.

I see, thanks :) I guess I can live with 2 or 3 frame skips now and then, just was happy i managed to create a custom resolution that actually does 23.976 :)

Jong
12th January 2013, 13:55
hey guys, just wondering if I will get frame drops no matter what I do unless i get reclock? I managed to get my display refresh to a 23.976xx something - madVR displays that, but still I get a 1 frame repeat every 12-13 minutes - or so the OSD shows. Unless I configured something in madVR badly? Cheers :)
If you don't like the "barely supported" nature of Reclock these days There are alternatives players that encorporate "Reclock-like" technology that work together with MadVR, both mediaportal and JRiver MediaCenter
for example.

I don't use Mediaportal but JRiver MC is now my normal HTPC frontend and they are now aggressively incorporating both the latest MadVR and LAV builds (in fact they somewhat overzeleousy included a LAV beta in a full release a few days ago!). JRiver MC includes Videoclock which has all the benefits of Reclock in a supported package with LAV and MadVR.

dansrfe
12th January 2013, 20:23
madshi, I know that you're on leave from madVR but this issue of not being able to drag to the second screen without MPC-HC immediately crashing is making me sad :( If you need any files from the crash then please let me know and I'll post all of them.

Thanks

nevcairiel
12th January 2013, 20:30
madshi, I know that you're on leave from madVR but this issue of not being able to drag to the second screen without MPC-HC immediately crashing is making me sad :( If you need any files from the crash then please let me know and I'll post all of them.


Works fine for me.

Edit:
Are you using native DXVA and moving from one screen on a GPU that supports that file in DXVA to another screen which doesn't by any chance?

dansrfe
13th January 2013, 05:55
I'm using the same GPU with both screens and DXVA2 Native.

kthxbye
13th January 2013, 13:19
I'm using the same GPU with both screens and DXVA2 Native.

Me too. Radeon HD7950. It worked fine before, but the last update seems to have problems.

Qaq
13th January 2013, 13:44
Please remind, do I need to set Catalyst video to 16-235 for DXVA2 de-interlacing no matter I use 0-255 for output? Does it affect DXVA decoding or anything else somehow?

Is it known problem that madVR can't get the EDID from TV after TV turn off/turn on? I can get the picture but "device" is greyed in madVR's properties and any adjustments are not possible untill the whole PC reboot.

Is it known problem that saturation adjustment produces kinda banding? If not I'll try to provide some pics and samples.

Superb
13th January 2013, 14:36
Can confirm the crash w/ DXVA2 native and moving the MPC-HC window to another monitor. Latest drivers. Trunk MPC-HC. Latest madVR. Latest official LAV. Single GPU (GT430) for both monitors. One is connected via DVI while the other one (TV) connected via HDMI in "Extend" [desktop] mode. Both are 1080p. Computer monitor is 60Hz. TV is 23.976.

madshi
13th January 2013, 14:48
Could you guys with multi-monitor DXVA2 problems please test different madVR versions, different media players or media player versions and maybe even different decoders or decoder versions? This used to work before, didn't it? We need to find out where the problem is coming from (madVR update, media player update, decoder update). Since the crash doesn't seem to occur inside of madVR, this will be hard to fix for me if I can't reproduce it and if we don't know under which exact circumstances the problem occurs. There's a chance it might not be madVR's fault, too.

nevcairiel
13th January 2013, 14:51
It crashes in LAV because some D3D things seem to go wrong which were not checked properly, and i fixed those checks, you can grab a fixed version here:
http://files.1f0.de/lavf/LAVFilters-0.55.1-11-gc82c1a0.zip

However, i was told that even with the crash resolved, it takes several seconds for playback to resume after a screen switch (which supposedly it didn't in previous versions). I can't reproduce, its fast for me (and it also didn't crash for me, i worked on a MPC-HC crash dump)
I suggest to follow madshis advice and test in which madVR version it started, or if any other external factors are involved.

dansrfe
13th January 2013, 19:33
After dragging to the second screen LAV automatically switches from dxva2 native to avcodec software decoding.

madshi,

I've tried previous MPC-HC versions, previous LAV Filters, and madVR builds all the way back to the beginning of December. Still no luck. I wish I could pinpoint the exact software and update in which the problem started happening but I was away from my second monitor during the holidays visiting family.

I do remember getting a "Failed to created D3D device" error once in madVR during all LAV Filters version changes with madVR 0.85.7.

nevcairiel
13th January 2013, 19:43
Now that it stopped crashing, you should probably provide a madVR log of the problem, and keep the logs simple. Delete old log, open file, move, stop, zip new log. :)
I can move it around just fine here, and decoding resumes pretty fast and still in DXVA. The log may tell madshi where it fails to deliver a D3D device.

dansrfe
13th January 2013, 20:06
Start clip, move MPC-HC to second screen, wait for video to start playing again, immediately close MPC-HC.

madVR log:http://www.sendspace.com/file/54c6u4

Libeluratio
13th January 2013, 21:16
hey guys, just wondering if I will get frame drops no matter what I do unless i get reclock? I managed to get my display refresh to a 23.976xx something - madVR displays that, but still I get a 1 frame repeat every 12-13 minutes - or so the OSD shows. Unless I configured something in madVR badly? Cheers

In fact targetting a perfect 23.976024 isn't a good idea.
I managed once to get 23.97602 but still dropped frames... it's because that number in madvr isn't exact.

The most important is to watch the clock deviation (has to be as little as possible) and the "1 frame repeat/dropped every" (of course has to be as big as possible). For exemple with my two gt 430 cards and custom nvidia resolution (took me 15h testing, and pc needs to be rebooted after every change or it does not correctly applies...), playing lord of the ring return of the king (extended so 4+h playing) I manage to get 0 video or audio drop and with the first, madvr displays 23.97532 and the other 23.97737, so see, targetting a 23.97602 here is not the way to go.

Sorry for my english !

chuuey
14th January 2013, 00:33
In fact targetting a perfect 23.976024 isn't a good idea.
I managed once to get 23.97602 but still dropped frames... it's because that number in madvr isn't exact.

The most important is to watch the clock deviation (has to be as little as possible) and the "1 frame repeat/dropped every" (of course has to be as big as possible). For exemple with my two gt 430 cards and custom nvidia resolution (took me 15h testing, and pc needs to be rebooted after every change or it does not correctly applies...), playing lord of the ring return of the king (extended so 4+h playing) I manage to get 0 video or audio drop and with the first, madvr displays 23.97532 and the other 23.97737, so see, targetting a 23.97602 here is not the way to go.

Sorry for my english !

Oh i see, ineteresting, I'll definetely do more testing, I though madVR displays an accurate refresh rate :( It's something around 23.976405 Thanks for the tip :)

cyberbeing
14th January 2013, 02:44
due to the clock deviation so your display will never exactly be 23.976.
There is only an indirect relationship between madVR's reported Refresh Rate and madVR's Clock Deviation calculation, so thinking in those terms will only cause confusion. madVR's refresh Rate calculation is accurate relative to other measurements from your computer, and that's all that matters for our purposes.

On the other hand, Clock Deviation has a direct relationship to your a/v Playback Rate which causes it to never be exactly 23.9760 FPS. Depending on your Clock Deviation, your actual Playback Rate would likely fall into the range of 23.9760 +/- 0.0005 FPS. Microsoft designed DirectShow in such a way that makes this skew completely invisible and transparent to the end-user. This can be confusing, since it results in all DirectShow playback FPS statistics being technically incorrect at face value.

If you match the Refresh Rate madVR reports to a multiple of your actual playback rate (calculated from Clock Deviation), you should never experience dropped frames assuming no madVR processing slowdowns or GPU driver glitches, but locking in such a high precision Refresh Rate is not always possible. See my post here (http://forum.doom9.org/showpost.php?p=1581585&postcount=13402) for how to calculate optimal Refresh Rate from madVR's Clock Deviation statistic.

Reclock works from the opposite direction, by adjusting your a/v Playback Rate to match your Refresh Rate.

6233638
14th January 2013, 05:20
23Hz is not 23.9670, it's 24/1.001 (which could be rounded to 23.9760, but madVR is using more precision than that)

Run ReClock, and your clock deviation will never be an issue. No dropped/duplicated frames or audio sync issues.
If you are running ReClock, I would also suggest targetting 24.0Hz. It's what films are natively shot at, and seems to have a much smaller deviation than 24/1.001 from a PC-based source.

23Hz is for legacy compatibility with NTSC. If you are running an HTPC source, you probably don't need that.

Unfortunately if you're running Windows 8, you can't get 24.0 with Nvidia now (and possibly AMD/Intel? I have no idea) as it seems to switch to 23Hz regardless.
It's unclear whether this is an Nvidia driver issue, Windows 8 issue, or compatibility issue with madVR and Windows 8.

jmone
14th January 2013, 07:54
I'm with 6233638 - use something like MC's "video clock", reclock etc and just pick a refresh rate close to the "real" one (eg 24, 25, 30, etc) and kick back - it will all be in sync. I can say from years of trying to chase tweaks to refresh rate on GPU to equal fps is a fools game.

MSL_DK
14th January 2013, 08:45
madshi> Are your own calibration solution still on your to do list?

Vyral
14th January 2013, 09:31
Hey people. For those who remember me, I made a graphic based on madVR algorithms to help make a range between the "Lowest" and "Highest" (previously "Ultra", heavy word). You can see it below.

http://i.imgur.com/8pNQv.png


Catmull-Rom AR & LL is better than Lanczos 4 AR for image downscaling ?

nevcairiel
14th January 2013, 09:41
Catmull-Rom AR & LL is better than Lanczos 4 AR for image downscaling ?

Yes, it produces a more natural image.
Higher algorithms don't necessarily produce better results.

FlygeSoppen
14th January 2013, 10:55
Hi

I have a strange problem I hope someone could help me with.

I have read through a large porsion of this thread and searched the internet for days,
but I have not found a solution for my problem yet.. Im about to go bananas!

Having installed MPC-HC + Madvr + Lav on different computers without problems.

One old gaming pc with Opteron cpu, a Geforce 620 card and WinXP, worked! but as expected a little choppy.

One Dell Precision M4300 Laptop With Quadro Card and WinXP, a little choppy in window mode but worked great in full screen.

I Did the same on my Home computer, Specs:
P5K Premium mainboard, QX6850 Quad core 3ghz(overclocked to 3.6ghz), 8gb RAM, Geforce 670 card, Xfi soundcard and WinXP.
It did not work out that well. I have tryed to follow different guides on the net without any success.

When all is installed and configured just like the other computers, all I get is about 1minute of hanging blackness
with choppy sound and then some laggy film afterwards.. Its the same in window and fullscreen.

Configurations on the my home computer is exactly the same as the others.
Windows is updated, I have tried different Nvidia drivers(i am now using 310.90)
Having tested all different settings within MadVr, LAV filters, MPC and Nvidia drivers,
All is the newest versions. Nothing helps! All of the Frameworks versions is allso updated..

This computer is completely stable, new games work great and all other codecs and filters work except MadVr.

Does anybody know what it could be?

Any help would be very mouch appreciated:)

agustin9
14th January 2013, 13:27
Why are you still using a 11 years old OS?

chuuey
14th January 2013, 13:39
There is only an indirect relationship between madVR's reported Refresh Rate and madVR's Clock Deviation calculation, so thinking in those terms will only cause confusion. madVR's refresh Rate calculation is accurate relative to other measurements from your computer, and that's all that matters for our purposes.

On the other hand, Clock Deviation has a direct relationship to your a/v Playback Rate which causes it to never be exactly 23.9760 FPS. Depending on your Clock Deviation, your actual Playback Rate would likely fall into the range of 23.9760 +/- 0.0005 FPS. Microsoft designed DirectShow in such a way that makes this skew completely invisible and transparent to the end-user. This can be confusing, since it results in all DirectShow playback FPS statistics being technically incorrect at face value.

If you match the Refresh Rate madVR reports to a multiple of your actual playback rate (calculated from Clock Deviation), you should never experience dropped frames assuming no madVR processing slowdowns or GPU driver glitches, but locking in such a high precision Refresh Rate is not always possible. See my post here (http://forum.doom9.org/showpost.php?p=1581585&postcount=13402) for how to calculate optimal Refresh Rate from madVR's Clock Deviation statistic.

Reclock works from the opposite direction, by adjusting your a/v Playback Rate to match your Refresh Rate.

That's an ineteresting note - I'll definetely do some testing :) By the way, since it's so problematic to get a fluid 23.976 playback rate without any additional tools - maybe something can be done in future versions of madVR about it? Or that's the player's responsibility? Anyway thanks for all the input :)

FlygeSoppen
14th January 2013, 15:44
Still love my Xp:)
It works great for me, for most things..
I have a Win7 partition on my main computer also but use it only for modern games.
I dont like all the extra fanzy stuff that came along with win7,
I have tweaked it down to look like Xp though:)
Its a taste thing I guess hehe

But does anybody know what it could be that makes it so MadVr doesent work on my main computer?
It is certainly powerful enough..
And it works on the other Xp machines I have tried it on.

njfoses
14th January 2013, 16:34
23Hz is not 23.9670, it's 24/1.001 (which could be rounded to 23.9760, but madVR is using more precision than that)

Run ReClock, and your clock deviation will never be an issue. No dropped/duplicated frames or audio sync issues.
If you are running ReClock, I would also suggest targetting 24.0Hz. It's what films are natively shot at, and seems to have a much smaller deviation than 24/1.001 from a PC-based source.

23Hz is for legacy compatibility with NTSC. If you are running an HTPC source, you probably don't need that.

Unfortunately if you're running Windows 8, you can't get 24.0 with Nvidia now (and possibly AMD/Intel? I have no idea) as it seems to switch to 23Hz regardless.
It's unclear whether this is an Nvidia driver issue, Windows 8 issue, or compatibility issue with madVR and Windows 8.

Excuse my ignorance as i have never used reclock but reclock and bitstreaming DTS-HD/TRUE-HD do not get along correct?

huhn
14th January 2013, 17:39
correct but what is more important perfect video playback or perfect audio?

SamuriHL
14th January 2013, 17:40
Both. Decode to bit perfect PCM.

huhn
14th January 2013, 18:21
that not the point reclock resamples

chuuey
14th January 2013, 18:22
well I decided to go for reclock, too much of pain adjusting those custom resolutions, I can't believe after so many years it's still an issue ;) But with reclock it works flawless, using 24hz :) Thanks for the tips :)

njfoses
14th January 2013, 21:11
Both. Decode to bit perfect PCM.

Right now i bitstream all my audio via lav via hdmi to my av receiver. Is there a guide anywhere that shows how to setup reclock with lav and madvr? I know i would not be able to bitstream anymore but if i can still use pcm it may be worth it for perfect video. I have played with custom resolutions and have gotten close but not perfect.

SamuriHL
14th January 2013, 21:19
Depends on your player. ReClock is the audio renderer. Then LAV can be set to decode audio, and if you have the ArcSoft dts decoder dll in your LAV instance, it will decode DTS-HD MA bit perfect. This is the ideal solution.

konakona
14th January 2013, 21:22
Hello there.
I've checked some pulldown detection patterns: http://www.avsforum.com/t/1276064/1920x1080-24-25-30fps-test-patterns-detect-pulldown-issues

and i do have same issue as the person that posted these patterns(long quote here) "(Pulldown / Frame Interpolation: One thing I've noticed that is interesting with the test files, it shows you what pull down and frame interpolation is being applied by the PC and/or TV. Each of the test files is only encoded with only 1 red square per frame. So when playing say the NTSC test file (29.97) you see two red squares when played at 60hz...in this case (I guess) the video renderer or TV displays each frame twice but overlaps them with the following frame. Now the interesting thing is when I play the Blu-ray test file (23.976) at 24hz I see 3 red boxs on my setup. As this is not being done in the PC, it looks like it must be the TV doing a 3:3 frame interpolation (though the documentation on the PIO LX608 is pretty vague on it's settings and options here)."

i do have screen forced to 72hz,and using reclock,but it looks like something in the video chain is putting some frame interpolation and i see 3(or 2,its really hard to see) red boxes. ive tried to force vsync,and play with pulldown detection in catalyst control center but in vain. Im using madvr+newest lav filters+reclock,playing using mpc-hc,screen is dvi-d connected with custom-reduced blanking times to allow 72hz on single-link using powerstrip.

im using xp 32bit,hd4870 and dell 2209wa (the 3squares also appear when i run 30fps test on 60hz,so i dont think its a screen issue,no one else reported that too)

Jong
14th January 2013, 21:22
that not the point reclock resamples
But resampling is a mathematically precise process and resampling in Reclock is done to a suitably high precision. Provided the adjustments Reclock is needing to make are low (<=0.1% if adjusting up to what is needed for NTSC slow down) it should have no noticeable impact for 99.9% of user, except for almost certainly noticeably smoother video. Of course there will always be audiophiles who do not want the audio touched at all and they will need to accept less smooth video. But for most of the population I think getting video smooth is the better trade off.

njfoses
14th January 2013, 21:23
Depends on your player. ReClock is the audio renderer. Then LAV can be set to decode audio, and if you have the ArcSoft dts decoder dll in your LAV instance, it will decode DTS-HD MA bit perfect. This is the ideal solution.

I use mpc-hc. Im assuming i would just uncheck all the options under bitstreaming in lav audio. I have the ArcSoft dts decoder. I just dont know what settings to choose in reclock for bit exact audio and perfect 24p playback.

SamuriHL
14th January 2013, 21:35
In MPC-HC you set ReClock as the audio renderer. I haven't used ReClock in forever so I don't remember all the checkboxes to check.

njfoses
14th January 2013, 21:39
In MPC-HC you set ReClock as the audio renderer. I haven't used ReClock in forever so I don't remember all the checkboxes to check.

Thanks, ill search around for reclock settings.

6233638
14th January 2013, 22:42
Excuse my ignorance as i have never used reclock but reclock and bitstreaming DTS-HD/TRUE-HD do not get along correct?LAV Audio can do lossless decoding of DTS-HD and TrueHD. (DTS requires the Arcsoft dtsdecoderdll.dll copied into LAV's directory)

ReClock has to resample audio to work, but it is high quality, and any theoretical loss of quality should be imperceptible.
ReClock also gives you the option to upsample the audio if your hardware supports it, in which case there should be no loss in quality at all.
If you have CPU cycles to spare, you can also try this resampler.dll (http://www.datafilehost.com/download-dc45ff3d.html), which offers slightly better resampling, at a big CPU cost compared to the current resampler.


If you choose to bitstream, that means you are locked to the audio clock, rather than the refresh rate, which means either dropping/duplicating frames in order to keep video in sync with the audio (obvious stuttering) or allowing the audio to go out of sync.
Either of those options are far more destructive to film quality than ReClock's resampling.


I have never seen anyone able to output an exact 24/1.001 from an HTPC, and even with very minimal clock deviation (e.g. madVR reports one dropped frame every 5+ hours) while it may theoretically be one frame dropped outside the duration of the film, it usually tends to happen at least once if not more during playback despite that estimate, in my experience.


These are my ReClock settings - some of which you probably don't want to change, unless you're having problems.

http://www.abload.de/thumb/reclock-1t0pz7.png (http://www.abload.de/img/reclock-1t0pz7.png) http://www.abload.de/thumb/reclock-2wzotd.png (http://www.abload.de/img/reclock-2wzotd.png) http://www.abload.de/thumb/reclock-3f7o32.png (http://www.abload.de/img/reclock-3f7o32.png)

Page 1: WASAPI Exclusive output will bypass your drivers, and block all other system sounds. It will also throw up an error if your sampling rate, format, and the number of channels being played are not supported by your hardware. (LAV Audio has options for downmixing to a supported number of channels)

DirectSound output is easier, as it lets all other sounds play, and any output format will work - but that may result in the Windows Mixer resampling it.

No need to change the sound pre-buffer or latency options unless you're having problems. I just wanted to have it as low as possible. If it's too low, you will start getting pops & clicks or crackling in the audio.

If you are using DirectSound output, set sampling rate and format to the highest options. With WASAPI output, set sampling rate to 96kHz if your hardware supports it, and the highest format supported. Generally there's no need to go beyond 96kHz. It may result in theoretically better resampling, but most (if not all) DAC chips actually perform worse once you go over 96kHz.

Time stretching will pitch-shift audio when slowing it down or speeding it up, to keep it at the original pitch. I do not recommend turning this on, as it is generally considered to be a lossy process, and the majority (if not all) of PAL or 24/1.001 content is not pitch-corrected, so it will actually play at the correct pitch with this option disabled.

Page 2: Set the "assumed framerate when not found" to what is most common with the formats you watch, or just leave it at <unknown>.

Page 3: I prefer to not have ReClock automatically load in any application - I only want it to load where specified. In my case, I just have it set as the default audio renderer in MPC-HC's preferences.


When playing a video, there is an additional preference dialogue you can bring up either from the tray icon (if enabled) or the filter list in your player.

http://www.abload.de/thumb/reclock-4yoyms.png (http://www.abload.de/img/reclock-4yoyms.png)

Under no circumstances should you enable the "slave reference clock to audio" option, as that effectively disables ReClock's resampling/sync corrections.

You should not use ReClock's V-Sync correction with madVR, or DSound resampling. (low quality) Most of these options are greyed out due to the other preferences I have set.

Note: Where ReClock says "Media Speed changed to 24.000fps" ignore it, it's not just outputting 24.000fps. It's a message that should have been changed a long time ago, but it seems no-one got round to it.

PAL SpeedDown is optional, and should only be enabled if you will be watching PAL film content, rather than PAL video content. (which is likely 25/50fps native) There is a corresponding option in madVR's preferences as well. If you are not watching PAL content (25/50fps) then it doesn't matter what this is set to.

Have you got the same comparison for JINC 3-4-8 with and without AR (or only if AR is already 'the best quality that we can have)Just thought I would mention that I did not miss this post, and I will try and get a comparison done soon. Hopefully by the end of the week.

njfoses
15th January 2013, 00:11
LAV Audio can do lossless decoding of DTS-HD and TrueHD. (DTS requires the Arcsoft dtsdecoderdll.dll copied into LAV's directory)

ReClock has to resample audio to work, but it is high quality, and any theoretical loss of quality should be imperceptible.
ReClock also gives you the option to upsample the audio if your hardware supports it, in which case there should be no loss in quality at all.
If you have CPU cycles to spare, you can also try this resampler.dll (http://www.datafilehost.com/download-dc45ff3d.html), which offers slightly better resampling, at a big CPU cost compared to the current resampler.


If you choose to bitstream, that means you are locked to the audio clock, rather than the refresh rate, which means either dropping/duplicating frames in order to keep video in sync with the audio (obvious stuttering) or allowing the audio to go out of sync.
Either of those options are far more destructive to film quality than ReClock's resampling.


I have never seen anyone able to output an exact 24/1.001 from an HTPC, and even with very minimal clock deviation (e.g. madVR reports one dropped frame every 5+ hours) while it may theoretically be one frame dropped outside the duration of the film, it usually tends to happen at least once if not more during playback despite that estimate, in my experience.


These are my ReClock settings - some of which you probably don't want to change, unless you're having problems.

http://www.abload.de/thumb/reclock-1t0pz7.png (http://www.abload.de/img/reclock-1t0pz7.png) http://www.abload.de/thumb/reclock-2wzotd.png (http://www.abload.de/img/reclock-2wzotd.png) http://www.abload.de/thumb/reclock-3f7o32.png (http://www.abload.de/img/reclock-3f7o32.png)

Page 1: WASAPI Exclusive output will bypass your drivers, and block all other system sounds. It will also throw up an error if your sampling rate, format, and the number of channels being played are not supported by your hardware. (LAV Audio has options for downmixing to a supported number of channels)

DirectSound output is easier, as it lets all other sounds play, and any output format will work - but that may result in the Windows Mixer resampling it.

No need to change the sound pre-buffer or latency options unless you're having problems. I just wanted to have it as low as possible. If it's too low, you will start getting pops & clicks or crackling in the audio.

If you are using DirectSound output, set sampling rate and format to the highest options. With WASAPI output, set sampling rate to 96kHz if your hardware supports it, and the highest format supported. Generally there's no need to go beyond 96kHz. It may result in theoretically better resampling, but most (if not all) DAC chips actually perform worse once you go over 96kHz.

Time stretching will pitch-shift audio when slowing it down or speeding it up, to keep it at the original pitch. I do not recommend turning this on, as it is generally considered to be a lossy process, and the majority (if not all) of PAL or 24/1.001 content is not pitch-corrected, so it will actually play at the correct pitch with this option disabled.

Page 2: Set the "assumed framerate when not found" to what is most common with the formats you watch, or just leave it at <unknown>.

Page 3: I prefer to not have ReClock automatically load in any application - I only want it to load where specified. In my case, I just have it set as the default audio renderer in MPC-HC's preferences.


When playing a video, there is an additional preference dialogue you can bring up either from the tray icon (if enabled) or the filter list in your player.

http://www.abload.de/thumb/reclock-4yoyms.png (http://www.abload.de/img/reclock-4yoyms.png)

Under no circumstances should you enable the "slave reference clock to audio" option, as that effectively disables ReClock's resampling/sync corrections.

You should not use ReClock's V-Sync correction with madVR, or DSound resampling. (low quality) Most of these options are greyed out due to the other preferences I have set.

Note: Where ReClock says "Media Speed changed to 24.000fps" ignore it, it's not just outputting 24.000fps. It's a message that should have been changed a long time ago, but it seems no-one got round to it.

PAL SpeedDown is optional, and should only be enabled if you will be watching PAL film content, rather than PAL video content. (which is likely 25/50fps native) There is a corresponding option in madVR's preferences as well. If you are not watching PAL content (25/50fps) then it doesn't matter what this is set to.

Just thought I would mention that I did not miss this post, and I will try and get a comparison done soon. Hopefully by the end of the week.



Thanks! This really helped me setup reclock.

njfoses
15th January 2013, 00:49
Is there anyway to automatically launch a file in full screen exclusive mode with mpc-hc? Right now once the file starts playing i have to right click and select fullscreen.

Neeto
15th January 2013, 00:58
Is there anyway to automatically launch a file in full screen exclusive mode with mpc-hc? Right now once the file starts playing i have to right click and select fullscreen.

There is a command line option that lets you do that.
Something like "fullscreen"

6233638
15th January 2013, 01:41
Is there anyway to automatically launch a file in full screen exclusive mode with mpc-hc? Right now once the file starts playing i have to right click and select fullscreen.I don't think it launches directly into fullscreen exclusive mode, but if you open MPC-HC's preferences, you can go to Playback > Fullscreen and enable the "Launch files in fullscreen" option.