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 648717 - Subwoofer turned off in pulseaudio when manually playing a track
Subwoofer turned off in pulseaudio when manually playing a track
Status: RESOLVED NOTGNOME
Product: GStreamer
Classification: Platform
Component: dont know
unspecified
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-04-27 00:20 UTC by Gaz Davidson
Modified: 2011-06-14 16:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
pulselog (939.51 KB, text/plain)
2011-04-27 00:20 UTC, Gaz Davidson
Details
bansheelog (49.72 KB, text/plain)
2011-04-27 00:21 UTC, Gaz Davidson
Details

Description Gaz Davidson 2011-04-27 00:20:26 UTC
Created attachment 186698 [details]
pulselog

Background:

I'm using a 7.1 surround sound system and Ubuntu 11.04, pulseaudio 0.9.22-24-g67d18 and banshee 2.0 nightly from the 23rd of April. 

Starting a track by double clicking or manually track skipping causes the bass channel to be muted in pulseaudio.

Steps:

1) I start pulseaudio and banshee in debug mode as per instructions from dneilsen on IRC, the log files are attached. 

2) I open Gnome's volume preferences and select the 7.1 surround sound option.

And I make a note of the position in the logs:

pulselog @ 683.533
bansheelog @ 00:25:44.107

3) I double click a track in Banshee and it plays The track sounds tinny, no sound is played back by my sub-woofer.

pulselog: 802.828 --- see output 05 is now muted, this is my sub 
          802.836 --- stuff has finished happening

bansheelog: 00:29:30.785 --- track is playing

3) While the track is playing, I adjust the volume preferences by changing the drop-down to 4.0 surround sound and back to 7.1 again, the bass returns and vibrates the entire room (which is nice).

pulselog: 987.469 --- oh hallo there Mr. bass!
bansheelog: no new log events

4) I then wait around until the end of the track, but because I'm slow and clumsy two track changes happen before I get round to noting the log positions. My sub-woofer is not muted, so 

pulselog: 1032.786 --- no reset and reams of text between automatic track changes
bansheelog: 00:34:18.711 to 00:35:17.394 --- two track changes in here.

5) I then pause the track from the volume widget thingy at the top of the screen next to the time. 

pulselog: 1208.476 --- not much happening here
banshee: 00:36:11.427 --- single event

6) Then click play again to resume the track. The sub-woofer is still working, I am happy :)

pulselog: 1247.832 --- nothing exciting happening here
banshee: 00:36:55.781 --- another single line

7) I then click the next track button because I didn't really like that track anyway. The next track is played without the sub-woofer, I am sad :(

pulselog: 1296.693 --- that's where my bass went
Comment 1 Gaz Davidson 2011-04-27 00:21:26 UTC
Created attachment 186699 [details]
bansheelog

The "bansheelog" mentioned above
Comment 2 David Nielsen 2011-04-27 03:43:40 UTC
Adding Sjoerd Simons to cc for PulseAudio insight on the advice of Jo Shields.
Comment 3 Gaz Davidson 2011-04-27 15:31:11 UTC
I just tried in Rhythmbox and the same behaviour is seen when double clicking on a song, so more likely a pulseaudio or GStreamer issue?
Comment 4 David Nielsen 2011-04-27 17:08:29 UTC
It is not a Banshee issue at least. I will reassign this to GStreamer and they will determine if this is something they are causing, I would also encourage you to file a bug against PulseAudio in your distribution and linking this report.
Comment 5 Sebastian Dröge (slomo) 2011-04-29 07:43:31 UTC
Sounds more like a pulseaudio problem. Do you get the same behaviour if you use a different player that uses pulseaudio but not gstreamer?
Comment 6 Gaz Davidson 2011-06-14 14:51:20 UTC
Yes it did turn out to be a Pulseaudio bug, as it also happens to Flash videos in web pages. Haven't had time to re-test and submit to my distro yet