Re: [Announce] Pierogi - a universal infrared remote control app
 

Alright, I have tinkered around with the internationalization support in Qt, and have managed to generate a dutch ".ts" file for Pierogi. At the moment, most of the strings in it are from the various buttons, with a smattering of panel names and window names. You can see it in all its glory at:

https://github.com/jpietrzak8/Pierog.../pierogi_nl.ts

The good news is that these .ts files are easy to generate! The bad news is that it'll probably take a lot of work to parse through them. (That, and Pierogi has an enormous amount of buttons to translate...) Thankfully, there's no need to try and fill out an entire .ts file in a single pass; partially completed translations work fine, with Qt falling back to the default language for any items not translated.

The Qt SDK also has a program called Linguist that provides support for editing .ts files. Downloading and running a copy of this program is probably the easiest way to fill out the translations...

So, mr_pingu, if you're not running for the exits after seeing what a .ts file looks like, please go ahead and try translating a button or two, and message me about how feasible this looks to you. :) And, if anybody else out there would like to try their hand at translating Pierogi, I'd love to have the help!

Re: [Announce] Pierogi - a universal infrared remote control app
 

Umpf, I guess I need to dig up the SDK again. No exits for this challenge ;) I will manage. Looked quickly but I don't know what has to be translated as many remotes come in english only.
For example my receiver remote + text on the receiver itself is in english, the UI is in dutch though. Ofcourse I will do the general interface, but not sure if the buttons must be translated so I will skip them for now. Oh and if it doesn't happen before easter, exams are coming but I promise I will do atleast the general interface.

Re: [Announce] Pierogi - a universal infrared remote control app
 

Add /path/to/app in /usr/share/policy/etc/rx51/syspart.conf (in classify desktop section) reboot and lags will gone. I use it in qmllockscreen and it helps. For qmlradio it works also but there are still little lags.

Re: [Announce] Pierogi - a universal infrared remote control app
 

Adding things to classify as desktop group seems to give them those parameters at the very end:

...which, as compard to "background" group of programs (aka rest), changes only the thing about cpu-shares. Is it safe tho throw any_random program to group with such shares? Won't it affect stability od "real" desktop things?

Take all the above with a grain of salt, I have no idea how this policy thing works.

/Estel

Re: [Announce] Pierogi - a universal infrared remote control app
 

You are not alone. I found this idea on qtlockscreen thread and use it for few months. Maybe other groups with lower priority will work to. I had problem with headphones after I messed up with adding application from fat partition so be aware of editing this file.

Re: [Announce] Pierogi - a universal infrared remote control app
 

Ok, this is slightly mind-blowing... I was checking out the Chinese N900 website mentioned in TMO member yaliang's signature, and it turns out that some folks in China are using Pierogi. And not only using it...

http://attimg.dospy.com/img/day_1303...kb7YdC454z.png

Wow! :eek: Someone's been hacking at the Pierogi code quite a bit. :)

(Link to original Chinese forum board posting)

Re: [Announce] Pierogi - a universal infrared remote control app
 

It's a pity that they're not contributing code back to mainstream :D Don't be surprised, if you find pierogi with price tag attached, at some chineese site, too ;)

Re: [Announce] Pierogi - a universal infrared remote control app
 

