-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mismatch in container and video duration for MPEG-TS #2087
Comments
The |
@plondino I implemented in #2073 what was buggy from my point of view but I am not sure that it is what you expect. General duration is now coherent with file size and overall bit rate (duration = file size * 8 / overall bit rate), it is the duration of the content transmission as indicated by the TS stream. It is not based on the duration of any A/V stream. When you say:
I don't consider as an issue directly, because the transmission duration could be 32.32s due to some small p/b frames at the end, no need of 32.65s for transmitting 32.65s of content. What is your idea behind this ticket? What do you expect from General duration not in other parts of MediaInfo? With an example, could you say what value you expect? Currently MI has: General duration is less than any stream in this example because the transmission was faster than any content. If something else is expected, is it max (A/V ends) - min (A/V starts) = 1.50s, max (max(A/V end per program) - min(A/V start per program)) = 1.20s, something else? You can test the latest dev snapshots knowing that this is maybe not as you expect due to a different idea we have of general duration field. |
I have an MPEG TS file that has a mismatch in the container and video duration:
The video reports:
A duration of 961 frames at 30000/1001 should be ~32.65s so not clear why the general section reports the duration as 32.32s.
I can provide a sample file if necessary.
The text was updated successfully, but these errors were encountered: