INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: An interesting Media Center vs. Media Center remote control discovery  (Read 1308 times)

matthewmattical

  • Regular Member
  • Junior Woodchuck
  • **
  • Posts: 94

Not only are the two names horribly confusing (Windows Media Center vs. J River Media Center), but I discovered an incredibly tricky conflicting bug between the two! For the past year or so, I have been running a Windows Media Center 2005 system in my living room. For this entire year,  I have been stumped about my inability to use the Skip, Replay and Stop buttons on my official Microsoft Media Center remote - all other buttons work flawlessly. Coincidentally, I have JRiver Media Center 11 set to auto-start with Windows so it runs next to Windows Media Center on my monitor (Windows MCE is displayed on the TV).

After trying every Windows hotfix ever released, deleting and re-creating Windows remote settings files and even attempting to short and reset my actual remote (all suggested by this post: http://blogs.msdn.com/astebner/archive/2005/10/24/484423.aspx), I found the final solution. JRiver Media Center's "media key mode" feature was intercepting the remote signals. After disabling this in options/general/advanced, my life has returned to normal peaceful digital bliss.  :)

This is not a complaint about either product, but simply a discovery that I thought the Media Center world should be aware of. You should have seen the look on my face when I figured this out on a slightly tipsy night with my girlfriend this week. It seems so obvious now, huh?  :-[


P.S. This applies to any version of Media Center that features the media key mode feature. I have since installed MC12 and the fix still works.
Logged

Rob L

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 469
Re: An interesting Media Center vs. Media Center remote control discovery
« Reply #1 on: December 01, 2006, 03:25:55 pm »

This got to me for quite some time too, and I even started some threads on here about it, though they never went anywhere....

Eventually, I solved the problem *properly* - set the option to "App Commands" rather than "Automatic".

I don't really know why this works, but it does - there seems to be no loss of functionality as a result.

It's just that in Automatic mode, MC "eats" *some* of the keypresses (as you say, I think it's stop and skip back/fwd, but play, pause etc. still work!). In "App Commands" mode, the keys still work fine in MC, but it doesn't stop other apps seeing them...
Logged
Pages: [1]   Go Up