Has anyone had any luck getting Emby to detect tuners (HDHomeRun in my case) on Windows Server 2016? Emby installs cleanly on 2016 and with the exception of Live TV tuner detection/access I haven't seen any Server 2016 specific issues. When I try to detect the tuners it comes back after less than a minute that it can't find the tuners. Manually adding them by type and IP doesn't work either.
In the attached log there are 2 captures.
- The first is debug turned on and trying to scan for the tuners. It doesn't give you much.
- The second is after manually adding a tuner by IP address and then attempting live playback. Again, debug is on.
In searching the threads I see that I'm not the first to encounter this but didn't see a resolution. Trying to diagnose this is a bit challenging as I'm not getting much to go on. It isn't A/V or Firewall related. Tried with both turned off. The PC can see the tuners. I installed the HDHomeRun setup program (20180817) and it sees the tuners and channels no problem. I can launch a channel (have VLC installed) from the HDHomeRun Setup app and it opens and plays fine.
One more confirmation Emby never talks to (locks) the tuner. I set up 1 tuner by IP and opened 2 Emby life TV sessions. Both sessions clocked like they were trying to connect. While the sessions clocked I opened the HDHomeRun Setup program and attempted to stream a channel. It worked. The tuner wasn't committed to Emby.
This 2016 server is my Media/NAS system and should be more than powerful enough to handle what I'll use Emby for. That is if I can get past this tuner challenge. From what I see with this I think Emby is likely the victim here. Just how to prove it and identify what needs to be done to work around it. Would be happy to test a diag runtime or run other tests to capture trace data. Just let me know.
Any help is appreciated.
Edited by accarshop, 30 August 2018 - 11:14 PM.