Is it possible to record a whole remote and export it as a LIRC config?
Sure, that is what the "Scrutinize remote" pane is for. As soon as you have capturing running, you just read them in one batch, you can read in the signals and type the names in any order you like. Then export as Lirc.
Ok, seems like irrecord at least starts up.and receives SOMETHING, at least the first time. This is good news. Then sometthing hangs :- possibly the IrToy...
If you want to use that 15 years old program, let me suggest that you post on the Lirc mailing list on sourceforge. Otherwise I would suggest using my program IrScrutinizer, preferably on a PC (Linux, Windows, Mac), still using the IrToy, but connected to the PC. You can use it to generate a lirc.conf file that way.
It is just a few days old, so it is not yet available through apt-get. 0.9.2 will probably to too, but I doubt that it is apt-get-table either. Have to compile it yourself.
[quote author="jantum"]Hello, any news on this topic. jan[/quote]
The news is that the current version is 0.9.2a,
Apart from that, the original problem is of the category "Linux beginner problems". I gave constructive suggestions for solving it, Did you (or the OP) even try them?
When I reinstalled my Win7, I had to reinstall the driver for IrToy: In the device manager, press update driver, and direct it to an unpacked version of the IrToy software package. Then it was recognized.
Another tip is to watch out for Bluetooth serial ports, they may delay e.g. the startup time of IrScrutinizer with 10 seconds or more, and clutter the device manager. Just throw them out with the device manager, unless you are sure you want them.
Hope this helps and that you enjoy the 'Scrutinizer!
As an experiment to isolate the problem. let me suggest that you try it out with IrScrutinizer (version 1.1.1). It has a completely different driver. You can import your Lirc configuration, and send it through the 'Toy, for example, 100 times in a row.
Since, as far as I am aware, there was no liblirc.so in Lirc 0.9.1 and earlier, I conclude that you have been downloading the current sources from GIT and compiled it yourself.
The error message means that the executable cannot find a shared library that it needs. Either the latter was not installed in the proper place, or the executable cannot find it. You did "make install", not just mv-ing stuff around, did you? You may point LD_LIBRARY_PATH to the actual location of the shared library to run the contained programs, but that is not a permanent solution.
Assuming that you did follow the instructions, please report the problem, giving all relevant data, to the Lirc mailing list, see https://lists.sourceforge.net/lists/listinfo/lirc-list . You will have to subscribe before you can post.
First of all, start with --loglevel=10 and either --nodaemon or a logfile, and look for errors. If that does not give a clue, I would use IrScrutinizer (on a PC, Linux or Windows) to capture known good signals for your device. Capture all (or some) the commands, and try to transmit them from the Scrutinizer, all using the 'toy. If that works, generate a lirc configuration file agaiin with the Scrutinizer, and try it with your Lirc setup. If that still does not work, file a bug report at http://sourceforge.net/p/lirc/tickets/ giving as many details as possible.
As some of you may know, the IrToy driver by Peter Kooiman is now officially in the GIT Lirc, although no official release has been done since. (I even managed to get an improvement into it myself.) See http://sourceforge.net/p/lirc/tickets/20/
I tried the GIT Lirc (master branch) and the included IrToy driver for sending. Slammed 100 irsend commands (without delay, with full debugging turned on) to it -- no problems. Not even being root was necessary. (Full debugging (--loglevel=10) is not really resource friendly either...)
1. You are obviously using the irman Lirc driver, which uses the 'toy in the IrMan emulation mode. However, since a few weeks, a native driver (by Peter Kooiman) is officially a part of Lirc (https://sourceforge.net/p/lirc/git/ci/m ... ns/irtoy.c), although not contained in a release yet. (I have even added a few lines there myself.) So you have to suck the Git code (including the rest of Lirc) and compile it yourself.
2. Please try to learn the signals you want using the 'toy and IrScrutinizer. You can then, if desired, export it to Lirc format. IrScutinizer + IrToy make a very good IR learner, as opposed to Lirc.
I am not sure if it is still an issue, but the recently released version 1.1.1 of IrScrutinizer generates the binary format the OP was soliciting. Just select "IrToy-bin" as the export format.
Version 1.1.1 - New export format: IrToy-bin - New importer: IrTrans - Fix bug in Hexcalc when number > 65535. - Splash screen on startup. - Multiple decodes from DecodeIR are no longer "censored" (in all places). - Parametric remote -> Advanced -> "Set misc. parameters" now replaces all old parameters except D, S, F, and T. - Fixed unclear semantic of "count" sends of an IrSignal. - Fixed issue with sending by IrToy.
Version 1.1.0a. - IrToy: fixed several issues. (Only FW version 222 is supported.) - the count for transmit generated is now a saved property. - csv-importer: can now parse hexadecimal numbers starting with 0x.