Status of TVos app

[Allan]

Is the TVos app still in development? If so, is commercial skipping a planned feature?

Also, how well does it currently handle watching in progress shows? So far, the closest I have found to handling viewing of recordings that are in progress is the the Kodi plugin (the only issue being it gets confused by com skip information that is provided and accessed during the broadcast - workaround is to post process comskip)

Thanks.

[sub]

Is the TVos app still in development?

No, not really. It's been a few years since any new features were added to it.

If so, is commercial skipping a planned feature?

It shows comskip markers, but doesn't auto skip them. I have no plans to make changes to further changes at this stage. Available time is my main reason. Holding down a job, busy family, and NextPVR doesn't leave me with a lot of time for focusing on the iOS/tvOS/Android client applications.

[Allan]

Can anyone comment on how well the TVos app currently handles watching in progress shows?

[mvallevand]

I think someone already commented if you do a forum search https://forums.nextpvr.com/showthread.ph...n-progress

Martin

[timbo3344]

Can anyone comment on how well the TVos app currently handles watching in progress shows?

While I do own the TVos app to support the development of NPVR everywhere, I don't really use the app for watching content.  I find it much better to point Plex to the NPVR recording directory and use Plex to watch the content.  What NPVR does best is record content.  What Plex does best is allow you to see that content!

[sub]

There is actually a slightly later tvOS app, which supports thumbnails. I did check it with in-progress recordings and it skipped fine. I'll try to find some time to get that released.

[Allan]

That would be great! An appletv frontend that works well is the only thing my setup is missing.

[Allan]

There is actually a slightly later tvOS app, which supports thumbnails. I did check it with in-progress recordings and it skipped fine. I'll try to find some time to get that released

When you are on that, there are a couple of issues that I have noticed with 3.5

I have identified a couple of issues.

1. When logging in for the first time, the search for servers offered me only the remote login IP address of the backend computer to my office network over a VPN. Here's the handshake, though, from the log:

Code:

2025-01-13 22:15:43.939    [DEBUG][13]    Received broadcast from 10.xxx.xxx.93:49391 : Anybody Out There?
2025-01-13 22:15:43.968    [DEBUG][13]    Local IP Address: 10.xxx.xxx.120
2025-01-13 22:15:43.968    [DEBUG][13]    Local IP Address: 192.168.xxx.xxx
2025-01-13 22:15:43.972    [DEBUG][13]    address: 192.168.xxx.xxx

As noted, I was not even offered the correct 10.xxx.xxx.120 IP address. Although this issue arises using the frontend, I gather it is a backend issue.

2.  I manually entered the correct IP address, but after I disconnected from the VPN, the TVos app continued offering me 10.xxx.xxx.120 and also 10.xxx.xxx.120 (same IP twice.

3. I deleted the app and started over. Now I was offered only the correct IP address, but the app persisted in scanning for servers each time I did what one does in every app to exit - the back button. May I suggest that this setting should be manually accessible under the settings tab.

Thanks.

[mvallevand]

The discovery issue was reported here for uidroid https://forums.nextpvr.com/showthread.ph...#pid598212 but that will apply to all devices. Your xxx's aren't useful what you are saying is the discovery comes in on one subnet that that subnet host IP should be returned.

Martin

[Allan]

Your xxx's aren't useful what you are saying is the discovery comes in on one subnet that that subnet host IP should be returned.

I do not understand what you mean. 

What I was trying to convey was that the backend identified two IP addresses,
• one of which was for my remote connection to my office over a VPN
• the other, which was my actual, correct, local IP address.

Then, the backend responded with only the incorrect IP address, rather than considering which or these was correct (given that only one was on the local subnet), or simply offering both to the frontend.