[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

  • still no success wtih satip-0.1.0 and Triax TSS400.

    Digibit R1 mit minisatip-axe : VDR 2.2.3 im docker container auf DS415+ (8GB RAM, 12TB Raid5) : Kodi 15.2 auf MacMini (2009) (8GB, Mavericks) : Kodi 15.2, 16rc3 auf MacBookPro retina (2012) (16GB, El Capitan) : ATV 1. Gen. : R-PI2 (OpenElec 6): DragonBoard 410 (Jessie) :

  • Hi!


    Same behaviour as before. A new log is attached.


    Niel

    Dateien

    • vdr.log.txt

      (55,51 kB, 75 Mal heruntergeladen, zuletzt: )

    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

    Digibit R1 mit minisatip-axe : VDR 2.2.3 im docker container auf DS415+ (8GB RAM, 12TB Raid5) : Kodi 15.2 auf MacMini (2009) (8GB, Mavericks) : Kodi 15.2, 16rc3 auf MacBookPro retina (2012) (16GB, El Capitan) : ATV 1. Gen. : R-PI2 (OpenElec 6): DragonBoard 410 (Jessie) :

  • 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
    1. CURLOPT_RTSP_SESSION_ID
    2. 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.
    3. 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.
    4. 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

  • How else can i verify it?

    Maybe due reading some help, e.g:


    Code
    1. #/> 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

  • Hi!


    Thank you, fnu.This shows me the following:


    Code
    1. svdrpsend PLUG satip list
    2. 220 raspberry-VDR SVDRP VideoDiskRecorder 2.1.4; Sun Mar 16 21:55:20 2014; UTF-8
    3. 900 192.168.13.29:DVBS2-4:GSSBOX-F005A4:SAT>IP
    4. 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

  • 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.

  • rofafor :
    thanks for the update. Unfortunately I'm travelling right now and the next days having no
    access to my sytems. I'll try it after my return and give feedback ASAP.

    Digibit R1 mit minisatip-axe : VDR 2.2.3 im docker container auf DS415+ (8GB RAM, 12TB Raid5) : Kodi 15.2 auf MacMini (2009) (8GB, Mavericks) : Kodi 15.2, 16rc3 auf MacBookPro retina (2012) (16GB, El Capitan) : ATV 1. Gen. : R-PI2 (OpenElec 6): DragonBoard 410 (Jessie) :

  • 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

    Digibit R1 mit minisatip-axe : VDR 2.2.3 im docker container auf DS415+ (8GB RAM, 12TB Raid5) : Kodi 15.2 auf MacMini (2009) (8GB, Mavericks) : Kodi 15.2, 16rc3 auf MacBookPro retina (2012) (16GB, El Capitan) : ATV 1. Gen. : R-PI2 (OpenElec 6): DragonBoard 410 (Jessie) :

    Dieser Beitrag wurde bereits 1 Mal editiert, zuletzt von mikelh ()

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

    Or, use at least:


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


    Regards
    fnu

    HowTo: APT pinning

  • 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

  • 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
    1. < RTSP/1.0 200 OK
    2. < Session:d2ab1c18e1a2c30;timeout=30
    3. < com.ses.streamID:987


    Then I'm commanding PLAY with that session id:

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


    But your device is responding with a another id:

    Code
    1. < RTSP/1.0 200 OK
    2. < RTP-Info:url=rtsp://192.168.1.138/stream=987;seq=23781
    3. * Got RTSP Session ID Line [2ab1c18e1a2c30
    4. ], 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
    1. lib/rtsp.c:
    2. /* Find the first non-space letter */
    3. - start = header + 9;
    4. + start = header + 8;


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