Posts by ghtester

The config file is here: http://sharegadget.com/754891094

No issues with zaps.

I have encountered the NextPVR client has been updated to version 21.0.1.1 after the LE12 upgrade to nightly-20230610-c7acfc7 but without any positive change (regarding to tuning & timeshift issues). I wonder what configuration change broke the tuning as at first it was working.

Check the fresh logs with debug enabled, the tuning issue should be visible there for sure:

http://mysharegadget.com/345723612

http://ix.io/4y5H

Jun 12 21:47:48 LE kernel: rpivid feb10000.codec: Missing DPB ent 0, timestamp=0

Jun 12 21:47:48 LE kernel: rpivid feb10000.codec: rpivid_h265_stop

Jun 12 21:48:29 LE service.nextpvr[27348]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 12 21:48:29 LE service.nextpvr[27348]: ERROR FE_SET_PROPERTY: Bad file descriptor

Jun 12 21:49:44 LE service.nextpvr[27348]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 12 21:49:44 LE service.nextpvr[27348]: ERROR FE_SET_PROPERTY: Bad file descriptor

Jun 12 21:49:47 LE service.nextpvr[27348]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 12 21:49:47 LE service.nextpvr[27348]: ERROR FE_SET_PROPERTY: Bad file descriptor

Jun 12 21:50:03 LE systemd[1]: Stopping service.nextpvr.service...

Jun 12 21:50:03 LE systemd[1]: service.nextpvr.service: Deactivated successfully.

Jun 12 21:50:03 LE systemd[1]: Stopped service.nextpvr.service.

Jun 12 21:50:03 LE systemd[1]: service.nextpvr.service: Consumed 1min 3.824s CPU time.

Jun 12 21:50:03 LE systemd[1]: Started service.nextpvr.service.

Jun 12 21:50:06 LE kernel: si2168 22-0064: downloading firmware from file 'dvb-demod-si2168-d60-01.fw'

Jun 12 21:50:08 LE kernel: si2168 22-0064: firmware version: D 6.0.13

Jun 12 21:50:11 LE connmand[697]: ntp: adjust (slew): -0.005944 sec

Jun 12 21:50:22 LE kernel: si2168 22-0064: downloading firmware from file 'dvb-demod-si2168-d60-01.fw'

Jun 12 21:50:23 LE kernel: si2168 22-0064: firmware version: D 6.0.13

Jun 12 21:50:31 LE kernel: rpivid feb10000.codec: rpivid_h265_start: (1920x1088)

Jun 12 21:50:31 LE kernel: rpivid feb10000.codec: SPS changed

Jun 12 21:50:31 LE kernel: rpivid feb10000.codec: PPS changed

Jun 12 21:50:31 LE kernel: rpivid feb10000.codec: Missing DPB ent 0, timestamp=0

Jun 12 21:50:31 LE kernel: rpivid feb10000.codec: Missing DPB ent 1, timestamp=0

Jun 12 21:50:31 LE kernel: rpivid feb10000.codec: Missing DPB ent 1, timestamp=0

Jun 12 21:50:31 LE kernel: rpivid feb10000.codec: Missing DPB ent 1, timestamp=0

Jun 12 21:56:24 LE service.nextpvr[52168]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 12 21:56:24 LE service.nextpvr[52168]: ERROR FE_SET_PROPERTY: Bad file descriptor

Jun 12 21:56:24 LE kernel: rpivid feb10000.codec: rpivid_h265_stop

Jun 12 21:57:19 LE service.nextpvr[52168]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 12 21:57:19 LE service.nextpvr[52168]: ERROR FE_SET_PROPERTY: Bad file descriptor

Jun 12 21:57:24 LE service.nextpvr[52168]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 12 21:57:24 LE service.nextpvr[52168]: ERROR FE_SET_PROPERTY: Bad file descriptor

Find the full muxes here: https://www.uschovna.cz/en/zasilka/LH9B8LBFU47RFTU4-UF3/

The commands used for grabbing are below, note the buffer overrun on some muxes.

# dvbv5-zap -c /storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf Nova -P -t 60 -o fullmux642.ts

using demux 'dvb0.demux0'

reading channels from file '/storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf'

service has pid type 0c: 8001

service has pid type 06: 278

service has pid type 05: 281

tuning to 642000000 Hz

dvb_dev_set_bufsize: buffer set to 6160384

