Tuner Sharing not working

I noticed tuner Sharing is not working unless all my Clients have the same source priority.

2020/10/11 16:26:44.954078 [TNR] Opened connection to 107829D3/0 for ch6.1 KOIN-HD [transcode=none]
2020/10/11 16:27:01.282212 [SNR] Statistics for ch6.1 KOIN-HD: ss=93%,87%-97% snq=99%,97%-100% seq=100% bps=10342349,582048-14928704 pps=982,55-1418
2020/10/11 16:27:01.282212 [TNR] Closed connection to 152035B1/0 for ch6.1 KOIN-HD
2020/10/11 16:27:01.282212 [HTTP] | 200 | 46m49s | 10.0.0.135 | GET "/devices/152035B1/channels/6.1/stream.mpg?transcode=none&codec=copy"
2020/10/11 16:27:01.636921 [HTTP] | 200 | 47m5s | 10.0.0.135 | GET "/dvr/events/subscribe"
2020/10/11 16:27:03.950805 [TNR] Opened connection to 152035B1/0 for ch6.1 KOIN-HD [transcode=none]
2020/10/11 16:27:05.856784 [SNR] Statistics for ch6.1 KOIN-HD: ss=94% snq=100% seq=100% bps=2776384 pps=263

While this sounds like a bug, I think this is how it works. The client makes a request using a particular source, and the DVR will see if it has that source/channel combination already open. If the client requests a different source from the existing connection, then the DVR will do as asked.

While not necessarily the expected behavior, I believe this is working properly. (I think when DVR/client/tuner syncing of priorities/favorites eventually comes, this situation will be more easily avoided.)

It was working before regardless of Priority when viewing locally ... it was not working if using a remote connection unless they had the same source priority.

This is not good .... using additional tuners not a problem in EMBY or SageTV.

020/10/11 16:55:49.414746 [TNR] Opened connection to 107829D3/0 for ch8.1 KGW [transcode=none]
2020/10/11 16:56:00.855443 [HTTP] | 200 | 993.8µs | 10.0.0.135 | GET "/status"
2020/10/11 16:56:00.999068 [HTTP] | 200 | 964.3µs | 10.0.0.135 | GET "/status"
2020/10/11 16:56:01.016957 [HTTP] | 200 | 997.5µs | 10.0.0.135 | GET "/auth"
2020/10/11 16:56:01.084232 [HTTP] | 200 | 9.0005ms | 10.0.0.135 | GET "/devices"
2020/10/11 16:56:01.088221 [HTTP] | 200 | 0s | 10.0.0.135 | GET "/dvr"
2020/10/11 16:56:01.114133 [HTTP] | 200 | 5.9933ms | 10.0.0.135 | GET "/dvr/programs"
2020/10/11 16:56:01.125093 [HTTP] | 200 | 28.9229ms | 10.0.0.135 | GET "/dvr/groups"
2020/10/11 16:56:01.184933 [HTTP] | 200 | 87.7658ms | 10.0.0.135 | GET "/dvr/rules"
2020/10/11 16:56:01.193909 [HTTP] | 200 | 106.7072ms | 10.0.0.135 | GET "/dvr/jobs"
2020/10/11 16:56:01.304613 [HTTP] | 200 | 175.5291ms | 10.0.0.135 | GET "/dvr/files?deleted=true"
2020/10/11 16:56:01.382405 [HTTP] | 200 | 294.1842ms | 10.0.0.135 | GET "/dvr/files"
2020/10/11 16:56:01.491144 [HTTP] | 200 | 187.528ms | 10.0.0.135 | GET "/devices/ANY/guide?time=1602460562&duration=14400"
2020/10/11 16:56:05.081998 [HTTP] | 200 | 145.5829ms | 10.0.0.135 | GET "/dvr/recordings/upnext"
2020/10/11 16:56:05.368982 [HTTP] | 200 | 191.031ms | 10.0.0.135 | GET "/devices/ANY/guide?time=1602460566&duration=14400"
2020/10/11 16:56:21.608168 [TNR] Opened connection to 152035B1/0 for ch8.1 KGW [transcode=none]

I thought I had remembered something of this from about a year ago. Originally I was going to mention that, and that this was probably a regression. I never saw the behavior locally, as I always have the clients with the same priority.

Sorry for the noise.

No problem your input is always appreciated ... I have 3 devices ready for the Seattle game and noticed they are all using different tuner devices. So I have to go and set the tuner priorities the same.

the 3rd device
2020/10/11 17:08:28.648779 [TNR] Opened connection to 10701381/0 for ch8.1 KGW [transcode=none]

What kind of clients?

FireTV ... Android Phone and FireTV Tablet.

Setting Same priority on all Clients .....

2020/10/11 17:20:39.838160 [TNR] Sharing existing connection to 152035B1/0 for ch8.1 KGW (clients=3, len=0, transcode=none)