Le 13/10/2012 08:35, David Smith a écrit :
phonon-backend-vlc seems unable to manipulate the sound volume at some point; manually changing it (with the little speaker icon near the time counter) still works, but replaygain and fade are broken.Can you be more specific about "unable to manipulate the sound volume at some point"?
Sorry, I couldn't see how to describe this problem better : what I thought to be the "software" volume can be manipulated with Amarok's little speaker icon. But now, I'm not sure anymore that this icon represents "software" volume, because I just noticed that the volume buttons on my keyboard change both the master volume in veromix' plasmoid and on this little speaker icon in Amarok, which rather seems to represent VLC's volume in pulseaudio. Being a long-time Amarok user, I wrongly thought that this icon had the same function as the little volume slider that was at the same place in Amarok 1.
fade is not (yet) supported by VLC phonon backend for Amarok. VLC is simply lacking the implementation for the feature. See here: https://bugs.kde.org/show_bug.cgi?id=287124 Since fade is not supported by the VLC phonon backend, it's recommended to disable fade-out in Amarok when you use the VLC phonon backend.
I see. sorry, I didn't know. Now that you mention it, fade doesn't work with Gstreamer backend either (but replaygain does).
For ReplayGain, can you make sure you don't have conflicting gain tags? Check if your files have a replaygain_track_peak tag, and if so, remove it. As far as I know, Amarok itself does not calculate ReplayGain values, you need to have a 3rd party app calculate it and store the information in a ID3 tag. I have just tested using mp3gain from Wheezy with the Amarok from Wheezy and the ReplayGain feature in Amarok works fine for me here with both the gstreamer and vlc backends. Of course, I made sure ReplayGain was enabled in Amarok in the menu. If you've used older mp3gain versions, it's very possible you could end up with conflicting ReplayGain tags which is known to cause problems as Amarok doesn't know which tag to use and may decide to use the wrong one (or neither). Also, if you use a very old version of mp3gain, the tag might get ignored by Amarok completely.
Most of my files are Ogg, but neither my MP3 files nor my Ogg files have any replaygain tags in them (clementine, which can use replaygain values stored in files as tags but can't calculate them - just as you say Amarok 2 does - doesn't adjust the volume either).
IIRC Amarok 1 did calculate replaygain values (either by itself or by calling mp3gain/vorbisgain, I'm not sure) and stored them in its config directory. Since replaygain works in Amarok 2 with the Gstreamer backend, I think Amarok 2 imported these values from Amarok 1's configuration during first launch.
If you think this is normal behavior, feel free to close the bug, but again, Amarok 2 with gstreamer backend seems to actually use those replaygain values, which would indicate that they were correctly imported from Amarok 1, and that the VLC backend indeed have a problem using them.
To be honest, I don't really use phonon-backend-vlc, but back then, when I tried both backends in order to decide which one to use, I noticed this behavior, and now I decided to file a bugreport only to help the Debian project, so I reinstalled it solely to do some tests for this bugreport, but normally I use phonon-backend-gstreamer, I'm just waiting for #690291 to be fixed.
I admit this is weird that I seem to be the only one in the Debian users community to have these problems with both backends : I noticed them for a long time, but no one ever reported them, could they both be caused by another tool in the chain ? pulseaudio maybe ?
If you need more info, feel free to ask. Regards, -- Raphaël HALIMI