You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MP4 edit list atoms('moov'/'trak'/'edts'/'elst') contain a table of edits, each with three entries. The entries are, loosely, duration, start, speed.
duration is given in movie timescale units(listed in 'moov'/'mvhd')
start is given in media timescale units(listed in 'moov'/'trak'/'mdia'/'mdhd')
speed is a unitless fixed-point number
I think that mediainfo's --details=1 human-readable output presents start using the same units as duration, as opposed to the timescale given in the track's media header.
The fix for this may require some inconvenient, out-of-order precessing. An alternate solution would be to present this value using some unit like "ticks" instead of converting to seconds.
The text was updated successfully, but these errors were encountered:
MP4 edit list atoms('moov'/'trak'/'edts'/'elst') contain a table of edits, each with three entries. The entries are, loosely,
duration, start, speed
.duration
is given in movie timescale units(listed in 'moov'/'mvhd')start
is given in media timescale units(listed in 'moov'/'trak'/'mdia'/'mdhd')speed
is a unitless fixed-point numberI think that mediainfo's
--details=1
human-readable output presentsstart
using the same units asduration
, as opposed to the timescale given in the track's media header.The fix for this may require some inconvenient, out-of-order precessing. An alternate solution would be to present this value using some unit like "ticks" instead of converting to seconds.
The text was updated successfully, but these errors were encountered: