DVR logic: Prioritizing ATSC 1.0-only tuners, but only within a device

[Cabal]

With college football in full swing, I found myself running out of tuners on my Flex 4K (another post on that in the future) and broke out my older Connect Quatro (HDHR5-4US). Everything is wired up, the HDHomeRun DVR (Linux) sees both devices, and signal levels look good on all channels. 8 simultaneous recordings tested successfully.

In single-device configuration with the Flex 4K, watching/recording ATSC 1.0 content will prioritize the 1.0-only tuners before using the 3.0-capable ones. Makes sense.

With both the Flex 4K and the Connect Quatro available, starting 4 ATSC 1.0 recordings will send all 4 recordings to the Flex 4K. That means that if I attempt to watch a 3.0 channel via Live TV, there are no tuners available, even though 4 ATSC 1.0 tuners remain unused on the second device!

How complex/advanced is the scheduling algorithm when multiple devices are used? I would think even a simple round-robin between both devices would give me a better chance of successfully tuning a 3.0 channel than the current all-on-one-device scheduling.

Thanks.

[signcarver]

If the dvr engine is on the Linux machine, typically the dvr engine will prefer the tuner with the lowest deviceid first (which would be your older connect) but when the flex records to its own attached drive, it will typically use its own tuners first.

On occasion I have seen the engine prefer ipv6 over ipv4 (if connect is on older firmware it might be ipv4 only) or need to be restarted to order things correctly.

Note I also said typically as any tuner (device) with the same virtual channel number is fair game... also if multiple engines are available, live can change things around and go to the flex if drive attached there and then we go back to the flex preferring it's own tuners.

[Cabal]

It's definitely preferring the Flex 4K (higher device ID) every time. All devices, DVR, and players are IPv6-enabled and logs indicate IPv6 is in use every time. No tuners have drives attached, everything lives with the Linux install and DVR service.

[Cabal]

ping

[NedS]

Can we have you enable diagnostics on both CONNECT and FLEX and do a channel scan?

[Cabal]

Can we have you enable diagnostics on both CONNECT and FLEX and do a channel scan?

Done.

FLEX: 10A4C0B0
CONNECT: 1077341E

A couple things I didn't include in the original post:

- Both devices are set with identical enabled/disabled channel lists, other than the additional ATSC 3.0 channels.
- When comparing the same channel's quality levels on both devices, the levels are the same, to the human eye.

After running the scan, I ran the experiment again, this time making sure all recordings were on 100/100/100 channels. Same as before, the first four ATSC 1.0 recordings went to the FLEX, and the 5th overflowed to the CONNECT. All recordings were initiated from the Discover tab.

Thanks.

[Cabal]

It looks like while recording 4 college football games today, all 4 are going to the CONNECT, leaving the FLEX for overflow. Not sure if that's intentional or just luck. First time I've seen it.