[gstreamer-bugs] [Bug 550274] no sound with sound blaster audigy se and ubuntu 8.04

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=550274

  GStreamer | gstreamer (core) | Ver: 0.10.18

Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |t.i.m at zen.co.uk
           Severity|blocker                     |normal
             Status|UNCONFIRMED                 |NEEDINFO




------- Comment #1 from Tim-Philipp Müller  2008-09-09 19:46 UTC -------
> miro, vlc and totem do not work.

This sounds very much like a configuration issue then, and not a
GStreamer-specific issue.


> In the ubuntu sound preferences the test buttons for 
> conferencing, music and movies, and sound events all produce a single
> tone when the test button is pressed and ALSA is selected 

That's good. That's the expected sound. If it works there, it should work in
totem-gstreamer and rhythmbox etc. too.

Are you actually using totem-gstreamer and not totem-xine? (The about dialog
from the totem Help menu will tell you)


> No sound is produced when the plugin is autodetect.

Right, that sounds a bit weird. Maybe you could run this:

 $ GST_DEBUG=*:5 gst-launch-0.10 audiotestsrc ! queue ! audioconvert !
autoaudiosink  2>dbg.log

and compress the log with 'bzip2 dbg.log' and then attach the log? (assuming
you don't get sound with this command line)


> Changing the setting in gstreamer-properties tends to mess something up
> in the card or ALSA which causes all applications that previously worked
> to play back way too fast and high pitched and still won't make any of
> the gstreamer applications work.
> Changing the setting back will not fix it. The only way I have found to fix
> it is to reboot the whole system.

That does sound like an alsa driver problem to me.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=550274.