When I run NextPVR client and try to watch live TV it crashes the client. Please see additional details below.
I am running Windows 8.1 and NextPVR 3.5.7
I am using HDHomeRun Extend (HDTC-2US)
When I click Live TV in NextPVR it pops up a window that states "...please wait..." and then stops responding.
If I try to watch through something else such as Emby or Kodi they cannot connect to the recording service.
Kodi every few seconds a pop up appears stating, "NextPVR PVR Client Connection Lost".
I am able to watch already recorded shows
I am able to view the guide (It is not up to date, but I do not think it is related, as I had it set up using MC2XML, which I believe there is another issue with. I will worry about this later, once I get Live TV working again).
If I check in services the NPVR Recording Service is running.
If I check in Task Manager NTray and Nrecord (32 bit) are both running.
If I check the logs the only two that have updated during this are NPVR and NRecord which I have attached.
There are two errors in NRecord log, both dealing with this error System.Net.Sockets.SocketException (0x80004005). Please see more detazils copied in below.
My network is set up as a private network in the Windows Firewall and NDigitalHost, NCableCardHost, NextPVR, and NRecord are all allowed on private networks.
I have gone through and deleted all of the channels and imported them again (this did wipe my guide settings as well)
I am able to watch live TV through the HDHomeRun application, VLC, and Kodi (leveraging the HDHomeRun plugin not NextPVR client)
As stated above in the bullets I have attached NPVR and NRecord logs. Also below is the two Errors that appear in NRecord.
Code:
2015-09-11 18:57:53.785 [INFO][4] RecordingService.Startup()
2015-09-11 18:57:53.785 [INFO][4] Starting remoting service (on port 8968)
2015-09-11 18:57:53.800 [ERROR][4] Error listing for recording service interface: System.Net.Sockets.SocketException (0x80004005): Only one usage of each socket address (protocol/network address/port) is normally permitted
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at System.Net.Sockets.TcpListener.Start(Int32 backlog)
at System.Runtime.Remoting.Channels.ExclusiveTcpListener.Start(Boolean exclusiveAddressUse)
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.StartListening(Object data)
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.SetupChannel()
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(Int32 port)
at NShared.RecordingService.Startup()
Code:
2015-09-11 18:57:58.833 [DEBUG][10] Client Listener starting on port 7969
2015-09-11 18:57:58.833 [ERROR][10] Unexpected error in Client Listener: System.Net.Sockets.SocketException (0x80004005): Only one usage of each socket address (protocol/network address/port) is normally permitted
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at NShared.ClientStreaming.WorkerThread()
With so much video clips taken with digital cameras, my photo library has a mix of jpg,mov,avi etc it would be really good to be able to play the videos, even if it's just some way to fire up a viewer like acdsee or InfranView which can play the files and have a command line interface.
I changed my audio decoders to AC3Filter. The time before the audio sync was better but the audio did eventually speed up. I read on a post that changing the config file <ForcedLiveTVClock>AC3 Audio Renderer</ForcedLiveTVClock> in config.xml, in the <Renderers> section. It worked perfectly for three days.
Well, Windows installed an update and my pc had to reboot. Now the issue is back. The config file is the same and the audio decoders are the same. Any suggestions?
I have used LAV, ffdshow, SAF, and AC3filter. Is there anything else I can try or any settings in one of these decoders that I can change?
I did a quick search but didn't hit it - may be to simple but do I just delete from the plugin directory - I tried one but it stayed on the menu, as there are installers for them is there an uninstaller?
I am trying to test code to check for conflicts, but I am having a hard time making a conflict. If I try to record five shows, NPVR won't let me. It makes me cancel or delete one of the first 4.
Comcast cable just mailed me explaining they are transitioning to MPEG4 in my area and Cablecard users should make sure their devices can handle MPEG4.
From what I've read, the Hdhomerun prime can handle this just fine.
Is this a non-event for NextPVR as well?
What would this mean to NextPVR for resources such as disk space and/or processing? Better?
Hello, I am having an issue with NPVR and FM radio on my Hauppauge 2255 in Windows 10. The normal digital tuners (both 1 and 2) work fine. However, neither tuner works with FM radio. My assumption is that Tuner 2 (the one listed as analog #2 in the screenshot) is the FM tuner. Either way, I cannot get FM radio to work on either tuner. I have started up WinTV 8 and successfully got HD OTA and FM radio to work seamlessly. Here is the screenshot and the logs. Any thoughts?
[ATTACHMENT NOT FOUND]
I am posting this in support because I'm passing on some of the problem stuff, but it is mostly a request for a change.
At some point along the line, I put some sort of option into my setup which creates a "netpush" file in C:\temp - don't remember how or why, but maybe I'll dig into it more if I decide to stop doing it. Anyway, I guess it is some sort of debug thing, and it's usually fine, but occasionally something goes wrong and the file grows like crazy. As in, it becomes gigabytes in size and fills up my C: drive. When this happens, there is usually a recording that doesn't get started (0 bytes in size), so I have basically left this in place as it acts as a "canary in the mine" sort of thing - when I get the "You are running out of space on C:" message, I know that something isn't getting recorded properly.
Anyway, it would be nice if this file had some sort of size limit or such on it, and did like the other log files do - close one and start writing to another, so I can just delete the older ones that have the same info over and over again, rather than having to shut down the NPVR service while other stuff is recording.
As for the problem, in case someone wants to look at it, the latest occurrence was tonight, when attempting to record The Nightly Show at 23:30. Attached is Nrecord log, and the netpush file had a bunch of this:
23:30:01.257 [5944] Constructor
23:30:01.257 [13936] StartReceiver
23:30:01.258 [12324] FillBuffer GetSize()=1880
23:30:01.317 [13936] About to bind port 36314
23:30:01.317 [13936] StartReceiver. Bind Failed
23:30:01.317 [13936] Successfully set socket buffer size
23:30:01.317 [13936] StartReceiver. recvfrom failed rc=00002726
23:30:01.317 [13936] closing socket
23:30:01.317 [13936] About to bind port 36314
23:30:01.317 [13936] StartReceiver. Bind Failed
23:30:01.317 [13936] Successfully set socket buffer size
23:30:01.317 [13936] StartReceiver. recvfrom failed rc=00002726
23:30:01.317 [13936] closing socket
23:30:01.317 [13936] About to bind port 36314
23:30:01.317 [13936] StartReceiver. Bind Failed
23:30:01.317 [13936] Successfully set socket buffer size
23:30:01.317 [13936] StartReceiver. recvfrom failed rc=00002726
23:30:01.317 [13936] closing socket
23:30:01.317 [13936] About to bind port 36314
23:30:01.317 [13936] StartReceiver. Bind Failed
23:30:01.317 [13936] Successfully set socket buffer size
23:30:01.317 [13936] StartReceiver. recvfrom failed rc=00002726
23:30:01.317 [13936] closing socket
23:30:01.317 [13936] About to bind port 36314
23:30:01.317 [13936] StartReceiver. Bind Failed
23:30:01.317 [13936] Successfully set socket buffer size
23:30:01.317 [13936] StartReceiver. recvfrom failed rc=00002726
23:30:01.317 [13936] closing socket
23:30:01.317 [13936] About to bind port 36314
23:30:01.317 [13936] StartReceiver. Bind Failed
23:30:01.317 [13936] Successfully set socket buffer size
23:30:01.317 [13936] StartReceiver. recvfrom failed rc=00002726
23:30:01.317 [13936] closing socket
23:30:01.317 [13936] About to bind port 36314
23:30:01.317 [13936] StartReceiver. Bind Failed
23:30:01.317 [13936] Successfully set socket buffer size
23:30:01.317 [13936] StartReceiver. recvfrom failed rc=00002726
23:30:01.317 [13936] closing socket
23:30:01.317 [13936] About to bind port 36314
23:30:01.317 [13936] StartReceiver. Bind Failed
23:30:01.317 [13936] Successfully set socket buffer size
23:30:01.317 [13936] StartReceiver. recvfrom failed rc=00002726
23:30:01.317 [13936] closing socket
Potentially dumb question here... I did a device setup-> scan and got my channel list, I then went through it and deleted channels i do not subscribe to, then copied that config to my other tuners... turns out i deleted a channel by mistake, is it possible to add it back without doing a whole scan and editing the list again?
