Returncode 404 from minisatip is not handled about vdr-plugin-satip HOT 6 CLOSED

As I need bonding for my satellite installation I will eventually do it myself. I will send you a diff if ready.
It will take some time as I will go on vacation soon :-)

from vdr-plugin-satip.

IIRC, this would required tuning code operating in a blocking mode making VDR much less responsive.

from vdr-plugin-satip.

Well, a frozen screen is not much responsive ether :-)
Is there any other solution possible ? The vdr itself does check if a transponder is tunable befor switching to it. But with satip it seems more difficult.
Also satip does not honor shared LNBs and vdr checks it only for build in tuners. I agree the the satip server should do it, but if you do not wait for the tuning answer maybe satip could do it before trying to tune. So I do not need to tell minisatip that it has shared LNBs, but satip takes care of it. It is anyway configured in vdr LNB setup.

Looking in your sources I think that the plugin has a general problem with failed tuning. It only infinite repeats to try to access the tuner/minisatip without an exit strategy. Having looked into the vdr sources it seems that it is also difficult to tell vdr that tuning is not possible. The return code for SetChannelDevice is not used anymore to stop the tuning at all. Even as you do a timeout there to get the tuning result. But you do not handle it in SetChannelDevice.

So error handling with devices handled by plugins seems to be difficult at least.

from vdr-plugin-satip.

After further investigating the issue I come to the conclusion that the plugin should handle bonded devices. This is missing in device.c and it is available in the vdr device handling. That way all the handling of non tunable return codes would be obsolete.

from vdr-plugin-satip.

The frozen picture is nothing when you're zapping with channel up and every zap takes seconds before proceeding the next channel with an outdated channels.conf. :)

Anyway, bonded devices were introduced later than this plugin and documentation states: May be dropped in a future version, if a better solution is found. Do not use otherwise!. The plugin has been developed for DVB-T/C only and all the satellite stuff just happens to work somehow at some level. I never had any satellite hardware to test it and I don't even have any working VDR setup right now. Contributions are more than welcome!

IMO, retrying is better than any exit strategy because we're talking about network devices having networking issues here.

from vdr-plugin-satip.

I switched to unicable and do not need bonding anymore :-)

from vdr-plugin-satip.