pass all PIDs to TS

dvb_set_pesfilter 8192

(0x00)

Lock (0x1f) Signal= -59.00dBm C/N= 27.00dB UCB= 13463 postBER= 0

Lock (0x1f) Signal= -59.00dBm C/N= 27.00dB UCB= 13463 postBER= 0

Record to file 'fullmux642.ts' started

received 245682160 bytes (3998 Kbytes/sec)

Lock (0x1f) Signal= -59.00dBm C/N= 27.00dB UCB= 26449 postBER= 990x10^-9

# dvbv5-zap -c /storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf NOVA -P -t 60 -o fullmux490.ts

using demux 'dvb0.demux0'

reading channels from file '/storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf'

service has pid type 0c: 8000

service has pid type 06: 3318

service has pid type 05: 3317

tuning to 490000000 Hz

dvb_dev_set_bufsize: buffer set to 6160384

pass all PIDs to TS

dvb_set_pesfilter 8192

(0x00)

Lock (0x1f) Signal= -42.00dBm C/N= 31.00dB UCB= 26449 postBER= 0

Lock (0x1f) Signal= -42.00dBm C/N= 31.00dB UCB= 26449 postBER= 0

Record to file 'fullmux490.ts' started

buffer overrun after 36.18 seconds

received 246022252 bytes (4004 Kbytes/sec)

Lock (0x1f) Signal= -42.00dBm C/N= 31.50dB UCB= 26449 postBER= 0

# dvbv5-zap -c /storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf CT\ 2\ HD\ T2 -P -t 60 -o fullmux514.ts

using demux 'dvb0.demux0'

reading channels from file '/storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf'

service has pid type 06: 2250 2130

service has pid type 05: 2260

tuning to 514000000 Hz

dvb_dev_set_bufsize: buffer set to 6160384

pass all PIDs to TS

dvb_set_pesfilter 8192

(0x00)

Lock (0x1f) Signal= -46.00dBm C/N= 36.25dB UCB= 26449 postBER= 0

Lock (0x1f) Signal= -46.00dBm C/N= 36.25dB UCB= 26449 postBER= 0

Record to file 'fullmux514.ts' started

received 249851812 bytes (4066 Kbytes/sec)

Lock (0x1f) Signal= -47.00dBm C/N= 38.25dB UCB= 26449 postBER= 0

# dvbv5-zap -c /storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf Ocko -P -t 60 -o fullmux626.ts

using demux 'dvb0.demux0'

reading channels from file '/storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf'

service has pid type 0c: 8000

service has pid type 05: 4211

tuning to 626000000 Hz

dvb_dev_set_bufsize: buffer set to 6160384

pass all PIDs to TS

dvb_set_pesfilter 8192

(0x00)

Lock (0x1f) Signal= -43.00dBm C/N= 34.25dB UCB= 26449 postBER= 0

Lock (0x1f) Signal= -43.00dBm C/N= 34.25dB UCB= 26449 postBER= 0

Record to file 'fullmux626.ts' started

buffer overrun after 35.87 seconds

received 246622160 bytes (4014 Kbytes/sec)

Lock (0x1f) Signal= -43.00dBm C/N= 36.25dB UCB= 26449 postBER= 0

# dvbv5-zap -c /storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf Ocko\ Black -P -t 60 -o fullmux682.

ts

using demux 'dvb0.demux0'

reading channels from file '/storage/.kodi/userdata/addon_data/service.nextpvr/config/adapter0-DVB-T-channels.conf'

service has pid type 0c: 8000

service has pid type 05: 1283

tuning to 682000000 Hz

dvb_dev_set_bufsize: buffer set to 6160384

pass all PIDs to TS

dvb_set_pesfilter 8192

(0x00)

Lock (0x1f) Signal= -60.00dBm C/N= 24.75dB UCB= 26449 postBER= 160x10^-6

Lock (0x1f) Signal= -60.00dBm C/N= 24.75dB UCB= 26449 postBER= 160x10^-6

Record to file 'fullmux682.ts' started

buffer overrun after 36.11 seconds

received 200292380 bytes (3259 Kbytes/sec)

Lock (0x1f) Signal= -60.00dBm C/N= 25.25dB UCB= 26449 postBER= 340x10^-6

Quote

