Been using mediabrowser/emby for a few years now and very happy with this platform. Previously using win7 and WMC for live tv with serverwmc and it was flawless. I've upgraded to insider release of windows 10 build 10240.
I have been using the web client using IE and Edge, with nextPVR installed for LiveTv
LiveTv works fine using NextPVR client directly, it's fast and doesn't use a lot of resources.
Emby works well too, it's fast and responsive. I needed to address loopback issues to localhost using netsh so Microsoft Edge and the Win10 client from illusions can access localhost http services. So far, this works a charm and I really like both the native win10 client and web client, great work!.
My issues started when I setup the NextPVR plugin to work with Emby.
Firstly, NextPVR was returning a 500 error, which I was able to resolve. The NextPVR web client used by Emby was failing due to authorisation issues attempting to access ASP.NET temporary files under .NET Framework folder - even though their website is not hosted in IIS and I didn't have a "ASP.NET temporary files" folder. Fixed by creating the appropriate folder and applying the correct security perms to the System account. I could then access the NextPvr client and it worked via emby.
Second issue I've encountered now is when I start up a LiveTV stream in emby, after a 30sec + wait time (due to transcode I'm guessing?), the stream from NextPVR will stream for a very short time then it cuts off in IE. In Edge, no stream loads and says "There was an error playing the video. Please ensure there is an open tuner available." - even though in NextPVR I can see the stream start and transcode.
When I looked in the emby server logs with LiveTv debugging enabled), I noticed the following error:
2015-07-22 21:30:46.2533 Error - HttpAsyncTaskHandler: Error occured while Processing Request: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. *** Error Report *** Version: 3.0.5675.1 Command line: C:\Users\Home\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Operating system: Microsoft Windows NT 6.2.9200.0 Processor count: 4 64-Bit OS: True 64-Bit Process: False Program data path: C:\Users\Home\AppData\Roaming\Emby-Server Application Path: C:\Users\Home\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. System.IO.IOException at System.Net.Sockets.NetworkStream.Write(Byte buffer, Int32 offset, Int32 size) at SocketHttpListener.Net.ResponseStream.InternalWrite(Byte buffer, Int32 offset, Int32 count) at SocketHttpListener.Net.ResponseStream.Write(Byte buffer, Int32 offset, Int32 count) at ServiceStack.Formats.HtmlFormat.SerializeToStream(IRequest request, Object response, IResponse httpRes) at ServiceStack.HttpResponseExtensionsInternal.WriteErrorToResponse(IResponse httpRes, IRequest httpReq, String contentType, String operationName, String errorMessage, Exception ex, Int32 statusCode) at ServiceStack.ServiceStackHost.OnUncaughtException(IRequest httpReq, IResponse httpRes, String operationName, Exception ex) at ServiceStack.HttpResponseExtensionsInternal.WriteToResponse(IResponse response, Object result, ResponseSerializerDelegate defaultAction, IRequest request, Byte bodyPrefix, Byte bodySuffix) at ServiceStack.HttpResponseExtensionsInternal.WriteToResponse(IResponse httpRes, IRequest httpReq, Object result, Byte bodyPrefix, Byte bodySuffix) at ServiceStack.HttpResponseExtensionsInternal.WriteToResponse(IResponse httpRes, IRequest httpReq, Object result) at ServiceStack.Host.RestHandler.<>c__DisplayClass5.<ProcessRequestAsync>b__0(Object response) at ServiceStack.Host.Handlers.ServiceStackHandlerBase.HandleResponse(Object response, Func`2 callback, Func`2 errorCallback) InnerException: System.Net.Sockets.SocketException An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.Send(Byte buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.Net.Sockets.NetworkStream.Write(Byte buffer, Int32 offset, Int32 size)
NextPVR has forced a closure of the connection to emby, I'm not sure if this is related to windows 10 or not, but either way these products just don't work well together on windows 10. I've posted the full log file plus transcode logs to assist with diagnosis.
I know Windows 10 is not RTM yet so I may get this is not supported, but it is only a week away and with people intending on upgrading and using NextPvr as their LiveTV solution with Emby, I'm hoping someone can provide direction to help sort this out.