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 610086 - Needs playbin2 debug/test app
Needs playbin2 debug/test app
Status: RESOLVED DUPLICATE of bug 553520
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-02-16 10:28 UTC by Bastien Nocera
Modified: 2013-08-16 11:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bastien Nocera 2010-02-16 10:28:49 UTC 
Currently, Totem is the de facto test application for some basic features of GStreamer, such as seeking, subtitle and audio tracks handling.

GStreamer (probably gst-plugins-base) should ship with a test application for those features, which, when bugs are replicated using it, can point to GStreamer bugs, instead of possible Totem bugs.

The "seek" test application in gst-plugins-base is already a good start for seeking testing.
Comment 1 Sebastian Dröge (slomo) 2011-05-23 15:00:56 UTC 
What exactly is missing in tests/examples/seek.c? It also has support for selecting different streams and subtitles
Comment 2 Bastien Nocera 2011-05-26 16:28:59 UTC 
(In reply to comment #1)
> What exactly is missing in tests/examples/seek.c? It also has support for
> selecting different streams and subtitles

It's not shipped is the problem. So it's not in the packages, and then not on end-user's machines to reproduce problems.
Comment 3 Tim-Philipp Müller 2011-05-26 16:37:28 UTC 
Not sure the seek app is something that should be installed ...

I agree that there should be something other than totem though.
Comment 4 Sebastian Dröge (slomo) 2013-08-16 11:54:49 UTC 
Let's mark this as a duplicate of the other bug about this ;)

*** This bug has been marked as a duplicate of bug 553520 ***