Posts by Da Flex

Quote from Wolfpig

I 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 default

This 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: connected

So I think kszaq is right, and it's a bug at iwd.

Quote from JimKillock

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:

Thread

Raspberry 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…

greenvorbisfan

June 29, 2021 at 3:05 PM

chewitt Sorry, I mixed up client and server.

taproots This seems to be the cause:

Quote

Code

[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 = SMB3

Then 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 failure

Seems like you always had a wrong WiFi configuration. Check your keys.

https://wiki.libreelec.tv/how-to/add-content-via-samba-shares

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:

Changes in HiFiBerry drivers | HiFiBerry

I think there was outdated data in the cache, and your "fix" has triggered a cache update.

Quote from JimKillock

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.

Quote from HiFiBerry Amp4

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.

The WiFi data rate seems to be the problem (A/V goes out-of-sync):

2024-10-29 20:48:30.709 T:1060    debug <general>: ActiveAE::SyncStream - average error of 29.588072, start adjusting
2024-10-29 20:48:30.709 T:1060    debug <general>: ActiveAE::SyncStream - average error 0.588072 below threshold of 30.000000
2024-10-29 20:48:31.815 T:1060    debug <general>: ActiveAE::SyncStream - average error -220.747135 above threshold of 100.000000
2024-10-29 20:48:32.303 T:1060    debug <general>: ActiveAE::SyncStream - average error -20.747135 below threshold of 30.000000
2024-10-29 20:48:33.063 T:1060  warning <general>: ActiveAE - large audio sync error: -1485.769446
2024-10-29 20:48:33.065 T:1060  warning <general>: ActiveAE - large audio sync error: -1485.769279
2024-10-29 20:48:33.356 T:1060  warning <general>: ActiveAE - large audio sync error: -1685.723723
2024-10-29 20:48:33.356 T:1060    debug <general>: ActiveAE::SyncStream - average error -963.297485 above threshold of 100.000000
2024-10-29 20:48:33.398 T:1394     info <general>: CVideoPlayerAudio::Process - stream stalled

I agree with VLouis . The RPi WiFi is known to be weak. You could buy a USB-to-WiFi, or Ethernet-to-WiFi adapter.

Before buying anything, I would try an Ethernet connection to the Odroid server. Maybe the WiFi is fine, but Odroid can't deliver higher data rates.

Quote from vasiliskal

This has nothing to do wtih what i asked. I asked though LE, not using extra hardware.

I know, that's why I said "BTW". Extra hardware is the most reliable way to make it work.