Print

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

[koolmees]

I have MC 12 and it worked fine, till now.

I always used a cabled keyboard and had no problems. Now I bought a Logitech MK330 set and I can only use the media keys of the board when MC is on the top of the screen. So if not I have to click on MC and than I can use the keyboard. Is the problem my Logitech of my version of MC?

[leoric]

I'm having exactly the same problem with my wireless Logitech K520 (with latest SetPoint), MC18 & Win8.

[koolmees]

To be complete: I use Windows 7 Pro.

[Random]

Had a similar problem myself when updating to the newest (6.61) Setpoint software. Went back to the 6.32 version and everything went back to working correctly.

[leoric]

The problem is my mouse is not supported in 6.32.
Found another solution: just add the following line to C:\Program Files\Logitech\SetPointP\players.ini in [Players] section:
MC=wac,Media Center 18.exe,JRiver Display Class,xxx,xxx,xxx,xxx,xxx,xxx,xxx,0,1,MC

JR guys, you could probably contact Logitech and arrange this to be out of the box in a future SetPoint ver.

[Arindelle]

just my two cents .... have you tried uninstalling Set-Point?

My past logitechs never had a probleme running without this bloated (IMO) software anyways. Always been plug and play and check for new drivers -- depends on what you are using setpoint for though of course .... there are other ways to customize keybinds

[leoric]

I'm afraid there is a number of functions that hardly can be used/customized w/o SetPoint. Two examples that I personally use: Fn key combinations and some non-standard mouse functionality, e.g. specials of a touch-sensitive mouse.

[leoric]

Last MC18 version uses a different window class, MJFrame. So the players.ini line should now look like
MC=wac,Media Center 18.exe,MJFrame,xxx,xxx,xxx,xxx,xxx,xxx,xxx,0,1,MC