[vdr-plugin-satip] this and that

    For the Debian & Ubuntu aware people I pushed vdr-plugin-satip-0.1.0 & vdr-plugin-femon-2.0.4 to my testing ppa.

    mini73

    Both do contain "dh_gencontrol" ... :)

    Regards
    fnu

    HowTo: APT pinning

    Click for my gear

    [¹] Intel NUC Kit NUC7i5BNH, Akasa Newton S7, 8GB DDR4, WD Black SN700 500GB NVMe, Crucial MX500 2TB, CIR, SAT>IP, Ubuntu LTS 18.04.5, VDR 2.4.1 (15W)
    [²] Intel NUC Kit NUC7i3BNH, 8GB DDR4, WD PC SN520 250GB NVMe, Crucial MX500 1TB, CIR, SAT>IP, Ubuntu LTS 20.04.1, VDR 2.4.1 (13W)
    [³] BQ500, Asrock X470D4U, AMD Ryzen 5 5600, 32GB DDR4 ECC, 2x WDC SN750 512GB, 4x Samsung SSD 4TB, 1x Samsung SSD 8TB, 1x Crucial MX500 500GB, 1x WDC Blue SSD 500GB, Windows Server 2019 Hyper-V (35W)
    [⁴] Jultec JPS0501-12AN, JPS0501-8M2, Octopus Net (DVBS2-8) & openHABian 3.3.0

    still no success wtih satip-0.1.0 and Triax TSS400.

    Hi!

    Same behaviour as before. A new log is attached.

    Niel

    Files

    vdr.log.txt 55.51 kB – 262 Downloads

    Client Wohnzimmer:
    RPi, VDR 2.1.6, rpihddevice, satip, remotetimers, osdteletext
    Client Schlafzimmer:
    zurzeit keiner
    VDR-Server:
    Epia 5000, 8 GB DOM, Skystar 2 HD, VDR 2.1.6, satip, svdrpservice
    (dient als Homeserver, macht auch noch andere Sachen, Zugriff auf 1TB NAS)
    Satip-Server:
    GSS.box DSI 400

    Here is my version:
    OS: Ubuntu 13.10, 32bit
    libcurl3:i386 7.35.0-1ubun i386

    Quote from mikelh

    libcurl3:i386 7.35.0-1ubun i386


    Well, I'm quite puzzled now. Your library version looks good and I'm seeing the sessions correctly on my setup as the libcurl is handling them internally:

    Code
    CURLOPT_RTSP_SESSION_ID
Pass a char * as a parameter to set the value of the current RTSP Session ID for the handle. Useful for resuming an in-progress session.
Once this value is set to any non-NULL value, libcurl will return CURLE_RTSP_SESSION_ERROR if ID received from the server does not match.
If unset (or set to NULL), libcurl will automatically set the ID the first time the server sets it in a response. (Added in 7.20.0)


    One possible reason might be a missing whitespace after your "Session:" header and therefore libcurl doesn't recognize it.

    Hi!

    The OSD of the plugin shows me the correct name and the model 'DVBS2-4' behind the IP address. I hope you mean the infos of the OSD. How else can i verify it?

    May it be that the model must be 'GSS.BOX' like the <modelName>GSS.BOX</modelName> in the desc.xml i attached?

    'DVBS2-4' is the <satip:X_SATIPCAP>DVBS2-4</satip:X_SATIPCAP> whatever it means.

    The behaviour is the same. But i have seen, that the picture go away after a few seconds (blank screen) and come back about 2 seconds later. After about a minute the picture freezes and it is the same as before. That was in 0.1.0 too.

    Thank you

    Niel

    Client Wohnzimmer:
    RPi, VDR 2.1.6, rpihddevice, satip, remotetimers, osdteletext
    Client Schlafzimmer:
    zurzeit keiner
    VDR-Server:
    Epia 5000, 8 GB DOM, Skystar 2 HD, VDR 2.1.6, satip, svdrpservice
    (dient als Homeserver, macht auch noch andere Sachen, Zugriff auf 1TB NAS)
    Satip-Server:
    GSS.box DSI 400

    Quote from Niel

    How else can i verify it?

    Maybe due reading some help, e.g:

    Code
    #/> svdrpsend plug satip help220 vdr2 SVDRP VideoDiskRecorder 2.1.5; Sun Mar 16 21:48:31 2014; UTF-8214-Plugin satip v0.1.1 - SAT>IP Geräte214-SVDRP commands:214-    INFO      MODE      LIST      CONT      OPER214 End of HELP info221 vdr2 closing connection...#/> svdrpsend plug satip list220 vdr2 SVDRP VideoDiskRecorder 2.1.5; Sun Mar 16 21:49:46 2014; UTF-8900 192.168.69.24:DVBS2-2:OctopusNet221 vdr2 closing connection


    Regards
    fnu

    HowTo: APT pinning

    Click for my gear

    [¹] Intel NUC Kit NUC7i5BNH, Akasa Newton S7, 8GB DDR4, WD Black SN700 500GB NVMe, Crucial MX500 2TB, CIR, SAT>IP, Ubuntu LTS 18.04.5, VDR 2.4.1 (15W)
    [²] Intel NUC Kit NUC7i3BNH, 8GB DDR4, WD PC SN520 250GB NVMe, Crucial MX500 1TB, CIR, SAT>IP, Ubuntu LTS 20.04.1, VDR 2.4.1 (13W)
    [³] BQ500, Asrock X470D4U, AMD Ryzen 5 5600, 32GB DDR4 ECC, 2x WDC SN750 512GB, 4x Samsung SSD 4TB, 1x Samsung SSD 8TB, 1x Crucial MX500 500GB, 1x WDC Blue SSD 500GB, Windows Server 2019 Hyper-V (35W)
    [⁴] Jultec JPS0501-12AN, JPS0501-8M2, Octopus Net (DVBS2-8) & openHABian 3.3.0

    Hi!

    Thank you, fnu.This shows me the following:

    Code
    svdrpsend PLUG satip list
