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 93195 - let's get a media test going
let's get a media test going
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: 0.5.0
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-09-13 10:27 UTC by Thomas Vander Stichele
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Thomas Vander Stichele 2002-09-13 10:27:44 UTC 
We need a media regression test.

What we need for that to happen is :

a) a bunch of good, well-described (format-wise) test files
b) an md5sink plug-in (which company wrote, we need to check if it's still ok)
c) a simple app that runs an md5test, and can retrieve the md5sum on eos
d) something that tests if gstreamer detects the right plug-in to use and
   so on

This shouldn't be that hard to do at all.

Please comment for further ideas
Comment 1 David Schleef 2003-05-02 03:53:37 UTC 
One component that we need is the ability to emulate a videosink like
xvideosink, and then tee off the frames so that they can be tested.

For example,

  filesrc location=AlienSong.mpg ! spider ! md5sum

doesn't currently work, nor would it do what we want.
Comment 2 Benjamin Otte (Company) 2003-05-02 16:28:12 UTC 
It would work if you used filtered links on the last link.
But you can currently only do this by writing code.
Comment 3 David Schleef 2003-09-12 11:04:57 UTC 
We'll say this is done, even though we just have prototypes.