Posts by diederik

Quote from frakkin64

There isn't one, this is why the user space on most ARM builds is still 32-bit.

Thanks

I recently installed the Retrospect addon on my Rock64 running nightly-20220208-72b6d0d (RK3328.arm) which downloaded some (ChromeOS?) recovery image to get the widevine library which is needed to watch 'NPO start' (Dutch public broadcaster). But trying to watch something, it was buffering constantly. I SSH-ed into my kodi device and noticed 1 core was at 100% all the time. The stream being 540p x264, that didn't make sense.

I found https://github.com/retrospect-add…ect/issues/1601 while I'm 99+% sure the title is incorrect it does describe the issue I had (and is in English). A similar Dutch issue suggest to revert to an older version of widevine which should fix the issue. But I only had one version.

That first link points to an issue with inputstream.adaptive and in one of the comments a DL to 4.10.2252.5-linux-armv7.so was provided, but that is armhf, while rock64 runs aarch64/arm64, so that seemed useless for me. Then I did the following:

kodi-rock64:~/.kodi/cdm # file libwidevinecdm.so 
libwidevinecdm.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=d673f7acd89399ecffaeb3c9ea1545f0c932ba00, stripped

So then I made a backup of that file, DL-ed the 4.10.2252.5-linux-armv7.so one and copied that onto libwidevinecdm.so and then a quick test indicated that the NPO Start stream worked perfectly

But shouldn't I have gotten (initially and afterwards) a 64bit version of the widevine library?

While my initial problem of getting an older version seems to be solved by DL-ing from a 'random' place, I still like to know if and how this can be done normally/properly.

In RE: PulseAudio network sending (rock64) I described how I did it with a systemd unit file.

If the file with the dropouts is from a remote location (nfs), the first test to do is having the file locally. While GbE should be fast enough, when things don't work, verify all assumptions. I believe that True HD + Atmos requires a sustained high throughput and if there's any interruption, that can cause audio drops. With a normal file copy, it'll just slow down (temporary) and therefor take a (slight) bit longer. With audio, you'll get audio drops.

Quote

i have the drops with passthrough mode and also decoding to multi ch pcm. With multi ch pcm it is worse. So for me the hdmi connection to my onkyo av rz-830 seems to be okay and not the issue.

You have (audio) problems in both cases, but in some cases it's worse. How does that lead to the conclusion that the hdmi connection is fine?

I would actually suggest trying whether the problem is the same with a different hdmi cable. (verify your assumptions)

I'm currently working to integrate that patch into a (self-compiled) Debian kernel, but I'd really prefer it if it was integrated upstream, so that Debian would pick it up automatically and I can go back to using Debian's kernels again.

So if there's a way I can help with this, I'd be happy to

Quote from JoeAverage

I wonder how do you do this:

do you do the download on the LE box only (no 2cd box involved) ?

how do you get the correct download link for the new nightly ?

I go to https://test.libreelec.tv/ and filter the list for 'rock64', right-click on the one entry that's still left and do 'Copy Link', then I switch to a terminal (tab) connected to my kodi device via SSH, change to ~/backup and do 'wget <paste-previously-copied-link>'.

IOW all manual and from a 'normal' PC.

I ran into a similar situation a while ago and since then I DL nightly images to ~/backup/ and copy it to ~/.update/ to apply a new nightly.

IOW, I keep several old nightly builds which I 'know' are good around. Backing that/those up to another drive/PC would also be a good idea in case the storage medium in my kodi device gives problems.

You can do that (too) until more nightly builds are kept, but even after that it may be useful to keep your own known-good copies around.

Is this supposed to be the way to customize the sorting?
If so, I can mark this thread as resolved. If not, I'd like to know the way it is supposed to work, assuming it is supported.

Quote from ryusez

Formatting the disc with UDF version 2.50 works:
$ sudo mkudffs --utf8 --blocksize=2048 --media-type=bdr --udfrev=0x0250 --lvid=Backup2 --vid=Backup2 /dev/sr0

After doing that, were you able to mount the disk then? I'm guessing 'yes' as you said it works, but better to verify then assume.

If you then do the same command, but then explicitly use '2.60', would it fail like before or would that work?

Another interesting test would be to only specify the required parameters, so it uses the default values for all others

Why? It won't be the first time a Windows tool doesn't create things/disks according to spec/standard and while it may work on a or that specific Windows machine (possibly 'assisted' by that same disk creation tool), another tool working according to spec, may choke on it.