I can't confirm on LE12 but on LE11, I just download the Debian package for libdvbv5 https://packages.debian.org/bullseye/libdvbv5-0 armhf version and extract dvbv5-zap to ~/.kodi/addons/service.nextpvr/nextpvr-bin/DeviceHost/arm32 from there confirm

LD_LIBRARY_PATH=./ ./dvbv5-zap --version

I did not find the requested utility in the linked package, found it here:http://ftp.us.debian.org/debian/pool/ma…-5+b2_armhf.deb

Unpacked and copied to destination folder.

LE:~/.kodi/addons/service.nextpvr/nextpvr-bin/DeviceHost/arm32 # LD_LIBRARY_PATH=./ dvbv5-zap --version

dvbv5-zap version 1.24.1

edit - btw. this utility was already part of LE (dvb-tools add-on?)

/usr/bin/dvbv5-zap

Here you are, debug level turned on recently but the latest tuning issue should be there.

http://ix.io/4xJ4

http://mysharegadget.com/230987988

At about 4:07 I have encountered a popup from Kodi GUI saying tuner is no longer available & timeshift stopped

http://mysharegadget.com/280447611

The reason was EPG update scheduled at 04:05:00

The "second image menu" I usually don't use for timeshift navigation. It was just last chance I have found, 'pushing' the highlighted button (didn't know it's chapter prev) to get back to timeshift starting position (very left) like it's visible on third image.

Usually (when it works like should) I am just using Left (arrow) and Right (arrow) on my remote control which opens the timeshift bar on display top like it's visible on first image. And moving inside the timeshift window back and forward with these two keys.

Yes only HEVC (h265) currently, don't use old DVB-T channels in mentioned issue examples.

Quote

I noted there is a PR submitted to have the DVB-T channels removed for the TVH repo.

Not the ideal choice as I have mentioned - there are still some local minor DVB-T providers which won't be found automatically then.

Quote

You would need to post a wishlist post of the forum for the author to optionally allow a size based buffer. I tend not to support that since it could be confusing for users to not really know how much buffer is available. I'd also have to rework pvr.nextpvr.

Well, currently I don't have a spare time to take a part in next two forums (TVH and NPVR). I would like to use better product under LE and it's up to developers if they are interested to improve their add-ons or not. The development of TVH is very slow and I don't see any progress here for years. So you have a chance to take over. `

Not supporting the requested feature is a bad choice because with variable data rates you can't predict at all how large buffer you need. So I believe my request has a reason. I don't know how the add-on communicate with Kodi regarding to timeshift "window", perhaps it's too complex to program it properly but I believe it should be possible.

Quote

For timeshifting I did see an seek back on Seznam.cz that had odd range headers for http that is why I would need the Kodi debug logs.

In my case it was not Seznam but CT1 (HD stream). Usually there are more issues with HD streams.

Quote

I can't confirm on LE12 but on LE11, I just download the Debian package for libdvbv5 https://packages.debian.org/bullseye/libdvbv5-0 armhf version and extract dvbv5-zap to ~/.kodi/addons/service.nextpvr/nextpvr-bin/DeviceHost/arm32 from there confirm

LD_LIBRARY_PATH=./ ./dvbv5-zap --version

works and then we can continue, if not I will install LE12.

Thanks, I'll give it a try and let you know when ready (it may take some time)

Quote from emveepee

Are you using the chapter arrows in PVR?

Probably not as I don't know what it is and how to use.

Simply using Left and Right buttons on my IR Remote control.

Currently I am not able to switch the channel (without restarting the NPVR service), as mentioned earlier in previous thread.

in Kodi's log I see this after the (unsuccessful) channel change:

Jun 08 02:41:22 LE service.nextpvr[224764]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 08 02:41:22 LE service.nextpvr[224764]: ERROR FE_SET_PROPERTY: Bad file descriptor

Jun 08 02:41:22 LE kernel: rpivid feb10000.codec: rpivid_h265_stop

The first attempt does not return any error in Kodi GUI, just like STOP pushed. Another attempt to start any channel returns Playback failed - One or more items failed to play. Check the log for more information about this message.

And the two lines appears in log again:

Jun 08 02:44:36 LE service.nextpvr[224764]: ERROR Can't retrieve DVB information for the new delivery system.: Bad file descriptor

Jun 08 02:44:36 LE service.nextpvr[224764]: ERROR FE_SET_PROPERTY: Bad file descriptor

After the NPVR service restart I can start playing any channel again.

