After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 657381 - [avidemux] Wrong duration reported in push mode
[avidemux] Wrong duration reported in push mode
Status: RESOLVED WONTFIX
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-08-25 20:49 UTC by Arnaud Vrac
Modified: 2012-01-18 12:56 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Arnaud Vrac 2011-08-25 20:49:41 UTC
Hi,

I have a few AVI files that do not report a correct duration when played using gstreamer, usually only a few seconds duration is reported.

This happens with a recent git checkout, and it also did in 0.10.28.

Here is a way to reproduce the issue:

gst-launch-0.10 -m souphttpsrc location='http://absolut.zogzog.org/share/samples/avi/big_buck_bunny_720p_surround.avi' ! avidemux ! progressreport update-freq=1 ! fakesink silent=true

progressreport shows a duration of 2 seconds. If I use filesrc instead of souphttpsrc 596 seconds is reported as expected.
Comment 1 Tim-Philipp Müller 2011-08-25 22:29:45 UTC
> gst-launch-0.10 -m souphttpsrc
> location='http://absolut.zogzog.org/share/samples/avi/big_buck_bunny_720p_surround.avi'
> ! avidemux ! progressreport update-freq=1 ! fakesink silent=true
> 
> progressreport shows a duration of 2 seconds.

I didn't look too deply, but that appears to be the duration according to the avi header.


> If I use filesrc instead of souphttpsrc 596 seconds is reported
> as expected.

Sure, in that case it can read additional info from the end as well (like the indices).


Try:

 souphttpsrc ... ! queue2 temp-template=/tmp/foo-XXXXXX  ! avidemux ....
Comment 2 Arnaud Vrac 2011-08-25 22:39:16 UTC
Hi Tim,

I know it works in push mode, I was just wondering if avidemux is bugged in push mode or if the wrong duration in the AVI file can be worked around. I'm using gstreamer on a system with limited memory and no local storage, so the queue file buffering is not an option.
Comment 3 Arnaud Vrac 2011-08-25 22:45:14 UTC
I meant I know it works in pull mode obviously.
Comment 4 Arnaud Vrac 2011-08-25 23:13:47 UTC
I have checked all the other AVI files I have that exhibit this behaviour and as you say, the number of frames in the stream is wrong for all of them.

A simple solution to my issue would be to make souphttpsrc in pull mode. Is that planned in the future ?

Thanks
Comment 5 David Schleef 2011-08-27 06:33:33 UTC
HTTP in pull mode would be rather ugly.  Every pull request (of which there are a lot) would require a round-trip to the server, which can be 100s of ms across the internet.  Smart caching and readahead would make this somewhat better, but not much.

If you want the capabilities of a streaming or play-while-downloading format, you need to use such a format, such as Ogg, Matroska, MPEG-TS, FLV, or ISO/QuickTime.
Comment 6 Vincent Penquerc'h 2012-01-18 12:56:21 UTC
Too intrusive a change to make for files with incorrect information in the first place. Closed as WONTFIX.