Yes, I open Emby theatre, and use the live TV feature with the NextPVR plugin. I have to start the stream twice, the first try just get the Emby waiting circle, but when I try again, 99% of the time it kicks in.
I have done a complete removal of the BG tuner from NextPVR and deleted the driver from Windows, then installed the 8.1.1.2 driver which worked when I first installed the card back in November. I want to see how it behaves after the server hibernates tonight.
It almost seems like the tuner takes too long to get a lock, but giving it a kick (channel scan, or retrying using the NPVR plugin in Emby) wakes it up.
I checked the signal again, and the strength was about 50 and quality was 100 when it did start working.
Ok so that really isn't Emby it is still NextPVR. However Emby just uses Live TV for recordings and these are used in opposite order from the device that NextPVR records with. How does Emby wake the server? NextPVR will have now idea that it needs to wake up for a recording.
I'm also wondering if your device just takes a long time to resume. I think in OnResume.bat you could add a delay and see if that helps.
When I have checked the wake log (for other reasons) it is the NextPVR service which resumes the machine prior to the recording. When I schedule a single recording through Emby, as far as I understand the plugin adds the schedule to NextPVR and lets it handle it. For series I have to use the NextPVR interface.
Ok it depends on how you use the program, but yes your are right if it is a scheduled recording then it will wake, if it is via their Live TV it will not.
So far, so good. The server came on this morning (manual trigger) and I was able to watch a live stream though Emby with no issues.
I started working on a wget script last night, to start and stop a live stream from 4 different MUX, to force all 4 tuners to be loaded up. It sort of works, but once NextPVR catches up and realises all the requests are coming from the same client, it closes the 1st 3 requests and leaves the 4th running. There is just enough time for a stream to start though (the timeshift ts file gets populated). Ill keep working on it and see if it works if I get the lock issue again.