All-Star Superman Errors

[KYThrill]

MakeMKV 1.6.12 cannot properly process all the content on the All-Star Superman blu-ray. The blu-ray contains two bonus cartoon episodes recorded in 480i AVC. MakeMKV corrupts these streams to the point that they are completely unwatchable. MakeMKV returns no errors in the process.



I also have had problems muxing these streams with MKVMerge (streams extracted from tsMuxer and eac3to). I get similar macroblocking errors, but much less severe. MakeMKV is definitely the worst.

I did notice that MakeMKV lists the framrate on these streams as 120000/4004, whereas tsmuxer and eac3to listed them as 30000/1001.

Anyway, I can't find any tool capable of processing these 480i AVC streams. I thought maybe MakeMKV could work on it and be the first.

[setarip_old]

Hi!

I did notice that MakeMKV lists the framrate on these streams as 120000/4004, whereas tsmuxer and eac3to listed them as 30000/1001.

Do the math - they are equal ;>}

[KYThrill]

Unfortunately, math isn't involved here, but rather convention. To the video processor 120000/4004 wouldn't be equal to 30000/1001.

My unsderstanding is that 120000/4004 would be the naming convention used to indicate progressive NTSC. It is how a 480p30 framerate would be annotated to differentiate it from a 480i30 signal. However, the actual footage on the disc is 480i60, which is not progressive NTSC. Interlaced NTSC is 480i/30 (30000/1001).

So it looks like MakeMKV processes the 480i60 stream as if it is 480p30, and the result is the screen cap I posted. I don't think it should have ever been authored at 480i60 (should have been 480i30, but I'm betting the author had a brain fart regarding fields per second and frames per second), but blu-ray players can handle it and process it correctly, so I think MakeMKV should try to as well.

[mike admin]

From the MakeMKV's perspective 120000/4004 and 30000/1001 are equal - frame rate is only used to assign timecodes and the fact that you get no errors means that timecodes were assigned properly. I would blame the player first and it's MKV support in particular. Please try demuxing an MKV file produced by MakeMKV and muxing it back with mmg - you should get the same result as if muxing streams from original M2TS.

Can you open the file in handbrake?

[KYThrill]

From the MakeMKV's perspective 120000/4004 and 30000/1001 are equal - frame rate is only used to assign timecodes and the fact that you get no errors means that timecodes were assigned properly. I would blame the player first and it's MKV support in particular. Please try demuxing an MKV file produced by MakeMKV and muxing it back with mmg - you should get the same result as if muxing streams from original M2TS.

Can you open the file in handbrake?

Yep, it turned out to be the PC software players. The same files played fine on my Dune players.

But what is odd is that if I extracted with eac3to and muxed with mmg, the files would play on the software players, but with an occasional patch of macroblocking. But they were mostly viewable, nothing like the screen cap I posted. Oh well, not a mystery worth spending any time to solve. Playback works on all my primary media devices, just not the PC I rip with.