After installing the latest version (209) and it won't connect unless I manually run NextPVRServer.exe which of course, keeps a window open. I did nothing different than I did when I ran 208.
However, I'm sure it's something stupid I did.
Logs attached.
I have been using NPVR 5.0.1.200103 installed on a RPi 4 (4GB, Raspbian Buster 290919) since it was released without any obvious problems.
Following the release of the latest Raspbian last week I upgraded to this version today and then also upgraded NPVR to the newly released 5.0.1.200209 using:
sudo dpkg -i nextpvr-helper.deb
after checking that nextpvr-helper.deb was v1.2
The upgrade seemed to go well except for a warning that I didn't have the zlib package installed. Given that the old version seem to work ok, and as far as I can tell the new version of NPVR is also OK, do I need tio worry about this ? I have attached the upgrade log file and the post upgrade NPVR logs for you to see.
However, my next task/problem is to get the blaster element working. I've originally been around this wheel once sort of in this thread: https://forums.nextpvr.com/showthread.ph...t=gdogg371 using my blaster script with an old 1080 DVB-T card. To concisely explain my blaster functionality:
1) It's a command line executable with arguments expected afterwards to make it do anything.
2) It literally mimics the STB remote 100% pretty much. So if you wanted to select channel 401, using NPVR v4 I mapped these as per the above thread to channel arguments 2, 3, 4.
I'm a bit lost though as to how to integrate my blaster with the way we have set things up using extras and v5 in this thread. I get that I need to add my blaster command line statement to my .bat file above my commands to activate a stream through VLC. What exactly should this format look like though? For example (and as a probably incorrect) stab in the dark, would my .bat file perhaps look something like this?
Code:
"C:\MyLocation\MyExecutableFile.exe {channel_d2} {channel_d3} {channel_d4}"
"G:\VLC\vlc <my very long vlc command>"
...or is there a (completely) different way of doing this in extras?
Brand new download and install of Windows 10
Downloaded most recent v4 NextPVR (version 5 still says beta and I wanted the stable release)
Connecting with Kodi
I am experiencing many many application crashes and instability. Sometimes live tv works, sometimes it doesn't. Last evening I watched tv downstairs for a while, no problem at all. Went upstairs to finish watching the show, and then it was not working. Checked it this morning and it's working again
I set the service to restart, so that keeps it running, otherwise after one of these crashes it doesn't start. I did find some messages relating to the PC trying to sleep. I turned that off for now, although I would like to be able to have it sleeping overnight when we're sleeping.
I tried running it in Windows 7 and Windows 8 compatibility mode but no joy.
What am I missing? I'm assuming if this was a widespread issue the forums would be full of messages about it. Can anyone offer any advice or tips on how to get NextPVR running? I'm currently using ServerWMC and Windows Media Center on Windows 7, but since the application and the OS are out of support I wanted to convert to NextPVR on Windows 10
Attached are Windows event log messages and logs from NextPVR
Sub, over the last 2 nights the recording service has stopped running and I've only found it in the morning when live TV wouldn't work. Interesting enough, the web UI still works fine and I can even play a existing recording but the tuners aren't available. This morning I SSH'd and ran "service nextpvr-server status" to see what was going on. It appeared everything was normal, but I didn't capture a screen shot. A restart get everything back running normally. This also happened several weeks ago, but I really didn't think much of it until today.
last night I had 4 recordings going starting at 8:58, 2 recorded to completion, 2 stopped mid recording.
Deputy.S01E06 - 8:58:00 PM - 10:02:00 PM - recorded full length
Tommy.S01E01 - 9:58:00 PM - 11:02:00 PM - recorded full length
A Million Little Things.S02E12 - 9:59:00 PM - 11:00:00 PM - stopped recording after 7min 49sec
Alone The Beast.S01E02 - 10:01:00 PM - 11:05:00 PM - stopped recording after 7min 49sec
Interesting enough, the 2 recordings that didn't complete only get released at 5:49am when I restarted the service. Apparently Npvr still held them both open the whole time until the restart. Both recordings are playable in both the web UI and VLC and appear to be normal other than being short.
I looked at the attached logs and nothing stands out but I really don't know what I'm looking at for the most part. Your thoughts?
Hi all.
NextPVR seems to randomly crash.
It happened both running the .exe and also as a service.
The logs don't seem to help much.
It had just finished recording something at 8pm tonight (which saved ok), but seems to crash after that.
However it doesn't always crash after recording something.
The log files don't seem particularly helpful either.
Also it seems that windows doesn't realise that it has crashed, even though I've set it to restart after it crashes.
The web-service is unavailable until I restart it.
Have attached log files.
Happy to provide any other logs/etc that are requested.
I wrote a little utility that will save the live tv buffer for a channel if recording is started while live tv is playing and it works pretty well https://youtu.be/ex-aP0VFlVQ It actually doesn't matter who is watching it live.
I have a second part of the utility that allows me to combine the two parts and that works the only is issue is the PAT entries in the recordings don't have the same sequence number. Is there any reason to fix this? I could insert a few PAT's to make them sync if necessary.
Hi all,
Have set up Next PVR at my parents house with a HDHomeRun (4 tuner).
I've tested remote viewing of the saved items (as I wanted to make sure it works in case they want to watch things whilst they are away) and was greeted with the error above.
Have pasted in relevant parts of the log file.
I noticed in an older v4 thread it said about trying a newer version of ffmpeg or v5, should I still try a newer ffmpeg, or is the one bundled with the latest version ok?
Any thoughts appreciated :-)
As it was saying the post was too long, have moved the log to a pastebin
EDIT: AS OF 03/25/2020 THE GIST TO GET DOCKER RUNNING ON WINDOWS 10 HOME DOES NOT WORK ANYMORE. I'm leaving the thread here because there was some other conversation, but if you want to run Docker on Windows, you will need to get Windows 10 Pro.
OK, the first thing I should say is: don't do this. I mean, there really is no reason. But I did, so I thought I'd at least document it here in case there's one or two other crazy people who want to do this.
Why did I do this crazy thing?
I had a perfectly good test setup running in Docker on my Mac (which was another crazy thing).
I'm planning to get a Synology NAS pretty soon and run NPVR on that in Docker.
I really wanted to go ahead and move to NPVR5 now but didn't want to do a new build on Windows and then try and move everything to Docker later.
What are the caveats?
You cannot use any USB based devices (tuners, IR blasters, nothing). Docker on Windows (and Mac) don't support passing through USB devices the way the Linux versions do.
Since I have an analog encoder (network based) and IR blaster (USB based), for me that meant I literally had to write a websockets wrapper around my IR blaster software so that I could call the blaster from a Docker container and have a Pi do the channel changes for me. Remember how I said you shouldn't do this? I'm serious. At some point this kind of became an exercise in stubbornness and seeing if I could program my way out of my issues.
And here's the kicker. Docker Desktop for Windows won't even install on Windows 10 Home by default. I found this Gist that let's you install the necessary VM components and then temporarily trick Windows 10 Home into saying it's Windows 10 Pro so the Docker Desktop for Windows installer will work.
With Docker running, you can download sub's AMD64 image and run it as the instructions in that section show. Because I needed Python3 in my image, I used my previously built NPVR image that includes Python3. More on that in this thread.
But after a couple of hours, it's done. I'm running NPVR5 on Windows 10 Home in a Docker container. And the performance is pretty good. And most of the time was spent exporting my scheduled and current recordings and fixing the XML for updated channel OIDs and Linux paths. Now when I finally get the new NAS it shouldn't take more than 10 minutes or so to migrate NPVR to it. I guess the other nice thing about this is that if I have to go back to NPVR4 for some reason, all I have to do is shutdown Docker and restart the NPVR4 service.
Old PC died. Setup good used one and Nextpvr can not find silicone dust tuners. Searched for hours and still never found out what I have done wrong. Under devices the only thing that shows is IPTV devices. Probably something simple I have missed......
