Recording stuck in loop

[Gmjh]

Yes you can change that yourself that is the default.  That way you will get padding if there isn't anything being recorded.

Martin.

Changing the padding to zero on both settings as resolved the issue. Thanks very much.

[Gmjh]

It says 'max connections 32'. I can't understand that. Who ever has 32 connections to an IPTV service.

People that are using freely available IPTV services, and not paying for a subscription, have effectively no connection limits.

ie, here in New Zealand all our main broadcast channels can be accessed over IPTV without connection limits




Hello again. I had thought this issue was resolved, and I haven't tried a recording for quite a while. I now find the issue is exactly the same, everything plays in a one or two minute loop. The log should show that this happens on the Kodi TV app, and also on the nextpvr player. Thanks very much

[mvallevand]

Certainly one timing file had for Antiques Roadshow was pure junk which matched the start of the recording. Are you using your IPTV on any other client?

Also it seems you m3u file could be out of sync with your provider you might need to reload everything.

<l>
<id>3818545</id>
<name>Channel No Longer Available</name>
<description>This channel is no longer available.</description>
<start>1756573200000</start>
<end>1756587600000</end>
<firstrun>true</firstrun>
</l>

Also see if your provider offers m3u8 files instead of .ts direct.

Martin

[Gmjh]

Certainly one timing file had for Antiques Roadshow was pure junk which matched the start of the recording.  Are you using your IPTV  on any other client?

Also it seems you m3u file could be out of sync with your provider you might need to reload everything.

<l>
  <id>3818545</id>
  <name>Channel No Longer Available</name>
  <description>This channel is no longer available.</description>
  <start>1756573200000</start>
  <end>1756587600000</end>
  <firstrun>true</firstrun>
</l>

Martin

I don't know what you mean by pure junk. I set it for the correct recording time and it started at the correct recording time. The m3u file is the same one I'm using on numerous other applications, and it is up to date. I don't know why the channel is showing as no longer available, the channel is BBC one, which is fully playable on next PVR and all other applications. It is possible that I may have played something during this recording by mistake. I can't say for sure. But overall I'm quite confused by your reply.

[mvallevand]

The logs say it all, a good recording would have the time codes incrementing one second at at time. Garbage in garbage out. The recordings shows the input stream looping from multiple IP addresses.

Code:

2025-08-31 15:23:27.130    [WARN][173]    clock jump of 50960.591478 seconds
2025-08-31 15:23:27.130    [WARN][173]    clock jump of -18.439999999995052 seconds
2025-08-31 15:23:27.130    [WARN][173]    clock jump of -20.479999999995925 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of 21.359999999993306 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -19.359999999993306 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -19.840000000003783 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -25.31999999999971 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -28.159999999996217 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -20.200000000004366 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -21.080000000001746 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -21.239999999997963 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -21.279999999998836 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -19.75999999999476 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -26.640000000006694 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -27.92000000000553 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -18.839999999996508 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -21.040000000000873 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -21.720000000001164 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of 55057.886211000005 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -55104.046211 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -21.279999999998836 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -21.200000000004366 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -19.239999999997963 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -18.400000000001455 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of 55062.206211000004 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -55104.806211 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -18.520000000004075 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -21.07999999999447 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -21.360000000000582 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -25.599999999998545 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -21.039999999993597 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -27.19999999999709 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of 55057.566211 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -55105.566211000005 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -21.040000000000873 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -21.12000000000262 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -19.479999999995925 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -21.60000000000582 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of 55062.766211 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -55105.406210999994 seconds
2025-08-31 15:23:27.134    [WARN][173]    clock jump of -21.080000000001746 seconds
2025-08-31 15:23:27.134    [WARN][173]    clock jump of -20.39999999999418 seconds
2025-08-31 15:23:27.134    [WARN][173]    clock jump of -21.19999999999709 seconds
2025-08-31 15:23:27.135    [WARN][173]    clock jump of -17.160000000003492 seconds
2025-08-31 15:23:27.136    [WARN][173]    clock jump of -19 seconds
2025-08-31 15:23:27.136    [WARN][173]    clock jump of 55064.64621100001 seconds
2025-08-31 15:23:27.136    [WARN][173]    clock jump of -55104.886211 seconds

Martin

[Gmjh]

The logs say it all, a good recording would have the time codes incrementing one second at at time.  Garbage in garbage out.  The recordings shows the input stream looping from multiple IP addresses.

Code:

2025-08-31 15:23:27.130    [WARN][173]    clock jump of 50960.591478 seconds
2025-08-31 15:23:27.130    [WARN][173]    clock jump of -18.439999999995052 seconds
2025-08-31 15:23:27.130    [WARN][173]    clock jump of -20.479999999995925 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of 21.359999999993306 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -19.359999999993306 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -19.840000000003783 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -25.31999999999971 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -28.159999999996217 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -20.200000000004366 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -21.080000000001746 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -21.239999999997963 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -21.279999999998836 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -19.75999999999476 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -26.640000000006694 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -27.92000000000553 seconds
2025-08-31 15:23:27.131    [WARN][173]    clock jump of -18.839999999996508 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -21.040000000000873 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -21.720000000001164 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of 55057.886211000005 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -55104.046211 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -21.279999999998836 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -21.200000000004366 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -19.239999999997963 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -18.400000000001455 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of 55062.206211000004 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -55104.806211 seconds
2025-08-31 15:23:27.132    [WARN][173]    clock jump of -18.520000000004075 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -21.07999999999447 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -21.360000000000582 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -25.599999999998545 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -21.039999999993597 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -27.19999999999709 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of 55057.566211 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -55105.566211000005 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -21.040000000000873 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -21.12000000000262 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -19.479999999995925 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -21.60000000000582 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of 55062.766211 seconds
2025-08-31 15:23:27.133    [WARN][173]    clock jump of -55105.406210999994 seconds
2025-08-31 15:23:27.134    [WARN][173]    clock jump of -21.080000000001746 seconds
2025-08-31 15:23:27.134    [WARN][173]    clock jump of -20.39999999999418 seconds
2025-08-31 15:23:27.134    [WARN][173]    clock jump of -21.19999999999709 seconds
2025-08-31 15:23:27.135    [WARN][173]    clock jump of -17.160000000003492 seconds
2025-08-31 15:23:27.136    [WARN][173]    clock jump of -19 seconds
2025-08-31 15:23:27.136    [WARN][173]    clock jump of 55064.64621100001 seconds
2025-08-31 15:23:27.136    [WARN][173]    clock jump of -55104.886211 seconds

Martin

The logs say nothing to me. And so far, neither are you really. What is the cause of this?

[mvallevand]

A bad input stream or crappy provider. I can't explain why one source stream is coming from multiple IP addresses unless as you suggested you could have used the provider URL in another app at the time. The results are similar to when you had issues with padding and one source.

Martin

[Gmjh]

A bad input stream or crappy provider.  I can't explain why one source stream is coming from multiple IP addresses unless as you suggested you could have used the provider URL in another app at the time.  The results are similar to when you had issues with padding and one source.

Martin

Okay well it's neither a bad input stream or a crappy provider. So it might be caused by me mistakenly watching something and recording. Either way, I won't be asking for help on this forum anymore.