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?
I use the guide for LiveTV in Kodi and it is such a stupid hassle that if I click on a listing, a screen opens and I have to scroll over to "SWITCH" to start viewing.. who in the world thought this up?
Why can't it be if I click a guide listing, that it will automatically start to play that channel. Makes absolutely zero sense the way it is now. I am sure someone will have some lame excuse why it is this way. So, at the very least have it so you can make it open in setup.
X-newa wont start when i restart server pc
Running on rpi2
Last version of xnewa and npvr worked fine till i updated npvr
Its always just worked im not sure what to post or where to start looking for the problem
Have to restart RPI once it goes into loop (saying working bottom right corner)
To me its like the PC is not serving what KODI needs
If i untick Autostart web client it then loads (but i want it to look like pc version of npvr)
Just got warning saying unable to load newa data then tried again and it loaded
After upgrading to 3.5.7, many of the buttons on my Hauppauge remote no longer work. The rewind and fast forward buttons work. But other buttons like the back button and the colored buttons do not.
Anyone have any ideas on how to troubleshoot/fix this?
