Any plans for updated How-To or Doc for latest beta?

[Livin]

Since there seem to be a lot of changes it would be nice to get some FAQ or How-To on the latest beta. I tried to use it but it just broke all my keyboard mappings... and I could not get an remapping to work - the log of my USB-UIRT codes changed drastically and not sure what to use.

I'd like to help test the new build but everytime I do it massively breaks functionality and I must revert back to an old version.

bit?

[jinxdone]

There's been some changes in the ir decode functions, I think you'll have to remap your buttons sooner or later..

[Livin]

I tried to remap them, it did not work... this is why I want to get docs on the changes and how to use it.

I already posted my problem in another thread but no one has offered help... seems like either most people don't frequent this forum much (even Bitmonster), or most use an old version and don't try the never versions, or no one really understands how things work... or a combination of these. It is frustrating to try the latest versions when they always break to the point of not being usable.

[jinxdone]

Uh.. Well, the thing is I don't have USB-UIRT myself.

Could you please explain why you could not remap them? What is the problem with it?

[Livin]

Uh.. Well, the thing is I don't have USB-UIRT myself.

Could you please explain why you could not remap them? What is the problem with it?

Sure. When the IR commands are logged in the .3.7 version they log "differently"... they are logged with a series of number codes and also, some, with something akin to an english-like command... USBUIRT.MCE.STOP, etc. Sorry about syntax not 100%, this is from memory.

I tried using the english-like command to do the remap, and it did not work.

Not sure if/what to do with the lines that are series of numbers... again, no docs on what they are. The last way version, the IR codes were logged seem to actually be more understandable... and mapping them works.

[jinxdone]

Previously you had events like USBUIRT.1234ABCD, right? The last bit (the hex number) represents the actual code received.

The bit of code that decodes these strings (which need to be different for each type of remote) has been somewhat redone. Support for new types of remotes should be now easier to add through plugin type scripts and modifications are now easier to make.

The new system will map some of these code strings to human readable form. Like now you should see USBUIRT.MCE.STOP instead of USBUIRT.800F0419. The USBUIRT.MCE.* tells you which file did the mapping from code -> human readable form, and should tell you what remote this is. However the support for all the possible remote codes is not too great so far so this leads to the USBUIRT.Unknown.1234ABCDE, which you will see when the code could not be mapped, which I think is about the same thing as what we had before + the .Unknown. bit in the middle.


That should be all there is to it as far as I know, correct me if I'm wrong.. As I said I don't have one of these devices myself so I havn't looked too closely at what it does.


Soo.. My advise is to just use the events as they appear in the log view, drag & drop into the config like usual. Or I suppose if you want and know some python you should be able to modify the scripts in the IrDecode dir and make it map codes from your remote to a human readable form..?

When you push a button on the remote and an event appears in the log (an entry with a star symbol, no matter if its USBUIRT.MCE.STOP or USBUIRT.Unknown.1234), you should be able to assign that event to a macro.