Posts by Da Flex

Quote from weaker

Now I have to figure out where I would file that bug with the alsa people. Maybe it has to do with the Conexant CX20632 HDA sound chip in the HP device that is maybe not that common. Any hints where to submit that issue that the device quirks are added upstream?

I was asking a developer, who is some sort of a Linux audio guru. His answer:

Quote

If it doesn't work at ubuntu either then it's best he reports it to ubuntu folks, then they can take action.

no idea what hdajackretask is, never heard of that before

Quote from stpf99

which CoreElec to try on S905D m8s plus-dvbs2x, only NE build i think have that kernel but this device is 1st gen S905D and builds suported egsists in NG which has 4.9 kernel

We don't answer CoreELEC questions here. They have their own forum.

Yeah, that was expected. You can uncomment audio_pwm_mode=1 for slightly better quality.

For good quality, buy an USB audio interface like this:

Thread

3.5mm audio output on Raspberry Pi 5

Hi,

this is my first post, thank you in advance for any help or support.

I bought a Raspberry Pi 5 to upgrade from Rpi4 that is already running on LibreELEC, but, I'm a noob, I realized that there is no 3.5mm audio output on the Rpi5 .

On Rpi4 I use that output for music playback using the audio profiles add-on.

My question is, if I buy an USB audio interface (i.e. https://www.amazon.it/dp/B08Y8CZB2S?ref=emc_p_m_5_i_atc but this is just an example), something simple that do not requires drivers,…

AndreaWozzup

March 1, 2024 at 5:13 PM

I'm an FHD guy, and I'm using RPi3B+.

Yes. If you have a look at the site from post #3, only NFO Filename and Title have those little "mandatory stars". The rest is optional.

Yes, it's the same for your Bluetooth device.

On Windows you can use PuTTY for remote SSH access. Of course RPi has to be connected to your router to use SSH. On your PC PuTTY will establish a connection to your router, and from there to your RPi.

• First login to your router menu to find the IP of your RPi. You will need that IP on PuTTY.
• Start PuTTY and establish an SSH connection to RPi.
• Username: root
• Password: libreelec
• After SSH login, type nano /storage/.config/autostart.sh to edit the file.

Obviously there are many optional tags you could add (see link at post #3).

So what's the question? Is the poster invisible? If so, take a working JPG, and analyze its density (PPI value). Then convert the non-working JPG to the same density.

Quote from PebrocFR

I use filezila in ftp and I cannot modify the file or replace it with a modified version

Use SSH (SSH client: PuTTY, user name: root, password: libreelec) or card reader method. Instructions:

https://wiki.libreelec.tv/configuration/config_txt

Please try this /storage/.config/autostart.sh script (use nano editor on SSH):

Post

RE: Using LibreElec as a bluetooth receiver

jmi Try this autostart.sh:

(Code, 6 lines)

autostart.sh starts before Kodi, so after sleeping some seconds in background, Kodi should run.

Da Flex

February 16, 2024 at 4:47 PM

I guess we have to update config.txt and Wiki, so users will know about dtoverlay=pisound.

As mentioned, we already had such audio issues. Every non-4K cable has it's own limits. I assume you have pass-through activated at the audio settings. To figure it out on your setup with 4K cables...

Quote from astromx333

Would the KT0210 perhaps work on a RPi2 as well?

Very likely, because there are the same drivers on both RPi.

Thanks HiassofT! We need a log to figure it out now...

Quote from Zygmunt

Cable shouldn't prevent from setting 60Hz.

That's not correct. If you increase HDMI data rate by using 60Hz, a bad cable can interrupt transmission. I suggest to check the standard of your HDMI cable. For 4K it has to have HDMI 2.0 or 2.1 standard.

We already had such misunderstanding a couple of times. Users think, an LE version is causing a loss of audio features, but most of the time that's not correct. Just a slightly higher HDMI data rate can remove audio features, when using a bad HDMI cable. "Bad" means bad shielding of the cable.

In short, get an HDMI cable, which is conform to HDMI 2.0 or 2.1 standard. Such cables have better shielding, and are able to transmit higher data rates, as necessary for HD audio.

Normal behavior after electricity outage. It's the same on my RPi3B+. It needs additional electronics to solve this. I guess you can buy a ready-to-go solution somewhere, because RPi is so popular.

Two options:

• go to the Kodi forum, and ask the skin developer for an update
• provide a log, as mentioned by chewitt

Switch to the default skin "Estuary", make adjustments, and then go back to your feature-incomplete custom skin.