Do the remote clients all have the same priority settings as the DVR they are accessing? If they differ, it might account for some of the discrepancies.
Yes, and I've also tested using only the web ui which adheres strictly to the DVR priority.
@tmm1 All Primes have been updated and each DVR instance has been rebooted. Each DVR can see all 3 Primes but they are only attempting to access the first priority. There are no issues with channels or sources being disabled to cause this.
The exception to this is that a local device will access another tuner if priority 1 is full. For example, three local devices are accessing all tuners of priority 1 Prime and I attempt to start a remote stream, it will fail even if the other two Primes are free. If a fourth local devices tries to start a channel it will grab a tuner from one of the unused primes. (I think it may also limit local devices that are transcoding to the first priority as well but I need to test this further)
I'm not seeing any errors in the log other than what was previously reported.
Also, is it strictly as issue with first priority and not the Primes, if I change the priority order it will correctly use priority #1 no matter which Prime that is, but will only use that single Prime for remote streams.
Bug confirmed. Only affects remote streams. Recordings use multiple tuners correctly, as does the Apple TV app when using Tuner Sharing at home.
1 Like
Wow!
Really impressed with ability and tenacity of both of you:
Congrats on job well done 
1 Like
Do I need to update to the beta or is a fix coming for stable?
I will be working on this later this week and fix will be in the pre-release for testing first.
Thanks!
Web-UI is now using the wrong tuners. For example, I have channel 13 disabled on my quatro and enabled on 2 lower priority extends. When I tune to channel 13 via the web-ui, it tunes the first priority quatro to the disabled channel. This uses the wrong antenna and has poor signal quality. It tunes correctly on Apple TV, though.
If you look at the disabled/favorite status in the web UI, is it disabled there? Sometimes the Channels DVR needs to be synced with changes to the device. To do this, choose the "Scan Network" option in the drop-down for the Sources section in the web UI.
No, this is not a config problem. It is a bug.
It is disabled in Web-UI. And disbaled on the actual HDHomeRun web-admin. Yet, Channels web-ui will still tune the first priority tuner to the disabled channel.
Ah, I see what you mean. You are correct, this does sound like a bug then.
As a workaround, what about marking that channel on other tuners as a favorite, to prioritize the other tuner for that channel.
Also, are both tuners sharing the same guide/lineup? I wonder if they had different guides, would Channels then honor the disabled flag for the higher priority tuner?
This bug is fixed in v2019.08.11.2352
1 Like
Thanks, my Channels is running perfectly now. Awesome!
1 Like
Is the fix specific to the web-ui or all remote streams? If all does it just need the Beta dvr or also the beta client app?
Only @djcastaldo's bug was fixed, which is specific to the web UI.
The broader related bug affecting all remote streams has not been addressed.
Updated... I only ran a quick test of opening up 4 remote streams, but that seems to indicate that it is fixed. It correctly filled the first priority and then moved to the second prime for the 4th stream.
2 Likes
The web-ui bug that you fixed in v2019.08.11.2352 is back again in latest betas. The most recent beta where web-ui used the correct tuners is v2019.08.13.0310
1 Like
Oops, looks like I broke it again fixing @JMcGuire's bug.
Should be fixed in v2019.08.15.2304
2 Likes