Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

audiosettings: add helper service to set ALSA defaults on RPI #3759

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

cmitu
Copy link
Contributor

@cmitu cmitu commented Oct 4, 2023

Added a helper method that installs a systemd service meant to automatically configure ALSA with the HDMI 0 port when using the ARM vc4hdmi RPI driver. The service will run once then disable itself.

Since the default ALSA configuration on RaspiOS goes through the analog output (Heaphones) when the vc4-kms-v3d overlay is present, if we want to configure the HDMI output by default there needs to be an additional configuration. The additional configuration needs also to be applied when only one audio output is present, since the ALSA config is a bit more involved.

There are a couple of reasons for using a service and creating the configuration on the device itself (on 1st boot):

  • the vc4hdmi device index can be different depending on the Pi model. Pi0(w)/Pi400 has no analog output by default and CM models may not have it also)
  • the card name can also be different (Pi4 with 2 devices vs Pi3/Pi2/Pi1 with 1 device)

Note that the service will configure the 1st HDMI port/device, on Pi models with multiple HDMI ports (Pi4/Pi 400/Pi5/CM4) the user will still need to use the Audio settings dialog to change it if they want to. There may be a way to detect which HDMI port is active and has audio, but that's not implemented.

@cmitu cmitu force-pushed the audio-kms-defaults branch from adffb9f to 39f7203 Compare October 4, 2023 04:47
Added a helper method that installs a `systemd` service meant to automatically configure ALSA with the HDMI 0 port when using the ARM `vc4hdmi` RPI driver. The service will run once then disable itself.

Since the default ALSA configuration on RaspiOS goes through the analog output (Heaphones) when the `vc4-kms-v3d` overlay is present, if we want to configure the HDMI output by default there needs to be an additional configuration.  The additional configuration needs also to be applied when only one audio output is present, since the ALSA config is a bit more involved.

There are a couple of reasons for which is a service:
 - the `vc4hdmi` device index can be different depending on the Pi model. Pi0(w)/Pi400 has no analog output by default and CM models may not have it also)
 - the card name can also be different (Pi4 with 2 devices vs Pi3/Pi2/Pi1 with 1 device)

Note that the service will configure the 1st HDMI port/device, on Pi models with multiple HDMI ports (Pi4/Pi 400/Pi5/CM4) the user will still need to use the Audio settings dialog to change it if they want to. There may be a way to detect which HDMI port is active and has audio, but that's not implemented.
@cmitu cmitu force-pushed the audio-kms-defaults branch from 39f7203 to e39d31c Compare October 5, 2023 02:36
@joolswills
Copy link
Member

joolswills commented Oct 8, 2023

Thanks for this. Where is this triggered from currently ? I can't see where the function is called - or is it for a future change ?

@cmitu
Copy link
Contributor Author

cmitu commented Oct 9, 2023

@joolswills for now it's not hooked anywhere, my initial thought is to add it to the image generation, like xpad, based on the platform and image (i.e. only add it to RPI and bullseye and later).

@joolswills
Copy link
Member

Thanks. I wonder if there is a way to do this without the duplication of alsa config. Also a function to remove the service would be needed, but I'm going to have a think about options.

@cmitu
Copy link
Contributor Author

cmitu commented Oct 11, 2023

I wonder if there is a way to do this without the duplication of alsa config.

Initially the implementation called audiosettings's _asoundrc_save_audiosettings method from the service, with the appropriate parameters, to generate the config. But I thought it would be faster to not load RetroPie's scripts, in order to finish up quickly before the autologin process is started and EmulationStation powers up. But that would start-up some additional processes and that's not what we want.
Maybe if I rewrite _asoundrc_save_audiosettings and remove any RetroPie specific functions (hasFlag, etc.) we can just source audiosettings.sh and call the function with the right parameters.

Also a function to remove the service would be needed, but I'm going to have a think about options.

I though about this also, was thinking to add a parameter to the new function call (alsa_defaults_service_audiosettings) to either install or remove the service. Right now it only does the installation. Not sure when to invoke the removal though, maybe at the start gui_audiosettings, when the user is configuring the audio themselves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants