And it worked great in that the record got inserted and appears in the
recurring recording listing.
The problem is that it never got scheduled. I tried scheduling other
manual recordings through the UI, and they all were added and got
scheduled, but the one that I INSERTed did not get scheduled.
When I deleted that record and scheduled the same recording through
the UI, the result looks the same in the database, but this time it
got scheduled.
I get the feeling that I have to do something extra to get an INSERT
scheduled. I tried closing and reopening NextPVR, and I tried it with
the -updatedb option, all with no luck.
I have lots of manual recurring recordings, and it would really be
great to have a command line way of scheduling them. The "Man-Rec" UI
is very hard to use, and I guess Schedule.exe only works for
non-recurring recordings.
So how can I use SQLite to schedule a recurring manual recording?
Actively recording a program, and system is restarted (for any reason) - I simply rebooted while recording.
Upon restart, the first clip is marked as service restarted, and is tucked away for playback.
The second (restarted) clip attempts to continue the recording, and is also marked as service restarted.
Everything looks right, but upon playing, only the first clip (before the restart) can be displayed (it is used for both clip1 and also clip2). Clip2 cannot be found, even while it is still reported as being recorded.
It appears that recording of the second clip has not actually started, even though NPVR indicates it has. The remainder of the recording is lost. In this case, I was recording Fox & Friends on 1214 which started at 6am today. I rebooted around 6:30am to correct another unrelated issue. When I restarted around 6:32am, NPVR indicated that it had restarted the recording, but it hadn't.
This has been going on consistently since I installed 3.6.6, but I don't know if it was also true in prior versions. I've asked about this previously, but was told I should pursue the reason for the reboot (lockups due to codecs), instead of this actual restart issue. Yes, I know that I shouldn't be rebooting during a recording. But, Murphy doesn't always follow the rules, and neither do I. I've been told that NPVR should recover and continue, but alas, it does not.
Building myself a nice new homeserver/TV recorder based on a Dell Poweredge T20, with a Xeon CPU which I got for £200 after cashback. Bargain!
Anyway I've been getting to grips with NextPVR, but have ended up deleting most of my channels my tuner card has picked up due to the seemingly random channel numbers. Can someone with a DVB-S2 tuner pointing at Astra 28.2 link me to/send me an exported XML of their channels so I don't have to manually organise all the channel numbers? Thanks
First time install on a windows 7 box which came OEM with a Hauppauge WinTV 885 ATSC/QAM tuner. When I try to scan either tuner in the device setup screen. a message pops up: "Unable to start device. unable to locate tuner filter..." (see attached screenshot). What am I missing?
Hi,
Is there any way to record directly into MP4 format? My TV only works well with MP4 files, not MPEG-2. N-PVR defaults to .ts format, which is MPEG-2 and doesn't play smoothly, and my converter program doesn't reliably create good .MP4 files from them.
I would like to be able to launch NextPVR, have it tune to a particular channel at a particular time and immediately present the video for viewing.
Many times I find myself missing a live telecast because I'm at the machine but immersed in another task. I know I can record it for later, but I'd rather not commit to watching it later. There may be no time later. Having the telecast just pop-up in front of me is appealing.
I'm on a quest to oust Kodi from my chain of distributed house-wide TV viewing. I'm having trouble getting NPVR to reliably show Live TV with weak signals.
First some pre-amble:
My line of sight to the main DVB-T transmitter for the area is blocked by trees. It's spring and the leaves are coming in so my DVB-T signal has weakened. I used to have NPVR record DVB-T and it coped really well with drops in signal and corruption of the resulting .TS files. Live TV playback was troublesome.
Over the winter I added a DVB-S twin tuner (PCI) on UK Freesat. This gives me all the main channels for my recordings on two tuners. I kept the two USB DVB-T sticks for four more DVB-T receivers to cope with (1) When as a household we need to record three things at once and they don't share the same transponder etc on DVB-S (2) to get a few channels that are available on DVB-T and not a UK-Freesat DVB-S or otherwise legally free to air on DVB-S. For those in the UK, mainly "Dave" and "Quest". So I set my preferences and channel order so that the DVB-S tuners are used first for recordings, then DVB-T only if necessary (overflow or oddball DVB-T channels) and set my live channel preference to be reverse so that the DVB-T tuners would be used first for live stream/small time shift.
And I'm very happy with recordings. I've been using the Kodi plug ins and using Kodi on various PCs around the house to watch the recorded TV, as well as WD Live boxes that get copies of the .TS files where I don't want a PC next to a TV.
Kodi can "call up" a live TV stream via NPVR and it sort of nearly works. Streams play for a few minutes then there is a click-crunch-pause-blip and then the stream continues.
But NPVR natively does something different. Logs included...
In this log from a client to an NPVR server called "DVB-S" (but including the DVB-T tuners just to confuse you!):
* I allow the remote client to start up and grab a whole pile of stuff
* I right click and use the channel selector to pick Channel 1 - BBCNE&C - a good strong signal on DVB-T
* After quite a while (understandable) the channel is tuned and begins to stream.
* I change channel (on the fly) to 2 - BBC Two
* This fails and I have a blank screen
* I choose stop
* I use the channel selector to tune to 2 - BBC Two
* This time it succeeds
* I am able to stop playback of the live stream
* Then I tune to Dave - a weaker DVB-T channel
* It plays for a short while then I see tell-tale mosaic-ing of the picture
* Rather interestingly - in the debug window (which I had on in case it helped), the playback position became a massive negative number but the file extent (in time) continued to progress
* I was able to press stop without a crash
* Then I use the channel selector to pick QUEST which is the weakest signal I can receive
* I get a few frames, debiug shows the massive negative position and playback stops
* I press stop then exit NPVR
Now here's my sort of question and thinking...
Does the playback engine in Kodi for .TS files handle over-running the end of the file/stream more gracefully than that in NPVR? I could see how with my dodgy recordings or "trick play" like pausing and fast forwarding and rewinding that there could be circumstances where my "playback position" would not correspond with availability of stream or file to playback? When nearing the end of the stream/file does Kodi kind of pause or slow down to see if more appears (true end). Does the NPVR engine just see that the playback position (presumably "clocked" from local time) is beyond the timestamp for the end of the data and end?
I see odd behaviour with dodgy recordings with my WD Live boxes, especially in "trick play" like pausing, fast forward and rewind - the progress bar blips back and forth and sections repeat over and over again, like the WD Live box is periodically trying to resolve "clock time" with "playback position" with "file-sequence time".
I guess that advice is going to be to run more cable from the satellite dish, find a PC with more PCI slots and add more tuners on DVB-S for live playback and give up on some channels that are DVB-T only and watch their catch-up web-streams instead. But if you have insight into the way that NPVR plays back TS files/streams then that would also be great - in particular what is the significance of the massive negative number in the debug window when the end of file/stream seems to be over-run. Investigating this might lead to improved "trick play" in live streams and make NPVR time shifting even on "clean" files even better.
It works great but... Buffer file gets created in the Buffer File directory, and ffmpeg transcoded file is created in the Recorded TV directory. Since both are temp files, I think it would be a better idea to get then both on the temp buffer size. But anyway... my problem is the ffmpeg transcoded ts file does not get deleted once the connection is closed. Is there any script I can use or setting I can adjust to force an auto cleanup?
Problem number 2 (since it has to do with streaming I though I'd use the same post): I need to restart the Recording Service after a couple of streaming calls. It just stops responding. Any help?
Hello,
I would like to start by saying I have been using Nextpvr for about 7 months with a single hd pvr2 gaming edition and it has been awesome. This is my first post to the forum. I just bought a new hd pvr2 GE and can not record or watch live tv with the second unit plugged in. I can unplug either unit and everything works, so both units work independently but not together. I have attached a snippet from the log. I have installed the latest driver from the Hauppauge support site. Any help or pointers would be most appreciated.