Bug 13396 - Single IR event causes multiple volume up steps
: Single IR event causes multiple volume up steps
Status: CLOSED FIXED
Product: SB Radio
Classification: Unclassified
Component: Menus
: Include FW version in comment
: PC Other
: P1 normal (vote)
: 7.4.0
Assigned To: Wadzinski Tom
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-13 18:12 UTC by Caleb Crome
Modified: 2010-05-27 14:46 UTC (History)
4 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Caleb Crome 2009-08-13 18:12:51 UTC
When running on Baby (don't know about fab4), a single volume up or down even causes multiple volume steps.  

This is unexpected behavior.  It should do a single volume step at a time I think, like Boom does.  

When the remote is pressd-and-held, it should slide.

This is related to https://bugs-archive.lyrion.org/show_bug.cgi?id=13163.  13163 is an microcontroller bug now with only boom remote.
Comment 1 Felix Mueller 2009-08-14 01:23:20 UTC
Does that have to do with the speed-up code, Tom?
Comment 2 Toby 2009-08-14 06:58:05 UTC
Yes this happens on FAB unit too.
Comment 3 SVN Bot 2009-08-14 10:20:03 UTC
 == Auto-comment from SVN commit #7085 to the jive repo by tom ==
 == https://svn.slimdevices.com/jive?view=revision&revision=7085 ==

Fixed Bug:13396
Description:
- Volume now uses IR accel class (which still needs improvement for 8.0 - bug 13405)
Comment 4 James Richardson 2009-10-05 14:36:49 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Comment 5 Chris Owens 2010-05-27 14:46:27 UTC
These bugs have all been marked resolved and belong to a component which is being removed.  Therefore they have been moved to the most applicable of the new components.