Bug 559692 - gstreamer/totem is unable to play 48000Hz *.wav
Summary: gstreamer/totem is unable to play 48000Hz *.wav
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: totem
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-28 18:45 UTC by Ralf Corsepius
Modified: 2010-12-03 23:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 23:41:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
result of: GST_DEBUG_NO_COLOR=1 GST_DEBUG=*:2 totem bugged.wav 2> log (1.88 KB, application/octet-stream)
2010-01-29 14:14 UTC, Ralf Corsepius
no flags Details
One of the *.wavs exposing the issue (118 bytes, application/octet-stream)
2010-02-01 09:30 UTC, Ralf Corsepius
no flags Details

Description Ralf Corsepius 2010-01-28 18:45:54 UTC
Description of problem:

totem/gstreamer is unable to play 48000Hz *.wavs.

Version-Release number of selected component (if applicable):

totem-2.28.5-1.fc12.x86_64
gstreamer-0.10.25.1-3.fc12.x86_64
gstreamer-plugins-good-0.10.17-3.fc12.x86_64

[And many more gstreamer-plugins]

How reproducible:
Always.

Steps to Reproduce:
1. Get a 48000Hz *wav (E.g. rip the audio track off from a DVD)
2. totem xxx.wav
3.
  
Actual results:

A dialog box pops up telling 
"An error occurred
Gstreamer encountered a general stream error"

Simultaneously, on a terminal, this error message appears:
* Message: Error: GStreamer encountered a general stream error.
gstwavparse.c(1638): gst_wavparse_stream_headers (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstDecodeBin2:decodebin20/GstWavParse:wavparse0:
Stream claims av_bsp = 24000000, which is more than 192000 - invalid data


Expected results:
Function.

Additional info:
* Many other audio/video players are able to play such files.
* Likely related to it: "Audio preview" of such files in nautilus also doesn't work.

Comment 1 José Matos 2010-01-28 19:40:51 UTC
I suspect that the component is wrong. :-)

You surely mean totem, not t1lib.

Comment 2 Ralf Corsepius 2010-01-29 05:06:09 UTC
(In reply to comment #1)
> I suspect that the component is wrong. :-)
> 
> You surely mean totem, not t1lib.    
Sorry, yes ... bugzilla's GUI :-)

Comment 3 Bastien Nocera 2010-01-29 12:15:36 UTC
Multiple things:
- Please provide a test file
- Update gstreamer-plugins-good to -4
- Test with gst-launch on the command-line as per http://projects.gnome.org/totem/#bugs

Comment 4 Ralf Corsepius 2010-01-29 14:12:45 UTC
(In reply to comment #3)
> Multiple things:
> - Please provide a test file
Unfortunately, all files exposing this issue, I currently have around, are copyrighted material, I don't have permission to distribute. 

I'll try to find one, I am allowed to distribute, but this may take time.

However, some interesting observations:
- An artificial file having been generated by audacity doesn't expose the issue.

- Comparing the real world case (bugged.wav) against an audacity generated file (noise.wav)

# ffmpeg -i bugged.wav
..
Input #0, wav, from 'bugged.wav':
  Duration: 00:00:04.91, bitrate: 192000 kb/s
    Stream #0.0: Audio: pcm_s16le, 48000 Hz, 2 channels, s16, 1536 kb/s

# ffmpeg -i ~/Music/noise.wav 
..
Input #0, wav, from 'noise.wav':
  Duration: 00:01:00.00, bitrate: 1536 kb/s
    Stream #0.0: Audio: pcm_s16le, 48000 Hz, 2 channels, s16, 1536 kb/s

> - Update gstreamer-plugins-good to -4
Installed, same issue.

> - Test with gst-launch on the command-line as per
> http://projects.gnome.org/totem/#bugs    

# gst-launch-0.10 playbin2 uri=file:$(pwd)/bugged.wav

(gst-launch-0.10:4747): GLib-WARNING **: g_set_prgname() called multiple times
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
ERROR: from element /GstPlayBin2:playbin20/GstURIDecodeBin:uridecodebin0/GstDecodeBin2:decodebin20/GstWavParse:wavparse0: GStreamer encountered a general stream error.
Additional debug info:
gstwavparse.c(1638): gst_wavparse_stream_headers (): /GstPlayBin2:playbin20/GstURIDecodeBin:uridecodebin0/GstDecodeBin2:decodebin20/GstWavParse:wavparse0:
Stream claims av_bsp = 24000000, which is more than 192000 - invalid data
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
Freeing pipeline ...

# gst-launch-0.10 playbin uri=file:$(pwd)/bugged.wav

(gst-launch-0.10:4760): GLib-WARNING **: g_set_prgname() called multiple times
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
ERROR: from element /GstPlayBin:playbin0/GstDecodeBin:decodebin0/GstWavParse:wavparse0: GStreamer encountered a general stream error.
Additional debug info:
gstwavparse.c(1638): gst_wavparse_stream_headers (): /GstPlayBin:playbin0/GstDecodeBin:decodebin0/GstWavParse:wavparse0:
Stream claims av_bsp = 24000000, which is more than 192000 - invalid data
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
Freeing pipeline ...

Comment 5 Ralf Corsepius 2010-01-29 14:14:42 UTC
Created attachment 387573 [details]
result of: GST_DEBUG_NO_COLOR=1 GST_DEBUG=*:2 totem bugged.wav 2> log

Comment 6 Bastien Nocera 2010-01-29 14:59:24 UTC
Unless proven otherwise, I'd say the files are broken. Please provide a test file, even if just the first meg of it, either in private or publically, it would be enough for testing.

Comment 7 Ralf Corsepius 2010-01-29 15:09:35 UTC
You can generate such files yourself if you want to - Take an arbitrary dvd and try:

transcode -i /dev/sr0 -T 1,1 -y wav -m test.wav

Comment 8 Bastien Nocera 2010-01-29 15:29:12 UTC
Don't have time for that, sorry.

Comment 9 Ralf Corsepius 2010-02-01 09:30:00 UTC
Created attachment 387996 [details]
One of the *.wavs exposing the issue

The contents is "just silence" ;)

This file originates from me recording ca. 30 seconds of "antenna unplugged video signal" with my HDR (i.e. video noise + audio silence), then burning this video to DVD, then ripping the audio signal off the DVD:

transcode -i /dev/sr0 -T1,-1 -a0 -y wav -m HDR01.wav

ffmpeg reports the corresponding HDR01.mpg to contain:
...
    Stream #0.0[0x1e0]: Video: mpeg2video, yuv420p, 720x576 [PAR 16:15 DAR 4:3], 4620 kb/s, 25 tbr, 90k tbn, 50 tbc
    Stream #0.1[0x80]: Audio: ac3, 48000 Hz, stereo, s16, 256 kb/s
...

Comment 10 Bug Zapper 2010-11-03 23:41:18 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 11 Bug Zapper 2010-12-03 23:41:00 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.