I seem to have stumbled upon a new sort of H.264 spec, which not only can’t play on the WD TV, it prevents any other file to play afterwards and requires a reset.
I’ve tried looking at the codec specifications, but I can’t find a difference between them and videos that do play. They aren’t corrupt, as they do play on the PC. If I transcode with Handbrake, it’s fixed, but that takes far too long.
Well, that’s the thing, I don’t know what it is. All I have are a few movies that do this and a bunch that don’t. mkvinfo doesn’t tell me anything, but maybe I’m not looking in the right place.
IceBone wrote:> I seem to have stumbled upon a new sort of H.264 spec, which not only can’t play on the WD TV, it prevents any other file to play afterwards and requires a reset.
Anyone have any idea where for the problem?
I’d bet quite a lot of money that it isn’t the codec, but the header compression issue.
The only difference between High@L4.0 and High@L4.1 is the bitrate – 4.0 allows up to 25 mbit and 4.1 allows up to 50mbit. So, it’s possible that a player could handle 4.0 but not 4.1, but the other way around is quite unlikely. That’d be like an audio player that could handle 320kbit mp3 files but couldn’t play 192kbit files.
And it wouldn’t be a "new spec. " 4.1 is newer than 4.0. I think that’s why they don’t have to list 4.0, since they list 4.1.
That’s what I thought, I was just thinking there were some new settings, which aren’t supported. I know that some old divx players couldn’t play xvid with more than 2 consecutive b-frames or GMC.
So… about your header compression issue… how could I check for that?
You could try re-muxing one of your “broken” files in MKVmerge GUI. What version do you have? If it’s 4.1.0 or later, you’ll just need to disable header compression and save as a new file, shouldn’t take long.
Alternatively, there’s a tool specifically for fixing MKVs on older WD players available here:
The package includes a commandline tool called mkWDclean. Don’t have first-hand experience with this one (was never affected by header compression issue).
Refer to the second post in this thread on a program which will fix the header compression. The post also includes a screenshot which shows which box to check in the options window to properly fix the issue when you remux…