Beiträge von carel

  • [vdr-plugin-satip] "SATIP-ERROR: bool cSatipFrontends::Attach(int, int) no Frontend found for attaching deviceID 0 (TP 386)"

    Hello again


    As a test I reduced the number of SAT IP devices on the server from 3 to 2.

    I switched frontends on the client with <left> <right> and the channels work on both devices.


    Funny is that the plugin still shows three 'error' lines, although I now only have two devices active

    Code
    jul 24 10:36:57 woonkamer vdr[1133904]: [1133911] SATIP-ERROR: bool cSatipFrontends::Attach(int, int) no Frontend found for attaching deviceID 0 (TP 386)
jul 24 10:36:57 woonkamer vdr[1133904]: [1133911] SATIP-ERROR: bool cSatipFrontends::Attach(int, int) no Frontend found for attaching deviceID 0 (TP 386)
jul 24 10:36:57 woonkamer vdr[1133904]: [1133911] SATIP-ERROR: bool cSatipFrontends::Attach(int, int) no Frontend found for attaching deviceID 0 (TP 386)

    So doesn't seem related to the number of devices in use

  • [vdr-plugin-satip] "SATIP-ERROR: bool cSatipFrontends::Attach(int, int) no Frontend found for attaching deviceID 0 (TP 386)"

    Thanks for the suggestions.


    Running with Psatip -d 3 using default port 553 did not change anything.


    minisatip recognizes the three adapters


    Just the error lines in the client, I still have a picture

  • [vdr-plugin-satip] "SATIP-ERROR: bool cSatipFrontends::Attach(int, int) no Frontend found for attaching deviceID 0 (TP 386)"

    Morning!


    Each time I switch channel I get below lines in the log, although it doesn't seem to have any impact.

    Code
    vdr[937050]: [937055] SATIP-ERROR: bool cSatipFrontends::Attach(int, int) no Frontend found for attaching deviceID 0 (TP 274)
vdr[937050]: [937055] SATIP-ERROR: bool cSatipFrontends::Attach(int, int) no Frontend found for attaching deviceID 0 (TP 274)
vdr[937050]: [937055] SATIP-ERROR: bool cSatipFrontends::Attach(int, int) no Frontend found for attaching deviceID 0 (TP 274)
vdr[937050]: [937055] SATIP-ERROR: bool cSatipFrontends::Attach(int, int) no Frontend found for attaching deviceID 0 (TP 386)
vdr[937050]: [937055] SATIP-ERROR: bool cSatipFrontends::Attach(int, int) no Frontend found for attaching deviceID 0 (TP 386)
vdr[937050]: [937055] SATIP-ERROR: bool cSatipFrontends::Attach(int, int) no Frontend found for attaching deviceID 0 (TP 386)


    Does the plugin start counting from 0 or 1? Currently starting as follows:

    Code
    -Psatip -d 3 -s meterkast:8554|DVBC-3|minisatip


    I'm using minisatip on a RPI4:

    Code
    minisatip --enable-adapters 0-2 --delsys 0:dvbc,1:dvbc,2:dvbc --logfile /var/log/minisatip/minisatip.log --http-port 8080 --rtsp-port 8554


    Settings

    Code
    satip.CICAM = 0 0
satip.DisabledFilters = 3 4
satip.DisabledSources =
satip.EnableCIExtension = 0
satip.EnableEITScan = 0
satip.EnableFrontendReuse = 1
satip.OperatingMode = 1
satip.TransportMode = 0


    Any idea what it can be? something wrongly set?


    Carel

  • Gibt es eine Alternative zu DVB-C welche mit VDR funktioniert?

    Below my an example of a more 'standard' vlc streamer for general 'iptv' from the web:

    Code
    /usr/bin/vlc -I dummy -v --network-caching=4000 --live-caching 2000 --http-reconnect --http-user-agent='Mozilla/5.0' --http-referrer="<url>" "<link to m3u8>" --sout #standard{access=udp,mux=ts{use-key-frames,pid-video=100,pid-audio=200,pid-spu=4096,tsid=4711},dst=localhost:4320}


    In a script:

    Code
    $VLC $VERBOSE $NETWORK_CACHING --http-reconnect --http-user-agent="Mozilla/5.0" --http-referrer="$REFERRER"  "${URL}" --sout \