Well, this weekend I tried to clean up some Denon receiver keysets, and ran up against a problem I've had since the beginning of Pierogi -- I just can't corral the input selector buttons into one "universal" set. High-end audio ends up being the hardest to manage, with some remotes having more than a dozen separate buttons for different input sources. And it seems like no two remotes label these sources in the same way... :(

So, I've given up. Rather than trying to create dozens of tiny buttons, or come up with some scrolling mechanism to show more buttons, I'm now collecting all the input control values and creating a combo box out of them. To use this mechanism, you'll need to first select the input you want to control from the list, then press the "Switch to Selected Input" button; so, what was a single step on the original remote is now two steps in Pierogi. Oh well. :( But, at least I can now manage enormous lists of input sources without tearing my hair out.

I've made a pass through the keysets, and placed all the current input controls into this new list mechanism, but I'm sure I'll need to catch more that I missed (and fix errors). Please do tell me if you find a problem!

I've managed to squeeze this new control into the bottom of the Utility panel; this may make the controls just a little hard to operate, though. It has also taken over the existing Input panel. I'll add some screenshots of these new panels.

I've also put together a new "Receiver" panel; it is now the first panel of the "Audio Device Panels" collection. It basically just adds controls for presets and radio band choices to the existing Main panel. I'll add a screenshot of it as well.

I'll hopefully get a little more cleanup work done on the audio device interfaces.

And as always, please watch for new bugs! :)

Re: [Announce] Pierogi - a universal infrared remote control app
 

As I said I had my thoughts on this. While I like the way it is done in the Utility tab, small and clean. However, yes it requires two steps but seeing the size of this button. I think you can atleast squeeze 5 of these selector things in the input panel. As you can see on the screenshot on the receiver panel. We are loosing so much estate on that big button. So what about making about 4-8 (depending how much can fit comfortable) buttons? I guess most people use something like 4 inputs regularly and sometimes the need for an other input. I use most of the times only 2. Well of course there are complications as this would mean that you need to save settings what users set per keyset. But advantages are that you for certain inputs get one step actions again :)
Will tell if I find a problem, so far none. Only tested the new Denon keyset though.

Given what I said above you maybe can leave that input selector there but revive the inputtab with 4-8 of these selectors.
Looks clean, thanks!

Re: [Announce] Pierogi - a universal infrared remote control app
 

It has been a wonderful app in my N900 which turns out to be the best universal remote.
I'm just curious, is it possible to have an app in N900 which uses wi-fi to remote control cameras with wi-fi such as the Canon 6D / Canon 70D.
Thanks.

Re: [Announce] Pierogi - a universal infrared remote control app
 

Yes, I agree the Input panel does need to be reworked somehow (or otherwise removed). :) Let me look in to what it would take to add some user-defined input buttons to that screen; I don't know how much work that would require...

Re: [Announce] Pierogi - a universal infrared remote control app
 

Hmm. In theory, yes -- the N900, or really pretty much any computer with wi-fi, should be able to connect to a wi-fi aware device like the 6D / 70D. In practice, though, wi-fi interfaces are quite a bit more complex than Commercial IR remote interfaces; also, as far as I know right now, most manufacturers are keeping closer control over their wireless software, and aren't keen on seeing open-source versions of their tools...

Ultimately, it isn't likely that such controls will be making it into Pierogi any time soon, but a closed-source control app might be feasible. Anyway, I'll take a look at what folks have been doing with the Canons... :)

Edit: Well, maybe I'm wrong! Looks like the GPhoto guys are already supporting remote control for a number of different cameras. There's even been an attempt to get GPhoto running on the N900, specifically for remote control purposes (although via USB, not wi-fi). Might be more doable than I'd thought. :)

Edit 2: A very nice little video. :)

Re: [Announce] Pierogi - a universal infrared remote control app
 

Yeah that would be awesome too, but I think that's beyond this project scope. Even if I don't own a wifi enabled cam.
Speaking of more ways of remote controlling. I really would like to use my N900 as bluetooth and wifi keyboard + mousepad. Yeah I know bluemaemo, but it sucks and it is buggy.

