fe=x issue

[9000h]

my command line is

-H3:50 -D5  -o 192.168.178.129:2000  -Y 4:dvbt2,5:dvbt2,6:dvbc2,7:dvbc2  -u 0:4-984[-48],1:5-1020[-23],2:6-1056[-88],3:7-1092[-204] -m 0040caa2c7ff  -s dvbc:192.168.178.1 -s dvbc:192.168.178.1 

status shows

when I use for dvbc the fe=x param like

mpv "http://127.0.0.1:8080/?fe=6&freq=434&bw=8&msys=dvbc&sr=6900&&mtype=256qam&specinv=1&pids=0,16,17,18,20,104,6881,6882,6883,6889"

then tuner 9 from webinterface status is in use
when fe=5 is used the tuner 8 is in use
when fe=4 is used I get a 404 back

so I think there is still a issue with fe=x
should the fe count not per delsys?

[catalinii]

There is a mapping between the fe=X to the actual adapters. The purpose is to have all the adapters mapped totether considering their delivery system. See fe_map in adapter.c

[lars18th]

Hi @9000h ,

Just one comment about the &fe= parameter:

• From the standard specification this value should not be used in a request from clients. This has only sense when using administration tools. For example, for setting one tuner to stream continously a multicast stream. It's the responsibility of the server to select the correct tuner.

Please, check that in the table inside the section "3.5.11 Query Syntax", page 43. It's writed in red: "Not required in normal client queries".
http://www.satip.info/sites/satip/files/resource/satip_specification_version_1_2_2.pdf

It's a common mistake of many client implementations to use this parameter. However, it should never be used.

Regards.

[catalinii]

Closing as no activity.