New USB-UIRT Events

[jsonnabend]

I upgraded from 1430 to r918 (using XP Pro). My event codes from my Hauppauge 43 key remote through the USB-UIRT are now showing as new "named" events instead of hex values. That would be ok, except that some keys are completely misnamed. For example, the "radio" key shows up as "power".

What is causing these new "named" events, and can I fix the misnamed events?

- Jeff

[jinxdone]

They are predefined IR code -> name value pairs in the EventGhost\eg\Classes\IrDecoder\*. The idea is that the raw codes can be interpreted by EG and mapped into a readable form. I'm not sure what Bitmonster has planned for these but I think a way to map the names yourself is certainly a good idea.

However in the meantime you could do something like this to work around the wrong names? Or if you really want you can just re-set them in the IrDecoder to correspond with the buttons on your remote for now..

Code: Select all

<?xml version="1.0" encoding="UTF-8" ?>
<EventGhost Version="851">
    <Macro Name="MapEvent" Expanded="True">
        <Event Name="Lirc.16:9" />
        <Action Name='eg.TriggerEvent("NewEvent")'>
            EventGhost.PythonCommand(u'eg.TriggerEvent("New")')
        </Action>
    </Macro>
</EventGhost>

Somebody else can answer you better as this is just about everything I know about this subject.. I don't have any devices that use the IrDecoder myself.

[jsonnabend]

I've rolled back to 1430. This morning when the HTPC resumed from hibernation, the remote control events were all showing as "unknown" (or something like that). The new IR decode code is just too buggy.

- Jeff