Suggestion

[BTUx9]

I'm not an active member of this community, but as an active member of a different hacking community (tivo), I wanted to say how impressive the s/w (ir, km, and rm) you've developed is.

That being said, I'd like to make an observation, and a suggestion.

Originally, IR was developed as a tool to load, analyze, modify, and re-load code from jp1 remotes. It's always been very data-driven, and the addition of external tools like KM and RM have been somewhat secondary. But with the maturity of those tools, I (and I assume others) am programming remotes solely based on collected imports (devices and protocols).

But, because of the way IR developed, the interface between it and KM/RM makes the procedure much less streamlined and more error-prone than it should be. With a fairly minor change to the programs, I think this could be changed.

The structure of the device and protocol upgrades is already defined, but instead of pasting them piecemeal, why not have an intermediate file format (say .iri), that has the device and protocol data within it. KM/RM could easily save this file at the same time they save their own format, and rather than having it as a 1-shot import into IR, have IR build the remote data based on a collection of these files... just before uploading to the remote, it'd rescan all files that have been designated, and rebuild. In this way, changes made from within RM/KM would be automatically integrated with no extra steps. Special protocols and extenders could be treated the same way... even macros and keymoves, for that matter.

I hope this makes sense, and welcome any feedback/comments on the idea.

[gfb107]

Hi BTUx9, I am also active in the tivo hacking community. I am the author of MovieLoader.

TiVo is actually what got me into JP1 in the first place, back in '99.

I am the primary developer of RM. You may not be aware of this, but there is a prototype of IR function built into RM. This is the current direction of the JP1(.x) tools. RM is currently an alternative to KM, and will eventually be an alternative to IR as well.

I think you'll like the direction this is going. For more information see the Prototype IR function in RM thread.

[BTUx9]

Thanx for the "heads up"

I saw a mention in the RM help file that development was intended to go in that direction, but I didn't find any other reference to it, there (might be worth sticking a reference to the thread, so people know it's more than just an intent).

I'll direct any other questions/comments to that thread, shall I?