Description of problem: Volume level lowers opening a media file using pulseaudio plugin. So, if you open a music file, the first time the level is high, but when you open another music file, audacious starts playing with a lower volume level and this step repeats itself with every follwinf music file you open until volume level reaches zero. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results:Volume lowers with each file Expected results:volume must stay at its last known level Additional info:
It's one of the many incarnations of bug 498158 and bug 488532 and lots of duplicates. Just recently, this has been worked around in GStreamer to fix Rhythmbox and Totem and other apps that use GStreamer, and it might be possible to add a similar work-around to Audacious' pulseaudio plugin. [Audacious upstream has killed the pulseaudio plugin, however, since they have received reports that the plugin would not work. So, it may be that one of the next releases of Audacious (e.g. 2.2) will remove that plugin.] But we can't upgrade to 2.1 or 2.2-alpha2 yet because of lots of problems not limited to audio playback.
Does this build fix the issue for you, too? http://koji.fedoraproject.org/koji/taskinfo?taskID=1754267 With "issue" I refer only to the volume decreasing with track changes. [...] [Please note that if you use external mixers / volume controls to alter the volume settings, Audacious older than 2.2 does not reflect that with its own volume slider. So, if you switch between multiple volume controls often, you can experience big jumps in volume level going up/down.]
Reading carefully through the bug reports you mentioned, I decided to update the gstreamer* packages from updates-testing repo first: gstreamer-plugins-good-devel-0.10.16-1.fc11.i586 gstreamer-plugins-flumpegdemux-0.10.15-6.fc11.i586 gstreamer-tools-0.10.25-1.fc11.i586 gstreamer-python-0.10.16-1.fc11.i586 gstreamer-devel-0.10.25-1.fc11.i586 gstreamer-plugins-base-0.10.25-1.fc11.i586 gstreamer-plugins-base-devel-0.10.25-1.fc11.i586 gstreamer-plugins-good-0.10.16-1.fc11.i586 gstreamer-plugins-ugly-0.10.12-2.fc11.i586 gstreamer-rtsp-0.10.4-1.fc11.i586 gstreamer-ffmpeg-0.10.8-1.fc11.i586 perl-GStreamer-0.15-1.fc11.i586 gstreamer-0.10.25-1.fc11.i586 totem-gstreamer-2.26.3-5.fc11.i586 Afterwards, i downloaded and installed the audacious-plugins* packages from the rpmbuild system from the link in your comment: Download/audacious-plugins-1.5.1-12.fc11.i586.rpm Download/audacious-plugins-amidi-1.5.1-12.fc11.i586.rpm Download/audacious-plugins-arts-1.5.1-12.fc11.i586.rpm Download/audacious-plugins-debuginfo-1.5.1-12.fc11.i586.rpm Download/audacious-plugins-esd-1.5.1-12.fc11.i586.rpm Download/audacious-plugins-jack-1.5.1-12.fc11.i586.rpm Download/audacious-plugins-metronome-1.5.1-12.fc11.i586.rpm Download/audacious-plugins-vortex-1.5.1-12.fc11.i586.rpm Download/audacious-plugins-wavpack-1.5.1-12.fc11.i586.rpm It seems to at least have solved my current problem although I'm not sure about the other plug-ins that have not been updated to the same version by this build: audacious-plugins-freeworld-1.5.1-2.fc11.i586 audacious-plugins-freeworld-alac-1.5.1-2.fc11.i586 audacious-plugins-freeworld-wma-1.5.1-2.fc11.i586 audacious-plugins-freeworld-tta-1.5.1-2.fc11.i586 audacious-plugins-freeworld-mp3-1.5.1-2.fc11.i586 audacious-plugins-freeworld-aac-1.5.1-2.fc11.i586 audacious-plugins-freeworld-mms-1.5.1-2.fc11.i586 Playing several mp3 files however, it all seems to do a very good job now. The playback volume stays at the same level all the time. So, I consider it to be solved, nice work. Regards, Eddie.
The amidi plugin seems to still use the alsa interface. This is what i get opening sky radio streaming audio: amidi-plug(amidi-plug.c:amidiplug_init:97): init, read configuration amidi-plug(i_backend.c:i_backend_load:107): loading backend '/usr/lib/audacious/Input/amidi-plug/ap-alsa.so' amidi-plug(i_backend.c:i_backend_load:145): backend /usr/lib/audacious/Input/amidi-plug/ap-alsa.so (name 'alsa') successfully loaded amidi-plug(b-alsa.c:i_configure_read_seq_ports_default:837): init, default values for seq ports detected: 17:0,17:1,17:2,17:3 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1800003 (Audacious) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1800003 (Audacious) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x180004e (Audacious ) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x180004e (Audacious ) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1800065 (Audacious ) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1800065 (Audacious ) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. amidi-plug(i_backend.c:i_backend_unload:164): unloading backend 'alsa' amidi-plug(i_backend.c:i_backend_unload:167): backend 'alsa' unloaded id3_file_vfsopen: file failed id3_file_vfsopen: file failed id3_file_vfsopen: file failed LASTFM: (cleanup) Cleanup finished
That just means that you haven't configured the amidi plugin yet. It defaults to playing MIDI files on MIDI capable audio hardware via ALSA. The alternative is to configure it to use the FluidSynth software synthesizer. Better disable/remove plugins you don't use.
Okay, I didn't knew that. And I do never play midi files anymore so i will remove it.
When I reboot and start audacious, volume is still going back by -1 or -2 but not by such huge steps anymore as it was before. Also, when I use the volume slider in audacious to set it back to my preferred level, it doesn't do this weird steps anymore. That is, of course, until I reboot the system again. Then it starts all over again. So, it's not completely solved as it seems.
How do you check that it's "-1 or -2"? Could you please post the output of grep vol ~/.config/audacious/config before you start Audacious after a reboot? (A reboot should not affect the internal volume levels at all, since the patched Audacious does only use what it has saved in its config file.)
I check that by observing the volume level which is shown when hovering the mouse pointer over the volume icon in the gnome panel. I also must correct my previous comment: I don't have to do a reboot. Just closing audacious and re-opening it by opening a different music source is enough to trigger the -1 decrease in volume level. grep vol ~/.config/audacious/config saved_volume=20817 software_volume_control=FALSE volume_right=1 volume_right=100 volume_right=100 volume_right=100 volume_left=100 volume_right=100 volume_right=100 volume_right=100 As long as I hold audacious open and changing music sources (after setting the volume once by moving the slider in audacious to the preferred level), the volume level remains unchanged. If I can provide more information to you please let me know, but I would not know how to describe in a different way. Regards, Eddie.
> saved_volume=20817 That is 81%. I can reproduce it. Volume decreases by 1%.
http://koji.fedoraproject.org/koji/taskinfo?taskID=1761670
Okay, this works. I tried it with both totem and audacious playing at the same moment using different volume levels and the levels are perfectly stored per application. I opened and closed them individually and both keep their original sound volume levels. This really looks very good! Thank you. Regards, Eddie.
Fix released in official update audacious-plugins-1.5.1-15.fc11 .