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 574882 - The volume slider should respond in real time
The volume slider should respond in real time
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: general
git master
Other All
: Normal minor
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
: 596818 (view as bug list)
Depends on: 513857
Blocks:
 
 
Reported: 2009-03-11 03:44 UTC by Andrés G. Aragoneses (IRC: knocte)
Modified: 2010-03-12 12:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andrés G. Aragoneses (IRC: knocte) 2009-03-11 03:44:59 UTC
Please describe the problem:
Just as like the Gnome volume slider, Banshee's one should modify the volume on real time (it doesn't do it for me, it changes like 3seconds after I move it).

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Alexander Kojevnikov 2009-03-11 03:59:23 UTC
It may be a dupe of bug 513857
Comment 2 Andrés G. Aragoneses (IRC: knocte) 2009-03-11 04:07:12 UTC
Marking dependency.
Comment 3 Gabriel Burt 2009-06-04 19:58:47 UTC
I thought Banshee used to intentionally delay the volume, I think to slowly fade to what you set it to, but afaict it doesn't do that anymore, and any delay is probably the bug Alexander mentioned.
Comment 4 Alexander Kojevnikov 2009-06-24 12:51:09 UTC
Marking as a dupe of bug 513857. I don't think working around GStreamer bugs is such a good idea.

*** This bug has been marked as a duplicate of 513857 ***
Comment 5 Andrés G. Aragoneses (IRC: knocte) 2009-09-30 15:30:20 UTC
*** Bug 596818 has been marked as a duplicate of this bug. ***
Comment 6 Andrés G. Aragoneses (IRC: knocte) 2010-03-12 12:48:02 UTC
This bug was closed as DUPE to a GStreamer's bug. However, Banshee just changed to use playbin2 (for the 1.5.5 release) and as a side-effect (I guess because of the change to playbin2) this bug was fixed without the duped bug being fixed necessarily, so I'm marking this bug as FIXED rather than DUPLICATED.