Tvheadend

It appears that the string in the SAT>IP XML description file describing the tuners is wrong from DVBViewer. TVH honors the order in the <urn:ses-com:satipX_SATIPCAP> xml tag (the description XML file). Could you check? This is only place where the tuners are described from the server.

Ah, just read a little more at http://www.satip.info/sites/satip/files/resource/satip_specification_version_1_2_2.pdf and I now see the numbers after each type in that tag indicate how many tuners are available, so zero DVBS2 tuners, zero DVBT, two DVBT2 and one DVBC, which is correct.

However, in that spec I can't see where it says the order is mandatory to match the host tuners, so is it incorrect that TVH should assume this is the correct order and the 'fe=x' param should match? Would it be better to omit the 'fe=' param completely and let the host choose what tuner to use?

Yes, the whole problem is that the spec does not handle the situation where the server uses multiple tuners with different types. The one way is to use the order from server (PnP) like tvh does by default. I don't see any other way to do it. Avoiding fe argument is not a right solution, because TVH must address the specific tuners (for example different DiseqC setup for DVB-S per tuner).

But the good thing is that you may override the reply from server in tvh - see "Tuner configuration" field - use 'DVBC-1,DVB-T2-2' for your setup (you should write string manually to the combobox field).

Yes, that works! Actually, a slight typo - it should be DVBC-1,DVBT2-2 (not DVB-T2-2) but I got the idea :)

Thanks for all your help.

Sorry about this typo. You may discuss with the dvbviewer developer to return the correct tuner order for the PnP configuration.

Jaroslav Kysela wrote:

Yes, the whole problem is that the spec does not handle the situation where the server uses multiple tuners with different types. The one way is to use the order from server (PnP) like tvh does by default. I don't see any other way to do it. Avoiding fe argument is not a right solution, because TVH must address the specific tuners (for example different DiseqC setup for DVB-S per tuner).

But the good thing is that you may override the reply from server in tvh - see "Tuner configuration" field - use 'DVBC-1,DVB-T2-2' for your setup (you should write string manually to the combobox field).

Hi!
Is there any way to solve the problem?
As it is said on DVBViewer site:
"That's just a questionable work-around. It must be considered that the RS handles request -> tuner assignnments dynamically. If you have two DVB-T tuners and the first one is occupied by a recording or another streaming client, the RS will automatically use the second one. This feature is spoiled by using the fe parameter unnecessarily. And it spoils similar features in other Sat>IP servers as well. If the RS has started a DVB-T recording, it will reject TVH as client, because it stubbornly insists on a particular tuner that is occupied."

https://www.dvbviewer.tv/forum/topic/58808-cannot-connect-to-rs-using-satip/

Plus
Where is ""Tuner configuration" field" to be overwritten in TVH 4.3.*?

Disable "FE supported" in the SAT>IP server configuration (input adapter tree - the root for the SAT>IP server - the "Tuner configuration" item is there also).

Jaroslav Kysela wrote:

Disable "FE supported" in the SAT>IP server configuration (input adapter tree - the root for the SAT>IP server - the "Tuner configuration" item is there also).

Thanks a lot.
I did it in the root, but anyway get errors:
2019-01-07 14:20:14.586 mpegts: 192.168.1.139 in IPTV Automatic Network - tuning on IPTV #1
2019-01-07 14:20:14.586 iptv: 192.168.1.139 in IPTV Automatic Network - unsupported scheme [none]
2019-01-07 14:20:15.555 http: 192.168.1.139: HTTP/1.1 POST (3) /api/mpegts/input/network_list -- 400
2019-01-07 14:20:15.602 http: 192.168.1.139: HTTP/1.1 POST (3) /api/mpegts/input/network_list -- 400

Maybe I missed some options, when tuning TVH as a client of DVBViewer RS

IPTV errors are not related to SAT>IP at all.

Jaroslav Kysela wrote:

IPTV errors are not related to SAT>IP at all.

Looked hrough the optionns.
Now it works.
But TVH always crushes DVBViewer RS

Bind address is wrong.

Flole Systems wrote:

Bind address is wrong.

In screenshots 192.168.1.139:554 is the right address in DVBViewer configuration

Please read documentation about that parameter again, this is not the Sat-IP server IP. In this case you most likely want to leave it empty anyways.

Flole Systems wrote:

Please read documentation about that parameter again, this is not the Sat-IP server IP. In this case you most likely want to leave it empty anyways.

Thanks.
I wouldn't say that documentation is overwhelming:
"Local bind IP address : Bind to specific local IP address."

Moreover, the read-only part says, that "IP address: = 192.168.1.139"

Anyway, leaving the field blank solves the binding problem.
But all the time tuners try to scan I get something like this:
"mpegts: 10979V in 19 - scan no data, failed"

Am I right configuring networks, as listed above?

OK, TVH seems to be unborn to work as a SAT>IP client and cannot work with CIs https://tvheadend.org/boards/4/topics/37353
Welcome dammned Windoes

OK, TVH seems to be unborn to work as a SAT>IP client and cannot work with CIs https://tvheadend.org/boards/4/topics/37353
Welcome dammned Windows

To me this looks like you're just messing around with parameters that you don't understand. Start over, understand what each parameter means and set it accordingly, then you can get it to work with almost every SAT-IP Server.

Flole Systems wrote:

To me this looks like you're just messing around with parameters that you don't understand. Start over, understand what each parameter means and set it accordingly, then you can get it to work with almost every SAT-IP Server.

For me the manuals are in a raw state, sorry