Support > Remote Buddy Forum > LIRC support for Remote Buddy // IOSPIRIT [EN]

Support

All support resources for our products. Here you can find answers to frequently asked questions, discuss with other users, recover a lost license code or file a support request.

Forum closed

This forum was closed and turned into an archive effective April 21, 2018. It is no longer possible to create new topics or reply to existing topics.

Thanks everyone for all the great questions and contributions over the years.

Please use the Contact form to get in touch.

Remote Buddy Forum

Overview

Author

Thread

User

07.01.2011 10:34:09

LIRC support for Remote Buddy

View

This posting is older than 6 months and can contain outdated information.

Hi there,

I think it would be an awesome feature and also easy to implement LIRC support for Remote Buddy. LIRCd (running as a server on some Linux box) provides a IP network socket (TCP or UDP) where it spits out all the IR events it receives decoded to the remote controller key level so no further timing calulation or other processing needs to be done. It uses a text based protocol delimited by newlines, so it is very very easy to parse.

Quote from the LIRCd manual:

With the --listen option you can let lircd listen for network connections on the given address/port. The default address is 0.0.0.0, which means that connections on all network interfaces will be accepted. The default port is 8765. No security checks are currently implemented. The listening lircd instance will send all IR events to the connecting lircd instances.

Thanks in advance,

Endre

Last edited: 07.01.2011 11:02:39

These entries from the FAQ may be relevant to this topic:

Hardware - Apple® Remote

After uninstalling/quitting Remote Buddy, my Mac® no longer reacts to the Apple® Remote. (FAQ015E0241)
To enable you to use all capabilities of the IR Receiver of your Mac®, Remote Buddy is using its own driver. In contrast, all other applications with integrated Apple® Remote support usually use the OS X Apple® Remote subsystem.

As long as you're running Remote Buddy, Remote Buddy and its driver are responsible for turning the received button presses into actions. As soon as you quit Remote Buddy, this task is again handled by the OS X Apple® Remote subsystem.

If other applications don't use the interface to the OS X Apple® Remote subsystem correctly, this can lead to the effect that nothing happens when you press a button on your Apple® Remote. For as long as you're running Remote Buddy, issues like this are covered by Remote Buddy and it's driver and are therefore not visible to you. However, as soon as you quit Remote Buddy, the OS X Apple® Remote subsystem is back in control and any issues caused in it by other applications become visible.

Therefore Remote Buddy is neither the cause of the issue nor is it responsible for it. Instead, the cause of the issue exists independently of Remote Buddy. It's located elsewhere and can also only be solved there.

Although our products can't cause any such issues, we're regularly contacted about such issues and asked for help. In order to make locating and fixing the cause of such issues as easy and efficient as possible, we've developed a free diagnostics tool: Remote Control Diagnostics. It can locate issues with a single click and will provide you with information about the issue as well as with instructions on how you can fix it.

User

18.01.2011 13:13:02

Re: LIRC support for Remote Buddy

View

This posting is older than 6 months and can contain outdated information.

Thanks for your feedback.

I'm afraid, though, that such a feature is beyond the scope of what I want to do (and provide technical support for) with Remote Buddy.

Best regards,
Felix Schwarz

Remote Buddy
Support
1. Overview
2. Manuals
3. FAQs
4. Forums
1. Lost license code
2. Support inquiry
IOSPIRIT
1. About us
2. Blog
3. Labs
4. Developers
1. Contact
2. Press releases
3. Imprint
4. Jobs