Flole Systems wrote:
> What are you talking about? Why would the latest version only work if it supports that? Just because an option is there it doesn't mean you need to enable it.
Hä ? You wrote: "Use latest Tvheadend and not some old version and don't enable that RTP/AVP/TCP option, your server most likely doesn't support it and it won't work."
O.K: so I use the latest tvh ; and I will not enable THE Option then your guess is: the SAT-IP Server does not support it and it will not work.
Or stripped down: don't enable the option and it won't work. Tertium non datur: it will only work if the option is set.
Or did you forget a "because" ?
> You're trying to come up with weird scenarios (that mostly consist of incorrect settings) right now and then complain about issues. Obviously if you specify wrong settings for the server you're trying to connect to it won't work, that shouldn't be surprising at all.
Wired szenarios ? tvh in front of an SAT-IP server is a weired szenario ? I don't think so. It's natural that in the first try a SAT-IP Server is not configured proberly. So it is straightforward to check that it responds as expected.
Instead it turns out that tvh 4.2.8 seems to work out-of-the-box if the SAT-IP Server is reachable. No need for special or magical setings. Or short: if Saen had shut up, then threadstarter would not focus on this option and there would be no problem at all.
> Also if you don't have the "disable firmware/device specific workarounds" option set part of your settings could be overridden automatically, then you can specify whatever your want and that option fixes those.
There is no documentation for this option at all - so I cannot comment on this point.
<<