I'm currently running version 5.0.9.201026. It seems like version 5.1.1.210329 has a fix for a problem I was having with missing channel logos, so I'd like to upgrade. I note that the directions for upgrading are quite simple, but I want to verify that, when I do upgrade, my settings, recordings, and scheduled recordings will be preserved.
Will these items be preserved?
Sorry if this is a dumb question and thanks in advance for any help.
I have 3 choices for the target directory when I add new recordings. In the WebApp, I can add a new individual recording (i.e. record once, not recurring) from the TV Guide and can select the desired recording directory. However, when I click on the on the resulting item in the WebApp on the "Scheduler/Pending" screen, the directory shown on the details is always the first one in the list -- not the one that was actually selected. This would appear to be an issue with the dialog's initialization because the recording will still occur in the directory that was initially selected. Also the details for the recording do appear correctly in the Desktop app.
I think this is a bug since the the selected directory does show correctly for recurring items that are on the Pending screen. This can make planning recordings from the WebApp difficult because, for me, one the target directories is a ramdisk with limited space. I can never tell where a recording is actually going to be saved.
I have a strange problem, if i want to watch a station via Kodi or browser i get Failed to start requested stream, but if i try to record it works fine with a 5 minute test so far. Any ideas how i can fix this?
I started noticing problems with ffmpeg when I upgrade from 2:4.3.2-6 to 2:4.4-3. Comskip wasn't processing files and when I ran them manually I would receive a segmentation fault. I modified my ini file to remove all the comments and remove items that are set to the default condition. That seemed to work, but I am sporadically receiving segmentation faults. I downgraded ffmpeg just now as more shows are failing to be processed than are making it through without a fault.
I haven't been watching much TV which I guess is a good thing. I went to watch 60 minutes and the news only to find nothing has recorded since 5/7.
I updated the epg data, restarted nextpvr, and rebooted the computer trying to get it to recognize scheduled recording for tonight. Last thing I did was rescan one of the tuners (Hauppauge QuadHD) and while it was scanning I did a system upgrade. One or the other or perhaps both of those things resulted in the scheduled recordings turning red.
Attached are logs from 5/7 and 5/9. I created a script to create logs whenever I restart nextpvr. I'm hoping to find out how to prevent future failures.
Mine says i am on 1.0.0.xxxxx. I clicked on https://nextpvr.com/NPVRSetup.exe. I would have thought I would have the latest and greatest. If there is a new download for 5.1.1xxx do I have to uninstall my existing or will it just upgrade to 5.1.1xxx
The Roku channel has been upgraded with some new features and improvements
1.11.8 update.
1. Version 10 of the Roku firmware handles some file type error responses differently.
2. NextPVR doesn't support files in the media libraries with an upper case extension, and causing a client loop.
3. Handle screen saver keystroke. If the Roku screensaver (which is blank in NextPVR) keys would be sent out of sequence to the client
4. Manual IP Configuration
- manual settings now saved on OK
- load manual dialog will used save settings if found.
- new option to delete the manual setting which will reset it to defaults.
5. When directplay is off (HLS mode) there is now pseudo client-side timeshifting
- Left and right move -/+ 30 seconds.
- transcode leases now sent during pauses and on ~6 second intervals
- enable channel switching and prev channel keys.
Since I am still not used to sub's timeline in NextPVR UI (or the web client) I personally recommend using the traditional style timeline. It doesn't have the red unwatchable area on the timeline that we had in past version but is is still more logical for me.
Code:
<OldStyleTimeLine>true</OldStyleTimeLine>
6. m3u8 support enhancement.
- needs 5.1.2 of NextPVR for server API change and improved m3u8 streaming.
- support for m3u8 auto-transcoded recordings, these work better then ts files.
- currently I still prefer mp4 remuxing over m3u8 playback
A couple days ago I ran out of program guide which means that it has been about 2 weeks (around April 22) that I haven't been downloading new guide information.
I use zap2it without an account through mc2xml commands. When I ran updateEPG.bat (which runs mc2xml.exe) by command line, I noticed this error:
Code:
Missing data : 44.239.89.126 [zipcode]-USA-lineupId-DEFAULT-1620496800124356R 124759H
When I deleted mc2xml.dat and ran it again with and without options "-1 -c US -g [zipcode]", I got:
Code:
Provider error: 34.213.157.23 124356R 124759H
After some reading, I realized I was using an old version of mc2xml (v 1.7) though v 1.7.2 was available. I obtained v1.7.2 from the mc2xml web archive (https://web.archive.org/web/202004260039...pace.info/) and tried it; it worked for me. Just wanted to post this here in case anyone else was having trouble.
I really don't imagine this is possible without directly driving the tuner....
However, in case I am wrong..
I set series recordings and then don't watch them for months. When I eventually come to watch them I sometimes find that for whatever reason the DVB signal had broken up enough in a recording to make it not worth watching.
At the time of the initial recording the episode which recorded badly was likely available a few days later, but a few months later it is long gone.
Does NPVR receive enough info about the quality of the DVB signal to understand that a recording may be rubbish? If so could it mark that episode for re-recording?
I should mention - this is more of an "I wonder" suggestion than "I would love if you could" because if I really cared I would have watched 6 months ago when it was aired
I am cleaning up some failed shows and I was wondering how to trigger the AutoRemoveMissingRecordings logic. I tried restarting the server and looking at the recording list in the web browser but the files I deleted are still there.
Also thanks for caching the event information on delete. It helps being selective with the history.
