Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#26497 - gstreamer0.10-ffmpeg issue: developers switched to libav

Attached to Project: Arch Linux
Opened by daimonion (demon) - Monday, 17 October 2011, 23:33 GMT
Last edited by Ionut Biru (wonder) - Saturday, 22 October 2011, 16:20 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Developers of gstreamer have decided to switch to libav (a fork of ffmpeg) as of version 0.10.12. Some of the functions libav provides are not the same as in ffmpeg, and there's a problem: any application that depends on those ffmpeg function calls (from gstreamer0.10-ffmpeg plugin) will not function (example:  FS#26165 , or Clementine, etc). Downgrading to version 0.10.11 of the plugin solves all problems.

There's nothing much to do at the moment, except to revert to v0.10.11. Or, to provide libav package alongside the plugin (haven't tried this yet, and I think it's a no go).

Perhaps we should notify developers and ask them to return to ffmpeg?
This task depends upon

Closed by  Ionut Biru (wonder)
Saturday, 22 October 2011, 16:20 GMT
Reason for closing:  Not a bug
Comment by daimonion (demon) - Monday, 17 October 2011, 23:41 GMT
http://gstreamer.freedesktop.org/releases/gst-ffmpeg/0.10.12.html
Comment by Ionut Biru (wonder) - Tuesday, 18 October 2011, 05:29 GMT
sure, notify yourself the developers. you seem to understand better what it happens.

imo switching to libav shouldn't affect applications that relies on gstreamer-ffmpeg and if it does then is a bug in gstreamer.
Comment by daimonion (demon) - Tuesday, 18 October 2011, 20:20 GMT
OK, I'll look into this deeper. But the more I dig the less I seem to understand what is the actual problem here.
Comment by daimonion (demon) - Wednesday, 19 October 2011, 17:55 GMT
This is what is causing problems:
http://cgit.freedesktop.org/gstreamer/gst-ffmpeg/commit/?id=2de5aaf22d6762450857d644e815d858bc0cce65

Developers of gst-ffmpeg decide to "switch off" this codec, forcing users to use gstreamer-ugly plugin set. I don't agree with this, so, patch included (in case someone is interested), bug resolved.
   mp3enable.patch (0.5 KiB)
Comment by Ionut Biru (wonder) - Wednesday, 19 October 2011, 18:03 GMT
we agree with gstreamer developers. install gstreamer0.10-ugly and get over it.
Comment by daimonion (demon) - Friday, 21 October 2011, 22:00 GMT
Ok, did. Really, there were some problems with this codec in gstreamer. :(
Close this, please. Thanks.

Loading...