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 511543 - cannot transcode wmv via mms to vorbis
cannot transcode wmv via mms to vorbis
Status: RESOLVED DUPLICATE of bug 351742
Product: GStreamer
Classification: Platform
Component: gst-plugins-ugly
0.10.6
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-23 13:53 UTC by Ingo Planz
Modified: 2011-05-19 06:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Ingo Planz 2008-01-23 13:53:07 UTC
Please describe the problem:
When trying to transcode the audio part of a mms stream to ogg vorbis, the resulting ogg is broken. That is, ogginfo says

  Warning: sequence number gap in stream 1. Got page 3 when expecting page 2. Indicates missing data.

and playing it with ogg123 sounds garbled. While running, vorbisenc keeps emitting  the "encoding at quality level x" message. 

IIRC this might be related to discontinous timestamps and the way vorbisenc deals with them, but I can't find that bug report again; Sorry for probably reposting this...


Steps to reproduce:
gst-launch-0.10 mmssrc location="mms://c36000-o.w.core.cdn.streamfarm.net/36000zdf/ondemand/3546zdf/zdf/3sat/ard/ard_80121_begegnungen_broder_vh.wmv" ! decodebin2 ! audioconvert ! progressreport ! vorbisenc ! oggmux ! filesink location="audio.ogg" -v


Actual results:
a broken ogg vorbis of the audio channel is created

Expected results:
the videos audio channel transcoded to an ogg vorbis audio

Does this happen every time?
yes. And with any mms server I've tried so far.

Other information:
gstreamer and libs as provided by ubuntu 7.10 i386
Comment 1 Ingo Planz 2008-01-24 09:20:55 UTC
Found the bug I mentioned: bug #351742 might be related
Comment 2 Sebastian Dröge (slomo) 2011-05-19 06:25:40 UTC
Let's close this as a duplicate of bug #351742 then? Feel free to reopen if the problem still exists and if it is not bug #549940.

*** This bug has been marked as a duplicate of bug 351742 ***