[PROBLEM] Connection problem soundbar

[pokkeweer]

I installed Moode Audioplayer on a Raspberry 3b+.

Works great, but not completely.
Our LG OLED65E9PLA television is connected to the LG (DSP11RA) soundbar via the (E)ARC connection with an HDMI cable. When the television is switched on, the soundbar is also activated. I see ARC on the soundbar display.
The Raspberry Pi is also connected to the soundbar via an HDMI cable on port HDMI-1. When I switch on the Raspberry Pi, I see that the connection between the television and the soundbar is lost. OPT appears on the soundbar. The sound of the television now comes from the speakers of the television.
The music that I want to listen to via Moode player is possible (the display of the soundbar shows HDMI-1, the port to which the Raspberry is connected). I have already tried different HDMI cables. If I switch off the Raspberry, the ARC connection is active again and I hear the sound of the TV via the soundbar again.
Now I read on the internet that some people say that I have to remove D14 on the Raspberry Pi. No idea where it is located and whether it is even on the 3b+ version.
Question: does anyone have a solution where I do not have to remove a part of the 3b+, but a software solution?

[Tim Curtis]

Since you are using an ARC connection between your soundbar and TV you should connect the Pi to an available HDMI port on the TV not the Soundbar. Switch to that port using your TV remote.

ETA: 
Menu > Configure > Peripherals
Turn on Local display to show moode WebUI on your TV
Turn on CEC control to send "power on" commands to TV/Soundbar when moode starts up

[pokkeweer]

Since you are using an ARC connection between your soundbar and TV you should connect the Pi to an available HDMI port on the TV not the Soundbar. Switch to that port using your TV remote.

ETA: 
Menu > Configure > Peripherals
Turn on Local display to show moode WebUI on your TV
Turn on CEC control to send "power on" commands to TV/Soundbar when moode starts up

Thanks for replying!
I connected the Raspberry to the tv (HDMI-1).
I have adjusted the settings you give in the web interface on my phone.
When I start the Raspberry I see a login screen on the TV. Do I need to create an account first and always have to login using the tv?
It is not my intention when I want to listen to music the television also turns on and need to login.... I have the idea that this does happen because of your solution?! Or am I doing something wrong?

[Tim Curtis]

Very odd.

I've never seen that login prompt before.

[pokkeweer]

Very odd.

I've never seen that login prompt before.

Probably I activated the Boot-option (S5) using raspi-config to Desktop (B2). After changing this option to Text console (B1), Moode audio player's webinterface appears after restart.

I only want to hear the music using Moode audio player on the soundbar. So using my phone, go to the webinterface of Moode to choose the music and then only hear music on the soundbar. 
Your method always needs to use the tv, but that is not what I want...

[Tim Curtis]

Just turn off Local display and CEC control (if you have that on). The WebUI won't be displayed on the TV.

In any case, in your original usage scenario you stated:

"The Raspberry Pi is also connected to the soundbar via an HDMI cable on port HDMI-1. When I switch on the Raspberry Pi, I see that the connection between the television and the soundbar is lost. OPT appears on the soundbar. The sound of the television now comes from the speakers of the television."

This automatic routing of the sound to the TV speakers is apparently being done by by your Soundbar/TV because neither PiOS or moode has any such automatic port switching or sound routing commands in its code.

I have a JBL Soundbar which is connected to a Samsung TV via HDMI eARC port. I ran a quick test this morning connecting a Pi to HDMI-1 input on the Soundbar and no issues whatsoever. All that was needed was to use the Soundbar remote to manually switch to the HDMI-1 port and moode plays to the Soundbar. There was no auto-port switching or sound routing to TV speakers when the Pi powers up.

Its not obvious to me whats happening on your end.

[pokkeweer]

I'm still trying to get a solution for the connection problem. 
So I first looked at the config.txt file (using Putty) in the boot-directory of Moode player. When I want to view this file it says I've to view this file in the /boot/firmware directory.

When I change the option CEC-control (HDMI-displays) in Moode player on or off nothing changes in the file config.txt in the /boot/firmware directory after a restart. Maybe because this is a copy of the original file in the /boot-directory, which can't be changed?
On the internet I read about adding the line hdmi_ignore_cec=1 to the config.txt file. Or is this line added in the original config.txt file changing the option CEC-control which can't be changed by the user?

[Tim Curtis]

Couple things:

1. In PiOS Bookworm the files config.txt and cmdlin.txt are located in /boot/firmware/
2. Moode uses the cec-ctl application to provide CEC command capability, not settings in config.txt
3. When you turn off CEC control in Peripheral config CEC commands are never sent during startup/shutdown

I think your nest bet is to just examine the source code. Try searching the two files below for the string "cec-ctl"
https://github.com/moode-player/moode/bl...atchdog.sh
https://github.com/moode-player/moode/bl...worker.php