Copernicus, I seeing forward for your next great solution (: Just duplicating the current button would already be sufficient in my opinion. Still you would need to make them independent of each other...

Re: [Announce] Pierogi - a universal infrared remote control app
 

@Copernicus

Thank you for your great work! All your apps are really useful, but i have to admin one great issue: the app's icons!! :)

Please consider something more related to the function of the application for pierogi, lanterne and orecchiette.

There is enough mess into the maemo application menu, and an icon describing the function would help a lot.

Thanks again!

Re: [Announce] Pierogi - a universal infrared remote control app
 

Yeah I stumled into that but as I use a custom icon theme I just adde my own png icons and this the result. A lot more useful icons. The flashlight icon is extracted from the known flashlight app before we all used Lanterne. The second icon is found by searching the web with the following term: "remote control icon". I don't know if they have any rights but I think you can find them yourself. Then look in the desktop file how the icon should be named and place them in /op/usr/share/icons/your_icon_theme/64x64/applications/

Result is attached

Re: [Announce] Pierogi - a universal infrared remote control app
 

I would love to! :) However, there's one significant issue I always bump into:

I have _zero_ artistic ability.

Is there a tutorial somewhere about how one comes up with icons? I would imagine that people draw them using various tools of art, but I have no real idea how one best accomplishes that. (Heck, when I created the first iteration of Lanterne, it took me longer to find a photo of the pasta and turn it into an icon than it did to write and prepare the rest of the app...)

Re: [Announce] Pierogi - a universal infrared remote control app
 

1014 bytes of crude pixel work... and a scaled photo of my personal torch..

But probably pierogi would need a better solution.

Re: [Announce] Pierogi - a universal infrared remote control app
 

Hey, I actually like the pasta icons! Found them strange at first, too, but now they're part of "folklore" :) And, you know, what better describes Pierogi than Pierogi icon? Orecchiette ressembles ear, and Lanterne icon is like... Errrm, a waveform of light? ;)

Seriously though, I understand where are you coming from with that icon request. Still, part of me would be sad to get rid of that "tradition" ;)

/Estel

Re: [Announce] Pierogi - a universal infrared remote control app
 

current icons are deciving but are ok acccording to the used naming convention. maybe a combination of old and new or some unique mark or overlay in each icon to represent the feature or significing pasta family.

Re: [Announce] Pierogi - a universal infrared remote control app
 

I also completely agree. if you don't like them it's fairly easy to change them.

The pasta icons make them stand out from other applications on the desktop.

As for Lanterne icon, I still like Torchio as a type of pasta that resembles a torch. :)

Re: [Announce] Pierogi - a universal infrared remote control app
 

Lanterne and Orecchiette are quite obvious if you ask me. I am not sure Pierogi - I did not even know it was a pasta shape until now, I thought the icon was a slice of a lemon - but I got used to it.

I'd say leave the icons be. Looking at my (Windows) desktop, only 8 out of 24 icons have anything to do with the functionality of the thing they represent (Recycle Bin, This PC, Calculator - all MS, plus Firefox, Firebird, Putty, ImgBurn, Audacity). 4 more are somehow related to the name (CodeBlocks, Qt Creator, Wireshark, Skype). Copernicus' pasta icons fall into this category. The rest are complete fabrications (Adobe Reader, Hugin, HexEdit, Inkscape. LibreOffice, WinSCP, Nokia Suite...).

Re: [Announce] Pierogi - a universal infrared remote control app
 

Epic thread. Good to see that devs are still active for N900 apps.

I myself moved to a GS4 a little while ago. I have to admit, it is a much better phone. I do miss the openness of having a full linux phone, but I don't miss all of the fun quirks when it came to the actual phone part.

That being said, the N900 is still an epic little computer! I'm trying to bring some life back into mine and have been working on a personal project to create a hacked-up jukebox type device connected to a stereo with a web based UI.

So far, I've managed to get the following working pretty well:

• Mounting NAS and syncing music to device nightly via script
• Running MPD on device (works with MPD remote apps in Android, using desktop MPD clients or over SSH, but not geeky enough.)
• Running lighttpd and php on device (surprisingly well performing!)
• running old PHP MPD remote apps in lighttpd which can play music and manage the queue*
• DNS masq from music.net on my router to the PHP file on N900 ip.