OK, let's continue here with NextPVR add-on only: NextPVR add-on issues

Fork from this thread: RE: NextPVR vs TVHeadend

The issue with timeshift rewind (using left key button) encountered again.

I have found I can jump to start but only with another menu invoked by OK button, then I can't use the Left or Right butons for rewind otherwise it jumps to middle position and can't rewind to start again.

The status of .ts files at that moment:

LE:~/.kodi/temp # ls -l -h /tmp/ramdisk/

total 480M

-rw-r--r-- 1 root root 102.9M Jun 8 01:11 live-CT 2 HD T2-0-1.ts

-rw-r--r-- 1 root root 376.7M Jun 8 01:09 live-CT 2 HD T2-0.ts

-rw-r--r-- 1 root root 4.0K Jun 8 01:00 live-CT 2 HD T2-0.ts.map

LE:~/.kodi/temp # cat /tmp/ramdisk/live-CT\ 2\ HD\ T2-0.ts.map

<map>

<stream_length>430068612</stream_length>

<stream_duration>532882</stream_duration>

<complete>false</complete>

<live>true</live>

<files>

<file>

<filename>/tmp/ramdisk/live-CT 2 HD T2-0-1.ts</filename>

<offset>394997212</offset>

<start_ms>501008</start_ms>

<end_ms>532882</end_ms>

</file>

<file>

<filename>/tmp/ramdisk/live-CT 2 HD T2-0.ts</filename>

<offset>0</offset>

<start_ms>0</start_ms>

<end_ms>501008</end_ms>

</file>

</files>

</map>

Thanks for your quick reply as well.

Quote from emveepee

However from what I can tell both those frequencies should be in the tables that the service downloads https://github.com/tvheadend/dtv-…nd/dvb-t/cz-All

This table looks OK but the DVB-T2 items are at the end while DVB-T is obsolete so this should be reflected. I am not sure how tuning works but I believe best option should be to put DVB-T2 and DVB-T sections together with the same frequency, like outlined above ( so the tuning could be perhaps quicker ).

Quote from emveepee

- You have timeshifting set to 25 minutes of buffering so it should be able to rewind to the beginning of the buffer not the show. The actual file might be a little longer but the API restricts it to 25 minutes. I would treat this as an add-on issue though and would need Kodi debug logs.

In this case I believe it was Kodi's bug. I think .ts files were recorded correctly but in Kodi I could (at specific time, when the .ts was about 15 minutes long) rewind about 5 mins back. With TVH sometimes I can get the timeshift point outside of timeshift window. It works quite bad. TVH timeshift also does not work if the option to limit saved timeshift data size is set. This is completely ignored. I would like to see this (working) option in NPVR because the limitation by time is not very good. There are different channels with different stream data rates so you have to limit timeshift for the maximum data rate channels. Thus you can't use the remaining capacity for timeshift when watching channels with low data rate and this is pity. I would just like to configure the ramdisk volume with some capacity and wish NPVR to use it for timeshift data completely (until it's capacity is exhausted) regardless the data rate ( or till the configurable data size limit instead of time limit ). Hopefully this shouldn't be so complex task to add that feature.

I'll keep testing and provide you with Kodi logs when I encounter an issue recorded there.

Quote from emveepee

saw some trouble tuning at the driver level "dvb_fe_set_parms failed" Since I am pretty sure that NextPVR always tunes the same way, I feel that is a driver issue.

Yeah when I sent the comments, rebooted LE and then switching channels did not work again (without detail from Kodi)... Then tried the web client to get the error message which was that there's no available tuner (but the tuner device was visible in settings and it's MyGica which was always very reliable, at least in earlier LE versions & Windows). So I believe there could be some issue. I can also try another tuner (Astrometa).

Quote from emveepee

To tackle the EPG problem sub (the author) would need a full mux capture, from the RPi or any other PC you have. I can help you with this if you would like to continue. I could also use the full mux to feed into a modulator here to see if I can duplicate the tuning issue.

OK, this shouldn't be a problem if the full muxes (5 muxes used in my case) can be recorded from LE 12 / 11. I am looking forward for your instructions. Thanks for your effort!

Quote from emveepee

Thanks for taking time to provide feedback ghtester. The scan tables that I download with the nextpvr service https://github.com/LibreELEC/Libr…ce/addon.py#L34 should be be the same ones that TVHeadend uses. I did suggest to CvH that they should be placed in a common location as opposed to being part of each PVR but that is not available yet.

