Hi,
Running 3.9.2 (161119)
Just wondering..
I want to auto schedule record a specific football game each week.. as you do..
The show is always labeled 'AFL - Live' (but there's like 9 matches televised a week)
Within each match.. the description will typically include the teams names..
eg:The Eagles have claimed local bragging rights winning the last three derbies, but Ross Lyon has turned the fortunes of his Dorkers around after a tough start to the season.
Eagles is the team/game I require...
so if I can enter 'AFL - Live' + 'Eagles' as the search term?
(so it has to satisfy the presence of BOTH terms to qualify..)
This way I don't end up having to record all 9 games each week, as the other AFL games won't have the word 'Eagles' in their descriptions.
(and I'm not so interested in all the nature shows with the word 'Eagles' in their description either...)
Is there some sort of algebraic capability already in the "Keyword" section of "Keyword Recording" that will achieve this?
If not, is there another way to set this up?
thanks
AJ
i am getting this error on NPVR (version 3.9.2) startup:
2017-04-23 15:58:59.177 [ERROR][1] TV Listings: error reading settings from database: Could not load file or assembly 'System.Data.SQLite, Version=1.0.65.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
2017-04-23 15:58:59.178 [DEBUG][1] TV Listings: Exception details: System.IO.FileLoadException: Could not load file or assembly 'System.Data.SQLite, Version=1.0.65.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'System.Data.SQLite, Version=1.0.65.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139'
at TVListings.BackendImpl.TVListingsDatabase.GetDbConnection()
at TVListings.BackendImpl.TVListingsDatabase.ReadSettings()
i also note that recordings are not being refreshed on kodi (unless i restart kodi).
could these issues be related?
NPVR would otherwise seem to be operating normally as far as I can tell.
In the last couple of weeks, I've had several recordings from my HDHR primes fail with the "No Errors but no Data Delivered" message. In the last 2 days these recordings failed:
4/18/17 8:59pm NCIS: New Orleans (tuner moved at record time)
4/20/17 7:59pm Scandal (not moved)
4/20/17 8:00pm The Amazing Race (moved)
I've looked in the logs (see attached) and can't really see any reason. Different channels, different tuners, some moved/some not, etc.
I also included the system logs from the HDHRs, and they don't show any sort of errors--everything looks the same there for recordings that work fine and those that failed.
Do you see anything, sub? Any ideas about anything else that I should check?
tl;dr version -- My NextPVR computer lost power and now the database is missing most shows it should have. What's the best way to make sure I've got a healthy database to go on with? (Restoring the missing shows would be nice, but it's not crucial.)
So. Yesterday someone accidentally knocked the power cord for the computer that I'm running NextPVR on out of its socket.
I found out about it about six hours later, and thought I fixed things; when I went to bed a couple of hours later, I thought it was back as it should be. (I can't remember if I checked what recordings it listed; I was very tired at the time.)
In the morning, I checked to make sure the program that should have recorded overnight did... but it didn't. That was when I noticed that the date on the computer was actually set to January 2008! It didn't record the program because it thought the recording date was nine years and four months in the future...
At the same time, I discovered that the database was only reporting 11 recordings, when I have easily six times that many. Thankfully, the actual files appear to all be where they should be, but the database only lists those 11.
I did a little digging in the NPVR data folder, and found the following files:
recording-backup.xml -- dated 4/21/2017 5:50 AM -- size 12 KB
recording-backup.xml.1 -- dated 1/1/2008 2:16 AM -- size 12 KB
recording-backup.xml.2 -- dated 4/20/2017 2:17 AM -- size 160 KB
A quick look in the files suggests that the first two files contain entries only for the 11 files the database reports now, while the last one -- the one that's 160 KB -- seems like it contains all the entries the database should contain.
What's the best way I can make sure the database is "clean", i.e. doesn't contain hidden corruption that'll cause disaster later on? Is there any (relatively easy) way to restore the database's missing entries while I'm at it? I should mention that the listing of my recurring recordings seems to be intact, thankfully.
I can watch multiple windows of TV in WINTV v8. NextPVR does not work.
Getting error "Unable to Communicate with Recording Services."
Checked Windows firewall for blocked apps. Set NextPVR, NRecord, NDigital Host to allowed public and private.
I'm testing out NextPVR as a possible replacement for Windows Media Center, but I have an issue with the format of the file names for recordings.
By default, the file names appear as "series.title.S01E01.episode.title.ts." The periods are an issue for another program I'm using to manage recordings. I found the option to disable "replace spaces with period character" under the recordings settings, but that doesn't resolve my issue. The files names now appear as "series title.S01E01.episode title.ts."
Is there any way to get NextPVR to create the file name with no periods at all (unless they are part of the title itself)? I need the file name to be in the format of "series title S01E01 episode title.ts."
when recording from this channel (log attached) the capture always stops early. npvr shows it is recording. the led for the tuner on the hdhomerun is lit. also, the network activity light on the ethernet port flashes, indicating data is transferring from the hdhomerun. this is the only channel that has this problem. the signal quality is not that bad.