It's not related to CEC. Your TV detects RPi as A/V source, and that's the cause of the switch.
Posts by Da Flex
-
-
We don't support Dolby Vision (DV). DV needs a license on the device. RPi's don't have such a license.
Some Amazon Fire devices and Nvidia Shield have a DV license. Get one of those.
-
PS: Just to explain: Better shielding is the major difference between FullHD and 4K HDMI cables.
-
...isn't quite up to the job at 4K but works great at 1080p.
Maybe it's enough to upgrade the shielding of the internal HDMI wiring.
-
LE seems to get data for the first frequencies, but afterwards no more data are coming in.
Code
Display MoreJun 23 13:00:56.422423 LibreELEC tvheadend[436]: mpegts: 704.5MHz in DVB-T Network - tuning on DiBcom 7000PC #0 : DVB-T #0 Jun 23 13:00:56.422510 LibreELEC tvheadend[436]: subscription: 0001: "epggrab" subscribing to mux "704.5MHz", weight: 4, adapter: "DiBcom 7000PC #0 : DVB-T #0", network: "DVB-T Network", service: "Raw PID Subscription" Jun 23 13:00:56.422531 LibreELEC tvheadend[436]: mpegts: 634.5MHz in DVB-T Network - tuning on DiBcom 7000PC #1 : DVB-T #0 Jun 23 13:00:56.422548 LibreELEC tvheadend[436]: subscription: 0002: "epggrab" subscribing to mux "634.5MHz", weight: 4, adapter: "DiBcom 7000PC #1 : DVB-T #0", network: "DVB-T Network", service: "Raw PID Subscription" Jun 23 13:00:59.435701 LibreELEC tvheadend[436]: htsp: Got connection from 127.0.0.1 Jun 23 13:00:59.435807 LibreELEC tvheadend[436]: htsp: 127.0.0.1: Welcomed client software: Kodi Media Center (HTSPv35) Jun 23 13:00:59.435829 LibreELEC tvheadend[436]: htsp: Got connection from 127.0.0.1 Jun 23 13:00:59.435864 LibreELEC tvheadend[436]: htsp: 127.0.0.1 [ Kodi Media Center ]: Identified as user '' Jun 23 13:00:59.435881 LibreELEC tvheadend[436]: htsp: 127.0.0.1: Welcomed client software: Kodi Media Center (HTSPv35) Jun 23 13:00:59.437605 LibreELEC tvheadend[436]: htsp: 127.0.0.1 [ Kodi Media Center ]: Identified as user '' Jun 23 13:01:23.644671 LibreELEC systemd[1]: systemd-hostnamed.service: Deactivated successfully. Jun 23 13:02:31.401301 LibreELEC tvheadend[436]: mpegts: 767.5MHz in DVB-T Network - tuning on DiBcom 7000PC #1 : DVB-T #0 Jun 23 13:02:31.401632 LibreELEC tvheadend[436]: subscription: 0002: "epggrab" unsubscribing Jun 23 13:02:31.402006 LibreELEC tvheadend[436]: subscription: 0004: "scan" subscribing to mux "767.5MHz", weight: 6, adapter: "DiBcom 7000PC #1 : DVB-T #0", network: "DVB-T Network", service: "Raw PID Subscription" Jun 23 13:02:31.402340 LibreELEC tvheadend[436]: mpegts: 725.5MHz in DVB-T Network - tuning on DiBcom 7000PC #0 : DVB-T #0 Jun 23 13:02:31.402523 LibreELEC tvheadend[436]: subscription: 0001: "epggrab" unsubscribing Jun 23 13:02:31.402740 LibreELEC tvheadend[436]: subscription: 0005: "scan" subscribing to mux "725.5MHz", weight: 6, adapter: "DiBcom 7000PC #0 : DVB-T #0", network: "DVB-T Network", service: "Raw PID Subscription" Jun 23 13:02:36.876663 LibreELEC tvheadend[436]: mpegts: 725.5MHz in DVB-T Network - scan no data, failedMaybe undervoltage inside of the receiver?
Please provide a product link of your DiBkom 7000PC. Does it have an optional PSU, which you can plug in?
-
PSU is fine, no undervoltage warning in the log.
Different time stamps in the same log?
Code2024-06-23 13:04:45.721 T:1282 info <general>: Loading skin file: DialogConfirm.xml, load type: KEEP_IN_MEMORY ========== journalctl -a -b -0 ========== Feb 28 03:26:04.560062 LibreELEC kernel: Booting Linux on physical CPU 0x0000000000 [0x410fd083]PS: Ah, it has no internal clock, so time is wrong until NTP gets it.
-
While it was scanning a few times a signal strength popped-up on the screen but then disappeared.
Repeat that procedure with logging. It could be a PSU issue. if so, it's visible in the log.
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Usage of banned add-ons means no support.
ThreadForum Rules
General Conduct- Be polite and respectful to forum staff and other users
- Be polite and respectful towards this project and other projects
- Be patient, user and staff are spread all over the world, an answer may take time
- One topic per thread
- Posts should be written in English (add text in your native language if needed)
- Be as descriptive and detailed as possible. We are not mind readers!
- If AI tools have been used to create your post or triage an issue, name the tool and version in the post
- Do not
newphreakMarch 15, 2016 at 1:02 AM -
Are there any plans to release a 12.0.1 with this fix?
Of course. No ETA for the next stable release.
-
Put the image into /storage/.update and reboot.
-
Pi-Desktop users will find it. I take care of it.

