|
JP1 Remotes
|
View previous topic :: View next topic |
Author |
Message |
probono
Joined: 12 Aug 2012 Posts: 48
|
Posted: Thu Jun 20, 2013 4:37 pm Post subject: irdb: a crowd-sourced infrared code database |
|
|
Here is a project I am working on:
http://irdb.tk/
Not specifically targeting JP1 remotes, but remote control codes in general. Also provides an online translator to convert between the different IR code representations.
There is an API as well.
This is a work in progress, so I'd appreciate your feedback. |
|
Back to top |
|
|
mdavej Expert
Joined: 08 Oct 2003 Posts: 4501
|
Posted: Fri Jun 21, 2013 9:26 am Post subject: |
|
|
Looks great so far. Nice work. I'll dig into it later and try to give you some feedback. |
|
Back to top |
|
|
vickyg2003 Site Admin
Joined: 20 Mar 2004 Posts: 7073 Location: Florida |
Posted: Fri Jun 21, 2013 11:24 am Post subject: |
|
|
Cool. Web based tools. I'll take a look with my android tablet and iphone browser later on. |
|
Back to top |
|
|
Barf Expert
Joined: 24 Oct 2008 Posts: 1415 Location: Munich, Germany |
Posted: Fri Jun 21, 2013 2:23 pm Post subject: |
|
|
Hi probono,
nice achievement.
It is always hard to give sensible feedback on ambitious projects, without spending all day. But I try to say something...
It may be worthwhile to point out to the user that your data base contains codes in protocol/parameter format (a word that needs explaining) and the computation of the rendered code is done in realtime using my IrpMaster library. Also, since you are appears to be using DecodeIR and ExchangeIR (possibly through my libraries), I think John Fine and Graham (mathdon) also should be given credit.
I will definitely be writing some stuff in the future that interfaces with your stuff, both the irdb-api and the Arduino stuff.
As it stands right now, I unfortunately thing the thing is of somewhat limited usability, at least for the non-expert. Say that I am looking for IR codes for a particular model, venor and model number (and deviice type). I give in the manufactorer, and get a number of devices, ordered after device type (useful) and device numbers, in the sense of IRP. This is not useful at all for the non-expert, he wants to enter a model number, and get its command. If you have to know device and subdevice, you may already possess an IR-Widget, suitable software and knowledge. Also, for example AVR receivers from Yamaha or Denon often uses approximately the same commands for different models, but the semantics may vary between the models.
I am not saying "useless" or such, just that a D, S-oriented DB is of limited use.
But a great achivement, dispite of my minor points. |
|
Back to top |
|
|
probono
Joined: 12 Aug 2012 Posts: 48
|
Posted: Fri Jun 21, 2013 2:39 pm Post subject: |
|
|
Thanks Barf for your feedback which I will incorporate. I have expanded the acknowledgments on the about page.
If possible, I would like to get away with not explicitly dealing with model numbers, since often a whole class of devices of the same manufacturer share the same set of codes. This probably means that the end user needs to try different sets of codes, but I think that is an acceptable price to pay for having a much, much more compact database.
I agree that the retrieval of codes needs to be streamlined for the non-technical user, without talking about technical stuff like protocols too much. Possibly a set of client-side scripts to retrieve, test, and submit codes would be the easiest to use for the non-expert. There is an API that should make this sort of things possible.
Then, for the expert, I will probably make codes accessible over a simple URL scheme that can easily be linked to. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|