The homepage of the 'udftools' package on Debian is https://github.com/pali/udftools and I'm guessing LE uses that too. You may find additional hints there (in issues f.e.).

If you can reproduce the problem on a disk created on a Linux machine, that's also the (best) place to report it, so it can be fixed.

I don't know if the trigger was a reboot or an upgrade to a later nightly build, but the one I put on top of the list, now did get displayed first

Quote from chewitt

personally I edit /storage/.kodi/usersdata/sources.xml as the format it simple and typing smb://user:pass@SERVER/SHARE is easier on a keyboad via SSH than using a remote in the GUI.

Oh man, that is so much easier I also just discovered the 'System Tools' addon which gave me vim \o/

I have one video source which I use the most, but it's listed last in 'Videos > Media sources'. I edited the sources.xml and put the source I use most often at the top of the list, but that didn't seem to affect the sorting.
Is there a way to (manually) change the sorting? If so, how?

I've had some mixed results so far. Several times it didn't see the soundcard I wanted it to see, so I've now blacklisted the module 'snd_soc_rockchip_spdif' on soundserver as I don't (plan to) use it anyway. Also when manually unloading and (re-)loading the pulseaudio modules, it sometimes worked and sometimes it didn't. I could not find any pattern in it.
OTOH, when my PC is on, it always sees the soundcards from that machine and I can select them in Settings > System > Audio.

I've just created one of my very first systemd unit file and rebooted my kodi device and it seems to work (now)

But if someone who's more knowledgeable in this area could take a look and suggest improvements, I'd appreciate that.

[Unit]
Description=Connect to PA server on 'soundserver'
Requires=pulseaudio.service network-online.target
After=sound.target network-online.target pulseaudio.service
Before=kodi.service

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/pactl load-module module-native-protocol-tcp auth-anonymous=1 auth-ip-acl="127.0.0.1;192.168.2.0/24"
ExecStart=/usr/bin/pactl load-module module-zeroconf-discover
ExecStart=/usr/bin/pactl load-module module-tunnel-sink server=[192.168.2.34]:4713 sink=alsa_output.platform-hdmi-sound.hdmi-surround71 format=s16le channels=8 rate=44100 sink_properties=device.icon_name=computer-desktop sink_name=tunnel.soundserver.local.alsa_output.platform-hdmi-sound.hdmi-surround71 channel_map=front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right
ExecStart=/usr/bin/pactl set-default-sink tunnel.soundserver.local.alsa_output.platform-hdmi-sound.hdmi-surround71

[Install]
WantedBy=multi-user.target

After creating that file, I put it in ~/.config/system.d/pulse-network-audio.service and then did "systemctl daemon-reload" and "systemctl enable pulse-network-audio.service" (and disabled my ~/.config/autostart.sh which did the things that are now in ExecStart)

Quote from richprim

I would like to change the skip forward and back from 10 seconds to 30 seconds .

In Settings > Player > Videos there's an Actions category where you can define 'Skip steps'.

If you press the skip button 2 times, you'll skip 30 seconds (and 1 min for 3 skips, 3 mins for 4 skips, etc).

Quote from ericthehalfabee

The RPi is still on, the HDD attached to it is still spinning and I can access it as a NAS; but the only way I can get it to output display is by switching it off and back on ... It's just really frustrating to have to go scrabbling around behind the TV stand to switch it off & on again, not to mention the fact that it's not good for the SD card or the HDD to be switched off like this, but I can't find another way to resolve the issue.

If you have enabled SSH, you can SSH into it and give a 'reboot' command.
If you have 'Kore' on your phone, you should be able to reboot it through that as well.
Not a proper solution to your problem, but better then pulling the plug.

Quote from mattIV

Something I did notice is that movies that I delete from the drive are not automatically deleted from the library when I run 'scan video library' yet new movies are added to the libary without any issue.

In Settings > Media > Library In the 'Video Library' section there's a 'Clean library' command which will get rid of those deleted items

Quote from diederik

If I did something wrong or you have new ideas to try out, I'd love to hear it

During my experiments, I came across something I found odd (then...)

kodi-rock64:~ # avahi-browse -a
Failed to create client object: Daemon not running

So I did something 'crazy' and started "avahi-daemon" ... and then I got several PULSE devices in the 'Audio output device' list

They were a bit 'oddly' named, but I could select them, including my 7.1 device.

Then I played a 4k HDR file and (after disabling pass-through) I had audio over my 4 speakers. Spoken word only came out of 1 of them, but after changing "Number of channels" to 4.0, that worked too.

