I have a Dell PC hooked to my TV acting as an HTPC. It used to run Win 7 and Win Media Center(WMC) with a Hauppauge TV tuner to record OTA channels. I now upgraded to Win 10 which no longer supports WMC so I installed NPVR and its working pretty well. The Dell came with an IR remote which supposedly was the standard when working with a Win PC and in fact all of its buttons functioned properly with WMC, including the "green" button that would start WMC. With NPVR many of the buttons on the Dell remote do work, but unfortunately not all of them. Specifically the green button and the blue button (to bring up the info bar during a video) do not work. I posted in the support section and got a lot of help and was even given some modified parts of NPVR to try to get all of my remote to work. Unfortunately those efforts were not successful.
So now I'm asking the community to tell me what remote they are using so I could buy one and then learn those buttons into my Harmony remote. So please post what brand and model IR remote you are using and if that remote's green and blue buttons are recognized by NPVR.
Hi there
If you go to the main nextpvr.com homepage, all you get is a brief outline of what the program can do, but there are no download or forum links. Is this a bug with my browser or is this affecting everyone?
Thanks
Application: NRecord.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at Native.AnalogRecorder.StartStream(System.String)
at NShared.AnalogRecorder.StartStream(NUtility.ChannelMapping, System.String, System.String ByRef)
at NShared.AnalogRecorder.SwitchStream(NUtility.Channel, NUtility.ChannelMapping, Int32, System.String)
at NShared.RecordingService.StartStream(Int32, System.String, Int32, NUtility.ChannelMapping ByRef, System.String ByRef)
at NShared.RecordingRemote.StartStream(Int32, System.String, Int32, NUtility.ChannelMapping ByRef, System.String ByRef)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr, System.Object[], System.Object, System.Object[] ByRef)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage)
at System.Runtime.Remoting.Messaging.ServerObjectTerminatorSink.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage)
at System.Runtime.Remoting.Lifetime.LeaseSink.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage)
at System.Runtime.Remoting.Messaging.ServerContextTerminatorSink.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage)
at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessageCallback(System.Object[])
at System.Runtime.Remoting.Channels.ChannelServices.DispatchMessage(System.Runtime.Remoting.Channels.IServerChannelSinkStack, System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessage ByRef)
at System.Runtime.Remoting.Channels.DispatchChannelSink.ProcessMessage(System.Runtime.Remoting.Channels.IServerChannelSinkStack, System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Channels.ITransportHeaders, System.IO.Stream, System.Runtime.Remoting.Messaging.IMessage ByRef, System.Runtime.Remoting.Channels.ITransportHeaders ByRef, System.IO.Stream ByRef)
at System.Runtime.Remoting.Channels.SoapServerFormatterSink.ProcessMessage(System.Runtime.Remoting.Channels.IServerChannelSinkStack, System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Channels.ITransportHeaders, System.IO.Stream, System.Runtime.Remoting.Messaging.IMessage ByRef, System.Runtime.Remoting.Channels.ITransportHeaders ByRef, System.IO.Stream ByRef)
at System.Runtime.Remoting.Channels.BinaryServerFormatterSink.ProcessMessage(System.Runtime.Remoting.Channels.IServerChannelSinkStack, System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Channels.ITransportHeaders, System.IO.Stream, System.Runtime.Remoting.Messaging.IMessage ByRef, System.Runtime.Remoting.Channels.ITransportHeaders ByRef, System.IO.Stream ByRef)
at System.Runtime.Remoting.Channels.Tcp.TcpServerTransportSink.ServiceRequest(System.Object)
at System.Runtime.Remoting.Channels.SocketHandler.ProcessRequestNow()
at System.Runtime.Remoting.Channels.RequestQueue.ProcessNextRequest(System.Runtime.Remoting.Channels.SocketHandler)
at System.Runtime.Remoting.Channels.SocketHandler.BeginReadMessageCallback(System.IAsyncResult)
at System.Net.LazyAsyncResult.Complete(IntPtr)
at System.Net.ContextAwareResult.CompleteCallback(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Net.ContextAwareResult.Complete(IntPtr)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(System.Object, IntPtr)
at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
You can find also the logs in attachment.
So when this happens i need to stop the service and start the service. Otherwise it doesn't work anymore...
I have had NPVR running on my HTPC for several months. Everything works out great; set up was simple and maintenance has been low. Recently, I added a second machine to act as a client in another part of the house. The documentation on the wiki is limited, but the setup seemed fairly simple. However, I cannot get the client to see/find the shared database file. I have confirmed the client machine can see and browse to the share location of the DB through windows explorer. Neither the use of the server machine name nor the IP address in "Server name" nor in the file path seem to work. Am I missing a setting somewhere else on the client machine? Possible on the server side? Both machines are up to date Win. 10 machines in the same Homegroup.
I am using one HdHomeRun Prime, and all three tuners are able to be used, and have been used in NextPVR, however, for some reason on Monday Better Call Saul refuses to record on an available tuner, and waits until another tuner is free, resulting in no post-padding for one of the earlier recordings, and no pre-padding for Better Call Saul.
Pre-padding: 1 minute, post-padding: 2 minutes
Recordings for the night:
8:00 - Superstore on 105 - 30 minutes
8:00 - Supergirl on 107 - 1 hour
8:00 - X-Files on 113 - 1 hour
9:00 - Lucifer on 113 - 1 hour
9:00 - Magicians on 676 - 1 hour
10:00 Better Call Saul on 697 - 1 hour
10:30 Samantha Bee on 664 - 1 hour
At 9:59, two tuners are in use, and should be in use until 10:02, at 9:59, Better Call Saul should use the third tuner that is idle since two tuners will be freed up at 10:02 and be available for the 10:30 recording, but the logs say that no tuner is available until 10:00 when it takes over the tuner recording The Magicians.
I have a subscription to Verizon FiOS in New York. I use NextPVR extensively to record TV through one of two hardware sources: 3-tuner Hauppauge DCR-3250(cable card) and a Hauppauge USB HDPVR(settop box). There were no issues recording Fox News network when I used Microsoft Windows Media Center. But, as you probably know, when I had to move to NextPVR, I lost the ability to record about 18 channels, all Fox Network. Web-based tuner utility shows those channels flagged with DRM, copy-once. For those channels, I now use the settop box and the USB HDPVR.
Can you help me understand why the cable card shows these channels with WMC but not NextPVR? Is NextPVR even aware that the screen is blank? How does the card "know" that an application has DRM?
Anyone else having issues with live tv and Kodi RC3 and above with NPVR?
I am getting this in the Kodi log.
14:28:38 T:18860 WARNING: CDVDMessageQueue(audio)::Get - asked for new data packet, with nothing available
14:28:39 T:20808 WARNING: CDVDMessageQueue(video)::Get - asked for new data packet, with nothing available
It seems completely random, last night watching James Bond on TV3 (NZ) it died after about 5 mins. This morning it played all the way through to at least 2:28.
I have attached the NPVR Log dir.
I have this same fault on 2 x Nvidia Shield TV and 1 x Windows 10 PC. Running Kodi 16 RC3 or above.
I'm in the UK and new to NextPVR (and XMLTV stuff generally) and finding in general that it works great on My Windows 7 PC with my ClimaxDigital USB DVBT stick.
However when I use Record Season (new episodes on this channel) I get repeat episodes recorded as well - an example would be the Dragon's Den programme on BBC2 which shows on Sundays and is then repeated on Mondays (on the same channel). The series itself is not a repeat but the Monday show is.
When I look in the NextPVR EPG there is nothing to indicate that the Monday show is a repeat. I tried with other software (eg arcsoft totalmedia that came with the tuner) and that looks the same too. However my 10 year old Sony HD recorder does handle this correctly so I assume that somewhere in the EPG info that is broadcast in my area for this show there is something to denote it is a repeat. Am I correct in assuming all devices/tuners would use the same EPG data or could my HD recorder be getting it over the air from somewhere else?
I took a peek inside the npvr.db3 database using sqlite_export_cmd and exported the epg_event table into a libreoffice spreadsheet and saw that the "first_run" field is actually set to Y for absolutely every programme on every channel and that the "original_air_date" is 0001-01-01 for everything, so I guess from that there is no way these duplicates can be prevented (and so many series do repeat shows in the same week these days).
I did try searching first but didn't find anything to specificall address this.
