Should v5 try to reconnect a scheduled recording?

[mvallevand]

Are you suggesting I'm a criminal, seriously?

Now I certainly wasn't talking about you at all or I wouldn't try to help you.

Martin

[markn62]

@mvallevand it seemed implied but fair enough. As I've mentioned earlier in this thread I am looking for either more reliable IPTV service or more reliable software. There are only 3 OTA channels here so my choice for perfect sources are limited. Since I can't find, nor can anyone suggest, highly reliable IPTV service I'm looking at how software handles the IPTV services that I know of that are less than perfect. I've tried four services and NextPvr is my 3rd software test drive. Sub offered to look into this so let's see what he has to say. Sub mentioned NextPvr should resume recording after a short stream interruption. I'm finding it isn't. This is the only matter left to discuss so how bout we keep this thread on topic. I know I'm not the only one with this concern. It's inherent.

[sub]

Sub offered to look into this so let's see what he has to say.  Sub mentioned NextPvr should resume recording after a short stream interruption. 

I'm 9000 miles away from my NextPVR development machine, so not in a position to look into anything right now.

[markn62]

@sub  Tried remuxing, doesn't reliably fix an m3u recorded file with corruption or bad index.  I find that recording an m3u stream typically finishes the recording to its end scheduled time but more likely has a index problems, or corruption where the audio/video desync's, or the video loops endlessly.  Bout 1 in 5 recordings.

In contrast, recording m3u8 most typically terminates the recording on the first encounter of any interruption in the chunked download and never restarts.  I don't see in the log the reason the download quits.

TvMosaic recorded the entire two hours as m3u8 but file had a bad index.  Couldn't play with Infuse.  I was able to play the non-remuxed version, using VLC, with difficulty by using a hyperactive slider to ff/rew.  The NextPvr recording was only useable in small pieces.

Below is an example of using NextPvr, w/Beast m3u8, to record an MMA fight, log attached.  Generally I don't see recordings fail this badly but it demonstrates why I am asking about NextPvr's ability to restart a recording after a short interrupt in the download either with m3u or m3u8.  Any suggestions would be appreciated.

Started recording UFC @ 2019-11-02, 17:00.
Quit recording @ 17:14:50
Cancelled failed recording and started new recording @ 17:22:30
Quit recording @ 17:24:45
Cancelled failed recording and started new recording @ 18:00:00
Quit recording @ 18:15:14
Cancelled failed recording and started new recording @ 18:18:02
Quit recording @ 18:33:30
Cancelled failed recording and started new recording @ 18:53:29
Finished recording to programmed end time @ 19:00:00

[sub]

m3u or m3u8

I assume you mean "ts or m3u8". IPTV providers supply an m3u playlist of channels, which contain either ts or m3u8 streams.

Started recording UFC @ 2019-11-02, 17:00.
Quit recording @ 17:14:50
Cancelled failed recording and started new recording @ 17:22:30
Quit recording @ 17:24:45
Cancelled failed recording and started new recording @ 18:00:00
Quit recording @ 18:15:14
Cancelled failed recording and started new recording @ 18:18:02
Quit recording @ 18:33:30
Cancelled failed recording and started new recording @ 18:53:29
Finished recording to programmed end time @ 19:00:00

What are those messages from? They don't look like NextPVR log messages.

[markn62]

Sorry for any confusion, yes ts & m3u8 or ts & hls. The messages are my own to explain what action I was taking relative to where to look in the attached log zip for a corresponding event.

[sub]

I'll try to reproduce it with m3u8/hls. Hopefully pulling the network cable for a few minutes is a close enough approximation.

[markn62]

Would think that would be a good simulation controlling how long the interrupt is vs how the process responds to a recording restart.  Since changing to a new source I'm getting much better performance. 18 hours of good recordings until this AM it quit abruptly @ 07:05:25, just over 1 hour into a 3 hr show, and didn't resume until a new scheduled program on the same channel started @ 09:00.

[markn62]

A 1 hr recording went 4 min last night & a 3 hr went 40 min this morning. They start but don’t always finish. About a dozen other recordings went fine.

[markn62]

I'll try to reproduce it with m3u8/hls. Hopefully pulling the network cable for a few minutes is a close enough approximation.

This remains my biggest struggle with using NextPvr.  TS corrupts on occasion but usually finishes recording. TLS fails almost every recording at some point in the scheduled time leaving partial recordings.  TLS never restarts.

Did pulling the network cable offer any insight?