Status of TVos app

[mvallevand]

I was just saying you were highlighting the machine's IP and not the subnet, NextPVR needs to reply with the right subnet IP. This is important because with your unusual networking you have two 10 subnets configured plus 192.168.xxx

Martin

[Allan]

Regarding playback of in progress recordings, here's what happens with TVos UI v. 3.5.

1. Start watching X minutes after the recording begins.
   
2. All is well until the X minute mark. Playback is fine, skipping is fine.
   
3. At the X minute mark, all hell breaks loose. Playback spontaneously jumps to another point in the recording, rather than continuing, timing is reported incorrectly and skipping is unusable. As far as I could tell, there was no way to continue playback beyond X minutes without exiting playback, restarting and skipping to the desired location.
   
4. If playback is restarted before recording is complete, problem #3 is repeated.
   

This behaviour, unfortunately, renders 3.5 unusable. I hope this has been fixed in the pending update.

[mvallevand]

You have now told us five times on 3 thread that in-progress recordings don't work on the Apple TV app and sub is aware.

We get it.

Martin

[Allan]

NextPVR needs to reply with the right subnet IP. This is important because with your unusual networking you have two 10 subnets configured plus 192.168.xxx

I have only one 10.x.x.x subnet configured. Every single device on my network is on that subnet.

The 192.168.x.x IP address is only when I am connected remotely to my office.

[Allan]

You have now told us five times on 3 thread that in-progress recordings don't work on the Apple TV app and sub is aware.

I bought it yesterday and reported the issue today, once, for the first time. I feel the information I provided was useful, because it was very specific about how to invoke the problem.

[mvallevand]

My mistake you have been complaining about the lack of in-progress on your Apple TV for so long I was getting dizzy. You also duplicated the report on the UDP discovery not working (it's the same on uidroid and Apple) I just feel these points are helping.

Still sub and others already told you it didn't work so just wait to see if sub releases something.

[Allan]

Martin, I have not been "complaining…for so long" about an app I had not even purchased until yesterday, and the reason I posted was because the other day sub said this:

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

Sub doesn't have to do anything, but it is not clear what his testing entailed, and he won't be able to test for the problem I experienced without details on invoking them.

In my view, my posts in these forums have been civil and thoughtful, and I would very much appreciate being able to post without the too frequent uncivil and unhelpful retorts.

[mvallevand]

I think things started badly when you didn't seem to accept the possibility of a local issue for your signal crash yet you couldn't set up Kodi logging properly to prove that. My macOS testing has been stellar and I wrote a login/logout script that ran for hours. Then things went downhill when you were telling me that I hard coded your 10.37 IP address int uidroid. since for me it was server-side.

I apologize again for today's comments. This discussion goes back to your initial comments on not being able to skip in MrMC since I still believe the a really good long term solution for you is to get Kodi running on you Apple TV since you have the skill.

I agree it is better not to continue our discussions we are not cooperating at all.

Martin

[Allan]

I'm sorry for my incorrect assumption about hard coding in the 10.37.x.x IP address, and meant no offence.

I did turn on debug logging and verbose logging of the PVR component from the Kodi GUI. It just didn't work. I was not depriving you, intentionally or stupidly, of the logs you requested. And, if you review the actual discussion about about my NextPVR process being killed, you all see that your characterization is incorrect. I stated facts, being the timing correlation of Kodi exiting and the kill signal, but drew no conclusion. I have always accepted that this timing correlation I reported, while worth noting, could merely be a coincidence. Indeed, the developing evidence points away from Kodi. Among other things, there has been no kill since I started launching NextPVR with a launchagent rather than in the terminal, over a week ago.

Finally, I appreciate that you have put a lot of good work into this project, that it may well feel thankless from time to time and even a rigidly factual issue report may feel like a personal criticism. I assure you that I had no such intention.

[Allan]

Mystery solved.

I am running parallels on the same machine as the NextPVR backend, and parallels creates a bridged network to the VM. If parallels is running, even if no VM is running, ifconfig (and nextpvr server) will see the address to the bridge. 

Similarly, when I was connected to a remote network over a VPN, nextPVR was detecting the IP address assigned by the remote firewall.

If I quit parallels and the vpn, nextpvr returns the correct address of the nextpvr server.