Print

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

[RoderickGI]

Could someone check that the Green Button on an MCE remote still launches MC, as long as the Media Server and/or MC Service is running, but the MC User Interface is not?

I have both MC and Media Server start with the HTPC, but sometimes I do close the User Interface, and I'm pretty sure I could just press the Guide button to get MC to launch again and display the Guide. But that isn't working at the moment, in this version, MC21.0.58, and probably in earlier versions. Nor does it work using the Green Button (MCE Media Center command), or any of the other buttons that would normally launch MC Theatre View. However, I have recently installed some new memory resident software on the HTPC, and it may be interfering, so confirmation would be good. Even if it is just confirmation that I'm losing my mind, and this never worked.  


I was made aware of this potential issue because of this thread;
http://yabb.jriver.com/interact/index.php?topic=103747.msg721087#msg721087

Thanks.

[Matt]

The green button still launches Theater View for me even from a totally different application.

[Yaobing]

The green button works here too.

[RoderickGI]

Okay. Thanks guys. I'll uninstall the suspect software and see if that fixes my issue.

[RoderickGI]

Yep, the memory resident software was interfering with the remote. It is gone now, never to return. I'll just have to find another solution to the issue it was resolving.

Thanks again for checking.

[JimH]

What was the software?

[RoderickGI]

It was a complied AutoIt script I got from here that is used to automatically close the Teamviewer nag screen on the HTPC. Every time I connect to the HTPC to do some maintenance, then exit, the nag screen is left up and active on the HTPC, which is very bad for the WAF. Annoying for me as well, since I need to use the keyboard to close it.

I could see that the HTPC received the Green Button IR command when the script was running, but any action seemed to be blocked.

This experience makes me wonder if other AutoIt scripts, and other similar software, would interfere with the IR capabilities.

The script was very simple, just;

Code: [Select]

Opt("TrayIconHide", 1)
while True
   WinWait("Sponsored session")        ;check if the TeaamViewer Sponsored session Window exist
   WinActivate("Sponsored session") ;activate the window
   Send("{Enter}")                      ;close it
WEnd
So I assume it was something to do with the compiled version, libraries it uses, or similar.