Tuners failing after upgrade

[sub]

Here is another try at it.

[persim]

That appears to have fixed everything. I was only able to do some limited testing but had live tv going on both machines. Will let you know if other issues pop up with more testing.

[sub]

Great

[mvallevand]

Yes this works, it might might still be good to log the X-HDHomeRun-Error instead of the stack track on the 503.

Martin

[pkscout]

I'm about to setup an HDHR Flex with the ATSC 3.0 tuners, but in a Docker container rather than on Windows. Will I likely need this fix as well and, if so, can I use the NShared file included in this thread? Or is there a different one needed for the Docker installs?

[sub]

If you’re not trying to use the tuners from other software at the same time, you should be fine without it.

As far as I can tell, it had been this way for quite a while.

[mvallevand]

The fix will work on Docker so I would use it.

Now Hijacking the thread a bit the issue for the Flex is the spec

• 4 tuners
• ATSC 3.0 (on 2 tuners)
• ATSC 1.0 (on 4 tuners)

so /tuner2 and /tuner3 will need to fall back if watching Live TV.

ATSC 3.0 AC-4 audio won't play in normal Kodi and only works in uidroid for NextPVR. If your Docker host is fast you might be able to use the ffmpeg from the Emby releases that has the "unofficial" ffmpeg patch with NextPVR web.

If watching ATSC 3.0 Live TV in uidroid is something you will do a lot of I would edit config.xml to not use reverse priority. You will also need to prioritize ATSC 3.0 recording to make sure they get tuner0/1 if that is what you want and this is where things might still get tricky. That is why I have mentioned that the Flex isn't optimized.

You can also disable tuner0/1 in NextPVR and use them in the HDHR app. The value of ATSC 3.0 right now is on disk space and bandwidth not quality. Even the SuperBowl will not be 4k.

Martin