Live TV timeshift misbehaving on Shield

[PeterWeb]

Your recordings as-at your last EPG update can be found at C:\Users\Public\NPVR\recording-backup.xml

Yes, the docs helpfully pointed me at that too, so all was well.

* No luck whatever getting my desired channel structure into v5 - there doesn't seem to be an "Import channels" function that matches the "Export channels" feature of v4. That feature creates channels-Other.xml, which has everything I'd like the channel setup to be. So that's a mess for now, but I'll sort it out eventually.

Above I said that since you're using an IPTV source, you're probably better off to set it up from scratch. There is some slight differences to the way IPTV channels are stored in v5, so you're better off just setting those channels up again.

Aye, I originally did as you suggested - since there was no other option anyway - but I sure wish I didn't have to. No doubt I'll be able to sort it out eventually through tedious renumbering, but at present it's a bit of a mess to say the least. I'm just trying to getting Matt's NZ TV and radio listings to sit together nicely, I'll probably get there ok if I start again in less of a hurry.

There's good reason to want to seamless upgrade that sort of config - but I understand that can be tricky to support at times.

To get the ball rolling, enable debug logging in kodi, restart the NextPVR (to reset the logs), reproduce that error above, then post those logs, and I'm sure he'll be able to check and give some advice when it's next in.

Understood, thanks. I couldn't find a debug log mode for v5 but this zipfile has the regular v5 logs and also contains debug logs for Kodi, which obligingly failed again in the same way:

I'll wait to hear from Martin when timing works for him.

Thanks again.

[sub]

* No luck whatever getting my desired channel structure into v5 - there doesn't seem to be an "Import channels" function that matches the "Export channels" feature of v4. That feature creates channels-Other.xml, which has everything I'd like the channel setup to be. So that's a mess for now, but I'll sort it out eventually.

Above I said that since you're using an IPTV source, you're probably better off to set it up from scratch. There is some slight differences to the way IPTV channels are stored in v5, so you're better off just setting those channels up again.

Aye, I originally did as you suggested - since there was no other option anyway - but I sure wish I didn't have to. No doubt I'll be able to sort it out eventually through tedious renumbering, but at present it's a bit of a mess to say the least. I'm just trying to getting Matt's NZ TV and radio listings to sit together nicely, I'll probably get there ok if I start again in less of a hurry.

There's good reason to want to seamless upgrade that sort of config - but I understand that can be tricky to support at times.

The reality is, NextPVR v5 is an entirely new app application, built in a different way to v4, and using different technologies.

That said, for the vast majority of users, you can just copy your C:\Users\Public\NPVR\npvr.db3 into your C:\Users\Public\NPVR-data directory, and your existing channels will be there and working. It'd probably even work for you with IPTV (which was the one device type that had a significant change to how channels are stored)

To get the ball rolling, enable debug logging in kodi, restart the NextPVR (to reset the logs), reproduce that error above, then post those logs, and I'm sure he'll be able to check and give some advice when it's next in.

Understood, thanks. I couldn't find a debug log mode for v5 but this zipfile has the regular v5 logs and also contains debug logs for Kodi, which obligingly failed again in the same way:

Debug mode is a Kodi setting. NextPVR logs are always in debug mode.

[PeterWeb]

That said, for the vast majority of users, you can just copy your C:\Users\Public\NPVR\npvr.db3 into your C:\Users\Public\NPVR-data directory, and your existing channels will be there and working. It'd probably even work for you with IPTV (which was the one device type that had a significant change to how channels are stored)

That did the trick, thanks!  (Stopped the service before the copy of course).

Noted that NPVR logs are always debug mode, Martin should hopefully find all he needs in that case.

[PeterWeb]

Just a quick report that the looping has been seen again with the v5 backend also. My wife noticed it after rewinding the Live TV a bit using the rewind (not skip-back) button, after watching for several minutes. Soon after she pressed play, it subsequently jumped back about four minutes further, i.e it seemed to have lost its place somewhat again.

[sub]

You could try to collect logs for that issue too.

You'll need to let us know what time it happened, so we know where we're looking in the logs.

[mvallevand]

For trick play with mpeg files I would never use ff or rewind on live files with http the small seeks won't be accurate enough

Martin

[PeterWeb]

For trick play with mpeg files I would never use ff or rewind on live files with http the small seeks won't be accurate enough

Martin

I'm not sure what you mean by "trick play with mpeg files" but I understand that skip is better than ff and rewind - only my wife uses those buttons. If I see the looping issue myself, I'll definitely try to collect logs.

Similarly for this issue, which I've seen happen more than once since I installed v5:

The Kodi NextPVR plugin can be unreliable on startup when using a v5 back end. The plugin gives a PIN error which is only resolved when I reset the v5 Access PIN to 0000 using the web UI, then exit and restart Kodi once again. Then it connects just fine. This was never an issue with the v4 back end running on the same server.

It's not that the PIN was ever anything different, it's just that the plugin fails to load until I manually re-enter 0000 as the PIN - it's as if the back end has spontaneously changed/forgotten the PIN, or some such.

I should be able to upload logs for this issue tomorrow.

[mvallevand]

For the pin issue make sure you never save passwords in the browser and remove saved sessions just use the remember me check box.

The trick mode is digital files don't really go ff or rewind the play in mini skips.


Martin

[sub]

As Martin says, the pin issue is probably something to do with the browser seeing the pin field is set as "a password field" so that it shows asterisk characters instead of clear text, and your browser is getting smart and trying to put a password in there replacing your pin. Which browser are you using? (firefox seems to be the most painful for this)

[PeterWeb]

As Martin says, the pin issue is probably something to do with the browser seeing the pin field is set as "a password field" so that it shows asterisk characters instead of clear text, and your browser is getting smart and trying to put a password in there replacing your pin. Which browser are you using? (firefox seems to be the most painful for this)

Thanks, both of you. I've been using FF and Chrome, latest Windows versions. I understand what you're describing as a possible cause; I've seen that sort of thing happen with PIN fields for other systems and usually notice and prevent it.

Since I don't really have cause to use the browser after the initial config (except to resolve this issue) I'll keep a close eye out to see whether there's any correlation that suggests another cause. Hopefully not.