*I've still got some work to do on the PHP UI. It can pull playlists and the full song list from the MPD DB, but for whatever reason, it doesn't have the artist>album>song hierarchy. Also, no way to put the play queue into random mode or move songs up/down. Might be something the original PHP dev never implemented. I'm pretty sure I can figure this out with some effort. And I'm likely going to have to as I can't find any modern PHP MPD clients or any with active development.

So where does pierogi come into this?

Well, right now, I need to turn my stereo on/off and adjust volume with the low tech original remote. That doesn't satisfy my inner nerd in the slightest. In my use case, I'm never actually touching my N900. It just sits on top of the stereo and plays music when the web UI tells it to.

Conveniently, the stereo 'tower' is inside of a glass cabinet. If I point the N900 just right with the door closed, the reflection on the glass works and I can control it with pierogi.

The problem in my case of course is that I don't want to touch the N900 (ever). I read through some of the history on this thread and through your documentation. Did you ever get a CLI running? What I would like to do is take advantage of all the protocol work that you did and call pierogi buttons from bash scripts from PHP. I'd add some PHP code and introduce buttons in my web UI for power and volume.

I've looked through your source, but I can't wrap my head around how the protocols actually work (Kaseikyo using the PanasonicAudio2 keyset; working flawless on Panasonic SA-AK40). Way too complicated for my current skill.

I was thinking that as more and more people need a non-phone use for their N900, that adding a CLI to pierogi could turn it into an IR blaster of sorts for the bash script happy like me. You could even write a PHP web ui in theory giving people whole home IR blaster capability.

Unfortunately, my C++ foo is limited to reading it and getting the gist. I've never written anything so adding a CLI to your app is out of my current capabilities.

If you are not interested in a CLI at the moment, perhaps you might be willing to share some info on constructing the command array[s] based on the protocol above? I'm assuming that if I modprobe the lirc0 device and echo a proper array to it that it would actually transmit?

I can easily create and destroy the device, just have no idea how to 'make it go' in bash.

Lastly, really well done on this app! Not only is it really well designed and implemented, but your commitment to the app and the users is truly amazing and impressive.

Re: [Announce] Pierogi - a universal infrared remote control app
 

No, I still have no CLI for Pierogi as yet. :( My problem has always been "how does the user specify the keyset and key they want to use"?

The LIRC server gets away with this by only loading a single keyset config file at a time, and letting the user match keyname strings against what is written in that file. Unfortunately, Pierogi has something like 700 keysets now, with more than 200 possible keys to be defined within each keyset (not including the many commands that I haven't yet matched up to a key). So, exposing all that information to the user, and doing so in a way that doesn't break their scripts every time I come out with an update, is something of a challenge. :)

(But yeah, you might want to check out using LIRC -- if you're only interested in controlling a single device, the LIRC already does everything you want, and you can control it completely from the command line.)

That said, I've been picking away at the half-broken Pierogi macro system for the last few days... A macro is really just an automated script telling Pierogi which keys to press; there's no reason you couldn't just specify a macro on the command line. That would allow me to hide all the ugly details where the macro is specified. :) I'll see if I can't get something working...

Ah, well, most of the code involved in one of Pierogi's "protocols" involves setting up a "device" value and a "command" value into a particular sequence (sometimes with a few extra numbers thrown in), which then gets converted to binary values. This lets me store just the actual command values as a keyset.

The LIRC doesn't bother with this, and its config files store the entire string of numbers that get converted to binary, without bothering to try to figure out what part is a device value or a command value or whatever. Easier to wrap your head around what is actually being sent that way, if you prefer...

Indeed! The infrared device driver has gotta be one of the simplest devices ever created. :) Fun to play with...

EDIT: Well, maybe not a bare array; I suppose you'll still need to make some kind of function call to properly communicate with it. It's still one of the simplest device drivers out there, though.

Thanks! But, I shall let you in on a little secret: the primary user of Pierogi is me! All you folks out there using it and telling me what does and does not work, are merely allowing me to perfect a single device that can CONTROL EVERYTHING AND TAKE OVER THE WORLD!!! Bwa ha ha ha ha!!!

Ahem. Anyway, I'm glad you're enjoying the app. ;)

