olibe | # 901 | 2013-04-30, 08:32 | Report

Hello Copernicus,
Any news about Cisco 8485DVB / Voocorder support?
I don't know if this link can help you http://www.hifi-remote.com/forums/dl...e&file_id=7129
Sincerely,
Olivier

stickymick | # 902 | 2013-04-30, 08:35 | Report

Update installed. Will do some testing when I get into work later.
Gonna have to do a search to find out what all those "Other" devices are. Be great to have an infra-red teabag squeezer, saves scalding your pinkies. :P

Copernicus | # 903 | 2013-04-30, 12:02 | Report

Interesting! And perplexing. I can't think of anything I've done in the last couple of updates that should affect this problem.

If nothing else, I suppose you could try a complete uninstall and reinstall of Pierogi, and see if the problem gets better (or worse). Although I can't think of anything that would fix. (But then, I can't see how an update would change things either...)

Let me ask, is Pierogi the only app behaving badly right now?

Copernicus | # 904 | 2013-04-30, 12:06 | Report

I've already got that particular config file set up as "Cisco Set-Top Box Keyset 1". Is that keyset not working? (Sorry if the naming is a bit generic, I've been trying to come up with names that describe all the possible devices that a particular keyset can match...)

Let me look around for other config files, maybe this one was bad.

olibe | # 905 | 2013-04-30, 12:48 | Report

My device is a Cisco 8485DVB Rev 1.7, rebranded VOOcorder by my operator (VOO) in Belgium. The Pierogi exit key is mapped by the Cisco 8485DVB info key so without an exit key isn't really usable

Whispering Weasel | # 906 | 2013-04-30, 13:03 | Report

I am beginning to suspect some kind of timing issue ?, maybe kernel or overclocking related or cssu-thumb. I unfortunately have no access to another (known good) ir-controlled device at the moment so it can also be the case that the speaker-system is very picky:
I reinstalled pierogi and after that it was the same as before, however, last time i tested I had some other apps open so I opened modrana, cloudgps, conky, and in terminal: top and midnight commander, to keep the system busy and when these are open the speakers-system response is much improved.

I have also tested this with the default profile for overclocking (max 600 mhz etc) and the same thing happens, when I open modrana for instance and switch back to pierogi the speaker-system response is much better

Copernicus | # 907 | 2013-04-30, 13:16 | Report

Ah, that would be a bug in the config file, then -- that file doesn't even have an "info" key listed. I'm not seeing anything else with the "voocorder" label, but there are piles and piles of Cisco config files available, I'll see if I can find another match.

(I'll go ahead and map what I've got as "exit" to "info", but that still leaves the exit button unmapped. )

Copernicus | # 908 | 2013-04-30, 13:32 | Report

Aha, interesting! Yes, in IR, everything is in the timings. However, lots of people have been using Pierogi with overclocking seemingly without poor results...

I'm sending raw timing values to the kernel via the /dev/lirc0 device driver. Something somewhere in the hardware has to be counting time (in microseconds) for the IR pulses to come out right. Maybe something other than the CPU itself is now being overclocked? Or, perhaps, a change in the kernel has started throwing off the timing mechanism, regardless of the clock setting.

In any case, this probably means I need to get up to speed with the latest kernel changes.

qwazix | # 909 | 2013-04-30, 14:55 | Report

For the record I am on latest thumb, without any OC (never OC'ed this particular N900) and I experience no problems.

Estel | # 910 | 2013-04-30, 16:22 | Report

I'm on kernel-power, CSSU-thumb, limits 500-900 mhz, and no problems either.

BTW, Copernicus, I know that you never meant to create a standard, but from what you've described, it seems that you're getting best things from all words, with the "culmination" of Pierogi being able to control stateful AC's, no small feat.

Maybe, in the long run, after creating some way of config update, it would be good idea, to try upstreaming it? IT seems that you "standard" is going to be a very flexible and powerful one. Something, that all "for internal use" (i.e. virtually all "standards" present now)
things are lacking.

Of course, I don't expect any help from manufacturers - I mean "standard" for linux world/DIY IR things use cases.

/Estel