So I installed a BT v4 USB adapter on our NPVR PC so I could use my new BT headphones to watch recordings and movies. I installed the software that came with it called CSR Harmony Wireless Software Stack and that worked fine, identifying my headphones after a reboot. I then realized NPVR was not running, so I launched it and it crashed. I tried removing the headphone pairing, removing dongle, rebooting, still crashed. Just to see if the BT was working I launched Kodi and that crashed too. I tried VLC which also crashed, but noted COM Surrogate was the problem. I then uninstalled the CSR software, but both NPVR and Kodi still crash while VLC would launch and run.
During the first reboot there were a couple Windoze updates that applied. I guess those could be suspect also, but I'm more inclined to believe it was the CSR software.
I was due to update, so I did install NPVRSetup_4_2_2_180623, but no change.
NPVR logs attached. Any pointers would be greatly appreciated.
Hello all,
Recently I am not able to communicate with the NEXTPVR server from the client with win 10. I have done nothing with my network settings. I have noticed that I am running 4.2.1 on the server and 4.2.2 on the client. Could this be the reason? If so How do I update the server with out having to reinstall all my settings on the server?
Please advise.
Thank you,
Bruce
I used the Android app to quickly schedule my wife's soap opera because she was going to be late. I just noticed my Parkinson's jerks made me hit the record option more than once and it recorded multiple copies of the same episode. Any way to prevent this going forward? Maybe have it check and see if it's already scheduled or add a confirmation option that can be turned on or off in the settings for those that may be annoyed by a confirmation box?
(I didn't post logs at this time due to personal logistical reasons. I will if you need me too.)
I have slowly been importing my old WMC recordings into NextPVR and without any problems. However, have just done a batch where the season/episode numbers don't appear in the Ready Recordings list. Here's a typical error message from the log :
2018-07-02 13:27:43.675 [ERROR][1] Unexpected error parsing EPGEvent xml: System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at NUtility.EPGEvent.Parse(String xml)
2018-07-02 13:27:43.675 [ERROR][1] xml:
<Event>
<OID>0</OID>
<Title>Coast</Title>
<SubTitle>Heart Of The British Isles - A Grand Tour</SubTitle>
<Description>In this first episode the team embark on an extraordinary circular tour of the Irish Sea to visit every country and territory within the United Kingdom. The hub for this wheel around the heart of the British Isles is the Isle of Man where Neil Oliver explores the small island. On the edge of the Irish Sea at Morecambe Bay, Alice Roberts gets trapped in quicksand to discover why it is so sticky and so deadly. In Northern Ireland, Miranda Krestovnikoff sees how seals cope with the struggle to find food as they bring up pups in the beautiful inland sea of Strangford Lough. Nick Crane goes sea cliff climbing on the remarkable rocks of Anglesey as he explores why this corner of North Wales is the site of some of Britain's biggest earthquakes. </Description>
<ChannelOID>BBC 2</ChannelOID>
<!-- BBC1=7158, BBC2=7159, ITV=7148, 4=7150, 5=7155 -->
<StartTime>2010-07-20T20:00:00.0000000Z</StartTime>
<EndTime>2010-07-25T21:00:00.0000000Z</EndTime>
<FirstRun>true</FirstRun>
<OriginalAirDate>2010-07-25T00:00:00.0000000Z</OriginalAirDate>
<Season>5</Season>
<Episode>1</Episode>
<Genres>
<Genre>Documentary</Genre>
</Genres>
<UniqueID>COAS0501000000</UniqueID>
<!-- 14 characters -->
</Event>
I didn't think I was doing anything different but I clearly am but I can't figure out what. Any thoughts?
My KODI/XBMC box is running on a Raspberry Pi. It's very solid and works great. The NextPVR addon seems to be doing it's job mostly; it downloads guide data, lets me watch live TV, and does recordings. The NextPVR backend is running on home built server running Windows Server 2012. It too is very solid, and works great! I have 53tb of storage, filled to 6tb free with Music, Family Pictures, TV Shows, Movies, Games, backup storage, etc. I also have 3 tuners capable of receiving 5 channels at once. The NextPVR backend software runs on boot up, and communicates with Kodi regularly, as I said working well in harmony.
Anyway, enough back story.. My problem:
I've been missing a lot of recordings due to (I believe) a problem with the addon not waking the server to record a show. If the server is running and awake when a recording is due to start, it works perfectly fine. But I've actually witnessed a show get missed because the server doesn't wake to start. At first, I thought there was a 2-way communication between Kodi (Raspberry Pi) and NextPVR (server). Where if a schedule is made, it creates a timer on the server to wake itself up in time for the recording. But the more I research it, it looks like that's not the case at all. Kodi is apparently supposed to be sending a WOL (wake-on-lan) packet to the server to get things started. In my case, it seems like it's not doing that job. When I look in the PVR settings of Kodi, there is a "Power Saving" tab, where there appears to be a script being called that initiates the wake up. That script is said to be located in "/usr/bin/setwakeup.sh". I looked at that file and it doesn't have any information as to what it's doing, or anywhere to input an IP address. Could this be where my problem is? Am I missing something here?
Contents of "/usr/bin/setwakeup.sh":
Code:
#!/bin/sh
################################################################################
# This file is part of OpenELEC - [url]http://www.openelec.tv[/url]
# Copyright (C) 2009-2014 Stephan Raue (stephan@openelec.tv)
#
# OpenELEC is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 2 of the License, or
# (at your option) any later version.
#
# OpenELEC is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with OpenELEC. If not, see <http://www.gnu.org/licenses/>.
################################################################################
if [ -f /sys/class/rtc/rtc0/wakealarm ]; then
logger -t setwakeup.sh "### Setting system wakeup time ###"
echo 0 > /sys/class/rtc/rtc0/wakealarm
echo $1 > /sys/class/rtc/rtc0/wakealarm
logger -t setwakeup.sh "### $(cat /proc/driver/rtc) ###"
fi
For a test, I have a set recording schedule made for "The Price is Right", which is on CBS daily at 11:00am (EST) M-F. When I'm home from work some days, I have watched to see if the server wakes up for the recording. I've had the schedule set for a month, and to date there have only been maybe 3 recordings. I know the show is on, and Kodi shows the timers are enabled and then missed, with an error like "NextPVR backend was not available". Well duh, you never woke the server up!
Is there some trick I need to do to make this work? I suppose I could go in on the server and manually create a wake up timer to have the system be on from 11:00am-12:00pm every day. But that defeats the purpose. Shouldn't this all work automatically? Looking for any help or advice here, I'm completely lost.
I am using Hauppauge Colossus on Windows 10 1803, NPVR V 4.2.2. I recently tried to switch from Rovi using mc2xml to create the XMLTV.XML file to zap2it using zap2xml to create the XMLTV.XML file. The XMLTV files generated look similar, however, when I IMPORT from the one generated from zap2it, I get channel names like "FUSION(108)" in NPVR. When I use the Rovi/Microsoft source, I get channel names like "108 FUSION". Looking into the generated XMLTV.XML files, the first 3 <display-name> parameters look the same to me with the first one being "108 FUSION". Can anyone tell me why the channel name is different in NPVR for these two cases?
Hope this wasn't too confusing!
C'mon, someone must have seen this! Basic questions is thy does NPVR import channel names like "FUSION(108)" from XMLTV.XML file created from ZAP2IT?
Issue: Kodi unable to play live tv through NextPVR backend
Equipment: HTPC with Kodi (ver. 17.5) and NextPVR (ver 4.2.2) on same machine. Tuner is a Hauppauge HDPVR 1212 connected via TIVO
Up until recently I had the above equipment working through KODI to watch cable channels from cable-card equipped TIVO via the Hauppauge 1212 tuner. I recently cut the cord (axed Comcast Cable) so in doing so I reset the Tivo Roamio for Over theAir channels (OTA ânote this uses sub channels which maybe be an issue). At this time I also removed a Hauppauge PCI card tuner from the HTPC that worked and was identified under NPVR settings along with the Hauppauge HDPVR 1212. I removed the PCI tuner card because I used the antenna feed from that to feed the TIVO. I also updated NPVR to version 4.2.2 (not sure if this may have caused any issues)
After the removal of the PCI Tuner Card and the upgrade of NPVR, I could not get KODI to start the NPVR tuner to start in LIVE TV (spinning and then states tuner unavailable). I did not touch any setting or connections as it relates to the Hauppauge 1212. In trying to troubleshoot, I read that subchannels maybe an issue, but as I recall the PCI tuner when installed used OTA subchannels and that worked?
In troubleshooting to eliminate the Hauppauge 1212 being the issue, I was able to see a live TV feed via the Arcsoft Total Media Extreme software that came with the device. So I know the tuner is working.
As to the NextPVR backend âI was never able to play live tv (black screen) though NPVR it -says I needed a different MPEG2 decoder (played around with different decoders-no luck) using the HDPVR 1212. It did work with the PCI tuner. I did not use NPVR for video purposes because KODI must have had the proper decoders because live tv worked in KODI through NPVR using the Hauppauge 1212.
Using http://127.0.0.1:8866 I was able to see the NPVR page-so it is not a networking issue?
I have posted the KODI log, if anyone can help identify the issues? Thanks
Since I upgraded to 4.2.2 (180623) I've been getting blocky recordings which skip so badly that they often won't play - but only on one channel at one time of day. If I start a recording manually (or schedule a timed recording for later that day on the same channel) it always records perfectly, as do recordings on other channels at all times of day. As far as I know, my system (aerial feed, two DVB devices, PC, recording location) hasn't changed.
My first thought is that reception of this channel's multiplex is poor at certain times of day (and I've scheduled a few more overlapping recordings on channels on the same and on different multiplexes for the same time tomorrow to investigate further). However I wanted to check here whether anyone else has had problems that started when 4.2.2 (180623) was installed.
The details are: recording on LCN 20 (Drama) (mux COM4) at 0800-0900 from Bilsdale transmitter in UK.
One of my two DVB devices gives signal strength/quality stats, and when I've checked (about 1000 each day) these have matched the values from before I started to experience the fault, so at least for that adaptor, at that time, the multiplex is not weaker or poorer quality.
Any Help on this issue would be appreciated I posted on KODI forum but no luck so far....
Issue: Kodi unable to play live tv through NextPVR backend
Equipment: HTPC -Windows 7 64 bit with Kodi (ver. 17.5) and NextPVR (ver 4.2.2) on same machine. Tuner is a Hauppauge HDPVR 1212 connected via TIVO
Up until recently I had the above equipment working through KODI to watch cable channels from cable-card equipped TIVO via the Hauppauge 1212 tuner. I recently cut the cord (axed Comcast Cable) so in doing so I reset the Tivo Roamio for Over theAir channels (OTA ânote this uses sub channels which maybe be an issue). At this time I also removed a Hauppauge PCI card tuner from the HTPC that worked and was identified under NPVR settings along with the Hauppauge HDPVR 1212. I removed the PCI tuner card because I used the antenna feed from that to feed the TIVO. I also updated NPVR to version 4.2.2 (not sure if this may have caused any issues)
After the removal of the PCI Tuner Card and the upgrade of NPVR, I could not get KODI to start the NPVR tuner to start in LIVE TV (spinning and then states tuner unavailable). I did not touch any setting or connections as it relates to the Hauppauge 1212. In trying to troubleshoot, I read that subchannels maybe an issue, but as I recall the PCI tuner when installed used OTA subchannels and that worked?
In troubleshooting to eliminate the Hauppauge 1212 being the issue, I was able to see a live TV feed via the Arcsoft Total Media Extreme software that came with the device. So I know the tuner is working.
As to the NextPVR backend âI was never able to play live tv (black screen) though NPVR it -says I needed a different MPEG2 decoder (played around with different decoders-no luck) using the HDPVR 1212. It did work with the PCI tuner. I did not use NPVR for video purposes because KODI must have had the proper decoders because live tv worked in KODI through NPVR using the Hauppauge 1212.
Using http://127.0.0.1:8866 I was able to see the NPVR page-so it is not a networking issue?
I have posted the KODI an NPVR logs if anyone can help identify the issues? Thanks
I ask as I recently went into the npvr.db3 database and removed some "TM" labels off the kids Harry Potter Shows.
Some of them kept the TM in the file name, so I thought maybe NEWA read it off these, but there are some shows WITHOUT TM in the "name " or "filename" in npvr.db3 and NEWA STILL shows TM in the name?
