The desktop app will not start on my system since the last update. I get the screen shown in the attach and that's it. Now, I don't generally use the desktop app, so it's no big deal for me, but wanted to let you know. I clicked it by mistake. I'm on Windows 11, 21H2 Build 22000.1098.
I'm running the latest (6.1.1.221106) version of NPVR on Windows 10. I signed up for Schedules Direct in October and I set it up, everything was running smoothly. I noticed it initially had about 1 week's worth of listings, but then it eventually increased it to 13 (or 14) days. It did this on its own, I didn't specify any numbers of days, so I left it to use whatever the default is.
Now it seems the listings have not been updating for about a week. I was away for about that time so did not notice until yesterday.
I don't see any mention of issues on the SD site.
Whenever I attempt a manual update of the guide in the web app, I get
EPG Update complete. [2337 inserted, 0 updated, 0 skipped]
One thing that stands out is that today's (Sunday Nov 6) listings go up to 11 pm only. The rest of the days show up to midnight, at least until 7 pm on Mon Nov 14 after which there are no more listings.
Quote:Fixed a crash that could occur on Linux/Docker when starting recordings or live tv
Fixed issue with ATSC scan on Linux where only the first channel was found on each frequency
Fixed issue with tuning to the correct channel on Linux when multiple channels with the same name are available.
Updated arm64 support (previously tuner components had become quite out of date on this platform)
Fixed issue with web translations on Settings page
Fixed cosmetic issue with Windows installer saying it was v5.
Fixed issue with the choice of channel name when importing from IPTV m3u
Fixed issue with SAT>IP tuner being stolen during a recording when multiple recordings were attempted
Added support for Linux devices with multiple frontends
Improved logging for some Schedules Direct errors
Has anyone any information on using an ATI 2GB Radeon 550 to assist with the transcoding. The default option of AMD in the drop down does not seem to work for me.
I'm connecting to my NextPVR instance running on my Linux server using the NextPVR Jellyfin plugin. The only reason I do this is so I can use the Jellyfin client on my Roku device. When watching a NextPVR recording via the Jellyfin plugin I notice it's using the following URL to access the recording stream (local private IP).
Recording 1049 is in fact the recording I requested to play. The Jellyfin client does not play the stream. As a test I copied and pasted the URL into VLC and it also will not play. Then I pasted the URL in a browser it downloads the video to a file... all 5.8gig of the recording.
Is this normal behavior for the "live" URI? I expected it to be a stream. I should mention, I have a post recording script that transcodes the recording to a MKV file and then uses the NScriptHelper.dll to rename the recording in the NextPVR database. The recording plays perfectly in NextPVR and the Jellyfin web client but it seems to fail for anything that uses the "live" URI. Maybe I need to leave the recording in TS format?
After the latest Windows 10 update, I can no longer access my mapped network drives with NPVR. I had the drives working before without any issues. I am using \\IPADDRESS\folder in the settings dialog. I am able to write to the folder from Windows explorer, and can add files/folders without any issues, but NPVR cannot get access. I cannot record to, nor can I browse/select any of the mapped folders from the NPVR settings. I tried creating a symlink from a local folder to the network folder, and that does not work either. I am at a loss here.
I assuming its some sort of permissions issue, but even tried giving EVERYONE full access. No luck.
I've been happily running next pvr for a year or so on a windows 10 machine with 16gb ram and a 2 TB HD - graphics are through intel board with i7
I use Kodi on the remote stations and on one smart tv
the server is effectively headless. the cards are older TBS6905
There are frequent occasions when the Kodi client (OSMC) loses contact with the serv er and even restarting the next server does not reinstate
I think it is to do with starting the TV tuner card more than next or Kodi because when I go to restart next I check the delivery on hte server machine an dit gives message 'could not start tuner'
This all seems to happen when one of thd frequent Windows updates takes place.
I was wondering if Linux might be more reliable ?
I guess the answer will be 'depends on TBS drivers for linux ? and perhaps newer TBS card might be the answer (they are 10 yrs old)
One side question - Given that it's a headless system does the quality of the graphics card make any difference?
What min spec would a linux machine need?
Sorry for the scatter gun of questions but all knowledge eagerly soaked up
Unable to login but login info works fine on schedulesdirect.org. I can only think that it is a problem with their server, so I opened a ticket with schedulesdirect. However, I think if the listings are not updating, then a warning of some kind might be in order. It is in the log which is great, but some people might not know what is happening. I did new install of nextpvr on another pc and the listings will not even load, so definitely login issue.
The attached file shows several(12) extracts from a web.log created during a live TV viewing sessionon a tablet with Kodi from a V4 desktop using WiFi and a Hauppauge HDPVR2 device. During the session, there were several 'freezes,' all of which resumed automatically after varying length of time.
Do the extracted log segments indicate where the trouble might be?
