You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Rolf,
since the satip-axe firmware on my Grundig GSS400 box always had issues after switching channels (streaming stopped) I've done some testing yesterday and fortunately perexg was able to fix it (please have a look at the comments made yesterday in this thread: perexg/satip-axe#108).
His latest release is a great improvement and stable so far (my VDR recorded permanently last night on different channels and I haven't had any new error!), but it may be helpful to have a look at a special behaviour.
In some situations the VDR satip plugin seems to send the PID 65535/-1 to the satip server what per se from my point of view is implausible:
[17/10 12:07:23.999 main]: PLAY rtsp://192.168.0.141/stream=3?addpids=65535 RTSP/1.0
perexg's comment is more direct ;-) and he asked me to open an issue for vdr-plugin-satip.
You can find additional information and my logs in the issue thread mentioned above. Please let me know if you need further information!
Thanks for your effort!
Klaus
The text was updated successfully, but these errors were encountered:
Well, the satip plugin is just relaying pids and these odd pids are usually used for cicam sections. Yes, I could filter out any pid over 8191, if the SAT>IP server doesn't support X_PMT extensions.
I'm only using FTA television (mainly german) and as far as I understand CICAM isn't necessary for these stations. Furthermore I thought that 65535 is -1 in 2-complement number representation and not a pid value which would be used by any station.
Filtering pids would great, maybe implemented via an additional parameter "pid_upper_bound"!?
Hi Rolf,
since the satip-axe firmware on my Grundig GSS400 box always had issues after switching channels (streaming stopped) I've done some testing yesterday and fortunately perexg was able to fix it (please have a look at the comments made yesterday in this thread: perexg/satip-axe#108).
His latest release is a great improvement and stable so far (my VDR recorded permanently last night on different channels and I haven't had any new error!), but it may be helpful to have a look at a special behaviour.
In some situations the VDR satip plugin seems to send the PID 65535/-1 to the satip server what per se from my point of view is implausible:
perexg's comment is more direct ;-) and he asked me to open an issue for vdr-plugin-satip.
You can find additional information and my logs in the issue thread mentioned above. Please let me know if you need further information!
Thanks for your effort!
Klaus
The text was updated successfully, but these errors were encountered: