Opened 18 months ago

Last modified 18 months ago

#13753 assigned bug

MediaPlayer assumes all videos have a fixed framerate

Reported by: pulkomandy Owned by: stippi
Priority: normal Milestone: Unscheduled
Component: Applications/MediaPlayer Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

MediaPlayer video timing is all frame-based and assumes frames are equally spaced in the video stream. This is not the case, ffmpeg may prodice frames with variable presentation time for various reasons (corrupt file, frame rate change in the middle of the stream, optimization by skipping identical frames, ...)

The time should be retrieved from the media_header.start_time for each frame, but MediaPlayer completely ignores this and compute the times itself using only the stream frame rate.

As a result, all efforts on media kit side to provide proper timings for the frames won't help MediaPlayer (but will help eg. WebPositive html5 video, which does this properly)

Change History (1)

comment:1 Changed 18 months ago by stippi

I thought this was compensated by MediaPlayer asking for a frame at a given time. The codec or reader may then return the same (buffered?) frame again, which is inefficient, but at least it should work more or less.

Note: See TracTickets for help on using tickets.