[vdr-plugin-satip] this and that

  • In my case it didn't help. My log looks good, so i dont know, what the problem is. Tried TS_SCRAMBLING_TIMEOUT 30.

    Dateien

    - Client1: Thermaltake DH 102 mit 7" TouchTFT * Debian Stretch/vdr-2.4.0/graphtft/MainMenuHooks-Patch * Zotac H55-ITX WiFi * Core i3 540 * 4GB RAM ** Zotac GT630 * 1 TB System HDD * 4 GB RAM * Harmony 900 * satip-Plugin

    - Client2: Alfawise H96 Pro Plus * KODI
    - Server: Intel Pentium G3220 * DH87RL * 16GB RAM * 4x4TB 3.5" WD RED + 1x500GB 2.5" * satip-Plugin
    - SAT>IP: Inverto iLNB

  • 3PO


    SAT>IP server doesn't answer properly, not protocol conform, and the plugin is obviously not able to handle this incomplete answer. Is the server "minisatip"?


    Regards
    fnu

    HowTo: APT pinning

  • I use always the newest git Revision.


    Code
    vdr01_64 satip # git log |head -n6
    commit 184ddf2a53c95b5ab084f4f34335000d691a1542
    Author: Rolf Ahrenberg <Rolf.Ahrenberg@sci.fi>
    Date:   Fri Jan 16 00:08:48 2015 +0200
    
    
        Fixed a wrong parameter type.
    
    
    vdr01_64 satip #
  • SAT>IP server doesn't answer properly, not protocol conform, and the plugin is obviously not able to handle this incomplete answer.


    Are you sure the description of the server is mandatory? I didn't find a hint in the SAT>IP spec.

    SAT Hardware: Gibertini SE75 | DuraSat Dur-Line UK-24 | DD OctopusNET V2 Rack (Firmware 1.1.6) mit MaxS8
    Server: Asus M5A78L-M/USB3 | Sempron 145@2Cores | 8GB ECC RAM | PicoPSU | Debian Stretch 64Bit | VDR 2.4.5 mit SAT>IP, epgsearch, live, markad
    Clients: RaspberryPI 2/3 | Yocto Poky Linux (Openembedded) 3.2+git | Linux Kernel 5.4.72 | VDR 2.4.5 mit SAT>IP, RpiHDDevice, SkinDesigner, Remote, Extrecmenu, Femon, Mlist


    R.I.P: Gigaset M740 mit VDR von open7x0.org

  • I have a question about the "-s" Parameter. Syntax is: <ipaddress>|<model>|<description>. Must the <description> fit to the UPnP friendly name and do you read his in the "server.c"? If i set it to "Triax SatIP Converter" in the log it only displays "Triax" and then the settings in the server.c may not apply.

    DVB Server Triax TSS400 SAT>IP Server
    VDR Server Synlogy Diskstation DS214play, debian chroot headless streaming Sever, VDR 2.1.7 mit vtuner/satip und vdr-plugin-satip
    VDR Client AMD X2 250, 4GB DDR3, G210 Passiv, 64GB SSD, Antec Fusion Micro iMON, Samsung LE 40 A659, Teufel E300, Logitech Harmony, yaVDR0.5 streamdev-client, (satip & USB DVBSKY S960 fallback)
    VDR Client Raspberry PI B+, raspian wheezy, VDR 2.1.6 mit RpiHDDevice, streamdev-client
    V/A Clients Windows PC's, Tablet, Smartphones via Streamdev or SatIP (UPNP)

  • If you want use any device specific quirks, you'll have to include the original friendly name in your description. Did you forgot to use a proper escaping for your server parameters?


    Code
    -P 'satip -d 4 -S -s \"192.168.0.9|DVBT2-1|OctopusNet;192.168.0.9|DVBS2-2|Triax SatIp Converter\"' "


    Code
    Jan 17 16:46:46 xxx vdr: [5228] SATIP: Adding server '192.168.0.9|DVBT2-1|OctopusNet #0'
    Jan 17 16:46:46 xxx vdr: [5228] SATIP: Adding server '192.168.0.9|DVBS2-2|Triax SatIp Converter #0'
  • If you want use any device specific quirks, you'll have to include the original friendly name in your description. Did you forgot to use a proper escaping for your server parameters?


    Code
    -P 'satip -d 4 -S -s \"192.168.0.9|DVBT2-1|OctopusNet;192.168.0.9|DVBS2-2|Triax SatIp Converter\"' "


    Code
    Jan 17 16:46:46 xxx vdr: [5228] SATIP: Adding server '192.168.0.9|DVBT2-1|OctopusNet #0'
    Jan 17 16:46:46 xxx vdr: [5228] SATIP: Adding server '192.168.0.9|DVBS2-2|Triax SatIp Converter #0'


    Added escaping, looks now better in in the logs. Don´t know if this realy has impact as it was running fine before, too.

    DVB Server Triax TSS400 SAT>IP Server
    VDR Server Synlogy Diskstation DS214play, debian chroot headless streaming Sever, VDR 2.1.7 mit vtuner/satip und vdr-plugin-satip
    VDR Client AMD X2 250, 4GB DDR3, G210 Passiv, 64GB SSD, Antec Fusion Micro iMON, Samsung LE 40 A659, Teufel E300, Logitech Harmony, yaVDR0.5 streamdev-client, (satip & USB DVBSKY S960 fallback)
    VDR Client Raspberry PI B+, raspian wheezy, VDR 2.1.6 mit RpiHDDevice, streamdev-client
    V/A Clients Windows PC's, Tablet, Smartphones via Streamdev or SatIP (UPNP)

  • Could someone using Inverto OEM using firmware V1.17.0.120 test whether the model quirks are really required anymore? There's a new command-line switch (-n) to disable the predefined server quirks in the GIT version.


    I tried -n switch with my Digitbit (1.17.0.120) device and it seems that all is still working.

    SAT Hardware: Gibertini SE75 | DuraSat Dur-Line UK-24 | DD OctopusNET V2 Rack (Firmware 1.1.6) mit MaxS8
    Server: Asus M5A78L-M/USB3 | Sempron 145@2Cores | 8GB ECC RAM | PicoPSU | Debian Stretch 64Bit | VDR 2.4.5 mit SAT>IP, epgsearch, live, markad
    Clients: RaspberryPI 2/3 | Yocto Poky Linux (Openembedded) 3.2+git | Linux Kernel 5.4.72 | VDR 2.4.5 mit SAT>IP, RpiHDDevice, SkinDesigner, Remote, Extrecmenu, Femon, Mlist


    R.I.P: Gigaset M740 mit VDR von open7x0.org

  • I've tested on my server machine again with -d4 -n switches on vdr-2.1.7. FTA channels no problem at all.


    Recording 3 encrypted channels and watching one FTA channel at the same time works as expected.


    Encrypted channels over streamdev works, if i open a channel twice.


    I patched my VDR with


    Code
    #define PMT_SCAN_TIMEOUT  2000
    and
    #define TS_SCRAMBLING_TIMEOUT    30


    Don't know, if it is really needed.


    Will test later on my LiveTV machine.


    EDIT:
    On my LiveTV machine with the same settings for timeouts everything works fine. I made a quick test. In the evening i will do more tests to see, that everything works as expected.

    - Client1: Thermaltake DH 102 mit 7" TouchTFT * Debian Stretch/vdr-2.4.0/graphtft/MainMenuHooks-Patch * Zotac H55-ITX WiFi * Core i3 540 * 4GB RAM ** Zotac GT630 * 1 TB System HDD * 4 GB RAM * Harmony 900 * satip-Plugin

    - Client2: Alfawise H96 Pro Plus * KODI
    - Server: Intel Pentium G3220 * DH87RL * 16GB RAM * 4x4TB 3.5" WD RED + 1x500GB 2.5" * satip-Plugin
    - SAT>IP: Inverto iLNB

    2 Mal editiert, zuletzt von TheChief ()

  • Guys, this sounds really great! Could you run the plugin for a week or something with the "-n" switch and report any oddities you'll notice?
    Can you also provide the latest XML the device provides as I'd like to see whether I can spot the running (read: fixed) firmware somehow.

  • Maybe it has also something to do with the latest changes in vdr-2.1.7. There were some changes in CAM-Handling i think. I will continue testing. :) Thank you for your work.


    Attached my desc.xml.

    Dateien

    - Client1: Thermaltake DH 102 mit 7" TouchTFT * Debian Stretch/vdr-2.4.0/graphtft/MainMenuHooks-Patch * Zotac H55-ITX WiFi * Core i3 540 * 4GB RAM ** Zotac GT630 * 1 TB System HDD * 4 GB RAM * Harmony 900 * satip-Plugin

    - Client2: Alfawise H96 Pro Plus * KODI
    - Server: Intel Pentium G3220 * DH87RL * 16GB RAM * 4x4TB 3.5" WD RED + 1x500GB 2.5" * satip-Plugin
    - SAT>IP: Inverto iLNB

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!