I tediously went through the entire list of published 10-bit 4:4:4 encodes here (
http://tasvideos.org/Ilari/Encodes10Bit444.html ) and checked for issues by downloading each 10-bit 4:4:4 encode. Here are my findings.
These lists are only concerned with the 10-bit 4:4:4 encodes on the linked pages. I didn't check the 8-bit encodes for these publications because I don't care enough about them and they probably have their own sets of issues.
---
This first list denotes 10-bit 4:4:4 encodes which use limited-range YUV. All of these are also flagged as full-range, causing a very visible range problem in correct video playback systems. I checked by using LAV Video Decoder 0.47 with output range set to "untouched" and all output colorspaces disabled except RGB24 and RGB32 in MPC-HC with madVR. If the video showed limited range, I then switched output range in LAV Video Decoder to "PC" to check if the encode belongs in the next list rather than this one. The name in brackets is the encoder who made the video. I don't mean any offense by including this data. I'm just trying to help tasvideos produce quality publications.
http://tasvideos.org/10M.html (ledauphinbenoit)
http://tasvideos.org/24M.html (ledauphinbenoit)
http://tasvideos.org/46M.html (ledauphinbenoit)
http://tasvideos.org/88M.html (ledauphinbenoit)
http://tasvideos.org/252M.html (ledauphinbenoit)
http://tasvideos.org/637M.html (ledauphinbenoit)
http://tasvideos.org/651M.html (ledauphinbenoit)
http://tasvideos.org/1849M.html (Lex; won't re-dump since this run was hell to dump, but if the full-range flag can be toggled, that could work)
http://tasvideos.org/1918M.html (omnipotententity)
http://tasvideos.org/1921M.html (ledauphinbenoit)
http://tasvideos.org/1924M.html (Dacicus)
http://tasvideos.org/1927M.html (grunt)
http://tasvideos.org/1928M.html (ledauphinbenoit)
http://tasvideos.org/1930M.html (ledauphinbenoit)
http://tasvideos.org/1934M.html (ledauphinbenoit)
http://tasvideos.org/1935M.html (Dacicus)
http://tasvideos.org/1936M.html (ledauphinbenoit)
http://tasvideos.org/1941M.html (ledauphinbenoit)
http://tasvideos.org/1943M.html (ledauphinbenoit)
http://tasvideos.org/1944M.html (ledauphinbenoit)
http://tasvideos.org/1945M.html (Dacicus)
http://tasvideos.org/1946M.html (Dacicus)
http://tasvideos.org/1950M.html (ledauphinbenoit)
http://tasvideos.org/1959M.html (omnipotententity)
http://tasvideos.org/1967M.html (Dacicus)
http://tasvideos.org/1976M.html (ledauphinbenoit)
http://tasvideos.org/1978M.html (omnipotententity)
http://tasvideos.org/1981M.html (ledauphinbenoit) <-- This was the last encode on
the list at the time I made this post.
http://tasvideos.org/1997M.html (omnipotententity; also, slightly late audio with some splitters and soft subtitle issues; recommend using mkv with .ass subtitles)
---
This second list denotes 10-bit 4:4:4 encodes which use limited-range YUV and are also flagged that way. This is not ideal, but at least they look good enough when played with range upscaling, which correct video playback systems will do. These, I would say, are low priority.
http://tasvideos.org/1882M.html (grunt)
http://tasvideos.org/1917M.html (turska)
http://tasvideos.org/1937M.html (omnipotententity)
http://tasvideos.org/1940M.html (omnipotententity)
---
other oddities:
http://tasvideos.org/756M.html (8-bit encode (by adelikat) uses limited range with limited range flag set in stream; is avi. also, archive.org links are swapped, causing me to have downloaded the 8-bit 4:2:0 encode instead of the 10-bit 4:4:4 encode at first, hence the analysis of the 8-bit encode)
http://tasvideos.org/1269M.html (BrandonE; a/v desync; very late audio)
http://tasvideos.org/1588M.html (BrandonE; a/v desync; very late audio)
---
I will be updating this post as encodes get fixed. If you fix something, please post and I'll update.
You can check what filters are currently in use like this (loaded video in screenshot is irrelevant):
Here, you can see I have Haali splitter ("Haali Media Source") in use for this particular file, which happens to be an mkv. If the loaded file was an mp4 file (such as the file we're discussing), you would see "LAV Splitter Source" there instead in my setup. With MPC-HC's internal mp4 splitter, you would see "MPC MP4/MOV Source". I can reproduce your issue, and I'm pretty sure that's it.
