Home » Category » Microsoft Windows Media

Microsoft Windows Media: MCE 2005 remote buttons can only be pressed once

204| Sun, 01 Jun 2008 12:16:00 GMT| mikez| Comments (3)
The buttons on my Microsoft MCE 2005 remote control can only be pressed once.
Pressing the button a second time will not provide any results until I
choose a different button.

For example, if I press the directional arrow Up key once, it will move up
one space on the main menu screen. But if I press it a second time, it will
not move up. The same thing happens when I try using the volume control on
the remote. If I press volume Up once, the volume will go higher. But if I
press that same volume up button a second time, the volume does not raise
again. I have to press a different button before that button I had used will
work again.

I just set up this system about a week ago. Everything was working great
until yesterday, but I can't think of anything that I am doing differently.
I have not installed any new software between the time it was working and now.

Anybody know what may fix this problem?

Thanks,
Mike

Keywords & Tags: mce, 2005, remote, buttons, only, pressed, once, microsoft, windows media

URL: http://www.cooldevelopers.com/microsoft-windows-media/62115/
 
«« Prev - Next »» 3 helpful answers below.
Hmm... I also have a Linksys MCE Extension. The Linksys remote works fine
on the main MCE PC.

I then tried my MCE PC remote on my Linksys MCE Extension box and it worked
fine there.

I return to the PC box and the MCE PC remote still will only do one button
command one time and then needs to have a different button pressed before it
will accept that original button again.

"Mike Z" wrote:

> The buttons on my Microsoft MCE 2005 remote control can only be pressed once.
> Pressing the button a second time will not provide any results until I
> choose a different button.
> For example, if I press the directional arrow Up key once, it will move up
> one space on the main menu screen. But if I press it a second time, it will
> not move up. The same thing happens when I try using the volume control on
> the remote. If I press volume Up once, the volume will go higher. But if I
> press that same volume up button a second time, the volume does not raise
> again. I have to press a different button before that button I had used will
> work again.
> I just set up this system about a week ago. Everything was working great
> until yesterday, but I can't think of anything that I am doing differently.
> I have not installed any new software between the time it was working and now.
> Anybody know what may fix this problem?
> Thanks,
> Mike

mikez | Sun, 01 Jun 2008 12:17:00 GMT |

I received a response on the thegreenbutton.com boards from RichGuy
(originally posted by Chad). Including it here so it may help someone in the
future.

Here is how to cure the problem. This was coped from a letter original
written by someone named Chad.

In environments where a lot of IR noise is present, a single press of a
button on the Media Center remote can often be misinterpreted as multiple
presses (a condition known as “bounce”).

A common technique to circumvent this problem is to have the remote actually
transmit different IR codes on alternating presses of the same button. (And,
in fact, the Media Center remote has behaved this way since it was first
released) With alternating codes, the driver can distinguish whether the
button was actually pressed once or twice, simply by comparing whether two
codes received sequentially are the same or different. This technique is
called “debouncing.”

When you train a learning remote to learn the codes of your Media Center
remote, you’re typically teaching it only one of the two alternating codes
that each button can transmit. So, the learning remote dutifully plays back
the same code every time. The driver, running with debounce mode turned on,
will ignore multiple presses of the same button on your learning remote,
because they look like bounces.

You can easily turn off debouncing mode in the latest version of MCE 2004.
Even if this critical update is applied. I have an HP MCE 2004 machine
applied this patch and had this exact problem. All you need to do is update
the following two reg keys.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi ces\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da]
"EnableDebounce"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi ces\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57db]
"EnableDebounce"=dword:00000000

Make sure they are both set to 0 and reboot the machine. Your universal
remote should work fine!

Chad.

"Mike Z" wrote:
[vbcol=seagreen]
> Hmm... I also have a Linksys MCE Extension. The Linksys remote works fine
> on the main MCE PC.
> I then tried my MCE PC remote on my Linksys MCE Extension box and it worked
> fine there.
> I return to the PC box and the MCE PC remote still will only do one button
> command one time and then needs to have a different button pressed before it
> will accept that original button again.
> "Mike Z" wrote:

mikez | Sun, 01 Jun 2008 12:19:00 GMT |

I had the same problem. This issue has been fixed and is posted here on the
boards. I woudl do a search if you want a more detailed explantiation look
for my name I started the thread. But form what I remember. you have to
download the winterservice pack. there are some MCE 2005 powertoys in there.
once you install it go to more programs
choose Tweak MCE
choose Remote
choose diable multibrand remote.
restart the computer
and it shoudl work.

in the thread JT outlines if that part dosent work what the next thign you
shoudl do.

"Mike Z" <MikeZ...discussions.microsoft.com> wrote in message
news:CA86A67D-B1AA-4076-87D0-C7C6C6B192C6...microsoft.com...
> I received a response on the thegreenbutton.com boards from RichGuy
> (originally posted by Chad). Including it here so it may help someone in
the
> future.
>
> Here is how to cure the problem. This was coped from a letter original
> written by someone named Chad.
>
> In environments where a lot of IR noise is present, a single press of a
> button on the Media Center remote can often be misinterpreted as multiple
> presses (a condition known as "bounce").
> A common technique to circumvent this problem is to have the remote
actually
> transmit different IR codes on alternating presses of the same button.
(And,
> in fact, the Media Center remote has behaved this way since it was first
> released) With alternating codes, the driver can distinguish whether the
> button was actually pressed once or twice, simply by comparing whether two
> codes received sequentially are the same or different. This technique is
> called "debouncing."
> When you train a learning remote to learn the codes of your Media Center
> remote, you're typically teaching it only one of the two alternating codes
> that each button can transmit. So, the learning remote dutifully plays
back
> the same code every time. The driver, running with debounce mode turned
on,
> will ignore multiple presses of the same button on your learning remote,
> because they look like bounces.
> You can easily turn off debouncing mode in the latest version of MCE 2004.
> Even if this critical update is applied. I have an HP MCE 2004 machine
> applied this patch and had this exact problem. All you need to do is
update
> the following two reg keys.
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi ces\HidIr\Remotes\745a17a0
-74d3-11d0-b6fe-00a0c90f57da]
> "EnableDebounce"=dword:00000000
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi ces\HidIr\Remotes\745a17a0
-74d3-11d0-b6fe-00a0c90f57db][vbcol=seagreen]
> "EnableDebounce"=dword:00000000
> Make sure they are both set to 0 and reboot the machine. Your universal
> remote should work fine!
> Chad.
>
> "Mike Z" wrote:
fine[vbcol=seagreen]
worked[vbcol=seagreen]
button[vbcol=seagreen]
before it[vbcol=seagreen]
pressed once.[vbcol=seagreen]
I[vbcol=seagreen]
move up[vbcol=seagreen]
it will[vbcol=seagreen]
control on[vbcol=seagreen]
But if I[vbcol=seagreen]
raise[vbcol=seagreen]
used will[vbcol=seagreen]
great[vbcol=seagreen]
differently.[vbcol=seagreen]
and now.[vbcol=seagreen]

rodneym_james | Sun, 01 Jun 2008 12:19:00 GMT |

Microsoft Windows Media Hot Answers

Microsoft Windows Media New questions

Microsoft Windows Media Related Categories