MythArchive encoder gives high cpu load with zero progress

[J.Pilk@…]

This has been reported for UK DVB-T2 and Comcast/ceton recordings. The cause appears to be the -copyts entry in the ffmpeg command line; the -r entry is probably unnecessary, too, and -b:v <value> seems to have little effect.

Often just -target ntsc-dvd or -target pal-dvd will give what is required.

​http://www.gossamer-threads.com/lists/mythtv/users/561824#561824

[J.Pilk@…]

Reported again from the US. Deleting the -copyts line seems to have worked.

​http://www.gossamer-threads.com/lists/mythtv/users/567922#567922

[Paul Harrison <pharrison@…>]

In b3c6b93176fb9998a7fe3ed120910ab2999ee1de/mythtv:

MythArchive?: Remove -copyts from the encoding profiles

There are reports this is causing more trouble than it fixes with current
ffmpeg. Fixes #12026.

[Paul Harrison <pharrison@…>]

In ecb3f1f78041b2f4fbd84b32e2971809fe1b2ccc/mythtv:

MythArchive?: Remove -copyts from the encoding profiles

There are reports this is causing more trouble than it fixes with current
ffmpeg. Fixes #12026.

(cherry picked from commit b3c6b93176fb9998a7fe3ed120910ab2999ee1de)

[jreiser]

mythffmpeg inifinite loop at end of input: context, debug info, gdb traceback, debug log

[jreiser]

This problem re-appears in mythtv-29.1+fixes.201812281328.af5d819~ubuntu18.04.1

The attachment above (ffmpeg.log) contains context, debug info, gdb traceback, and debug log (-debug_ts -v 48). The problem is reproducible every time on saved input (2183585792 bytes [2GB]).

If the cause cannot be identified and fixed, then it seems that a fail-safe could be detected by any one of:

1. Processing of frames after the maximum number of frames in the duration of the scheduled recording.
2. Processing more than 5 seconds of frames after End-Of-File on input.
3. Processing more than 5 seconds of frames with no writes to output file.

[jpilk]

I have a large collection of MythArchive? DVDs, but the last one was created in 2018 August and I suspect that it would take me some time to get back to an effective system based on current master.

I used only a small subset of the features offered. Any problem would cause failure with no easy way of re-using the results so far. So transcoding and cutting, if needed, were done first, and output was to an .iso file to be burned by K3B.

I rarely used HD input, but this sort of thing worked for me, for 1 video and 1 mp2 audio track. Rename the original recording to get it out of the way, and replace it.

ionice -c3 nice mythffmpeg -v "verbose" -i infile.xxx -target pal-dvd -qscale:v 3 -s 720x576 -acodec mp2 -b:a 192k -ac 2 -aspect 16:9 outfile.mpg

[Stuart Auchterlonie]

We have moved all bug tracking to github [1]

If you continue to have this issue, please open a new issue at github, referencing this ticket.

[1] - ​https://github.com/MythTV/mythtv/issues