USB-UIRT Event Codes

[Jaymax]

Hi.

I was playing around with a different profiles in a cheap universal remote in EventGhost, and suddenly, rather than getting the normal event strings like "USB_UIRT.NEC.32CD2856", "USB_UIRT.Unknown.545578D4" and "", I started getting "USB_UIRT.RC5.TV1.VolumeUp" and "USB_UIRT.RC5.TV1.Green"

Which is way cool - but what's going on? Are these definition in the USB-UIRT windows driver, or the USB-UIRT EventGhost plugin, or somewhere else? Where do I find a list of them? Are they configurable? [etc...]

Cheers,
-J

[krambriw]

Hi,

EventGhost has built in ir-decoding. When you changed the profile in your remote, it was suddenly recognized by EG!!!

All source is open in python and can be studied (\Program Files\EventGhost\eg\Classes\IrDecoder) which is very helpful in getting a deeper understanding of what is happening

But why would you need to change the configuration in EG?

Normally your remote events will appear in the left pane (log window). If you want something to be triggered by such an event, you simply drag & drop it into a defined macro in the right pane. You don't have to change anything for this


Best regards, Walter

[stottle]

By default (IIRC), only RC6 and RC5 have the translation from a ir code to an input name. As you noticed, there are a bunch of other types of encoding, and there are codes that aren't mapped.

I personally like having the code mapped to a button with a name on my remote. This has two benefits. First, it is much easier to mentally associate an event like "play" with an action. Second, if I change remotes but the new remote still has a play button, it still works and I don't need to change my config.

For the EGBeta I've developed, it will read an xml file that maps ir codes to button names which are then passed to the irdecoder. If the codes matches, you get the name, otherwise you get the original hex code. That also gives me the ability to automatically match these named events to named actions in an application plugin. That way you don't have to make a macro to have your play button run the play action all the time - it's handled for you.

Check it out here if you are interested.

Brett

[Jaymax]

OP here.

Thanks for replies.

But why would you need to change the configuration in EG?

It's more curiosity than need. But it's inconsistent to have some arbitrary profiles 'translated' and others not - so configurable (or rather, extensibility - eg: drop in a 'translation' file for a particular non-native remote control)

I personally like having the code mapped to a button with a name on my remote

Me too - so I ended up setting up an event for every remote button (ended up using a different profile that enabled all buttons), that just triggers an event named for the remote button - which works fine, and leaves the question - is there a reason (speed perhaps?) to put any translations internal to EG distinct from the event tree? Might it be more flexible to just use a 'hive' on the tree?

[Bartman]

Me too - so I ended up setting up an event for every remote button (ended up using a different profile that enabled all buttons), that just triggers an event named for the remote button - which works fine, and leaves the question - is there a reason (speed perhaps?) to put any translations internal to EG distinct from the event tree? Might it be more flexible to just use a 'hive' on the tree?

You can directly map any codes from the USB-UIRT with single script in the autostart. This way you also keep enduring events.

http://www.eventghost.org/forum/viewtop ... 34&start=0

[stottle]

This is a recent change within EG, and was only applied to a few decoders. I do not believe there was any consistent rule (not speed or anything like that).

Bartman - As for the ability to remap, that is an interesting tip that I hadn't seen. So thank you for posting that. At the same time, though, I think there are a lot of people that would benefit from EG's IR capability who do not have the perseverance or inclination to learn how to script EG - at least not to get started. The automatic translation in a few of the decoders is (in my opinion) a step in the right direction for appealing to those users.

Brett