NextPVR server on LibreElec

[mvallevand]

OK I thought you were mounting your Windows drive as a share not as physical drive, hopefully that will only be temporary as you migrate to a safe Linux filesystem.

Martin

[jcjefferies]

Martin
The LibreElec server seems to be working correctly and am collecting “Recently Deleted” items from the “FreeSat” EPG ready for the EPG changeover when the next version of NextPVR is released and I change from XMLTV EPG to the Freesat(UK) EPG.

However I have found a “Date Format” problem! The LibreElec server and the LibreElec clients are all set to UK(24) under Regional settings.

Looking at the LibreElec server web page both the Pending Recordings and Recent Recordings all have the correct Date format dd/mm/yyyy.

The TV Guide on the server’s web page use 12 hour clock but on the LibreElec clients the 24 hour clock is used as specified!

However on the “NextPVR New Client” client of the LibreElec server the date format on files under “Recordings” and “Scheduler” is mm/dd/yyyy!

I have tried two clients both of which show the correct date when connected to the old Windows server but incorrect date when connected to the LibreElec server! All have been rebooted several times!

I repeated it on a second PC but this time the NextPVR server and NextPVR client were running on the same computer running LibreElec. A pending recording had mm/dd/yyyy format as the date when viewed on the client. The same pending recording viewed via the server web page has the normal date format!

However I disabled “TVheadend” and “NextPVR New Client” and install the “NextPVR PVR Client” which I have never previously installed. Listings under “Recent Recordings” and “Timers” all seem to have the correct date format. It looks like the date problem is with “NextPVR PVR New Client”!

Looking at “NextPVR PVR Client” existing “Timers” seem to be working but should I be able to edit “Timer Rules” entries? I seem to be able “Add Timer” but not edit existing timers. I have never used this client before so don’t know what should happen!!


Chris

[mvallevand]

I don't know what you mean. Are you talking about pvr.nextpvr and UI clients like knewc? Sub has a mix of hard coded date and formats and os format so you have to be specific for him to reply it is not a client issue.

UI clients including NextPVR.exe don't have much flexibility on editing timer types.

Either way OS defaults on Windows and Linux are different

[jcjefferies]

There seems to be no "Date" problem on the LibreElec NextPVR server as they all seems OK when dates are viewed via the web page!

The date problem seems to be with the "NextPVR New Client" when connected to the LibreElec NextPVR Server. Its the only client I have ever used for many years and is OK when connected to a Windows server!

Chris

[mvallevand]

I already explained the user understanding issue with UI clients like knewc Did you have the example for sub I asked for?

Martin

[mvallevand]

Looking at “NextPVR PVR Client” existing “Timers” seem to be working but should I be able to edit “Timer Rules” entries? I seem to be able “Add Timer” but not edit existing timers. I have never used this client before so don’t know what should happen!!

Sorry I was away and replying by phone.  On recurring recordings since enter opens the individual scheduled items, you have to use Kodi the context key to get more menu options.  The default on the remote is long press OK.  The context menu is very import in Kodi and you might want to read up on it on the Kodi wiki.

 In pvr.nextpvr you actually have more ways of editing timer rules then you do with other NextPVR clients since the types can sometimes be changed.  

Martin

[sub]

What is the "NextPVR New Client"? You might need to post a screenshot so we can see where you mean

For the most part NextPVR just relies on the system short/long date and time formats, which ultimately just comes down to your regional settings / locale configured in your operating system.

[mvallevand]

I figure he means knewc the Kodi UI client

There is a lot of user confusion because users expect the Windows ShortTimeString and Linux ShortDateString to look the same when in fact even in Windows the default with LocalSystem account and the user can be different. Jaggy's post here shows that https://forums.nextpvr.com/showthread.php?tid=65666  The API documentation clearly indicates there is an OS difference and no bug in NextPVR and certainly not in the UI client itself.

The recordings2.xml he points to with the @period field with Yesterday, Today and Tomorrow  etc shows both short date and short time format difference well on Windows and Linux.  I can't find the definitive explanation of how a user can set the short date and time in Linux or Docker.  It relates to locales and I figure the LC_TIME setting.

For LibreELEC this may require a user post since then LE GUI allows some short date and time formatting but I don't know if that is at the OS level. There is a locale service addon that might change it but I can't tell if netcore will read it this way.


#LC_TIME=en_GB.UTF-8 date +%x
30/08/24
#LC_TIME=en_GB.UTF-8 date +%X
20:55:01

#LC_TIME=en_US.UTF-8 date +%x
08/30/2024
#LC_TIME=en_US.UTF-8 date +%X
08:55:29 PM

# LC_TIME=en_CA.UTF-8 date +%x
2024-08-30
LC_TIME=en_CA.UTF-8 date +%X
08:56:00 PM


Martin

[jcjefferies]

Sorry for the delay as was unwell!!

The only NextPVR client I have ever used on LibreElec is installed as "NextPVR New Client" under "Program Add-ons"

"Did you have the example for sub I asked for?" What form of example is wanted? Something as simple as a screenshot or some of the logs?

Screenshot Enclosed.
LibreElec server set to UK(24) and short date set to (DD/MM/YYYY)
Screenshot taken on Windows running Nlite connected to LibreElec server.

Chris

[mvallevand]

Right that is knewc https://forums.nextpvr.com/showthread.php?tid=60309 which is a UI client. I understand the issue but it is not a NextPVR issue.

Did you install the locale service addon in LibreELEC I referenced in my last post and configure it too?

Martin