Hi, I'm just discovering LE, is it useful to do it every night? Is it a “stable” version ?
And if I make a backup of version 12, can I come back to it without worrying ?
Our nightly builds are very stable, they are just not tested as much as the stable ones.
Make a backup from LE 12, and if something goes wrong with LE 13, you can go back by update folder method.
Tell me if I can merge it or do I have to wait until it's official ?
Just update to the latest LE 13 nightly from SSH:
cd /storage/.update
wget https://test.libreelec.tv/13.0/RPi/RPi5/LibreELEC-RPi5.aarch64-13.0-nightly-20241103-f662bea.img.gz
rebootI will check but.....what key are we talking exactly from?
And why is the connection running without issues if there is something "wrong" with it?
The WiFi key was wrong at the first attempt to connect, but at the second attempt it worked:
Oct 08 17:44:37.351915 LibreELEC connmand[631]: Interface wlan0 [ wifi ] state is ready
Oct 08 17:44:37.352030 LibreELEC connmand[631]: Interface wlan0 [ wifi ] is the defaultThis message only appears once, right before the second attempt:
Oct 08 17:44:31.629219 LibreELEC iwd[1001]: hardware_rekey not supported
Oct 08 17:44:31.629788 LibreELEC iwd[1001]: event: state, old: connecting, new: connectedSo I think kszaq is right, and it's a bug at iwd.
Do any of the Linux options for streaming to / from support adjustments to latency in the way that Airplay does? (This would allow one box to play video, while another outputs the audio from the video that is playing.)
Kodi provides latency options at advancedsettings.xml. You have to create that file, if A/V goes out-of-sync.
For your setup I suggest MPD, which has a client/server architecture. So you can stream in any direction.
Some audio aficionados also use RPi/HiFiBerry for DSD playback:
chewitt Sorry, I mixed up client and server.
taproots This seems to be the cause:
[2024/11/01 11:52:28.900990, 3] source3/smbd/smb2_negprot.c:345(smbd_smb2_request_process_negprot) Selected protocol SMB3_11
On your Ubuntu Samba server, add/edit this at /etc/samba/smb.conf:
client min protocol = SMB2
client max protocol = SMB3Then restart the Samba server: sudo service smbd restart
Connect RPi HDMI-0 to TV, and RPi HDMI-1 to AVR.
This is from the "working" log:
Oct 08 17:44:20.146869 LibreELEC connmand[631]: Interface wlan0 [ wifi ] error "invalid-key"
Oct 08 17:44:20.146905 LibreELEC connmand[631]: Interface wlan0 [ wifi ] state is failureSeems like you always had a wrong WiFi configuration. Check your keys.
Wolfpig Sometimes WiFi quality changes, but it has nothing to do with LE. It could be a weak PSU. To know for sure...
I copy the solution from another thread, just in case. This is the current workaround from HiFiBerry:
I think there was outdated data in the cache, and your "fix" has triggered a cache update.
In case helpful, I edited /flash/config.txt and added the line dtoverlay=hifiberry-amp
For good measure, I also added dtoverlay=hifiberry-dac and dtoverlay=hifiberry-amp4
The Hifiberry-dac file did appear in System » Audio, but selecting it does not appear to produce audio output, although the advice from Hifiberry is that Hifiberry DAC drivers usually work for their Amp.
Only use the first line, and answer my question. Background: RPi5 needs more wattage, compared to RPi4.
You only need a single 12-24V power supply to power the Raspberry Pi and the Amp4. With 4 Ohm speakers, we recommend 12-20V. Higher operating voltages are only recommended with 8 Ohm speakers.
What's the power supply of your RPi / HiFiBerry system? Maybe you don't get enough wattage for A/V.
Hmm, then other users should answer. 
Ask your Windows support team.
Better use EXT4 as your file system.
