ok, thanks.
All files are soft-telecined which can be verified by inspecting the top_field_first and repeat_pict flags of the stream, which show the expected cadence for 2:3 pulldown, like top_field_first = 001100110011..... and the repeat_pict flags = 01010101...... Hence the player can output the fields accordingly at 59.94 fields per second through its interface to an NTSC TV or similar device. On a progressive monitor or PC the frames are displayed at 23.97 fps as you noticed, as there is no need for "pulldown" of fields.
Basically this is the same for all 3 files (in 3 different containers), and when you get different results it's due to the player handling the containers/formats differently. I have seen this here as well. I am still of the opinion that hard-telecine is more "robust" for AVC on various playback scenarios and containers, but is less efficient (bigger files) as we know.
Quote:
|
MediaInfo identifies your .m2ts and .mkv file as progressive, and the .mp4 version as interlaced, bottom field first.
|
Yes, I have seen this. Inspecting the stream however indicates that only 2 of the first 4 frames are flagged as interlaced (probably an editing effect, orphaned field or something), all the rest is progressive frames. So MediaInfo might have been fooled. When I re-did this .mp4 for fixing the AR issue MediaInfo reported it as progressive (with interlace=fake) as well.