For the "code page" issue is the data correct in either Kodi(pvr.nextpvr) or the web browser? I am trying to determine where the issue might be. For the OTA guide the character set is in the EIT data and there might be an issue with the utf conversion if both are incorrect.

You absolutely should not be using the web player if it is hosted by the RPi for broadcast TV it is not powerful enough for the on-fly-transcoding. It may not crash the server but the transcoding can no doubt max out the system. There is also about a 15 second lag in web playback before a tuner can be used. Personally, I don't think the web player provides a good PVR experience anyway but I also like using a remote. Some people are mouse/desktop users and use IPTV that doesn't need transcoding or have an x64 device with h/w transcoding and appreciate it.

If you experience issues with playback in pvr.nextpvr when you don't touch the web server I would be interested in seeing the NextPVR logs especially if Kodi is crashing on the raw mpeg ts streams.

The logs level is in config.xml the default is <LogLevel>DEBUG</LogLevel> which is probably correct during the initial testing but you can change it to ERROR at some point. The entire data area, logs, database, channel icon, art etc can also be stored on better storage if you want by editing this line in the service startup https://github.com/LibreELEC/Libr…xtpvr.start#L14

OTA EPG updates are designed to be scheduled daily in off hours when you aren't watching or recording. That could be an advantage for TVHeadend if it never interferes with the broadcasts.

Thanks again for helping out.

Display More

Thanks for your reply, it's great to see a developer's interest to improve his product.

As there are still some minor DVB-T providers here, the cz-All scan table should contain two sections for every frequency, like this (tested and working for both DVB-T and DVB-T2 providers):

[CHANNEL]

DELIVERY_SYSTEM = DVBT

FREQUENCY = 474000000

BANDWIDTH_HZ = 8000000

CODE_RATE_HP = 2/3

CODE_RATE_LP = NONE

MODULATION = QAM/64

TRANSMISSION_MODE = 8K

GUARD_INTERVAL = 1/8

HIERARCHY = NONE

INVERSION = AUTO

[CHANNEL]

DELIVERY_SYSTEM = DVBT2

FREQUENCY = 474000000

BANDWIDTH_HZ = 8000000

CODE_RATE_HP = AUTO

CODE_RATE_LP = AUTO

MODULATION = QAM/AUTO

TRANSMISSION_MODE = AUTO

GUARD_INTERVAL = AUTO

HIERARCHY = AUTO

The EPG text has a bad coding in both Kodi & web browser, it's the same and I believe the reason is the ISO-6937 coding is used here (AFAIK) for EPG ( https://en.wikipedia.org/wiki/T.51/ISO/IEC_6937 ) . So instead of local character with diacritics I see two characters - first is a sign of diacritic and second one is an ASCII character.

I don't use web player, just tested quickly and the primary reason for opening the web interface was a configuration of some NPVR parameters which are not available in Kodi NPVR add-ons settings. Currently I don't need transcoding, I am watching the Live-TV from RPi but a "must have" feature for me is timeshift (to RAM). So I was looking where I need to enable it and surprisingly it's only under Streeaming options - Live TV method - Transcoded submenu in NPVR client add-on. It looks it have to be enabled there and then it's necessary to switch the Live TV method to Timeshift from Transcoded. It's a bit confusing. Now I have the Streaming options - Live TV method in NPVR client set to Timeshift and switching channels works. When playing with this settings, not just NPVR client but even Kodi restarted sometimes. You can look at some recent logs here: http://mysharegadget.com/809460486

I have experienced the playing was stopped suddenly, maybe it could be visible in the log but I don't remember the time.

There are issues with timeshift but I am sure Kodi is buggy in this part of functionality - I saw the .ts files created by NPVR in /tmp/ramdisk folder, i could copy them to permanent folder and play using VLC remotely but in Kodi I suddenly could not "rewind" to starting point. I never had such strange and random troubles with timeshift on Windows with several DVB-T applications like on LE/Kodi. This works really bad here and at least Kodi and Tvheadend should be significantly improved in this part, but I see the lowest priority of LiveTV...

Thanks for sharing details regarding to logs / data area settings, it's helpful.

