Okay, so the KMS HDMI devices appear between the onboard firmware audio devices and external/USB ones.
I'd not switch off my amp or made any changes. I went to put another film on and the audio had switched to the Default (Headphones). So the other night I was watching a film and the audio was set to my Denon amp (hdmi1) and the film ended.
Is there a way to remove some of the audio options from Kodi? Or at least change the Default audio? Any help greatly received!Ĭode: Select all **** List of PLAYBACK Hardware Devices ****Ĭard 0: Headphones, device 0: bcm2835 Headphones Ĭard 1: vc4hdmi0, device 0: MAI PCM i2s-hifi-0 Ĭard 2: vc4hdmi1, device 0: MAI PCM i2s-hifi-0 Ĭard 3: IQaudIODAC, device 0: IQaudIO DAC HiFi pcm512x-hifi-0 Previously I was able to use CGI scripts to change my audio but now they are not working well either. It's quite annoying as I'm having to go into settings everytime and put it back. I can't quite work out what is triggering it but every so often my Pi changes the audio to the Default (Headphones). KMS means that I now have audio passthrough which is big step forward But a downside is that the audio is a bit messed up. Hmm I suspect what you mention here might be related to my audio problem. Keep using the firmware HDMI audio via `noaudio` KMS parameter solves this, but breaks Kodi, and other downsides would be interesting to know. The KMS/VC4 HDMI device however always show up, regardless whether a HDMI screen is attached or not, and additionally they do not take `card 0` (and in case `card 1`) but get `card 1` (and in case `card 2`) while 3.5mm remains `card 0`, so that the auto fallback does not work and switching between legacy video or fKMS and KMS requires a change of the default ALSA/audio device index. Without `vc4-kms-v3d` enabled, we are able to use `card 0` as default ALSA device, and with an HDMI screen attached, this maps to HDMI audio (while 3.5mm is then `card 1`, respectively `card 2` on RPi 4 with two HDMI audio devices), while with no HDMI screen attached, the firmware HDMI device is not available which makes 3.5mm `card 0`, which is a nice default to ship Raspberry Pi images with.
Kodi unable to create gui triple screen driver#
Somehow related is the question what benefit the KMS/VC4 HDMI audio driver actually has over the firmware HDMI driver? A downside of KMS audio is that it cannot be configured anymore with a fallback to 3.5mm audio when no (HDMI capable) screen is attached. running an X server via KMS (modesetting DDX) works well with this parameter and hence using the firmware HDMI sound device. Just one question/issue: With `vc4-kms-v3d,noaudio` Kodi denies to start/show anything on the screen, while e.g.
Looks like I tested this with the Kodi build from Debian where X11 support is included, which fails as well when forcing Kodi to start with GBM. Many thanks for providing the new Kodi 19.3 package with the stable RPi repository, it works very well.Įarlier in this thread I was btw indeed wrong: With GBM Kodi cannot be started from a desktop session without changing the VT due to the mentioned exclusive DRM access occupied by the X session.
0 kommentar(er)