Re: [Announce] Pierogi - a universal infrared remote control app
 

Yeah, I see now how a CLI would be difficult especially regarding how to standardize so things don't break when you edit keysets. Thanks for the clarification on the protocols. It makes more sense now.

I'll look into LIRC for my purpose. Should be just what I need to accomplish my (odd) goal.

That being said, have you considered porting pierogi to android? The IR remote apps in the play store all suck the big one.

Re: [Announce] Pierogi - a universal infrared remote control app
 

I would _love_ to do that! I really should try again... The last time I tried (last year), it turned out that, while I could easily port the Pierogi code to Android, the IR hardware could only be reached by using device drivers provided by the manufacturers. I contacted one manufacturer (HTC), and they were more than happy to give me everything I needed to get it up and running on their devices -- once I had signed the appropriate NDA. Unfortunately, said NDA required that no code using the device driver (or, really, their entire SDK) could be open-source.

This is a problem for me, as not only is Pierogi currently distributed under an open-source license, it was originally based partly on the LIRC (although that really isn't the case any more), and more importantly relies upon keyset data provided publicly on sites like "hifi-remotes.com". I don't think there's any way I could realistically convert it into a closed-source app at this point.

Maybe things have gotten better on the device driver front. I should take another look...

EDIT: Well, heck! It looks like main-line Android now has an API for infrared. I'll have to download it and take a look. :) (Anybody out there have an Android device with IR who would be willing to test? I don't personally own any Android devices myself...)

Re: [Announce] Pierogi - a universal infrared remote control app
 

I would be happy to test. I have a GS4 running kit kat which at very least 'works' (blinks the ir led; seen via camera; apps are too crappy to test further) with the crappy IR apps in the play store. Would be great to have a working IR app that doesn't pop up an ad every 2 seconds and limit the usage to barely anything even though it's ad supported.

Though I'm having a fairly rare free time spurt which doesn't happen often so I might not be the most responsive tester in the world, but I'll do what I can.

Good call on LIRC btw. I have it sending the proper ir commands by script and getting php to call my scripts should be trivial. Problem is that I can only call irsend with root permissions and I'm struggling to find out where in the program chain the permissions issue is. Don't really want to give my lighttpd user root permissions....

Thanks for the helpful suggestion there.

Re: [Announce] Pierogi - a universal infrared remote control app
 

Macros! I've finally started to clean up Pierogi's macro mechanism. I've realized that there were two major design issues holding me back; first, I was too caught up in the notion of making macros into "user-defined buttons". Ultimately, macros work by doing exactly what the user does -- selecting and sending commands to the IR port. You just can't have the user and a macro controlling Pierogi at the same time. So now, while a macro is running, a modal dialog box will pop up, showing what the macro is doing, but also blocking the UI; if the user closes the dialog box, he or she will regain access to the UI, but the macro will be aborted. Very simple, very clean.

The other issue was attempting to create, edit, and save macros completely from within Pierogi itself. This allowed me to hide some of the internal ugliness from the user, but ultimately it's just way, way too complex of a UI for me to maintain. So, I have instead moved to storing macros in an XML file. I admit that writing and loading these files will be a burden on the user, but it can't be as much of a burden as trying to negotiate the previous macro editor UI.

Ok, so Pierogi 1.1.32, with a first attempt at this new macro system, is now working its way up into extras-devel.

To get the bad news out of the way: if you've been using the existing macro mechanism, this is going to break your macros. I apologize, but the existing system was just such a mess, that I didn't think I could easily find some way to transition to the new system.

The good news is that the new system should be working just as well as the old one. (I've more or less just repackaged the existing macro functionality.) So, you should be able to do as much with the new system as with the old one.

As mentioned, macros are now defined in an XML file. I haven't put a whole lot of effort into defining the file format yet (I don't even have a DTD for it), but I've got a little bit of documentation set up describing how to create this XML file.