"#standard{access=udp,mux=ts{use-key-frames,pid-video=${VPID},pid-audio=${APID},pid-spu=${PID_SPU},tsid=${TID}},dst=${HOST}:${PORT}}" \
&>"$LOG_FILE" &

    Some web sites want the referrer URL in the http header, use this to avoid a 403 error


    When you want VLC to always chose the highest resolution use:

    Code
    --adaptive-logic highest

  • Gibt es eine Alternative zu DVB-C welche mit VDR funktioniert?

    Hi Paulaner,


    ffmpeg reads the stream just fine, the issue is with the UDP streaming.


    When you tune to the test channel the first time, can you then please check if you see just one ffmpeg process? Or even vlc?

    If there are, for some reason, that will lead to conflicts in the UDP stream.


    Just to be sure we have all signals available to kill ffmpeg, add HUP to it:

    Code
    trap 'kill -SIGKILL ${PID} 2>/dev/null; exit' INT TERM KILL HUP


    And please don't forget before you test:

    Code
    sudo sysctl -w net.core.rmem_max=2097152
sudo sysctl -w net.core.rmem_default=2097152
sudo sysctl -w net.core.wmem_max=2097152
sudo sysctl -w net.core.wmem_default=2097152

    Maybe an idea to add to /etc/rc.local (if that's available)


    If it fails, try this from SHF

    Zitat

    Hier ein Link zum Thema UDP und Puffer:

    Monitoring the UDP Socket Buffer

  • Gibt es eine Alternative zu DVB-C welche mit VDR funktioniert?

    Hi Paulaner

    I still don’t understand why your ffmpeg based script is not working well.

    I compiled ffmpeg 4.4.2 on my test system and it’s working well. (Not with all your options, don’t need all those)


    Important options during execution are:

    -re

    $HOST:$PORT?pkt_size=1316&buffer_size=65536


    And sufficiently high

    -probesize

    -analyzeduration


    Just to be sure, execute below

    Code
    sudo sysctl -w net.core.rmem_max=2097152
sudo sysctl -w net.core.rmem_default=2097152
sudo sysctl -w net.core.wmem_max=2097152
sudo sysctl -w net.core.wmem_default=2097152


    And if all ‘PIDs’ match it should work

  • Gibt es eine Alternative zu DVB-C welche mit VDR funktioniert?

    I think this is (also) related to your problem:

    I'm not seeing that on my side

    Code
    [hls @ 0x559eef0fda00] No longer receiving playlist 2 ('https://hse24.akamaized.net/hls/live/2006663/hse24/master_900p25.m3u8')
[hls @ 0x559eef0fda00] No longer receiving playlist 4 ('https://hse24.akamaized.net/hls/live/2006663/hse24/master_576p25.m3u8')
[hls @ 0x559eef0fda00] No longer receiving playlist 1 ('https://hse24.akamaized.net/hls/live/2006663-b/hse24/master_1080p25.m3u8')
[hls @ 0x559eef0fda00] No longer receiving playlist 3 ('https://hse24.akamaized.net/hls/live/2006663-b/hse24/master_900p25.m3u8')
[hls @ 0x559eef0fda00] No longer receiving playlist 5 ('https://hse24.akamaized.net/hls/live/2006663-b/hse24/master_576p25.m3u8')


    With regards to the vlc2iptv script, just kill -9 vlc when switching channel:

    Change trap line like below

    Code
    trap 'kill -KILL  ${PID} 2> /dev/null' INT EXIT QUIT TERM KILL

    Maybe not very gentle but effective

  • Gibt es eine Alternative zu DVB-C welche mit VDR funktioniert?

    Runs like a charm


    This is my ffmpeg command running:

    Code
    ffmpeg -y -hide_banner -user_agent Mozilla/5.0 -reconnect 1 -reconnect_streamed 1 -reconnect_delay_max 1 -probesize 8000000 -analyzeduration 8000000 -f hls -http_persistent 0 -re -i https://hse24.akamaized.net/hls/live/2006663/hse24/playlist.m3u8 -codec:v copy -codec:a copy -streamid 0:100 -streamid 1:200 -flush_packets -1 -f mpegts -mpegts_transport_stream_id 2836 -mpegts_pmt_start_pid 4096 -mpegts_service_id 6016 -mpegts_original_network_id 65281 udp://brix:4320?pkt_size=1316&buffer_size=65536&overrun_nonfatal=1


    Try to find obvious difference with your ffmpeg while running ‘HSE’

    Especially this part is important

    Code
     pkt_size=1316&buffer_size=65536&overrun_nonfatal=1