vdr-plugin-satip nicht alle Sender haben ein Bild (Kathrein ExIP 414/E)

    Da die Hardware ja scheinbar einwandfrei funktioniert und hier rein ein Klient Problem vor liegt (vdr-satip Plugin) versehe ich nicht ganz warum man jetzt auf andere HW setzen sollte anstatt einfach bei rofafors github ein issue auf machen mit den angeforderten Logs.


    Quote from fnu

    vdr-plugin-satip greift recht massiv per rtsp auf die Server zu, nur so können alle gewohnte VDR Features genutzt werden, und das müssen die ab können. Digibit R1 und Verwandten geht z.B. dabei mit der orig. FW "die Puste aus", HW zu schwach dimensioniert


    Ist das auch heute noch so oder war das mit der alten verbuggten Firmware? Mir wären noch nicht mal vom Hörensagen irgendwelche Probleme bekannt in der Richtung seitdem es das offizielle Update gab (bei normaler Nutzung).

    Code
    a=fmtp:33 ver=1.0;src=1;tuner=1,0,0,0,11493.00,h,dvbs2,8psk,off,0.35,22000,23;pids=0,16,17,18,20,5101,5102,5103,5105,5106


a=fmtp:33 ver=<major>.<minor>;src=<srcID>;tuner=<feID>,<level>,<lock>,<quality>,<frequency>,<polarisation>,<system>,<type>,<pilots>,<roll_off>,<symbol_rate>,<fec_inner>;pids=<pid0>,…,<pidn>


    As I suspected the server doesn't get a lock, that's a requirement for informing VDR core to proceed. Now, if the server works with DVBViewer as client, you'll need to verify whether it really has got a lock (RTCP packet or DESCRIBE response). If yes, the current 2 seconds tuning timeout in the satip plugin might be a too short and you could try out a higher one.


    One RTP error per channel change is normal, but any higher number indicates performance problems somewhere in your SAT>IP chain (client-network-server).

    Quote

    Und hast Du irgendwas hilfreiches zu SAT>IP in den letzten 2-3 Jahren beigetragen?

    Nein, das habe ich nicht, aber ich werde daran arbeiten. Aber ich denke, dass ich hier zur Analyse dieses Problems eine Kleinigkeit beitrage und damit vielleicht auch weitere Verwender unterstütze. Und ich habe nun gelernt, dass ich nicht-lösungsorientierte Antworten in Zukunft einfach ignoriere. Ich kanns aber nicht versprechen ?(


    Deine Antwort und Dein Exkurs zu den SAT>IP-Clients waren allerdings äußerst hilfreich für mich. Vielen Dank dafür! :]

    yavdr 0.6.1 auf Zotac ZBox ID41, Kathrein ExIP 414E, Raspberry Pi mit OpenELEC

    Quote

    One RTP error per channel change is normal, but any higher number indicates performance problems somewhere in your SAT>IP chain (client-network-server).


    Thanks a lot rofafor!

    There're two Gigabit switches in between. I've removed one of them but the problem persits. If it would be helpful I could connect the VDR directly to the SAT>IP server.


    In the client's web frontend I see that the connected tuner indicates "playing" but gets no lock in case of non-working channels. All other channels and each channel with DVBViewer get a lock.

    yavdr 0.6.1 auf Zotac ZBox ID41, Kathrein ExIP 414E, Raspberry Pi mit OpenELEC

    Quote from CvH

    Ist das auch heute noch so oder war das mit der alten verbuggten Firmware?

    Ich denke ich beziehe mich da auf Firmwarestände die vor einiger Zeit einfach unbrauchbar waren. Wenn es inzwischen eine offizielle FW gibt die funktioniert, umso besser. Dennoch ist das Referenzdesign von Digitbit und Verwandten recht schmal ausgelegt. Man hat es ja gesehen, ein oder mehrere Fehler in der SAT>IP Server Software und schon ist der Betrieb schwierig bis unmöglich. Software ist Software und wird prinzipbedingt immer Fehler haben.


    Man wird sehen wie die Kistchen dann mal mit den deutlich erhöhten Anforderungen der UHD Transponder klar kommen ...


    Quote from SiKr

    If it would be helpful I could connect the VDR directly to the SAT>IP server.

    Yes, please do so. Steps like this are normal to isolate or to exclude error causes.


    Network can be critical for SAT>IP, using a(ny) ethernet switch might not guarantee that is does work porperly. I don't say it will not work, e.g. do I have 3 hops in between my VDRs and the Octopus Net. Just proof if your switches do influence SAT>IP operation.


    So, is there a menu option on this SAT>IP server for network settings? If yes, which ones and how do they look like?


    Regards
    fnu

    HowTo: APT pinning

    Quote from SiKr

    There're two Gigabit switches in between. I've removed one of them but the problem persits. If it would be helpful I could connect the VDR directly to the SAT>IP server.


    Those RTP errors are just annoyances: you'll just see some minor picture/sound distortions. Enabling TCP communication instead of default UDP might fix problems.


    Quote from SiKr

    In the client's web frontend I see that the connected tuner indicates "playing" but gets no lock in case of non-working channels. All other channels and each channel with DVBViewer get a lock.


    Can you provide similar RT(S/C)P statistics from DVBViewer? Your channels.conf entry might also be broken as VDR loves DVB API's autoconfiguration that's missing from SAT>IP specs. DVBViewer channels.dat or network captures its's SETUP commands would help a lot.

    Das ist super.


    Aber ich präzisiere, man wird sehen wie Digitbit R1 mit den erhöhten Anforderung der UHD Transponder klar kommt, wenn ein oder mehrere VDR mal massiv darauf zugreifen, z.B. mit mehrfach parallelen Aufnahmen etc. Wir sind hier ja im VDR Portal und nicht im Panasonic Portal ... :rolleyes:


    Regards
    fnu

    HowTo: APT pinning

    Edited once, last by fnu ().

    Hi rofafor,

    Quote

    Those RTP errors are just annoyances: you'll just see some minor picture/sound distortions.

    So I don't need to care about any network devices?


    Quote

    Enabling TCP communication instead of default UDP might fix problems.

    UseRtpOverTcp? I've vdr-plugin-satip 2.2.3 which doesn't seem to have such an option. I saw that UseRtpOverTcp was commited in June. Do I have to build the plugin or can it just be updated?


    Quote

    Can you provide similar RT(S/C)P statistics from DVBViewer?

    I can't find any logs/statistics from DVBViewer at all. I'm using the Lite version. I found that there's a trial version of DVBViewer Pro which might support debug/log. I'm working on it.



    Quote

    Your channels.conf entry might also be broken as VDR loves DVB API's autoconfiguration that's missing from SAT>IP specs.

    The entries are from the channelpedia, here's one of the failing channels:

    Code
    Das Erste HD;ARD:11493:HC23M5O35P0S1:S19.2E:22000:5101=27:5102=deu@3,5103=mis@3;5106=deu@106:5104;5105=deu:0:10301:1:1019:0


    Quote

    DVBViewer channels.dat

    Attached (from the lite version)


    Quote

    Network captures its's SETUP commands would help a lot.

    Do you mean TCPDUMP? What exactly and how much?


    Cheers,
    SiKr

    Hi rofafor,



    here's the Wireshark output for DVBViewer on Windows starting and playing "Das Erste HD" which is not working on VDR. I exited DVBViewer after ~6 seconds. I hope it's sufficient and in the correct format. Let me know if anything is missing/wrong.


    I also made a tcpdump on the VDR and saw that in comparison DVBViewer has two additional parameters in the SETUP command: plts=on and pids=0. Does this mean anything?


    Cheers,
    SiKr

    The capture is great, thanks! I noticed that DVBViewer is using frequency 11494 MHz instead of VDR's 11493 MHz. Please, check whether this small change makes any difference. Also DVBVIewer is setting the pilot tones on, but VDR's channels.conf entry doesn't have any definition for it. Set it on by adding 'N1' parameter string or via VDR's channel editor.

    Quote

    I noticed that DVBViewer is using frequency 11494 MHz instead of VDR's 11493 MHz

    Yes, I saw this too and changed the channels.conf accordingly but it doesn't made a difference.


    Quote

    Also VDR is setting the pilot tones on and DVBViewer is not defining it at all, so you might test toggling it off (the parameter 'N0' in channels.conf or more easily via VDR's channel editor).


    Pilot tones is "plts", right? I saw this parameter in the DVBViewers SETUP command (plts=on) but NOT with tcpdump on the VDR. There's no such "N0" in the channels.conf (taken from channelpedia). Should I add it and if, where?


    Here's my channels.conf entry for "Das Erste HD":

    Code
    Das Erste HD;ARD:11493:HC23M5O35P0S1:S19.2E:22000:5101=27:5102=deu@3,5103=mis@3;5106=deu@106:5104;5105=deu:0:10301:1:1019:0

    yavdr 0.6.1 auf Zotac ZBox ID41, Kathrein ExIP 414E, Raspberry Pi mit OpenELEC

    Quote from SiKr

    Pilot tones is "plts", right? I saw this parameter in the DVBViewers SETUP command (plts=on) but NOT with tcpdump on the VDR. There's no such "N0" in the channels.conf (taken from channelpedia). Should I add it and if, where?


    VDR is using 'auto' setting for the parameter by default and that translates into 'off' in the plugin as the specs advises to set this DVB-S2 parameters always off for DVB-S. If you want modify manually the channels.conf, take a look at the manual pages: man 5 vdr. Otherwise, just select "Main Menu -> Channels -> Edit" and set parameters as required.

    That channel is DVB-S2, translating Pilot=auto in VDR (let the hardware choose) into Pilot=off in Plugin for that channel doesnt make sense.
    But the spec misses 'auto' setting.


    On the other hand, VDR itself cannot read this from NIT and add it to channels.conf, as Pilot property isnt transmitted in NIT at all. And
    manual changes of that channel would be overidden by vdrs next automatic update of channels.conf.


    Two possible solutions:
    a) What about a default for pilot settable inside the plugin?
    b) for DVBS: specify as 'off' <-> for DVBS2: try one setting, if it fails after timeout retry the opposite ( order configured by a) )



    btw it's likely in use only at high symbolrates or modulation different from qpsk.

    Well, the Pilot should already be always off for all DVB-S channels, but finding a sane default auto value for DVB-S2 channels is another thing. Setting it to off seems to be working quite well as only a few channels are non-accessible. Re-tuning with toggled value isn't a viable solution either due to long timeouts - you wouldn't want to wait for 20s for zapping. The real fix to modify core VDR in a such way, that any NIT change wouldn't overwrite the Pilot value and setting it correctly once would be enough.

    Quote from rofafor

    Well, the Pilot should already be always off for all DVB-S channels


    Correct.


    Quote

    but finding a sane default auto value for DVB-S2 channels is another thing. Setting it to off seems to be working quite well as only a few channels are non-accessible. Re-tuning with toggled value isn't a viable solution either due to long timeouts


    Why at all a long timeout? Short should be enough. Some windows BDA dvb drivers do that.


    Quote

    ]The real fix to modify core VDR in a such way, that any NIT change wouldn't overwrite the Pilot value and setting it correctly once would be enough.


    But that solution requires users to edit each single channel that is not tuning by hand. Really..?

Participate now!

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

Register Yourself Login