Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[coolblue]

Despite J River's (much appreciated) hard work getting multimedia keys to function properly for all the different keyboards and drivers out there I've still been having problems with my keyboard and the latest IntelliType drivers. I did find a way to fix it though:

I opened Keyboard Properties from the Control Panel and clicked the Key Settings tab. For each of the entries:

Play/Pause
Stop (media)
Prev. Track
Next Track

I set the key assignment (double-click the Key Name to open the reassignment dialog) to "Disabled." Now MC handles the keystrokes (they still work fine even if MC doesn't have focus)  and all is well. I rebooted to make sure this was not a temporary solution.

This resolved all issues with the keyboard. If others are having problems with different makes of keyboard this might be one area to investigate (disabling the driver's native handling of the multimedia keys).

[jgreen]

Just tried it myself and it seems okay.  I still hold to the "resident evil" hypothesis, but that's just me.  My heart goes out to all the hard-working jrivers, who must be tearing their hair out reading this.

[JimH]

I still hold to the "resident evil" hypothesis, but that's just me.

No, I had to laugh out loud at your comment, and I agree.  Something's rotten in the keyboard.

[coolblue]

No, I had to laugh out loud at your comment, and I agree.  Something's rotten in the keyboard.

My thinking is Microsoft's intent is that you would use the multimedia keys on their multimedia keyboard with their multimedia player (such as it is). They seem to have a way with confounding/sabotaging users and vendors of non-Microsoft products. The 'net is full of examples.

[jgreen]

Just for giggles, I went back to mc 11.0.266, the build that presented the worst issues with repeating keystrokes, and tried it now that I've disbled the MS driver per this technique.  The seek functionality worked perfectly. 

I know that jriver is continuing to add keystroke anti-repeat delay  successive builds.  This seems to be the less-than-optimum approach, since the problem appears to be with the keyboard drivers.  From build 266 to build 272 there is a downgrade in seek function because of the added delay.