Still happening with version 2019.05.24.1933
Letting an H.264 remux play in the web UI from the beginning without any trick play (pause/skip fwd/skip back) it stopped (stuck) at 11 min, 37 secs.
Appears the value ViewPosition: "9m0s" is incorrectly calculated by assuming each hls segment is exactly 1 sec long, when in reality the segment sizes vary from 0.016678 to 2.001333 secs long.
540 segemnts were output (540 * 1 sec each) = 540 secs or 9m0s
m3u8 playlist generated by ffmpeg in the streaming directory shows segement lengths
#EXTM3U
#EXT-X-VERSION:3
#EXT-X-TARGETDURATION:2
#EXT-X-MEDIA-SEQUENCE:0
#EXTINF:1.984656,
stream0.ts
#EXTINF:2.001333,
stream1.ts
#EXTINF:2.001333,
stream2.ts
#EXTINF:2.001333,
stream3.ts
#EXTINF:2.001333,
stream4.ts
#EXTINF:1.150767,
stream5.ts
#EXTINF:0.850567,
stream6.ts
#EXTINF:2.001333,
stream7.ts
#EXTINF:2.001333,
stream8.ts
#EXTINF:0.350233,
stream9.ts
#EXTINF:1.651100,
stream10.ts
#EXTINF:0.216811,
stream11.ts
...
...
#EXTINF:0.483656,
stream533.ts
#EXTINF:1.517678,
stream534.ts
#EXTINF:0.983989,
stream535.ts
#EXTINF:1.017344,
stream536.ts
#EXTINF:0.950633,
stream537.ts
#EXTINF:1.050700,
stream538.ts
#EXTINF:0.116744,
stream539.ts
Curious (but unable to test) if removing the ffmpeg parameter hls_time 1 (to let it default to 2+ second segments) or removing hls_flags split_by_ts (to let it split segments at reference frames) would help.
Not sure where that ViewPosition variable is coming from, ffmpeg or Channels. The web player knows the current view position being played, but appears Channels DVR doesn't so it doesn't unpause the remux and the player eventually hits the last remuxed hls segment and appears to be buffering. Only way out is to pause, stop and then continue play.
