2014-10-31, 13:34
(2014-10-31, 06:52)allan87 Wrote: • 200 ms before repeating was fine. I did not see any point trying faster. 300 would also have been fine.
• I went as high as 150 on repeat rate, because I felt the repeat had to be slowed down. Even at 150, the interface lagged behind the button press - although it started to repeat quickly, it didn't start scrolling fast until a fairly sustained button down, and then it significantly outran the button release. I had to get the hang of how it responded, because it would inevitably run past 5 to 10 more items after button release.
Do you have a release of 0? Can you check log for "button up" events?
The lack of a button up event leads to overrunning by the release amount. If release is 0 and there are no "button up" events then the release is assumed after 500ms.
Setting release to a smaller number (e.g. 300 may overshoot less).
It could be a cpu issue where the button events are not being consumed quickly enough and the queue gets longer when scrolling.
I haven't seen that, but explain where in the xbmc UI you are when this happens, and perhaps post a log (with debug and CEC component logging enabled).