Posts by mglae

Likely being German speaking you may not need a translator for this.

When searching cherry trail audio in this forum you find several reports but there seem to be no solution.

If motivated you may extend the search to the whole web.

Looking at your documentation links, tidal addon configuration is having some complexity.

Please check your config again, especially if dash support is enabled

Are you really booting with EFI?

Please check /sys/firmware/efi and /sys/firmware/efi/efivars

nasawyer7

2024-06-16 14:06:13.155 T:1453     info <general>: AddOnLog: inputstream.ffmpegdirect: inputstream.ffmpegdirect property: inputstream.ffmpegdirect.manifest_type = hls
2024-06-16 14:06:13.155 T:1453     info <general>: AddOnLog: inputstream.ffmpegdirect: inputstream.ffmpegdirect property: inputstream.ffmpegdirect.open_mode = ffmpeg
2024-06-16 14:06:13.155 T:1453     info <general>: AddOnLog: inputstream.ffmpegdirect: Stream mimetype: application/vnd.apple.mpegurl

The tidal plugin is requesting a HLS stream which is failing with 403 Forbidden. IMO no dash involved.

The second stream is played directly without any inputstream addon.

chewitt With a new image I can play a FTA live dash stream using inputstream.ffmpegdirect without rebuilding the addon. (And the stream can even be played with kodi directly).

May not help, but default route is still active on Generic (X86).

On such a Generic system I would first check with break=prepare_sysroot kernel parameter if the config is correct in init. But this may require some debug shell serial line setup with your board.

Then with route >~/autostart.route in autostart.sh if it is still there before starting kodi.

And always share a debug log.

chewitt You missed:

WARNING: Disabled dash_demuxer because not all dependencies are satisfied: libxml2

With the following patch ffmpeg is building dash demuxer (still with --enable-demuxers). Only build tested.

diff --git a/packages/multimedia/ffmpeg/package.mk b/packages/multimedia/ffmpeg/package.mk
index 63ae0683bf..b55ffbd2c8 100644
--- a/packages/multimedia/ffmpeg/package.mk
+++ b/packages/multimedia/ffmpeg/package.mk
@@ -8,7 +8,7 @@ PKG_SHA256="9b16b8731d78e596b4be0d720428ca42df642bb2d78342881ff7f5bc29fc9623"
 PKG_LICENSE="GPL-3.0-only"
 PKG_SITE="https://ffmpeg.org"
 PKG_URL="http://ffmpeg.org/releases/ffmpeg-${PKG_VERSION}.tar.xz"
-PKG_DEPENDS_TARGET="toolchain zlib bzip2 openssl speex"
+PKG_DEPENDS_TARGET="toolchain zlib bzip2 openssl speex libxml2"
 PKG_LONGDESC="FFmpeg is a complete, cross-platform solution to record, convert and stream audio and video."
 PKG_PATCH_DIRS="libreelec"
 
@@ -227,6 +227,7 @@ configure_target() {
               --disable-libvpx \
               --disable-libx264 \
               --disable-libxavs \
+              --enable-libxml2 \
               --disable-libxvid \
               --enable-zlib \
               --enable-asm \

Same is required for ffmpegx addon.

Quote from tailkinker

Can I just dd the installer to a USB stick?

Yes, as root (or with sudo) use e.g: gzip -dc *.img.gz|dd of=/dev/sdX bs=64k

Likely you have to create an allowed_options_ntfs. See the "allowed_options" section.

Automount is done via udevil. To test use:

udevil mount /dev/sda1

Please check/post /flash/fs-resize.log

Quote from olze

Is there any way to tell libreelec to mount this device in RO?

cp /etc/udevil/udevil.conf /storage/.config/udevil.conf
nano /storage/.config/udevil.conf

... and edit the ntfs options.

With Chrome 109.0.5414.74 you are still using the LE11 addon.

LE12 is at 123.0.6312.122 and still working.

Manual force a repo update to get the correct LE12 addon(s).

In addition you should consider increasing the "Wait on network" time in LE-Settings Addon to reliable get the repos updated after boot.

... and I'm wondering if choosing a different kernel is only a variation of temporary using a different distribution.

If a chkdsk on Windows does not fix the issue you can only wait until the kernel ntfs3 driver is is more stable in the future.

Defaults may have changed, there is a different kernel in LE12 and now using mount.nfs instead of busybox mount.

Try from command line for faster testing turn around times:

mount -t nfs 172.25.2.60:/mnt/Backup/Kodi/RockPi4 /storage/backup 

This should fail too. Then start with setting NFSV3:

mount -t nfs -o vers=3 172.25.2.60:/mnt/Backup/Kodi/RockPi4 /storage/backup