220 raspberry-VDR SVDRP VideoDiskRecorder 2.1.4; Sun Mar 16 21:55:20 2014; UTF-8
900 192.168.13.29:DVBS2-4:GSSBOX-F005A4:SAT>IP
221 raspberry-VDR closing connection


    Regards

    Niel

    Client Wohnzimmer:
    RPi, VDR 2.1.6, rpihddevice, satip, remotetimers, osdteletext
    Client Schlafzimmer:
    zurzeit keiner
    VDR-Server:
    Epia 5000, 8 GB DOM, Skystar 2 HD, VDR 2.1.6, satip, svdrpservice
    (dient als Homeserver, macht auch noch andere Sachen, Zugriff auf 1TB NAS)
    Satip-Server:
    GSS.box DSI 400

    Quote from Niel

    The behaviour is the same. But i have seen, that the picture go away after a few seconds (blank screen) and come back about 2 seconds later. After about a minute the picture freezes and it is the same as before.


    No fixes in this area yet as I don't have yet a proper environment to debug it. That black screen effect sounds like a normal VDR behaviour while retuning due to pid changes.

    EDIT: You might want to try disabling PAT filter in the plugin's setup menu and check whether that helps on your problems.

    Edited once, last by rofafor (March 18, 2014 at 5:58 PM).

    rofafor:
    sorry, but back to sqaure one now with version 0.1.1:

    seems that refactoring broke the first fix...

    Edit: Sorry, Hope it's better now

    Edited once, last by clh27 (March 18, 2014 at 7:28 PM).

    Quote from mikelh

    seems that refactoring broke the first fix...


    Why do you have to post more than 300 Lines? They say all the same.

    Gerald


    HP Proliant MicroServer Gen8, Xeon E3-1230, 12 GB RAM, 3xWD red 2TB im RAID 5, 2xSundtek MediaTV Home DVB-C/T, L4M TWIN-C/T, Ubuntu Server 14.04.1, Plex Media Server
    Samsung UE55H6470

    Quote from gda

    Why do you have to post more than 300 Lines? They say all the same.

    Or, use at least:

    Code
    [spoiler]>>put in stuff here<<[/spoiler]


    Regards
    fnu

    HowTo: APT pinning

    Click for my gear

    [¹] Intel NUC Kit NUC7i5BNH, Akasa Newton S7, 8GB DDR4, WD Black SN700 500GB NVMe, Crucial MX500 2TB, CIR, SAT>IP, Ubuntu LTS 18.04.5, VDR 2.4.1 (15W)
    [²] Intel NUC Kit NUC7i3BNH, 8GB DDR4, WD PC SN520 250GB NVMe, Crucial MX500 1TB, CIR, SAT>IP, Ubuntu LTS 20.04.1, VDR 2.4.1 (13W)
    [³] BQ500, Asrock X470D4U, AMD Ryzen 5 5600, 32GB DDR4 ECC, 2x WDC SN750 512GB, 4x Samsung SSD 4TB, 1x Samsung SSD 8TB, 1x Crucial MX500 500GB, 1x WDC Blue SSD 500GB, Windows Server 2019 Hyper-V (35W)
    [⁴] Jultec JPS0501-12AN, JPS0501-8M2, Octopus Net (DVBS2-8) & openHABian 3.3.0

    A spoiler wouldn't help, as I was curious what the problem is about.
    Then I have to see >300 lines for an off by one error.

    Gerald


    HP Proliant MicroServer Gen8, Xeon E3-1230, 12 GB RAM, 3xWD red 2TB im RAID 5, 2xSundtek MediaTV Home DVB-C/T, L4M TWIN-C/T, Ubuntu Server 14.04.1, Plex Media Server
    Samsung UE55H6470

    Quote from mikelh

    seems that refactoring broke the first fix...


    Your log states it otherwise. The session header is now sent correctly, but your SAT>IP server is simply a broken one. It's replying to SETUP command by defining a session "d2ab1c18e1a2c30":

    Code
    < RTSP/1.0 200 OK
< Session:d2ab1c18e1a2c30;timeout=30
< com.ses.streamID:987

    Then I'm commanding PLAY with that session id:

    Code
    PLAY rtsp://192.168.1.138/stream=987 RTSP/1.0
CSeq: 3
Session: d2ab1c18e1a2c30


    But your device is responding with a another id:

    Code
    < RTSP/1.0 200 OK
< RTP-Info:url=rtsp://192.168.1.138/stream=987;seq=23781
* Got RTSP Session ID Line [2ab1c18e1a2c30
], but wanted ID [d2ab1c18e1a2c30]


    The first character of its' session id seems to be a bogus one. It seems that libcurl requires a whitespace after the ":" character and the first character gets eaten out. You could try to patch the libcurl instead:

    Code
    lib/rtsp.c:


    /* Find the first non-space letter */
-    start = header + 9;
+    start = header + 8;


    PS. I'd return the device back to the shop... ;)

    Edited 2 times, last by rofafor (March 18, 2014 at 8:26 PM).

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login