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 114972 - gdk_pixbuf decoder/encoder plugin
gdk_pixbuf decoder/encoder plugin
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: Normal normal
: 0.7.x
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-06-11 21:13 UTC by David Schleef
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Schleef 2003-06-11 21:13:08 UTC
I've discovered a number of QuickTime movies that are sequences of gif
images.  I would not be surprised to see other image formats.
Comment 1 Ronald Bultje 2003-06-11 22:34:02 UTC
Funnily, libs liek ffmpeg, mplayer (lib?) etc. also implement their
own image loader, so why don't we? Although it sounds interesting to
test out subclassing here, I don't think we'll gain anything by it
(unfortunately).

We already have jpegenc(broken)/dec and pngenc, how about implementing
some more (pngdec, gif, maybe others)? We can copy the actual
loading/saving code (this is only a few lines) from gdkpixbuf, of
course, but it'd make us not depend on gdkpixbuf for this feature,
which is a good thing if KDE would want to use such a feature later on.
Comment 2 David Schleef 2003-06-11 22:50:11 UTC
Good point.  We would only be using a fraction of gdk_pixbuf's capability.

However, I have little interest in writing yet another generic image
loader when gdk_pixbuf is readily usable.  So if I write it, it will
use gdk_pixbuf directly.  If anyone cares, I can write it in such a
way that the gdk_pixbuf code can be copied into GStreamer and used if
gdk_pixbuf is not found on the system.
Comment 3 David Schleef 2003-06-30 21:40:37 UTC
In HEAD CVS.  If someone wants it in 0.6, file a new backport bug.