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 372660 - [FAQ] add section: what to do with media file that doesn't work
[FAQ] add section: what to do with media file that doesn't work
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: www
git master
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-08 21:04 UTC by Jaakko R
Modified: 2018-11-03 10:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jaakko R 2006-11-08 21:04:37 UTC
http://gstreamer.freedesktop.org/dev/ claims automated media tests are run regularly.  Latest results seem to be from Jan 2006.

Mayby a line of advise could be added about what to do with a list of favourite media files that refuse to function in Gstreamer but work ok in other applications.
Comment 1 Tim-Philipp Müller 2006-12-13 15:06:44 UTC
They are run regularly with various sets of files, but not automatically (the tests are 'automated' though in the sense that you throw a directory or bunch of files at it and it will go through each one and do the rest without further intervention). Runs are not always uploaded to the web site.

Some more recent runs have been added now, so changing bug to enhancement for better advise on what to do with media files that don't play.


> Mayby a line of advise could be added about what to do with a list of favourite
> media files that refuse to function in Gstreamer but work ok in other
> applications.

Not sure where to add this, this doesn't really belong on the 'Developers' page IMHO.

If you know how to, try GStreamer CVS first to see if the issues have already been fixed.

If not, please file bugs about them. It helps a lot if you can make those files available to the GStreamer developers somehow (e.g. by putting them up on a webspace/ftp server). If you get crashes, it helps a lot if you have a GStreamer build that has debugging symbols (ubuntu/debian have -dbg packages available for the core and all plugins, for example). (FWIW, there are known issues with asf/wmv/wma files and with .rm files.)

Comment 2 Edward Hervey 2013-07-18 04:45:16 UTC
Should we have a section somewhere in the docs or website about this ?

If a file doesn't work with your application
* Does it play correctly with gst-launch-1.0 playbin uri=... ?
  => If it does the probability is high that the bug is with the application's custom pipeline/sinks
* Open a bug
* Provide information from gst-discoverer-1.0 [<filename>|<uri>]
* If file is small enough, attach it
* If not upload it somewhere
 * Provide list of known/reliable upload sites ?

* Maybe we could provide a small shell script that runs the above, asks simple questions, grabs current versions of gstreamer/plugins, and outputs all of it in a file that people can attach to bugzilla ? Gentoo has a script that extracts information about your systems settings that you can/must then attach to any bug report. It helps speed up tracking down the issues.
Comment 3 GStreamer system administrator 2018-11-03 10:31:18 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/www/issues/1.