In fact I don't know how exactly TVH works with EPG (as previously mentioned, it's buggy and I am sometimes experiencing corrupted items), I think without Internet connection it can't grab EPG despite it should get it OTA. But it works somehow and soon or later I see EPG on all channels.

With NPVR, so far I don't see EPG on many channels despite the Automatic EPG update was initiated. Maybe I should try to increase the Seconds per freq: parameter. To be tested...

I still see the streaming interruption (when the Automatic EPG update occurs) as an issue, I understand the reason but there should be any alternative...

Thanks for your work, I believe NPVR has a potential to be very useful for many users.

Quote from emveepee

I would be interested in you expanding on your comments about NextPVR specifically as it relates to functionality of pvr.nextpvr vs pvr.hts and stability of the server (missed recordings and server failures). I believe these are things that can be addressed. Ignore the web server playback since that is not expected to be useful on anything other than IPTV with any Arm devices.

Since NextPVR only records raw mpeg ts streams, does that change anything regarding pvr.nextpvr playback. While Linux support is relatively new and LE support even newer, pvr.nextpvr has been playing these same raw streams from Windows servers for years and we don't often get comments that timeshift is unstable. You may just have poor quality streams, which can easily be tested by creating recordings.

At first I had to edit the cz-All scan table to add DVBT2 items otherwise only DVB-T channels were found (in our country the move to DVB-T2 occured a couple years ago). Luckily it was easy to find the appropriate table but I had to edit it manually.

Another issue is with EPG code page which does not reflect national characters and so far I did not find a settings where it could be configured.

When I played with the timeshift settings, several times the add-on stopped working, sometimes even Kodi restarted.

The worst issue I am now facing to is that after switching the Live TV channel the error Playback failed is returned in Kodi and Streaming Failed (transcoder exited) when I try to play a channel with web player. Then the nextpvr service needs to be restarted. Sometimes the similar issue happen with a report from web player there's no free tuner (despite it is). Maybe the change of timeshift path to ramdisk could be an issue, I need more time for testing. Nevertheless, it looks the nextpvr service is writing to filesystem (logs?) quite often which is a thing you don't want when booting LE from micro SD card (and so far I did not find a settings to prevent that).

Another issue is with EPG update (there's a timestamp setting for this) which interrupts the ongoiing LiveTV streaming.

From my experience on RPi 4b / LE 9 -12:

- Tvheadend is a great product but with some serious bugs which there are for years (timeshift unstable and buggy, EPG corruption, issues with subtitles on version 4.3 ).

- NPVR I am now testing on RPi 4b / LE 12 and unfortunately I have to say it's much worse regarding to functionality/configurability and stability

Just to confirm this annoying bug is still present in LE 12 Nightly ( nightly-20230527-557e821 (RPi4.aarch64) ).

Also sometimes the audio stream (usually AAC) is not detected at all after switching Live TV channels, even though the signal quality is great.

After upgrade from LE11 to LE12 nightly-20230522-794a8ad (RPi4.aarch64) Raspberry Pi Tools (Team LibreELEC - 11.0.0.0) is not working properly anymore and it looks there's no updated version yet.

python /storage/downloads/shutdown.py &

LE:~ # Traceback (most recent call last):

File "/storage/downloads/shutdown.py", line 10, in <module>

import RPi.GPIO as GPIO

File "/storage/.kodi/addons/virtual.rpi-tools/lib/RPi/GPIO/__init__.py", line 23, in <module>

from RPi._GPIO import *

ImportError: /storage/.kodi/addons/virtual.rpi-tools/lib/RPi/_GPIO.so: wrong ELF class: ELFCLASS32

[1]+ Done(1) python /storage/downloads/shutdown.py

OK, I understand, thanks.

For those who fell into the same issue, this should be enough to revert to LE 10.0.4 (as the time interval from reboot to crash is long enough):

cd /storage/.update
wget -c https://releases.libreelec.tv/LibreELEC-Generic.x86_64-10.0.4.img.gz
touch /storage/.update/.nocompat

Thanks for a quick reply. Is there any workaround known yet (except moving back to LE 10.0.4) please?

http://ix.io/4sAk

When a SD cards turns out to read-only, usually it means it's gone. Please note the write cycles are limited on such media so even a high quality SD cards can't be expected to live forever if there are daily writes from running OS (and LE can generate writes very quickly in some occassions if you don't tune up the logging options).

The better solution is to avoid using SD cards and switch to HDD connected through USB/SATA adapter instead.