And then I remembered something from the startup wizard where I had disabled the Avahi service. So I enabled it and rebooted my devices and now I have a (several actually) 'normally' named PULSE devices, including "PULSE: Built-in Audio Digital Surround 7.1 (HDMI) on pulse@soundserver"

\o/ \o/ \o/

So I gave it another go. I disabled "client.conf" and rebooted my device.

I created the following "/storage/.config/autostart.sh" which contained the same command as I had done manually:

kodi-rock64:~ # cat .config/autostart.sh  
#!/bin/sh

(
sleep 5
pactl load-module module-native-protocol-tcp auth-anonymous=1 auth-ip-acl="127.0.0.1;192.168.2.0/24"
sleep 2
pactl load-module module-zeroconf-discover
sleep 2
pactl load-module module-tunnel-sink server=[192.168.2.34]:4713 sink=alsa_output.platform-hdmi-sound.hdmi-surround71 format=s16le channels=8 rate=44100 sink_properties=device.icon_name=computer-desktop sink_name=tunnel.soundserver.local.alsa_output.platform-hdmi-sound.hdmi-surround71 channel_map=front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right
sleep 2
pactl set-default-sink tunnel.soundserver.local.alsa_output.platform-hdmi-sound.hdmi-surround71
)

After loading "module-native-protocol-tcp" (with above params) and loading "module-zeroconf-discover" I believe I should have seen the "module-tunnel-sink" loaded automatically, but that was not the case. Consequently (?) I did not see the sink from 'soundserver', so I loaded that module manually (and now via this script) and then I did see the sink from 'soundserver':

kodi-rock64:~ # pactl list short sinks

1       tunnel.soundserver.local.alsa_output.platform-hdmi-sound.hdmi-surround71        module-tunnel.c s16le 8ch 44100Hz       SUSPENDED

Then setting that sink as default didn't give an error, so I assumed it worked.

But checking in Settings > System > Audio > Audio output device and the only PULSE device was for Bluetooth, but not the default sink.

IIUC, it's better to convert the "autostart.sh" to a systemd unit file and I'll work on that, but I don't see how that could result in a different outcome.

For completeness I've also enabled debug logging and rebooted and that resulted in this log file: http://ix.io/3Fox

PulseAudio info:

kodi-rock64:~ # pactl list short modules

0       module-native-protocol-unix
1       module-stream-restore
2       module-device-restore
3       module-card-restore
4       module-default-device-restore
5       module-always-sink
7       module-suspend-on-idle
8       module-dbus-protocol
9       module-bluetooth-policy
10      module-bluetooth-discover
11      module-bluez5-discover
12      module-zeroconf-publish
13      module-switch-on-connect
14      module-native-protocol-tcp      auth-anonymous=1 auth-ip-acl=127.0.0.1;192.168.2.0/24
15      module-zeroconf-discover
16      module-tunnel-sink      server=[192.168.2.34]:4713 sink=alsa_output.platform-hdmi-sound.hdmi-surround71 format=s16le channels=8 rate=44100 sink_properties=device.icon_name=computer-desktop sink_name=tunnel.soundserver.local.alsa_output.platform-hdmi-sound.hdmi-surround71 channel_map=front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right
kodi-rock64:~ # pactl info
Server String: /var/run/pulse/native
Library Protocol Version: 34
Server Protocol Version: 34
Is Local: yes
Client Index: 9
Tile Size: 65496
User Name: root
Host Name: kodi-rock64
Server Name: pulseaudio
Server Version: 14.2
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
Default Sink: tunnel.soundserver.local.alsa_output.platform-hdmi-sound.hdmi-surround71
Default Source: tunnel.soundserver.local.alsa_output.platform-hdmi-sound.hdmi-surround71.monitor
Cookie: 

If I did something wrong or you have new ideas to try out, I'd love to hear it

Thanks for your response. I didn't know it would show only one (besides PULSE bluetooth I assume).

Quote

So you'll have to use that default pulseaudio device

AFAICT the default device is the HDMI card (see 'various data' in OP) and that is exactly what I want. If I blacklist 'snd_soc_rockchip_spdif', it is the only device, which is also fine by me. What I don't understand is why it isn't picking up that device.

Or am I misunderstanding you?

Quote

make sure that pulse has your network tunnel as the default device

I'm now using the 'Direct connection' as described in https://www.freedesktop.org/wiki/Software/…n/User/Network/. Is that my (main) problem and I should get the 'Using a tunnel' method working? My attempts thus far have failed (but it is working on my PC), but if this is the way it is supposed to work, I'll give it another go.