lirc | lirc.go - a library to send and receive via lircd

use ls -ld /usr/share to see what the permissions on the directory are (without -d, you get the contents and their permissions).

Use code like:

They are not the same. The devinput driver uses the kernel decoder, and feeds these decoded events to the lircd fifo. This fifo is what clients read from.

The default driver reads raw timing data from the kernel and makes it's own decoding using lircd.conf.

In general, if the devinput driver works it could safely be used and is a simpler setup. The default driver is useful in contexts where the kernel decoding doesn't work for example when a remote isn't supported by the kernel or there is a need to send (blast) ir signals -- the latter cannot be done using the devinput driver.

More info: https://www.lirc.org/html/configuration-guide.html

There is no way to dump the options as such. However, by setting the loglevel to debug and inspect the logs using for example journalctl the values are visible.

EDIT: /dev/lirc0 and friends provides the raw, unencoded data from the kernel. The devinput driver reads from a /dev/input/eventXX device. In both cases 'auto' make lircd to use the first found usable device which works as long as there is only one remote connected.

I finally found the problem! After reading How to set `com.apple.developer.driverkit.transport.usb` entitlement?, I decided to experiment with the entitlements for my DEXT. This made me realize that the DEXT was not being loaded at all.

I changed the DEXT entitlements from:

See https://support.microsoft.com/en-us/help/316992/file-types-supported-by-windows-media-player

MP4 Video file (.mp4, .m4v, .mp4v, .3g2, .3gp2, .3gp, .3gpp)

[..] Windows Media Player does not support the playback of the .mp4 file format. You can play back .mp4 media files in Windows Media Player when you install DirectShow-compatible MPEG-4 decoder packs [..]

This answer assumes the RPi is running raspbian (version Buster Jun 2019). Also a working knowledge of the terminal, basic commands from the command prompt and editing text files is assumed.

Step 1: Install lirc

1) Open terminal window and install LIRC. Be forewarned that this will likely raise an error "Failed to start Flexible IR remote input/output application support" as the installed files now have .dist appended and the suffix must be removed as noted below. Not hard but frustrating.

I don't fully understand what you are trying to do at this point yet (you have provided very little hard information), so I'd ideally need some more information to be certain - kext info.plist, the API calls that are triggering the error, etc.

However, considering you list "IOProviderClass(IOUSBInterface)" in your comments and com.apple.iokit.IOUSBFamily shows up in the backtrace you quoted, my suspicion is that you are running into bugs in the increasingly badly maintained IOUSBFamily legacy compatibility layer you seem to be using in your kext. I have found various problems with this layer in Mojave and even more so in Catalina, some of them hardware-dependent (e.g. some problems only occur on some Mac models).

You can try reporting the bugs to Apple, but I suspect you will get the same advice I am about to give you: you should port your driver to the newer IOUSBHostFamily API. If possible, using DriverKit or as a regular user space daemon, otherwise as a kernel extension. If it must be a kernel extension, the IOUSBHost*.h header files from the macOS SDK contain porting instructions in the comments at the top of each file.

After reading your logs, it seems that you are able to connect to the RTSP protocol, but the RTP protocol fails.

I'd try two things:

• stream with rtp{dst=172.19.0.1
• Play the stream with --rtsp-tcp (if that works, it's an issue with UDP and your VM configuration)

After spending a great amount of time, trying to figure out how to solve this issue, I was finally able to resolve it. So hopefully my answer will help someone else.

First things first, it's important to note that infrared device has changed from lirc-rpi to gpio-ir

Although, I already had this change in my /boot/config.txt file,like below: