Ok, then select GPIO 4, donât change other settings for now and click âSaveâ.
Thanks, it work
Hi All,
I have, earlier today, posted a question regarding exactly this Audiophonics remote control being discussed here in another thread (DAC sabre Audiophonics). As explained over there, I have:
- AUDIOPHONICS EVO-SABRE Balanced DAC 2x ES9038Q2M USB GPIO Raspberry Pi SPDIF Bluetooth XLR RCA
- a RBPI4
- the Waveshare 7.9inch HDMI touch display
- and of course Volumio running on it
My problem is that the remote control provided with the Audiophonics DAC was only working partially, the play/pause and left/right etc. buttons were not working. Everything else is just fine.
Later then, I found this thread and followed the suggestions:
- install the âIR Remote Controllerâ plugin
- copy the content of that zip with the âAudiophonics RaspDAC Miniâ profile to the right place
- select that profile in the plugin, and set GPIO to 4 (simply because I did not know any better)
- reboot
Now I have the play/pause and left/right buttons also working nicely, with the only issue being that sometimes pressing a button once results into more than 1 action - e.g. pressing ârightâ once, but moving to the second or third next track.
Maybe also relevant, the status of the remote control int the âAudiophonics Evo Sabreâ plugin is now showing errors (and fomerly did not).
So, in essence it seems that that Audiophonics RaspDAC Mini profile is doing something better than the DAC plugin, but is also somehow conflicting with it.
Any suggestions anyone?
If you are using the âAudiophonics Evo Sabreâ plugin I suggest not to install the IR Controller plugin, too. The âAudiophonics Evo Sabreâ plugin should already handle the remote controls signals. Having both plugins may lead to conflicts/interferences.
Assuming you want to use the âAudiophonics Evo Sabreâ plugin I suggest to uninstall the IR Controller plugin. Since this will also uninstall lirc you will probably have to uninstall and reinstall the âAudiophonics Evo Sabreâ plugin after that.
I did what you suggested:
- uninstalled the IR controller plugin
- uninstalled the Audiophonics Evo Sabre plugin. This failed for lirc was missing, so I had to uninstall it manually (remove the directory, and its reference in plugins.json)
- reboot
now I am back to where I was - the remote control only working partially (just the volume, mute, power, input and filter buttons).
It seems the Audiophonics Evo Sabre plugin is not installing lirc by itself. It should be in the dev folder, right?
It should.
Since this appears to be an issue with the Audiophonics Evo Sabre plugin I suggest to ask for support in the [ [PLUGIN] Audiophonics EVO Sabre thread.
I was already in contact with Audiophonics directly, and they had even offered that I sent the DAC back and they test it. Since I was sure this is a config issue I played around with it a bit more first.
I now have everything working. I am not sure why though. I installed lirc manually again (python - Setup IR Remote Control Using LIRC for the Raspberry PI (RPi) - Stack Overflow), added âdtoverlay=gpio-ir,gpio_pin=4â to my userconfig.txt, rebooted several times, and now it does what it should.
@gvolt the plugin does not start properly on the latest beta with kernel 6.6, could you please have a look?
it gives an error of failing configuration
the workaround is to add the overlay manually on userconfig.txt
Are you referring to version 3.771 or to 0.012 (Bookworm)?
to the buster version with kernel 6.6 (beta 3.771)
we are currently blocked to promote it as stable because several plugins are still not working
Hi Dario, I believe there is a mixup with âIR Activity LEDâ. Tested the IR controller again, but no issues found.
@gvolt
Minor:
Location of IR-configurations is still located at: /data/plugins/system_hardware/ir_controller/configurations
Should move to: /data/INTERNAL/ir_controller/configurations
/data/plugins/system_hardware/ir_controller/configurations contains only the configurations that come with the plugin (âfactory profilesâ).
/data/INTERNAL/ir_controller/configurations is for configurations the user provides.
It is necessary to maintain this separation, as this makes it possible to modify existing profiles and save them in /data/INTERNAL/ir_controller/configurations without having to modify the âfactory profilesâ.
From the pluginâs readme:
User-specific configurations for remote controls can be stored in a dedicated folder named â/data/INTERNAL/ir_controller/configurationsâ. A subfolder must be created in the aforementioned directory for each remote control, in which the LIRC files âlircrcâ and âlirc.confâ are stored for the remote control.
The name of the subfolder appears in the list of selectable remote controls. If this name is also used for one of the remote control configurations already supplied, the userâs own configuration with the same name takes precedence.
Note: Updating the plugin does not affect the user-defined configurations. However, when the plugin is uninstalled, the â/data/INTERNAL/ir_controllerâ directory is deleted along with all the subfolders and files it contains.
So, IMHO the locations of factory and user IR configurations are correct and should not be changed.
in the plugin overview table of the beta thread it is mentioned what is the problem
I confirm I get a popup error when I activate the plugin, I will try to grab a screenshot
I tried several times to reproduce the popup with the error message, without success.
I can confirm that the plugin works out-of-the-box on the latest beta image with kernel 6.6, no need to release a new version.
I also tried it with the latest img v3.771, 6.6 kernel.
also comment out dtoverlay=gpio-ir,gpio_pin=25 in userconfig.txt
problem is gone all is well now.
raspberry Pi5, 4 GB