I am using the default skin on Windows 10 and am in the UK, I use NextPVR for watching and recording TV. I would like to change the subtitle font, particularly Teletext. I can't find it defined anywhere, is it possible to do or is it defined externally? I am currently using VLC to watch recordings as the subtitles are handled better but this really shouldn't be necessary. I cannot find any useful up-to-date information on the forum so any help would be appreciated.

Placeholder - info to be added here soon.

FYI, this is a phone/tablet application, not an Android TV app.

I've just retired a WD 2tb green (EARS) HDD from my UNRAID server due to Capacity Upgrade (Seagate IronBru 4tb) and and replaced the 1TB Samsung F3 recording drive in the NPVR HTPC with it, along with a SSD for Live TV (Already had SSD for OS) Head parking has been changed from 8 seconds to 300 seconds.
Finally I can use a non raid driver and use TRIM and SMART etc.

Thought I would Run CrystalDiskMark on the drive and was a bit surprised to see that although sequential reads and writes were around 90 MB/s, Random reads and writes were well under 1MB/s.

Has anyone used these green drives for recordings? And how do they cope with Multiple Recordings and Recording / Playback at the same time?

Otherwise I may have to replace with a Seagate Barracuda or WD Blue.

Hi,

Quite new to NextPVR, but so far it looks amazing, so well done. However, I have an issue.

Firstly, this is my setup: HD Homerun (DVB-T2) tuner, a dedicated PC acting as a server / recorder and several Raspberry Pi's on TV's all over the place.
I'm using the latest (December 2017) version of NextPVR.

The issue I have, has been seen before, where the tuner remains in use, recording to a 'c:\devxxxxx\null.ts' or something like that (Sorry cleared the problem, by restarting the NextPVR background service). Anyway, it's happening quite a lot. I only noticed because my network light was flashing like crazy when no recording where taking place.. or EPG updates.. so it shouldn't have been talking to the tuner. I'm not 100% sure what causes it, but once cleared it doesn't seem to appear by itself, so is probably after a recording.

As per the readme, I'm including the complete log files. On this subject, I noticed the loggs have a 'lot' of this...

2018-02-25 17:12:53.402 [DEBUG][25] Renew lease ok (0x160001)
2018-02-25 17:12:58.597 [DEBUG][25] Renew lease ok (0x160001)
2018-02-25 17:13:03.884 [DEBUG][23] Renew lease ok (0x160001)
2018-02-25 17:13:09.084 [DEBUG][23] Renew lease ok (0x160001)
2018-02-25 17:13:14.122 [DEBUG][23] Renew lease ok (0x160001)
2018-02-25 17:13:19.261 [DEBUG][20] Renew lease ok (0x160001)
2018-02-25 17:13:24.485 [DEBUG][20] Renew lease ok (0x160001)
2018-02-25 17:13:29.781 [DEBUG][20] Renew lease ok (0x160001)
2018-02-25 17:13:34.967 [DEBUG][25] Renew lease ok (0x160001)
2018-02-25 17:13:40.101 [DEBUG][25] Renew lease ok (0x160001)

.... so some of the log files are 500K, most of it these messags. (Notice theres ten odd per min... seems odd, but probably another un-related issue?)

Hope this drivel helps!

Thanks for NextPVR, it's great. Would love to get it to a reliable state for me. Thanks.

Is there a way to manually create broadcast channels in the channel list that exist but may be too weak to pick up at the time an auto-search is initiated?
I can move the antenna around to get fringe channels but that activity also loses other channels.. depending on where I place the antenna, I get 25 - 30 channels out of 45 I know of, which ones I get (or lose) in channel search depends on antenna placement.

Worked OK when installed last week. Today, it tunes but blank screen, no audio..

Win-10, SAF6 drivers, tried various decoder options, reboot, no joy..

