Posts by ghtester

    HTPC:~/.config/irtrans # irserver -loglevel 4 -debug_code /dev/ttyUSB0

    This is wrong. If you try to run it inside the folder, you have to enter ./irserver

    That's why I put the example with absolute path which must work ( /storage/.config/irtrans/irserver )

    Otherwise you have an issue with SSH client or a filesystem issue.

    The source codes needs to be compiled. The better option should be to get the necessary files from OpenELEC package.

    You need to follow the instructions from thread you mentioned above.

    Start here: RE: irserver add-on

    You need to obtain the necessary files from this package or an alternative files from OpenELEC as apa explained.

    For the original irserver installation to /storage/.config/irtrans/ folder, try copy & paste these commands to SSH console:

    Code
    cd /tmp
    wget -c http://www.irtrans.de/download/Server/Linux/irserver.tar.gz
    tar -xf irserver.tar.gz
    sed -i 's+/usr/local/+/storage/.config/+g' install.sh
    ./install.sh

    Then try to run it manually to see if it's doing something:

    /storage/.config/irtrans/irserver -loglevel 4 -debug_code /dev/ttyUSB0

    If it works, you may try to put the startup line to /storage/.config/autostart.sh file, which could perhaps be something like:

    /storage/.config/irtrans/irserver -logfile /var/log/irserver.log -pidfile /var/run/irserver.pid -daemon /dev/ttyUSB0

    If you get the irserver running, then you need to finish the remaining instructions from this and next posts, starting from this point:

    • Instruct Kodi to listen on the alternate LIRC socket (/run/lirc/lircd.itrans) by changing the Kodi command-line parameter with which it is launched.

    I don't have this hardware so you have to give it a try.

    Thanks.

    Do you mean on live tv though?

    This is a recording.

    I watched half of it with audio, then tried to watch it again and it has no audio.

    Even the first part of the film that had audio the first time round has no audio.

    Yes I meant Live TV.

    Sometimes it even happens when I switch to some TV channel (don't know if it's an issue in latest LE 10 Nightly builds but most likely it's related to TV signal quality which is not perfect on some channels in my case) but of course it's hard to say if the same issue happened when your recording started or if there's another reason...

    In my case the same stream profile is used for watching and for recording (pass) so the configuration is same, so far I did not encounter a missing audio in recording but I don't record very often.

    But when I played with Timeshift data (configured to use a filesystem) a bit, some Timeshift files had no audio, some could be played without issue including audio and some could not be played at all... I suppose that's because the Timeshift files probably does not have a header and every file is just a part of a live stream but I don't know any technical details how it works.

    Perhaps there's an utility which could be used to check / repair integrity of your recordings. Also I would to try to play it with another player (VLC on workstation?) to check if the audio is missing / not playing as well.

    Yes it happens sometimes. Usually if the signal level is not strong enough, the audio is "lost" sometimes, when the data stream is corrupted temporarily (usually you can also see a video drop / corruption at that moment).

    Sometimes it recovers later, sometimes not and you need to stop / start the channel again (or switch to another channel and back) to get the audio working again. It's a quite annoying, I don't know why the video can recover and audio not but this happens.

    There's an issue with Subtitles on TVH 4.3 which are not displayed on some TV channels. The settings (all I could find) is exactly the same as on TVH 4.2. The affected TV channel's Subtitles has different look (font type and size) on TVH 4.2 in comparison with Subtitles on other channels.

    Does anyone know why this happens (the different Subtitles look ) and what should I check / configure to make it working on TVH 4.3 (to display Subtitles on affected channel)?

    Edit - VLC is able to display the subtitles properly.

    Edit 20230115 - this stupid bug / incompatibility is still there...

    Nothing special should be necessary if your RPi 4B does not have a very obsolete bootloader.

    Just write a LE image to your external SSD, connect it to RPi 4B and try to boot.

    if it won't work, try the same with SD card ( this should definitely work ), then check the VL805 USB firmware & RPi bootloader versions and upgrade them to latest available (check the release notes here).

    How to check the CURRENT versions: rpi-eeprom-update

    VL805 release should be: 00138a1

    BOOTLOADER should be: Thu Apr 29 16:11:25 UTC 2021 (1619712685) or later.

    You may easily upgrade the VL805 USB firmware & RPi bootloader (not to latest available but to versions contained in LE but useable) from Kodi: Settings - Libreelec - Updates - Firmware Updates

    Usually the VL805 USB firmware is already at the latest available version (00138a1) but the bootloader is a bit obsolete.

    This way you may upgrade it from SSH console to (currently latest) release 2021-04-29 (and the VL805 as well, if it's not the 00138a1 yet):

    Then you may try to boot from external SSD again. If it still won't work (test on both USB3/USB2 ports), check if the power from USB port is sufficient for your SSD (test with USB hub with external power supply or with a fork USB cable).

    The last thing to be done when you make the LE booting from external SSD is to add this line to /flash/config.txt file in LE:

    dtparam=sd_poll_once=on

    otherwise there was a repeating error message filling log due to missing SD card (not sure if it's still necessary).

    Code
    mount -o remount,rw /flash
    echo dtparam=sd_poll_once=on >> /flash/config.txt
    mount -o remount,ro /flash

    Hope this helps.

    Edit: 2021-05-01 - updated link to current firmware above.

    Edit: 2023-01-15 - added update scripts for most current releases below.

    Code
    # RPi 4B - USB controller upgrade:
    cd /tmp
    wget -O USBfirmware.bin -c https://github.com/raspberrypi/rpi-eeprom/raw/master/firmware/stable/vl805-000138c0.bin
    rpi-eeprom-update -u USBfirmware.bin
    reboot
    #

    AFAIK this is not an issue as the signal level on some channels is not perfect so I suppose that's why there are the Continuity errors. They don't increase much in general... It was an issue in past, I was struggling with a driver configuration (Astrometa DVB-T/T2 tuner) but now it works quite good.

    I believe anybody else (who is also using a Live TV & Tvheadend) should be able to reproduce the described Timeshift / Tvheadend issue.

    I don't know what exactly happens when the RAM only parameter is used but on filesystem it's immediately visible if the Timeshift / Maximum size limit is currently working or not.

    I am using tmpfs for the Timethift buffer this way and it's pretty usable:

    mkdir /tmp/ramdisk

    chmod 777 /tmp/ramdisk

    mount -t tmpfs -o size=800m myramdisk /tmp/ramdisk

    I could accept that Timeshift stops (stops writing buffer data) when the buffer is about to overflow... But Kodi does not handle that situation (which happens) correctly (the question is what should be done in this case but I am sure the Timeshift pointer should not jump to nonsense / left border).

    It looks nobody else is interested in nor has this issue.

    But I have spent some time with investigation and now I know more. Maybe it's useless but let me share it anyway:

    - perhaps I should rename this thread because the Timeshift data are not discarded randomly as I thought earlier.

    - the behavior depends on Tvheadend server Timeshift configuration (where the Timeshift buffer should be stored - RAM or filesystem). The better solution seems to use a storage path as it's visible what's happening and the Timeshift data can be accessed / used when necessary.

    - the reason is the Timeshift buffer is overflowed (when the Timeshift buffer is already full and you pause it or move the Timeshift pointer to left border). Then the Tvheadend stops overwriting the buffer data. When unpaused, Kodi can play the buffer files until end and then gets confused, jumps outside of left Timeshift border and decrementing the Timeshift offset to nonsense values.

    - Tvheadend 4.3 has a serious bug in Timeshift configuration - the Maximum size (MB): option is ignored so it may lead to unpredictable results.

    - only Maximum period (mins): can be used but files are created every minute so with very variable size which depends on data stream parameters so the filesystem size can't be effectively used for data streams with lower resolution.

    - Kodi does not count with any possible Timeshift data buffer overflow and this issue is not covered.

    I was thinking, since I have a Raspberry Pi 4b with dual HDMI outputs, would it work to connect output 1 directly to the beamer and output 2 to the receiver to get the audio?

    Yes it's possible, at least in LE10 (don't remember if I tried it in LE 9.2.6 as well or not) to have a video on HDMI0 and an audio on HDMI1.

    But the HDMI devices must be detected when Kodi starts (otherwise you would need to play with EDID etc...).

    Then you should be able to configure the audio output in Kodi menu Settings - System - Audio - Audio output device

    There you should see your receiver at HDMI1.

    Another update - at least there's an issue with Tvheadend backend - Build: 4.3-1940 ~ LibreELEC Tvh-addon v9.80.11.100 (2021-03-10T21:50:53+0100)

    In configuration described above it ignores the parameter Maximum size (MB): and keeps writing buffer files until the filesystem is full or the Maximum period (mins): limit is achieved.

    Even though the Maximum period (mins): parameter is set as the limit (to keep some free space on filesystem), when this limit is achieved, after some time (when moving the Timeshift pointer, perhaps the left border is a critical point), the Timeshift stops working as well as described in previous post... :(

    OK - so now I can see how it works when Timeshift in Tvheadend backend service is configured to use files and when the Timeshift is active:

    There's created folder named buffer, inside appears a subfolder with buffer files (every minute a new file is created until their total size match the Timeshift Maximum size configuration).

    This subfolder's name is a number - starting from 0, as soon as I switch the channel, the folder with buffer files is deleted and a new folder with incremented number is created and a new buffer files are generated. Everything looks working fine...

    Now what happens - sometimes - usually when I try to move the Timeshift pointer in Kodi (with left - right arrows on RC), usually backwards to see the part of the Live stream again:

    - The Timeshift pointer in Kodi does not jump as expected and it's position is lost, then jumps to left border of Timeshift bar (which represents the Timeshift buffer recorded size)

    - The Timeshift feature stops - the buffer data files stays there and it's possible to play them again but it looks at some further point are corrupted

    - TheTimeshift offset can't be moved to zero anymore with Timeshift running (until the channel is switched to another or stopped / started again). But when I try to move the Timeshift pointer to right Timeshift bar's border (keeping right arrow pressed) until the Seeking offset is >= negative Timeshift offset, it switches to Live stream (but it does not record to Timeshift buffer anymore). In this state any left-right arrow push starts playing the Timeshift buffer from begin.

    Don't know if anyone can ever read this and understand what I mean - better try. But it's a real nightmare, how this feature (not)work. :(

    When I tried the same with Timeshift to RAM only, it was even worse because the buffer data were immediately discarded when the Timeshift pointer was lost so there was nothing to analyze.

    I don't know how it works together, if Tvheadend backend (4.3) has a bug or if that's Kodi but it looks more likely that Kodi can't work properly with Timeshift / Timeshift buffer data.

    Also it looks the critical moment is when the Timeshift buffer gets full (so a circle write must start).