Are you using the Logitech Setpoint software? This seems to be a problem with that software. See:
http://forums.logitech.com/t5/Keyboards ... d-p/737128

You can just uninstall the Setpoint software/drivers and rely on the standard MS keyboard drivers, and I expect the problem will be solved.

-Rusty

Guest wrote:Bug is still up for me in MM 4.0.0.1459
Using Logitech USB Keyboard on Windows 7, if my MM is in foreground it works well, as far as I switch to another Application it jumps 2 Tracks forward if I press ">>|".
I don't have the Problem with the "|<<" Key, just forward is a Problem.

Updated to MM 4.0.5.1486 the Issue is still current.
Does anyone know where's the problem?

ijonasse2,

Are you using MediaMonkey 4.0.3?

-Rusty

Same problem here. Logitech K520 Desktop set (Keyboard/mouse) Skps two tracks forward.Backwards is ok.

Bug is still up for me in MM 4.0.0.1459
Using Logitech USB Keyboard on Windows 7, if my MM is in foreground it works well, as far as I switch to another Application it jumps 2 Tracks forward if I press ">>|".
I don't have the Problem with the "|<<" Key, just forward is a Problem.

THANK YOU!! THANK YOU!! THANK YOU!!

So far this is fixed in 1433.

Nyn

Thanks. Should be resolved in build 1433.

-Rusty

Here is a debug log, the skips are around 836 and 3753 (I think). The songs that were skipped were Planet Rock and Did it Again. It doesn't skip consistently nor always on the same songs: http://dl.dropbox.com/u/13254132/fast%2 ... tracks.LOG

Nyn

Rusty:

Currently working on generating the debug logs both for my work computer and my home computer. But what happens is, I hit either the play forward or play previous media keys and instead of MM moving to the next song or the previous song it will move two songs forward or two songs back, thereby skipping the previous and next tracks. This happens more frequently on my home computer, thought that may be because I use those keys more at home. Since I am concentrating on work at my work computer (yeah right!) I do not skip and fast forward as often, but at work I use the fast forward more than the previous since I am usually skipping past tracks that are not appropriate for an office. But as soon as I generate the logs for both computers I will post them. Both computers do use multimedia keyboards and both are Logitech's.

Nyn

Hi Nyn,

Can you explain exactly what you mean? The problem you're describing sounds different than the bug described earlier in the thread re. Media Keys not functioning.

Note also: we don't see any problems with playback, so a debug log would be helpful as well.

Thanks.

-Rusty

I am on 1430 and this is still a problem, can this be looked at again because it is becoming very annoying not to have the correct songs played when the play next or play previous key is selected?

Nyn

Alhought I cannot reproduce I found the reason that most probably causes the issue for you.
Will be fixed in build 1424.

romeyinfc wrote:It looks like Bug 8200 is still rearing its ugly head in the latest builds. This time when I press one of my keyboard's media keys, the 2nd button delay arrives many seconds later. For example if I hit ">>", it'll skip by one song immediately, then a few seconds later it skips again. The same action is repeated with the Play/Pause button.

I cannot reproduce with 1423, could you generate debug log using the DbgView and build 1423?

It looks like Bug 8200 is still rearing its ugly head in the latest builds. This time when I press one of my keyboard's media keys, the 2nd button delay arrives many seconds later. For example if I hit ">>", it'll skip by one song immediately, then a few seconds later it skips again. The same action is repeated with the Play/Pause button.

Thanks Rusty, but It think it's rearing its ugly head again in 1419. This time when I press one of my keyboard's media keys, the 2nd button delay arrives many seconds later. For example if I hit ">>", it'll skip by one song immediately, then a few seconds later it skips again. The same action is repeated with the Play/Pause button. Should I submit this as a new bug?