In-Progress Record Seek/Skip Broken Since 3.2.28

September 5, 2017

I've noticed that as of late an active recording will no longer seek correctly and leads to the following:

A) When seeking you get sent back to the beginning of the recording

When seeking you get sent to a point very early in the recording

Once the recording has completed all seeking works as it should.

This is with the default .ts files, enabling the conversion to MKV on the fly causes other issues.

I tried to reproduce just this action in my log(s) which are attached.

In this example I have recorded ~5 minutes of recording, however when I go to seek I can get to ~1:00, and every time I try to seek I get stuck at that exact point (repeat at each seek attempt).

The WebUI shows the duration of the recording (in this example) as the same part it gets stuck at, but that is not always the case.

Also, this recording is incorrectly probed as interlaced, which it is not (it is 720P, not 720i).

All options set to default as far as I know.

Edit: Added logs from last night as well, this media is also probed incorrectly (720p probed as 720i), that log is much larger, the issue will be towards the end of the log file, that log is "server-63640121517", with a transcode of "ffmpeg-transcode-12241e8f...".

server-63640226834.txt

ffmpeg-transcode-7eb441bb-9cd8-4196-88a1-a88e35396d8f.txt

ffmpeg-transcode-2fb281d5-e343-4ba7-b693-df96cd6f75d9.txt

ffmpeg-transcode-0ca26c1d-5159-4298-b4f4-c0a96fddd0a4.txt

server-63640121517.txt

ffmpeg-transcode-12241e8f-b3b2-4f3b-a960-86faac3f7f68.txt