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 600307 - Gstreamer isn't able to decode a loosless wma version 4 while xine can.
Gstreamer isn't able to decode a loosless wma version 4 while xine can.
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-libav
0.10.23
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-01 13:47 UTC by Laurent Peuch
Modified: 2010-05-30 12:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Laurent Peuch 2009-11-01 13:47:29 UTC 
Hello,

I'm using Gstreamer 0.10.23 with Totem under ubuntu jaunty 9.4 and I'm not able to play a lossless .wma version 4 with while xine is able to decode it.

I've spend some installing nofree pkg in hope to make it work but nothing work.

Totem always try to search for a codec and isn't able to find any.

This has been confirmed by 2 others person (the incapacity to play the file with gstreamer).

I've attached an incriminate file.

File free to ask me more details,

Regards,

Laurent Peuch
Comment 1 Laurent Peuch 2009-11-01 13:56:31 UTC 
Damn, the file is to big to be attached. 
Btw Tim-Philipp Müller and Zaheer Abbas Merali both have a sample file.
Comment 2 Wim Taymans 2009-11-02 09:50:27 UTC 
xine is probably using the win32 codecs. Maybe it works with pitfdll
Comment 3 Edward Hervey 2010-03-04 09:06:13 UTC 
Laurent, can you try with latest 0.10.9.x pre-release of gst-ffmpeg ?
Comment 4 Laurent Peuch 2010-03-11 23:04:24 UTC 
Hello, I've tried to compiled it but I lack of free time to do this, maybe another day.

If some .deb/binary/ppa for karmic exist tell me please.
Comment 5 Tobias Mueller 2010-05-30 12:06:45 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!