Posts by nvdias

    SNR 28 db

    strenght -78 dBm

    Well ... assuming those are DVB-C signals, I will suggest you to try a different connection.

    do you have a way to connect to 1 of the first cable wall plugs ?

    Or even directly in the cable that enters your home ?

    (just to make sure you are not getting a big signal drop in your home cabling, and assure that that is not the reason for your breaks)

    Further testing and it looks like issue is with my streams and even recordings...ffmpeg is showing many errors while transcoding both live tv and recordings..strange thing is these corrupt segments are not teally visible when watching live tv and not even on recordings...my reception is a bit on the low side tough..about 43%..

    Have you've been successful meanwhile ?


    When you say 43%, can you report the SNR ? (in tvheadend's interface, status/stream).

    For your reference, in average I have:
    cable - SNR 36.3 dBm ; Signal strength 51.0 dBm.
    sat - SNR 15. dBm ; -30.5 dBm.

    Using a TBS 5520 SE combo receiver.

    About your error:

    is strange, I use libreelec 9.2.6 and my ffmpeg works ok.

    libdrm.so.2 is in /usr/lib/libdrm.so.2

    Have you tried executing ffmpeg from a ssh shell ?


    About clients:

    I do my tests with vlc in PC to connect to tvheadend in my Rpi trough a m3u list got from http://tvheadend_ip_address:9981/playlist/channels

    This transcoding, takes some seconds to start, after starting 5 to 10s after it stops for 2 seconds (buffering), but then it plays all the time without issues, providing I have a good network connection. of course.

    There is also a nice free tvheadend client for iOS devices that works great, and it is easy to select a codec profile from it.

    This is very strange.

    I use the exact same approach with a RPi3 and a RPi4, but I have none of those issues.

    As I've posted in another thread, this is my ffmpeg command line,

    Code
    /storage/.kodi/addons/service.ffmpeg/bin/ffmpeg -loglevel quiet -i pipe:0 -vf scale=640:360 -vcodec h264_omx -vb 512k -bufsize 2048k -g 100 -af "aresample=async=1:first_pts=0" -acodec aac -ab 128k -f mpegts pipe:1

    The major diferences are that I'm not forcing the frame rate nor the pixel format and I use a different ffmpeg version.

    I use a ffmpeg version compiled directly in my RPi3 from the official ffmpeg sources.

    If you want to test with it, just download from this link:

    https://mega.nz/file/NGIxxSIa#…IAtSfNVEoInPmL8

    Install the add-on directly from libreelec's kodi interface.

    ffmpeg path is:

    Code
    /storage/.kodi/addons/service.ffmpeg/bin/ffmpeg


    Note: Also take a look into gpu_mem in /flash/config.txt (i'm using 256 in my RPi3, and 512 imnRPi4)

    Note: It is a personal add-on that I've not yet released, which includes ffmpeg to help nginx to serve as a transcode server

    (if you are interested in knowing more, just read the txt file inside the add-on, or take a look at http://RPi_ip_address:9996/cgi-bin/movies.cgi?/storage after install - user/pass)


    Another thing: What client are you using to test the stream ?

    Gonna try your command...you have some code I never tryed before..

    what is this for?

    Code
    -g 100 -af "aresample=async=1:first_pts=0"

    Still stopping on my setup..max it plays is 10 minutes...are you using FFMPEG addon from Libreelec repo?

    Your 10 mins, might be a memory problem.

    I am not using ffmpeg from libreelec. I've made a ffmpeg compilation with omx serving nginx server for live web transcoding of recordings - I might share it in the forum but I do not believe that is the issue.

    -g 100 is the GOP length. 100 is recommended for mpeg streams.

    -af "aresample=async=1:first_pts=0", helps audio resampling when there are interruptions in tv reception and solving audio de-syncs.

    -bufsize 2048k increases the buffer size to help again handling interruptions in reception.

    These had been very helpfull for me in receiving steady streams.

    • For your tests I suggest you use an unencrypted channel.
    • Also confirm you have a good cable connection (of course).
    • And depending in your device, as I have a Raspberry Pi4 with 4GB, I have dedicated 512 KB to the GPU, which has been helpfull in timeshift buffering and fast-forward and rewiding recordings (gpu_mem=512 in /flash/config.txt)
    • About timeshift, i only use RAM for timeshift, never disk, which also increases stability, as less disk access when watching tv.

    Have you tried nextpvr? not sure if it's any good or not but it seems to be actively supported. Maybe somebody here knows if it's any good or not.

    I've tried nextpvr in my RPi4 with libreelec.

    As i have docker installed is wuite easy, just need to add privileges and devi /dev/dvb/adapter0, and adjust directories.
    But ...... NEXTPVR fails the transcoding in RPI devices.

    AND ... does not support encrypted channels.


    Tvheadend, even with not much updates in the past years is still the best pvr backend.


    TRANSCODING WITH TVHEADEND AND FFMPEG

    About some issues, some people asked some threads above, regarding transcoding with tvheadend.

    I use tvheadend nighlty build (4.3 beta) which support spawning.

    I'm using ffmpeg compiled with omx installed in libreelec.

    for reference I share my ffmpeg transcoding for tvheanded.

    I call it "transcode-omx". It uses about 60% of RPi4 total performance:

    Code
    {path_ffmpeg}/ffmpeg -loglevel quiet -i pipe:0  -vf scale=640:360 -vcodec h264_omx -vb 512k -bufsize 2048k -g 100 -af "aresample=async=1:first_pts=0" -acodec aac -ab 128k -f mpegts pipe:1

    Just add-it "configuration/ stream" in tvheaded webui.

    some additional tweaks I use for it in the attached picture.

    This configuration summary:

    • codec omx from Raspberry Pi hardware
    • output video 640x360,
    • ar 16:9
    • video bitrate 512 kbps
    • audio bitrate 128 kbps
    • audio resync (to handle some drop frames that could happen during reception of channels).


    This profile is great for watching tv channels in a rmeote smartphone connected to tvheadend running in libreelec.

    This profile can also be applied to record programmes with lower bitrates

    With the change suggested, compilation for RPi4 failed:

    - Compiled with:

    PROJECT=RPi DEVICE=RPi4 ARCH=arm make image

    - Returned error. Log here:

    Ubuntu Pastebin


    Hi,

    I tried to install it for TBS 5955. The installation was successful, without any visible error. But TVheadend doesn't show USB TBS 5955 tuner.

    Can you help me, please ?

    The patch that smp made seems to be only for 5520SE.

    Maybe he could help with 5955 too ...


    Btw, i've just updated the driver for the new kernel version that goes with last LE10 nightly builds (5.10.25).

    https://mega.nz/file/MCpFVS6a#…hOBte5fIgANvTxg

    Does Tvheadend have a way to transcode a recording from MPEG2 to H264 on disk (not on-demand via a stream profile)? I think that's the one thing it was missing for me when I looked at it a 4 or 5 years ago. I think it was hacky like MythTV's transcode, except the transcode solution I have in MythTV also broke commercial skipping.

    Nope. For transcoding recordings I had to create an addon for kodi that uses nginx to serve a cgi that spawns ffmpeg to list and transcode files from a directory.

    I’ve been using tvheadend for quite a while. Without major complains.

    Good kodi integration.

    Spawning ffmpeg for stream transcode and using m3u playlist to access the channels in my mobile devices. ( there’s a very good client for idevices in the Apple Store ).

    Been keeping tvheadend updated with the nightly builds, or my own builds taken from GitHub.

    It is true that no official new versions had Been released, but 4.3 betas are very stable.

    No interest here in changing 😉

    It's not trivial and there are other things with a higher priority right now.

    And Alternatively won’t it be possible to keep omx/mmal decoding in LE10 as an option to the user ?

    This could led to the ability to choose between DRM_Prime and omx/mmal in the settings and so to have deinterlace available (the quality is really worst in tv viewing without deinterlace when compared to 9.2.6).