Log Files attached (includes when it was good, and when it weren't..)

[ATTACHMENT NOT FOUND]

Hi

I had a weird problem with two channels that could not be streamed in Kodi and web browser. It gave no errors (Kodi just hangs and web browser got stuck on "Requesting stream for channel. Standby..."). The channels plays fine in both WinTV and NextPVR. When troubleshooting, I found out that the channels contain two audio tracks - MPEG1 and AC3. When I change to AC3, the video gets very laggy with no sound in NextPVR. I believe this is causing the streaming problem. Still, it plays fine in WinTV.

I've tried all the available decoders for AC3:
https://pasteboard.co/H9surPb.png

(bear in mind that all the other decoders are not set up correctly for testing purpose).

It somehow looks like NextPVR is trying to use the wrong decoder, because when I disable AC3 decoding, it doesn't give me an error, and the same problem persists.

Recording the channels work perfectly fine. Here is the codec info from VLC:
https://pasteboard.co/H9svHdo.png

Here is a recording of the problem:
https://www.youtube.com/watch?v=SX8evsku5zI
First, it plays normally with MPEG-1 track, and then I change to AC3.

Log files from NextPVR taken 5min. after video recording.
https://www.jottacloud.com/p/jeppe-honor...87acae603e

Hope some one can help me out here. Let me know if you need any info - I tried my best to collect the most essential stuff.

I've been using NextPVR for the last four years very successfully with a TBS Dual HD card and an old dual Nova T500 on UK Freeview, Mendip transmitter.

Since January, i've been experiencing major problems. First problem was the Legacy Kernel Caller sleep problem, where it does not release sleep lock on the PC and it stays away. Second problem is bad recordings, either it fails or it creates a giant GB recording which does not play. Third problem is not stopping recording, one ended up about 200GB!

First thought was bad hardware, so I removed the old Nova T (10 years old).. no good. Then I retroed NextPVR back to 3.X - no good. Nothing worked. So I thought fresh hardware (and I wanted one too) so I bought a Hauppauge quad channel card. Just that in the PC. Same problems.

So last week I reinstalled windows, completely clean, just nextpvr and the Hauppauge card. No other peripherals.

But its still going wrong. And as I noted in another post, I too saw last night that the digital host was using 1.5GB of ram. And it won't sleep (randomly), still creating bad recordings, etc.

So to sum up, i've tried different cards, therefore different drivers. I've cleaned the PC and just had NextPVR running. And its still bad.

Now something else someone says may be causing this. In Jan we had a minor retune, BBC4 HD to com8. This is around the time problems started. I record BBC 4 HD often. Last friday 23rd I recorded a bbc 4 program and it was bad, gigantic, never slept etc. Last night I recorded one from 8-9:30pm and it did not stop the recording and stopped the machine from sleeping on time.

I'm wondering if there is an underlying bug which is causing either nextpvr or the drivers to go wrong due to this retune and use of this multiplex (note i've used both TBS and Hauppauge cards, so different drivers). I also wonder if its related to recording multiple programs from one multiplex. All in all its not obvious the direct cause.

The major retune is tomorrow, 27th, when the 700MHz band is removed. So maybe that will fix it..

In the meanwhile, today, i'll try record multiple shows but avoid BBC 4 HD and see if I can isolate it to that multiplex.

Rob

I've checked the NextPVR Wiki and found nothing about starting up live TV from the command line. If I can do this, I can start TV at a particular time using Task Scheduler.

Any words of wisdom? Can this be done?

Thanks.

I have two NPVR servers that I access with multiple devices, and everything works fine. But, on one server, the recording service stops working every night at exactly 2:40am. If I check services.msc, the recording service is still running, but clients like Kodi say the tuner is no longer available. A quick restart of the service brings it back immediately.

My assumption is that it's either Windows Defender or MalwareBytes doing an overnight scan that's hitting one of the NPVR executables and temporarily locking it. But, I've checked Task Scheduler and I can't find anything that actually runs at 2:40am.

Not a big deal, and I'm sure a wipe and reinstall of Windows on that machine would fix it. Just wondering if anyone else had run into that.