The previous "User" panel has been renamed "Macros", and has a new button allowing you to load an XML file. Along with the previous six user-defined buttons, it also has a combo box allowing you to access any macro from the file.

Another side-effect of this new macro system is that it allows you to access the entire set of keys defined within Pierogi (which you can now find listed in the above-mentioned documentation). This means that, for example, you now have access to some of the commands that I've been too nervous to place into the main user interface. So, if you want to access the service menu of a TV (which I have defined for some LG, Samsung, and Sanyo keysets), the following XML file will do the trick for you:

The nice thing about using XML is that it should be much easier for me to extend the macro functionality. Timers, loops, conditionals, pretty much anything should be fair game...

As always, please be prepared for a lot of bugs. (Especially with the entirely new XML parser! Also, the keyboard controls are currently broken, but I think they were broken before...)

P.S., new Pierogi website!

Re: [Announce] Pierogi - a universal infrared remote control app
 

Qt does indeed live up to the hype; it took me some hair-pulling to set up an Android environment for the first time, but once that was done, it's surprisingly easy to port an app over... (Although I obviously need to do a lot of work to support a portrait layout. Maybe I could port that layout back and finally make Sixwheeledbeast happy. :) )

Pierogi running in an Android emulator (and this is Qt Widgets, not QML!):

Re: [Announce] Pierogi - a universal infrared remote control app
 

Ok, so I have been playing with the new macro update.
While it takes a bit more typing, it seems easier after a while.

A few comments...

All the links in app go to the old website so I had to come to TMO to find the link to the macro docs.

Having trouble getting the pause command to work, you have no examples to copy in the docs.

The logical guess, IMO

Throws up parsing errors in application and with an XML validator.
So I have get to work that out.

Also it would be nice if we could hide the XML file away from MyDocs, I hate settings files missing up documents folders. Open file will only allow user accessible locations. Ideally I would locate it in /home/user/.pierogi for example.

Re: [Announce] Pierogi - a universal infrared remote control app
 

Oops, sorry, I really do need to clean up the documentation. (I keep putting that off...)

Also, I honestly do intend to finally try and get a extras-worthy version of 1.1 prepared once the documentation is updated. :)

Sorry about that! Yeah, the current syntax is:

I was thinking that other attributes, such as "millisecond" or "minute", might be convenient in other situations. (Pausing by minute, along with a loop, would be enough to implement an intervalometer. I really need to get some more work done on adding more macro features...)

Hmm. That sounds quite logical; and, it's yet another strike against the Qt "getOpenFileName" dialog. :( I'm going to have to come up with some custom dialog of my own, I guess... Thanks!

Re: [Announce] Pierogi - a universal infrared remote control app
 

Is Pierogi really working on air conditioner?
I try Pierogi on Panasonic and General Electric air con, but I can't get it work.
No keyset is working.
I have no problem using Pierogi on my tv.
Does air con on Pierogi need special step (like change carrier frequency)?

Re: [Announce] Pierogi - a universal infrared remote control app
 

Well, I have to admit that Pierogi is just barely working on air conditioners. The big problem here is that there are just no good (public) sources of keyset data for air conditioners. Especially for the "stateful" A/Cs; in general, if your A/C's remote control has an LCD screen on it, that means it retains information about all the settings within the remote itself. Because of this, each time you send a command from the remote, all the settings get sent at the same time. This makes decoding signals a lot more of a hassle.

That said, I'll take another look around; things might have improved a bit since the last time I checked... :)

Edit: Hey, does your A/C remote look like this?

http://cdn.instructables.com/FQH/XC4...K3QV.LARGE.jpg

I've found a site where someone did the hard work of decoding this thing's signals... I'll add it in to Pierogi asap. :)

Re: [Announce] Pierogi - a universal infrared remote control app
 

