Bug 184732 - Phonon::VolumeFaderEffect doesn't maintain state with Xine backend
Summary: Phonon::VolumeFaderEffect doesn't maintain state with Xine backend
Status: RESOLVED FIXED
Alias: None
Product: Phonon
Classification: Frameworks and Libraries
Component: Xine backend (show other bugs)
Version: 4.3.0 (KDE 4.2.0)
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Matthias Kretz
URL:
Keywords:
: 249942 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-02-18 00:07 UTC by Thorsten Mühlfelder
Modified: 2010-12-14 00:12 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thorsten Mühlfelder 2009-02-18 00:07:52 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Unspecified

If ReplayGain is used with Xine backend it does not work (does not change volume). It works with GStreamer backend though.
Comment 1 Mark Kretschmann 2009-02-18 07:56:10 UTC
Shouldn't this be reported to Phonon, instead of Amarok?

Reassigning the report.


Also see related report for more info:

https://bugs.kde.org/show_bug.cgi?id=81661
Comment 2 Thorsten Mühlfelder 2009-02-18 12:35:53 UTC
I don't know where the bug is. Perhaps it's even in Xine ;-)
Comment 3 Alex Merry 2009-02-19 20:51:05 UTC
A brief description of the actual problem:

The VolumeSlider implementation for the Xine backend reverts to full volume as soon as the fade is complete.  This also means that setVolume() has no effect.

VolumeSlider works as expected with the GStreamer backend.
Comment 4 Alex Merry 2009-02-19 21:24:49 UTC
Not thinking straight... for VolumeSlider, read VolumeFaderEffect.
Comment 5 Alex Merry 2009-02-22 00:44:39 UTC
Re-assigning to Matthias Kretz because he knows the code.
Comment 6 Thorsten Mühlfelder 2009-06-17 14:05:03 UTC
Any progress on this problem?
Comment 7 Myriam Schweingruber 2009-11-08 20:00:07 UTC
Closed in r1028879
Comment 8 Myriam Schweingruber 2010-12-14 00:12:19 UTC
*** Bug 249942 has been marked as a duplicate of this bug. ***