After setting up the Schedules Direct lineups for my Xfinity cable and local over-the-air channels, the mappings keep reverting to the wildly inaccurate ones done automatically by NextPVR rather than using my own settings.

Whether I use the Bulk Map or alter each channel individually in their Details window, they just keep reverting to the blasted AutoMap which I absolutely hate.

This wouldn't be a problem if automap would just match by numbers instead of names. Why doesn't it do that? I want channel 6 to be matched to channel 6, not channel 550!!! :mad:

Anyway, how do I stop it from reverting. Is there something in the settings I can change to disable automapping entirely?

Hi, would any body be able to help me find out why i get this error on itv hd / bbc2 hd free sat channels, they work fine with v4. Please see attached logs.

Since this new version of NextPVR is designed to be cross-platform, that does mean that the recorded .TS files no longer contain Alternate Data Streams, right?

It has always been annoying that I can't store my recordings on non-NTFS systems, at least not without losing data.

Does this also mean that NextPVR now writes the .XML file with the recording's metadata right next to its .TS file by default?

It would be nice if that was true by default instead of having to go into the config.xml file and manually change <StoreSeparateMetadataXml> under <Recording> to True.

Just want to make sure. I'm also curious how well NextPVR handles without them if they truly are gone. If I recall correctly, I think it needed the other non-XML ADS in each TS file for time-shifting or some other reason.

My port will not forward. I have gone in my router and disabled windows firewall. What could I be doing wrong?

I get this error now: (IP) took too long to respond.

Now that I'm able to find the right location of the scripts for PostProcessing, I'm able to execute the script but has anyone successfully written a script to execute comskip?

To execute Comskip it's ~/git/Comskip/comskip for me and then the file location and file.

Is there documentation on how to refer to the recording? I think for windows its %2. Also not sure if I'm going to run into a permissions issue.

I'm also wondering if there is a way to limit the amount of comskips running in case I have multiple files.

Flyingsubs

Hi All,

Trying to figure out where NPVR is installed too. I think its here? /opt/nextpvr/system/data/scripts

Also trying to figure out how to get Comskip to run via the PostProcessing.sh.

I have comskip installed on linux but not sure how to get the script above to fire if I'm in the right place.

-Flyingsubs

I am feeling really dense today.

I need a simple Linux bash script to move a finished recording to a monitored directory so Medusa can rename and put it in the correct spot.

The problem is if I record to the monitored directory Medusa can't tell if it is finished and renames and moves it prematurely.

I am just having a devil's time understanding the script samples.

Hi, does anybody got the V5 multiple directories working?

thanks

Well, after NextPVR's recording service crashed yet again last night, destroying almost all of Toonami without my knowledge until the following morning, I finally decided to bite the bullet and build an app to do something about it. I only regret not doing it sooner.

This app is designed to basically babysit NextPVR by monitoring the state of its recording service once per second. If it detects that the service has stopped for whatever reason, it will log the time at which this occurred, copy all of NextPVR's log files into a separate directory with this timestamp, and then attempt to restart the service. Once the service has been successfully restarted, it will log the time at which it restarted the service. From my own tests of manually stopping the service, it seems to restart it within 5 seconds of it stopping. The new folder full of the log file copies is in the same directory as the original log file folder, which is C:\Users\Public\NPVR\Log_yyyy-MM-DD_hh\hmm_ss, and it can then be perused at your leisure, or compressed and uploaded to this forum for the developers to peruse.

The application is completely open source and the code is available to download as part of the suite of tools that I have been developing to complement NextPVR. It can be found and downlaoded at my GitHub repository here:

https://github.com/ChaosMageX/NextPVR-Utilities

WARNING: USE THIS SOFTWARE AT YOUR OWN RISK. It is designed to directly mess with NextPVR's central recording service, but only to restart it if it has stopped. Still, Murphy's Law: What can go wrong, will go wrong. NextPVR itself has proven that to me time and time again. I've tried my best to fool proof it by ensuring that it can only run one instance at a time and always run with administrator privileges so it can successfully restart the recording service, but still, be wary.

If anything does go wrong, please let me know in a reply to this thread and I'll do my best to fix it in the code and upload a new version.

If you have any suggestions on how I can further improve this application and any new features I can add to it, please don't hesitate to let me know in a reply to this thread.

Installation is simple. Just extract the contents of the ZIP file to the directory of your choice, and begin running the application with administrator privileges. It should ask you for admin privileges from the start, but if it doesn't, it will simply refuse to run, and you'll have to right click it and choose Run As Administrator.

If you want, you can also right click the executable and choose Create Shortcut, and then move the created shortcut file into either

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp

or

C:\Users\<username>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

in order to get it to start up at the time you start your computer so that it can monitor NextPVR's recording service right from the start.

EDIT 9/23/2019: Added SecsToStart to the configuration file that comes with the application so that the seconds it waits at startup before monitoring can be adjusted for when it's run from Startup on computers where NextPVR takes longer than usual to start its recording service itself.

EDIT 9/24/2019: Added a "Backup NextPVR Logs Now" button so that users can backup NextPVR's logs into a separate timestamped button at any time with just a single click, in case they need to backup the logs for another reason besides the recording service crashing.

Since this is a change to the GUI, I think it warrants a new version, Version 1.1, which can be downloaded below.

EDIT 9/29/2019: Improved the internal handling of the application, so that its GUI is no longer stuck frozen and unusable while waiting on initial startup. These improvements are in version 1.1 only, so I'm removing version 1 now.

Hi! I'm trying out the new version of NPVR on Linux on a raspberry pi. Thanks Sub for all the awesome work!


I have NPVR set up and I can see my HDHomerunPrime and under Devices I can see the 3 tuners. I exported my channels in an XML file from my windows NPVR instance but when I use the file location and I click scan, it shows all the channels and not the subset of channels as well as the new names I have for those channels. Am I doing something wrong or does this feature not exist in NPVR currently on the webserver?

Thanks,
Flyingsubs