No problem

This is good to here

Great that worked.

I now have a compatible XML.
Having issues getting the Sleep command to work on LG again, I am sure we had this issue before. Works ok in Utility but Macro seems to fail.

TBH I'd be happy with a fixed place, it's only a small file. Maybe even a open with "your favourite text editor" button.

Re: [Announce] Pierogi - a universal infrared remote control app
 

Hmm. Maybe a timing issue? The macro system currently simulates a very quick keypress for each "send" command; if you need to hold the sleep button down for a little while before the TV will accept it, that could be the problem. (This is another parameter I need to add to the XML spec. :) )

Yeah, I think you're right; there should at least be a "default" macros file. (I was kind of hoping that it'd be useful to have multiple macro packs available; maybe a pack specific to the living room, another one for the bedroom. Or perhaps even set up complicated macro packs for special purposes -- trick photography, recording TV broadcasts, controlling a media room, etc. Anyway, I'm kinda getting ahead of myself here... :) ) I'll see what I can do. :)

Re: [Announce] Pierogi - a universal infrared remote control app
 

You could do that in the one file.
You have the macropack's listed by name.
I don't see why one file can't have multiple macropack tags as long as the name's don't conflict.
Maybe upon loading the Macro panel, the file is refreshed an the macropack's are listed in a combobox?

Re: [Announce] Pierogi - a universal infrared remote control app
 

Maybe, I don't know. It was the A/C on the Church :p

Re: [Announce] Pierogi - a universal infrared remote control app
 

A note on icons... After the discussion earlier in this thread about my pasta-flavored icons, followed by the need to create a new icon for Torchio, followed by the discovery that my current icons are all simply too small for use on Android, I've come to the realization that I probably do need to create some new icons. Sixwheeledbeast suggested that for Torchio I could use an icon for a terminal screen overlaid by a pasta image, and I'm thinking that combining a functional icon with a pasta icon might be a good idea for all my apps.

Anyway, I've been playing around with a very cool little vector graphics program called Inkscape, and have been trying out some ideas. For Pierogi, I was thinking that a power icon overlaid by a pierogi might work. I'll append a few shots of what I've got right now to this post (one at the resolution used by the N900 for app icons, and one a little bigger to see some detail). Please tell me what you think! Thanks.

Re: [Announce] Pierogi - a universal infrared remote control app
 

I have a cheap and rare low quality LCD TV: Buslink MLT-8V.

http://www.amazon.com/Buslink-MLT-8V.../dp/B000BLHZO2
http://www.newegg.com/Product/Produc...82E16889119001

I'd request it be added, but I don't know where to look for the IR commands for it. Pierogi automatic search did not help.

Re: [Announce] Pierogi - a universal infrared remote control app
 

Wow. When you say "rare", you ain't kidding. I can't find any mention of a "Buslink" brand in the LIRC archive or the hifi-remotes site. The Buslink company does have a website, but nothing there describes them ever producing TVs, and all links to Buslink TV product or support pages on their site are coming up as "Page not found" errors. Heck, I just did a general Google search for "Buslink MLT-8V", and the post you just made is now entry #37 in that list (and is probably more informative than most of the stuff ahead of it).

Chances of finding a ready-built config file are, I suspect, slim to none. :)

Hmm. If none of the existing Pierogi keysets can power it on, I'm not sure what else there is to do at this point. The only thing left would be to use a device that can "learn" the remote codes off the Buslink remote. (I know that a PC with an IR receiver running the LIRC server can do it, and there are a number of other ways to do so as well.) If you can get those codes, I can probably decode them and add them in to Pierogi...

Re: [Announce] Pierogi - a universal infrared remote control app
 

The new icon is very appetizing! Thumbs(and NEONS) up for it. If I would change something, it would be color of Pierog (singular) there - from artificial yellow to more natural-looking, edible one.

...is it still a thread about InfraRed remote control program? ;)

/Estel