On Raspberry Pi 4, the hardware encoder may fail spontaneously after several weeks of uptime, and the ffmpeg process accessing it cannot be killed. The only known remedy is to reboot. At present, Mr. OTCS will attempt to restart encoding repeatedly and never succeed until it is killed, generating warning (not error) messages that flood the e-mail daemon.
On Raspberry Pi 4, the hardware encoder may fail spontaneously after several weeks of uptime, and the ffmpeg process accessing it cannot be killed. The only known remedy is to reboot. At present, Mr. OTCS will attempt to restart encoding repeatedly and never succeed until it is killed, generating warning (not error) messages that flood the e-mail daemon.