Filter Recordings

[jrockow]

sub
Let me start by saying this is not a request for you to change anything, it's just a question.
Is there a way, in the web UI, to display/filter the recordings according to the folders they were recorded in, as opposed to displaying all recordings that were made?
This is a feature I've been using in V4.

[BrettB]

Is there a way, in the web UI, to display/filter the recordings according to the folders they were recorded in, as opposed to displaying all recordings that were made?
This is a feature I've been using in V4.

Do you really mean in the new "web UI" or do you mean in the web app interface?

In the web app, I don't believe there is a way to do this.

However, in the web uiclient interface (http://server:8866/uiclient.html), you can go to the Recording screen, go to the hidden menu at the top, select Filter, and then select the recording destination to filter to. I'm not positive if this will work in the new icon view, but it definitely does for the list view. (And in a little limited testing I just did seems like it does change the display for the icon view so might be working there, too.) I did notice that in the web uiclient, after you select the filter directory, it gives a pop-up indicating that it is filtering to that directory, and that pop-up didn't seem to go away until I pressed a key.

[jrockow]

BrettB
Thanx for your response.
I'm just learning V5 and may have used the wrong description.
This is how I access the "web ui". (http://server:8866/index.html)

[BrettB]

BrettB
Thanx for your response.
I'm just learning V5 and may have used the wrong description.
This is how I access the "web ui". (http://server:8866/index.html)
If that's what you call the web app, how do you navigate; strickly mouse/keyboard or touch screen?

That is the web app. The web interface to the UI Client (at /uiclient.html rather than /index.html) is brand new (and probably still "beta"). But the UI Client backend server that it uses is the same that is used by uidroid, knewc, Roku, so it is very solid.

I'm not sure what you mean by "If that's what you call the web app, how do you navigate; strickly mouse/keyboard or touch screen?". The /index.html is the web app. Using it (keyboard, mouse, touch screen) would be however you normally do that with your web browser.

[jrockow]

BrettB
Thanx for your response.
I'm just learning V5 and may have used the wrong description.
This is how I access the "web ui". (http://server:8866/index.html)
If that's what you call the web app, how do you navigate; strickly mouse/keyboard or touch screen?

That is the web app. The web interface to the UI Client (at /uiclient.html rather than /index.html) is brand new (and probably still "beta"). But the UI Client backend server that it uses is the same that is used by uidroid, knewc, Roku, so it is very solid.

I'm not sure what you mean by "If that's what you call the web app, how do you navigate; strickly mouse/keyboard or touch screen?". The /index.html is the web app. Using it (keyboard, mouse, touch screen) would be however you normally do that with your web browser.

Thanx for clearing that up.
I'm trying to upgrade my V4 setup to V5, and I'm finding some things are different.
How do most people setup V5 for their living room TV and use a remote control?

[BrettB]

Thanx for clearing that up.
I'm trying to upgrade my V4 setup to V5, and I'm finding some things are different.
How do most people setup V5 for their living room TV and use a remote control?

I would say that "most people" use one of the clients for TVs. Fewer and fewer actually connect their actual server to a TV.

There are basically 2 "classes" of clients: (Remote) UI Clients and Native Apps.

UI Clients all have the same user interface which is actually generated by the server and sent to the client as screen images. The biggest advantages of them are:

1. The UI and user experience is basically the same no matter which H/W is used
   
2. The UI Client user interface "feels like" a traditional PVR or set-top box
   
3. You can use lots of different H/W including very inexpensive ($30-$50) H/W. (Note: Many of the streaming hardware devices have remotes with very limited keys which aren't particularly great for a PVR. But, for most of them, you can add a very full functional remote inexpensively.)
   
4. sub can add new features to back-end server and they are (generally) instantly available on all UI Client devices
   

Native Apps have the user interface generate by the app locally on the device and use API calls to access the NextPVR server backend as needed to get data only. These generally have user interfaces which "feel like" other apps on those devices. Typically this means more icon and single list based. These interfaces (and feature set) can vary significantly from device to device.

UI Clients currently available include:
knewc (in the remote UI mode) running under kodi
Roku
uidroid
nlite (the new version of nlite found as client.zip)

Native Apps currently available include:
AppleTV app
iOS app
sub's Android app
kodi (via the kodi NextPVR PVR add-on or via the knewc add-on in non-remote UI mode)

Personally, I "require" the UI Client user interface with it's PVR/set-top box look-and-feel. So, I've been using knewc running under Kodi on primarily Raspberry PIs for years (since v4 days). After Martin developed the Roku UI Client, that was becoming my new go-to. But then, he developed the uidroid client which is now my go-to. There are several very inexpensive Android TV based streaming devices available. My favorite right now is the TiVo Stream 4K because it has the best remote for PVR usage since it includes a full number keypad which is very useful for skipping by xx seconds, moving y% through lists, etc. and can also be overloaded with long-press options to turn color dots on/off, jump directly to screens like the TV Guide, What's New, Recordings, etc. But, as I said, you can get inexpensive "good" remotes to use with many other Android TV streamers. (I've got a few others, too.)

[jrockow]

BrettB

Thanx for the in-depth response; very good!
If I understand it, I guess what I've been using with V4 is a native app.
It appears I would still have this option with V5, using the desktop app included in the build.

One of my test systems has V5 installed on my NAS using Docker.
I liked the concept of this, but it rules out using the desktop app.

Thanx again; looks like I need to do more research.

[BrettB]

BrettB

Thanx for the in-depth response; very good!
If I understand it, I guess what I've been using with V4 is a native app.
It appears I would still have this option with V5, using the desktop app included in the build.

One of my test systems has V5 installed on my NAS using Docker.
I liked the concept of this, but it rules out using the desktop app.

Thanx again; looks like I need to do more research.

This discussion should really be moved to a new thread since it is not really related to the Filtering Recordings topic. Maybe sub can do that for us.

With V4, there was one NextPVR.exe image which included both the back-end server (typically running as a service) AND a native Windows front-end user interface. By default that front-end user interface would access NextPVR running on the same Windows machine as the back-end server. But, there was also a "client mode" which enabled the NextPVR.exe front-end interface to run on another Windows PC on the same network as the server.

With V5, one of sub's primary goals was to make the back-end server O/S independent--which he did extremely well. In that process, he did create a NextPVR.exe client image which would still work IF the client and back-end were both running on the same Windows machine. But that Windows client no longer supported the "client mode" because the server support for that no longer existed.

Now, the user interface generated by that NextPVR.exe front-end is basically the UI Client interface/user experience. So, if that is what you are used to and like, then you should look for a UI Client user client application.

Recently, sub made an updated version of nlite which runs on Windows, but unlike the NextPVR.exe client which is dependent upon running on the same machine as the server, this Windows version of nlite uses the UI Client interface so it can run on any Windows machine which has network access to the server. I would predict that with V6, there will no longer be a native Windows client that will run on the same Windows machine as the server and there will just be the new nlite Windows client. And that Windows client can access a NextPVR server running on any of the supported platforms.

[sub]

BrettB

Thanx for the in-depth response; very good!
If I understand it, I guess what I've been using with V4 is a native app.
It appears I would still have this option with V5, using the desktop app included in the build.

One of my test systems has V5 installed on my NAS using Docker.
I liked the concept of this, but it rules out using the desktop app.

Thanx again; looks like I need to do more research.

The desktop app is nextpvr.exe. It's only able to access a NextPVR server on the same machine.

For pretty much the same experience, but using v5 installed on your NAS, you can download https://nextpvr.com/client.zip, extract it some where on the windows PC you want to watch from, and run nlite.exe. It gives the same user interface as nextpvr.exe, but can be used with a different server on your network (your NAS server in this case)

[sub]

I'm trying to upgrade my V4 setup to V5, and I'm finding some things are different.
How do most people setup V5 for their living room TV and use a remote control?

If that machine is where your NextPVR server is installed, you can still just use nextpvr.exe like you have previously. It's pretty much the same as v4 was in the past.

If your server is on a different machine, you can run NLite.exe from https://nextpvr.com/client.zip.

If your TV doesn't have a PC connected, there are options for using Android or Apple TV or other clients.