Hi Martin
I had to do some major repairs to the HTPC as it had recently started Crashing to a hard restart or complete lock up.
After a Repair via Windows update and reinstalling the graphics drivers, I thought I would see if Piers was any more stable.
All the plugins updated OK except the NPVR addon which was disabled. After a bit of research I tried the latest artifact NPVR plugin which would not install due to an unavailable dependency (Direct-ffmpeg or something like) Then went back to Omega using my last Disk backup.
I'm sure you are on the case but will Piers be available for NPVR any time soon?
It appears the problem with the HTPC may have been that some time previously the NPVR Plugin switched from Time shift to Live Stream and the latest AMD Drivers were crashing on any small glitch in the stream. (especially now the weather is warming up) Changed to 3 sec Time shift and reverted AMD drivers to 26.3.1 - so far so good
Hello,
I have a channel set up via iptv m3u the stream has three different audio tracks, but in nextpvr I only have one (can't select any) this then also applies to my recordings.
It simply uses track 2 which is the track with audiodescription.
I have a Linux server running NextPVR 6 and a few years ago had it configured to work with my NextCom R50000-HD network encoder and DISH network. I ad to switched to FIOS and have not used the R5000 and am now trying to set it up again. The R500 is working perfectly writing to a QNAP network NFS share. However when acccessing the R5000 from my NextPVR Linux server, the R5000 appears to b writing to the share but it is actually creating a zero byte file. The file is readable and writeable by owner, group, and everyone else (666 permissions). If from the command line as the NextPVR user (currently called sagetv I run the command:
python3 r5000.py START R5ooo-HD 150 /R5000_Recordings/todays_test-on-the-r5000. The opendct.sh file is called by an extra.xml file and the opendct calls an opendct.py script provided by Martin a few years ago.
The file todays_test-on-the-r5000 is created fine and has watchable video.
My opendct.sh file is as follows:
nextname=//R5000_Recordings//$2.ts
I've been beating my head against the wall on this for days now to no avail. Frustrating since it was working the last time I used it bad sadly don't have all the config files from when it was. Since it still works in SageTV it seems like I'm missing something simple, but I can't wrap my head around it. Can anyone point me in the right direction on this.
Hello,
I installed NextPVR on my VPS using docker which worked just fine.
Then I added a new iptv device and imported channles using XC or however it's called.
The login I used has thousand of channels, which might have been too much for nextpvr...
It imported all channels but when I tried to click "save", nothing happened. I closed the setup window and also reloaded the interface page and after some time I saw two iptv devices. One with I think about 16000 channels and one with a little more than 3000 channels. Anyways, thinks have been weird since then: Under "Channels" in the settings page it didn't show me any channels at first, in the "Channels" Tab on the main interface page there where no channels too and when I tried top schedule a recording, no channels where available as well.
I tried deleting my iptv devices, but that didn't work (Ctrl. --> delete did nothing).
Anyways, I removed nextpvr and installed again, but now I can't add a new iptv. The areas ist just blank.
Frustratingly, I discovered last night that my DVR hasn't been working correctly for a few days now, and that the Recordings database has somehow become corrupted. Recordings that I have made in the past have disappeared from both NextPVR and Kodi, new recordings aren't working, the whole nine.
(Oh: Windows 11 PC, NextPVR as the backend, Kodi as the front, HDHomeRun Prime as the tuner. All updated fully.)
On the upside, the file themselves (the .ts, and .xml, and thumbnail and timing for more recent recordings) still exist for everything.
I'm thinking NextTool is the way to go to get my recording database cleaned and rebuilt. Problem is when I ran it the first time (with "nexttool --import <path to my Recordings folder which has no spaces>", and yes, I backed up the NPVR-Data folder first), it appeared to run, and it looks like it may have fixed some things, but it missed some folders in there, which leads me to believe that there is still some corruption in my Recordings database and that I'm best served recreating that from go, especially considering I have all of the proper metadata to do it right.
Other weirdness: the NextPVR web client can't find any files to play back, while Kodi and the NPVR desktop apps play back what it found just fine. It just either didn't find everything in my Recordings folder (even though the logs say they were processed), or there is still DB corruption.
I would rather not blow the whole npvr.db3 out and have to set everything up from scratch. How can I clear out just the recordings DB so that NextTool can rebuild my recordings directory? I am not afraid to go in there with DB Browser if I have instructions as to what to do.
Hi,
I recently upgraded my ageing media server to a Raspberry Pi 5 running Libreelec 12.2.1
I have a Triax TSS400 SAT>IP server which I thought I might be able to us, but it does not show up under the 'Devices' section of the web app.
It appears to be found as seen in the logs, but it does not indicate that it is a 4 channel DVBS2 4 receiver device.
I have had this device running under TVHeadend but found that I to specifically tell TVHeadend that it was a DVBS2-4 device.
I have included a status screen from the Triax showing it receiving TVNZ 1, as well as a specification document all included in the logs archive.
I would be really grateful if you can suggest how I might proceed to get it to work with NextPVR?
Please let me know if you need me to provide any further information.
I am getting ready to start packaging yauiclient3 and was wondering if anyone wants to test a pre-release version. It is quite different from the previous versions with improved performance and multiple OS support and it will be open source too.
For those that don't know UI clients they give the same great PVR experience as NextPVR.exe on Windows on remote PC's and devices. Up to now these device have been limited to Smart TVs, Windows and Android Roku boxes. With yauiclient 3 many more devices are available. There are test versions for macOS Linux and RPis as well as Windows and even with Windows the performance has improved over previous versions. In the next version of NextPVR, the clients will be much faster on localhost too.
If you like using thumbnails they work exceptionally well on yauiclient 3 and if you don't use them, you might start, they work that well.
One new platform that I feel is really is nice is a LibreELEC 12 and 13 version that allow yauiclient to replace Kodi and provide a true NextPVR appliance capable of not only having a hardware player but the server can be installed. This is working with x64, RPi4 and 5 (3 could work but not client and server), and new aarch64 SoC like the Rockchip 358x SoCs. Kodi is a good client too, but there are many people that prefer the NextPVR interface or just don't like the Kodi look and feel and this provides an alternative. I have tested this on 15+ year old laptops I have setting around and the performance is great, better than on today's RPi5. I had similar findings with sub $100 thin clients so while the RPi5 prices make them almost PC priced, this give a cheap way to add more clients. Using LibreELEC as a base makes it easy to use full MCE or Hauppauge remote too.
A big thanks to artmetz and also to the entire NextPVR pre-release time for getting me to this stage. I have to thank Claude too, I would have struggled to get here without it.
I have resorted to getting epg updates ota but I only get about 11 hours, to work around this nextpvr runs an auto update 2 times a day. I am hoping to run it 3 times a day to cover the gaps but noticed every time it runs it wipes the previous 11 hours.
How can i keep a history of the epg so at least I can see a full day without gaps or if i decide to run the update more frequently.
Gemini tells me add these to my config, but i didn't see any references if this is still valid?
Is there any option to set a default TV channel? I'd like when I go into my epg to be at channel 101 (In UK this is the start of the main Freeview HD channels) rather that at channel 1 which are the SD versions. I know I can renumber channels and make the HD ones first, but as channel lineups change frequently I want as easy a solution as possible so I can just do a rescan and be able to use the rescanned channel list with minimal manual manipulation. Would be great if this was possible, Appreciate any suggestions
Not sure that this sub-forum is the right one for this topic, so mods please move it to a sub-forum where it might fit better.
I have a dedicated offline Windows 10 laptop that I use to watch baseball games on the treadmill (otherwise the experience would be tedious to the point of inducing insanity). For years, I happily recorded games on Windows Media Center and transferred the .WTV files to the laptop via sneakernet. The laptop has a receiver connected for use with the WMC remote.
As Verizon has sunsetted our CableCARDs, this model for viewing will become obsolete once I finish watching the last game recorded via CableCARD. In anticipation of this event, I tried putting .TS files produced by NextPVR (using a Hauppauge HD PVR 2 1512) onto the laptop, to play via VLC. However, I don't have a remote that (to my knowledge) will control VLC, at least not with the granularity that a WMC remote can control WMC (30-second skip forward, 6-second skip back). So I resorted to converting the .TS files into .WTV files so that I could use the WMC remote.
This has worked OK, but there is a nagging visual issue where the WTV video looks choppy: for example, whereas the crawl line on the .TS file flows smoothly, on the .WTV conversion it moves along in little fits. The motion of a batted or pitched baseball looks similarly jerky in comparison to the .TS file.
What, if anything, can I do to mitigate/eliminate this issue? I'm open to solutions that will either (preferably) improve the .WTV output or, barring that, improve the VLC experience (a useful remote?).
In case it makes a difference, for the conversion to .WTV I'm using iDealshare VideoGo, at its highest settings for both video size and video quality.
