Bug 1391 - Remote has become too sensitive
: Remote has become too sensitive
Status: RESOLVED WORKSFORME
Product: Logitech Media Server
Classification: Unclassified
Component: Player UI
: 6.1.0
: PC Debian Linux
: P2 normal (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-18 03:50 UTC by Christian Pernegger
Modified: 2005-06-07 15:46 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments
Proposed patch for 6.0.x branch (962 bytes, patch)
2005-04-21 16:21 UTC, Vidur Apparao
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Pernegger 2005-04-18 03:50:25 UTC
With the new firmware 10 and 6.1-299x builds I have trouble getting SlimServer
to register just one button press.
Example:
I'm at "Now Playing", track 1 and want to select track 2 via the grey "Down"
button, yet it is nearly impossible to press it short enough. It will go over 2
and on to 3 far too quickly. Has a repeat delay setting quietly died? The fw 9
releases are fine.
Comment 1 Vidur Apparao 2005-04-21 16:20:07 UTC
It may not be the device itself, but a SlimServer issue. It turns out that we're
sometimes sharing mode state between clients. I'm able to recreate the specific
problem that Christian mentions when I have more than one Squeezebox running in
the same room. If they happen to be getting the same remote signals and are in
the same mode, they wind up sharing mode state and certain remote signals such
as up & down act redundantly.

Attaching a patch momentarily. Cc:ing kdf to review it.
Comment 2 Vidur Apparao 2005-04-21 16:21:10 UTC
Created attachment 439 [details]
Proposed patch for 6.0.x branch
Comment 3 KDF 2005-04-21 20:05:27 UTC
looks fine to me.  

well spotted!  I've had two boxen in the same field of view for months now, but
I spent so much effort making sure they were always set to work with two
different remote types that I never came across this problem :)
Comment 4 Christian Pernegger 2005-04-22 01:43:57 UTC
FWIW, I have only one sb2 running and I'm quite sure not even softsqueeze was
running at the time. Anyway, I just took the plunge again (to 3033) and it
seemed fine, at least for the ten minutes I tested it. Either the original issue
got fixed or it is harder to trigger than I first thought.
Comment 5 Vidur Apparao 2005-04-22 09:39:12 UTC
Hmm...with the proposed patch in (change 3035 and change 3036 on the trunk and
branch respectively), I'm going to close this bug since you aren't able to
recreate. Feel free to reopen if you see it again and can suggest a reproducible
case. Thanks!
Comment 6 Christian Pernegger 2005-05-01 05:12:01 UTC
Sorry I have to reopen this - I waited a little because it either seemed a bit
better in the last couple of builds or it didn't bother me that much.

FWIW, my "steps to reproduce":

1. see to it that there's some songs in the current playlist, start playing
2. move to next item using the remote's "down" key.
3. repeat 2. a few times

After the third to fifth key press it will not move down one item but two,
scrolling by the skipped item very quickly. After that, the next few presses are
fine. It's the same with the "up" key.
Of course I might be pressing the buttons too long but why every few key presses
then? Besides I have to hold a button quite some time for the repeat to trigger.
The problem actually seems to get worse when the server machine is idle except
for running slimserver.
Comment 7 Blackketter Dean 2005-06-07 15:46:48 UTC
Christian: I think you are seeing acceleration that happens when you press the up and down arrows.  I 
can't reproduce the behavior you are seeing except when acceleration kicks in.