Notices

Just an idea, why not implement a in-app update for keyset? this came into my mind while checking the changelog of 1.1.18

Yes, I really should do that. It'd be a little painful to do so, though. The original reason I created Pierogi, way way back when, was that I was pretty well disgusted with the way that the available remote control apps worked; either they were hard-coded to support a single device, or they only allowed you to use a config file for one device at a time. The idea of having to download individual config files kind of turned me off; each config file is tiny, you should be able to store them all locally. I also knew that many manufacturers reuse their command sets over time (and often just copy the command sets of other manufacturers wholesale), so you could potentially save some space by not storing lots of config files containing the same data.

So, I went ahead and started building my own database of keysets. I started off by grabbing config files from the Linux Infrared Remote Control project, which has a massive collection and is the main resource for all things IR in the Linux world. Unfortunately, the file format they use, while flexible, is very poorly suited to my needs; you can either store the raw timing value for each on-off pulse of the IR, or use an extremely rudimentary format to store individual bit values. There's almost no built-in support for the "protocols" that each manufacturer uses, and I wanted to leverage those protocols to save space and make my life easier.

So, I started creating my own internal format. I am, in fact, still playing around with that format; I'm learning about the low-level details of IR programming as I go.

It wouldn't be impossible to create files that match my internal format. I could certainly follow the lead of the hifi-remotes.com website; those guys create config files for "JP1" universal remotes, and their file formats are much closer to what I would want, although they've got a lot of extra material dealing with JP1 assembler programming and EFC codes that are entirely unnecessary for me. But it'd probably take a bit of time to expose my protocol formats in such a way as to make them usable by others. (And converting from LIRC or other config formats to what I'm using wouldn't necessarily be trivial, either...)

Anyway, I've been thinking about it, but I'm not quite there yet.

For those who are facing problems, why don't you do an automatic search, the N900 IR oriented toward the TV and see what remote works or doen't work?? Just a little suggestion! That's what I did to make it work with a TV which were not listed in the remotes.

Yes, thanks! I haven't yet put it into the documentation, but yeah, I'm hoping to make that one of the primary ways to find working keysets.

Oh, and by the way, if you've got the time, could you note down the model of the TV and the keyset that worked with it? You could either post that info here, or enter it directly into the Pierogi devices list. I'm (slowly) working on getting all those devices into Pierogi in some hopefully useful manner...

Yeah, the Brand of my TV is Venturer (I don't have it right know so i can't give you the model) but the Keyset which worked for me is KENWOOD TV Keyset 1 (and an other remote wihch i don't remember - I deleted it due to incompatibilty with some functions).

But the Kenwood TV Keyset 1 works basically (I mean, changing channels, volume, mute the TV and of course Power ON/OFF)

Model number is AQV24NSAN sir!

Ah, yeah -- that keyset is using the NEC protocol with a device code of "4". Unfortunately, device code 4 seems to be pretty popular; I've already got almost half a dozen different keysets using it, and all of them are just slightly incompatible with each other.

And yeah, I just looked, and there are some Venturer config files available, and their commands are slightly different too. I'll get them into the next Pierogi release.

Yeah that will be cool! I'll stick with this post. Thanks

I've already tried that function, none worked
But... When my tv is turned off, somehow, the TV will turn on by some keysets when searching in automatic mode. But when I select the keyset manually and press the power button, nothing happens... (LOL!)

If I "Fast forward" it, it will also trigger something that will turn on the TV, but when it's on, it won't trigger anything.... (nothing happens at all)

This thing happens when it's fast forwarding just after: Aiwa Car Stereo Keyset 1 and just after Beko/BenQ

If I manually go left and right (step by step) it won't work. It only works with the Fast forward and the Automatic search.



EDIT:
Oh by the way, I have a Dreambox DM800 HD SE (I've got a fake one though, but as far as I know, the remotes are the same).
None of the keysets are working. Already tried all the DreamMultimedia keysets

Hmm. I've got Pierogi spending the minimal time paused between commands in the fast forward and automatic search; quite possibly, the TV is combining two commands into what it thinks is a single command.

I haven't seen that kind of behavior before, but if so, it may make using the automatic keyset search troublesome. (Perhaps I need to put a longer pause between commands...)

I've gotta admit, I'm having real problems coming up with complete MT-Logic keysets (or Audiosonic, or Tristar). The only source I've got so far is just chock full of bad data. It may be a while before I can come up with something that works.

Ah, yes, Dreambox is interesting -- I've never seen so many different remotes associated with so few devices from one brand name. I'm not sure you could actually use the remote from one model of Dreambox with any other Dreambox. Let me do some research on the DM800...