Strange Problems

[BarryD99]

I have Girder working with the MCE plugin and the MCE remote that comes with my HP MCE computer. Works great!

I'm using it to control Zoom Player and Power Point and plan to use it for other applications.

Now for the strange part. When I teach my MX-800 I have no problems with non Girder applications. When using Girder, the MX800, and either the Zoom Player or Power Point plug, the first time I use a command like advance to next slide in Power Point or skip to next file in Zoom Player. it works fine. Then, if I try to use that command again, it will not work. If I use the MCE remote, the command works and then I can use the MX800 one more time for the same command (like the skip). It then won't work again unless I use the MCE remote again.

Any thoughts?

[Promixis]

Are you learning the MCE commands into the MX800?

This may be related to RC5 codes which alternate every press. I am not sure if there is a solution..

[BarryD99]

>>Are you learning the MCE commands into the MX800? >>

yes

>>This may be related to RC5 codes which alternate every press. I am not sure if there is a solution..>>

Bummer

I assume that the ir receiver that comes with my HP MCE computer won't recognize and pass off to Girder ir codes from a foreign remote. Is that correct?

If this isn't correct, I wouldn't have a problem using another remote to sewnd my codes.

After doing a search on this for forum for RC5 codes, I think I understand the problem.

Am I correct that the Philips toggles 2 codes for each button? If so, would either or both of these solutions work:

1. I just learn two codes for each command
2. If this was a big enough proble for Girder users, could Girder be modified to accept two ir codes and the sequence would be:

on code1 or code2 do...
_________________

[Promixis]

Hi Barry,

Yes you have the right idea, RC 5 codes alternate.

You could press the button on your remote once and have the 800 learn it and then do it again on a seperate button. - Can you then look at the codes in the 800 software? Are they different?

This isn't a Girder issue. Your receiver won't send a new event to girder unless its get the alternate code.

[BarryD99]

Mike:

The MCE remote works great with Girder. Are you saying that the remote is sending two different codes and the receiver is somehow stripping one or more bits and then always sending the same code to Girder?

I thought I'd be smart and use the logging dll to see the codes, but the receiver only passes the first button press (as I think you were trying to tell me)

Can I assume that most or all learning remotes will that this problem with Girder or even when just using the mce reciever with any program?

[Promixis]

I believe the receiver captures the ir signals and then send the event - so for rc5 codes, it will send one event for 2 different codes.

Most of the time, this is not an issue. Ie. other receivers don't block the signal if it isn't alternating. I don't know how the learning remotes deal with rc5 codes - anything in their manual?

You ultimately may want to get a different IR receiver. You have a great remote, shame to be limited by the receiver....

[BarryD99]

Problem Solved!

I found the following on remote central and used method 1 create a macro that sent the desired command and then a dummy command which in effect clears the receiver.

I found this txt file in the Pronto section and used method 1 to solve my problem. Basically, I just created a macro to generate a dummy button press after the button I really want. This clears the IR receiver.
>>
.
.
.
Basically, MCE requires the code to toggle between keypresses so if you learn your universal remote, it always sends what it learned which obviously doesn't toggle and thus the button will not repeat.

You can get around this with a registry hack to turn off debounce. Documented in the forums somewhere. Or you can use these codes and create your own toggle 3 ways:

1. Follow your desired code with a "do nothing" code like "clear". This won't work for channels as clear clears the input, so I used Vol+ and vol- (macro= 3, v+,3,v- to tune channel 33)

2. Create duplicate pages in a device and jump to the opposite hex code page after each keypress. This does not work for hard buttons.

3. Create duplicate DEVICES and do the same as #2 between devices instead of pages.

All these methods work, and in practice are fully usable.

In fact, the page/device jumps are nice in that the time delay between keypresses as devices jump eliminates the need for a manually added delay.>>

[Promixis]

Glad you got it working Barry.