[gstreamer-bugs] [Bug 168406] asfdemux always uses 25fps

bugzilla-daemon at bugzilla.gnome.org bugzilla-daemon at bugzilla.gnome.org
Fri Apr 15 04:24:59 PDT 2005


Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.

 http://bugzilla.gnome.org/show_bug.cgi?id=168406
 GStreamer | gst-plugins | Ver: HEAD CVS





------- Additional Comments From Ronald Bultje  2005-04-15 07:24 -------
Created an attachment (id=45289)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=45289&action=view)
first try

So, the attached patch implements rude FPS detection, which works OK for some
movies. However, for others, it doesn't work at all. Reason is timestamps in
ASF:

Time: 0:00:29.666000000
Time: 0:00:29.733000000
Time: 0:00:29.800000000
Time: 0:00:29.866000000
Time: 0:00:29.933000000
Time: 0:00:30.000000000
Time: 0:00:30.066000000
Time: 0:00:30.133000000
Time: 0:00:30.200000000
Time: 0:00:28.352000000
Time: 0:00:30.333000000
Time: 0:00:30.400000000
Time: 0:00:30.466000000
Time: 0:00:30.533000000
Time: 0:00:30.600000000
Time: 0:00:30.666000000
Time: 0:00:28.928000000
Time: 0:00:30.800000000
Time: 0:00:30.866000000

I don't know how come, but video is way ahead of audio. Also, it's very choppy,
probably for the same reason (i.e. sometimes it processes 10 frames in a snap,
sometimes it hangs for a second). Apparently, the early timestamps are
I-frames, and are wrong, but because they are I-frames, ffmpeg uses them as
base for timestamping. I'll need to see how other apps solve this issue.

------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact for the bug.




More information about the Gstreamer-bugs mailing list