Tuner Sharing Still a Problem

I appreciate all the features and Settings but I have posted about this in the past ... unless you have the same tuner order on the Server and the client tuner sharing does not work. This is really a problem wasting tuners when tuner sharing is turned on ... on all clients. Every Client has tuner sharing on but unless I go around setting all clients to the same tuner order it is useless.

2021/04/13 09:12:42.138139 [TNR] Opened connection to 152035B1/1 for ch2.1 KATU [transcode=none]
2021/04/13 09:13:09.824200 [TNR] Opened connection to 107829D3/0 for ch2.1 KATU [transcode=none]

021/04/13 08:44:37.115714 [TNR] Opened connection to 131A192A/0 for ch744 CNNHD [transcode=none]
2021/04/13 08:44:54.738786 [TNR] Opened connection to 13147C7B/0 for ch744 CNNHD [transcode=none]

1 Like

Is this on Apple or Android clients?

Android ... I have multiple HDHomeRun tuners and Primes ... So each Client starts initial startup with different tuner priorities. The only way to make sure tuners are shared is to have each client with the exact same tuner priority.

Tuner Sharing not working - Channels DVR / Troubleshooting - Channels Community (getchannels.com)

Easily recreate if you have 2 Homerun devices set clients with different tuner priorities then play same channel in clients.

Including the Tuner Priority on the Client Settings Override would solve for this I believe.

yeah but it is supposed to work without all Clients having the Same priority settings for tuners.

1 Like

Agreed. I tend to align them on the client side and having the server override would have saved me a little time or when I login remotely from our mountain house. I've got 6 prime tuners and 6 OTA tuners along with TVE, so don't have issues with running out of tuners, but I like to be efficient as possible.

1 Like

I have 2 Primes units and 8 OTA units ... but I do share them with EMBY and SageTV ... plus I like software to work as designed and at the moment Channels is not doing that.

But i would be happy with tuner settings that populate to each Client on Startup.

1 Like

Works for me on Android clients when I tried it. Need diagnostics to investigate what is going on in your setup.

2021/04/17 08:59:02.004093 [TNR] Opened connection to 107829D3/0 for ch2.1 KATU [transcode=none]
2021/04/17 08:59:11.047156 [TNR] Opened connection to 152035B1/0 for ch2.1 KATU [transcode=none]

Logs have been submitted as c3680cde-009d-409f-9e26-08c214e57c4b.

Please stop both the live tv streams and then resubmit

Logs have been submitted as 5c4aa09e-7e46-413b-a817-3a6f46f4de62.

Thanks. I see the problem. It's not something that is easy to fix. That's why we're rewriting the tuning framework in both apps to give us more flexibility for edge cases like this.

2 Likes

OK for now I will just make sure that all Clients have the same tuner priority as the Server. Thanks for looking into it.

@tmm1 Is it possible on the server to add a Global setting for the tuners ?

Maybe we could add a setting to use the same tuner priority as the DVR server.

6 Likes

This is available in the latest prerelease + beta apps

5 Likes

Thanks works great.

Thanks now I can set new connecting clients for tuner sharing/Inherit tuner priority and KIOSK mode. Can't wait for the Android release version.

2 Likes

In the Global Client Settings I added "Playback > Advanced > Tuner Sharing" a while ago, but I just noticed that it's been disabled. Do beta updates mess with this setting?