-
NSXD We support native DSD for some audio interfaces, but it's limited on HDMI (PCM down-sampled, as described by you).
Please read those threads:
ThreadHow to use MPD for native DSD via USB DAC
I guess my question is even more general in that I have no idea how to use the MPD service add-on at all. Once installed, how do I utilize it?
For background, I posted this thread and was asked to repost my specific MPD question here Native DSD on Raspberry Pi
I know that native DSD via USB from a Raspberry Pi is possible, as VolumIO supports it. It is also my understanding that VolumIO is MPD based.
That's about where my understanding ends. I found this thread: Raspberry Pi 4 + LibreElec +…flizApril 5, 2024 at 6:07 PM ThreadRaspberry Pi 4 + LibreElec + Music Player Daemon + WavPack DSD
Hello!
I installed LibreElec 9.95.1 and mpd (as service addon) and found that when playing WavPack DSD files with a samplerate of more than 384 kHz, the sound is very interrupted. A search on the Internet did not give anything, the mpd settings also did not bring any result. And then I accidentally looked into:
mpd -V
— and found that it was built without native support for the WavPack format, that is, it decodes it using ffmpeg. And ffmpeg DOES NOT RECOGNIZE DSD compressed with WavPack.
In…
greenvorbisfanJune 29, 2021 at 3:05 PM -
...where are the all the video and other folders kept, are they on that boot partition or on the storage partition?
Storage partition.
-
Still trying to sort out TVheadend.
Please use our PVR & DVB Support for this.
TVHeadEnd also has an own forum:
-
Niceguy We do support for free in our spare time. We expect that users do some research by themselves. Use our search function (magnifier icon on top) and Google. We don't waste our time on lazy users.
-
install new drives i dont tryed to this point. but simply because i dont know how because libreelec is totaly different to distros i know.
is that the right instructions for installing new drivers? https://wiki.libreelec.tv/how-to/add-firmware or is there a better fitting one i dont know?
You need Windows to update the firmware. You can create a portable Windows USB stick, or install it beside LE (use GParted to create necessary partitions).
Warning: This procedure will take hours. Editing partitions requires care.
However, we already had a couple of users here, who fixed their HDMI problems by such firmware updates.
-
i switched back to the amlogic device with coreelec.
Thanks! Closed.
-
Install the Multimedia Tools add-on, and run alsamixer from SSH.