.TS File Problem

[BrettB]

Could it be added as a hidden menu option for recordings?  I envision trying to watch a recording, seeing it has issues, selecting to remux it in the background, watch another recording and then, come back and watch the now fixed recording.

That sounds good but many people don't use NextPVR.exe or UI clients.  v4's Timing.info was actually a good workaround for the ts container, and worked pretty well on on bad recordings.  I think a byterange m3u8 file might be just as effective for non-transcoding clients that support.

Martin

I do like this idea. Most of my recordings don't need remuxing. But there definitely are occasionally ones where the timeline is messed up. Having an easy way to request a messed up one to be remuxed once it's discovered would be a nice alternative.

[ElihuRozen]

Could sub support something like http://localhost:8866/service?method=sys...&oid=12345 ? Then, the hidden menu item would call that.

Maybe have the method name be configurable in config.xml. That way if Brett & I want to be able to call remux, we could do that, but somebody else could have it transcode. I don't think it would be a security issue since you would need access to config.xml to change it & you could always manually type in the URL anyway.

[mvallevand]

Yes via Kodi I could add another context menu selection to do something like that. Ideally I'd queue mine for updating overnight if I could since I would have deferred it anyway.

Ultimately I would think NextPVR is better remuxing everything to mp4 under it's control. Be far the biggest recurring issues over all my years here is playback issues after the seek and a seekable container should help on all platforms.

Martin

[BrettB]

Yes via Kodi I could add another context menu selection to do something like that.  Ideally I'd queue mine for updating overnight if I could since I would have deferred it anyway. 

Ultimately I would think NextPVR is better remuxing everything to mp4 under it's control. Be far the biggest recurring issues over all my years here is playback issues after the seek and a seekable container should help on all platforms.

All of my new recordings are being remuxed to mp4 (for the Roku) right now anyway. I guess in theory, when I find a "bad" recording, I could manually go to the server and delete the .ts file to force the non-Roku UI clients to use the .mp4 version. I hadn't specifically thought about doing that.

[jobby99]

Thank you! I just remembered that and put the fix in. Maybe, if we had configuration change log or something people would not forget that they configured something causing the problem. I have autoimmune disorder and that happens quite a lot with brain fog. I have to design systems around myself to make them idiot proof, unfortunately.