Closed paddatrapper closed 1 year ago
Weird, the child threads handling the output of the parent 'listening thread' should be joined and automatically stop after the process exited.
I'll check if I can reproduce.
Even exiting completely is a valid solution here - for me, it runs in Kubernetes, so gets restarted anyway. The issue is having the parent continuing, but not actually listening to the stream.
Could you check if the new release fixes your issue ?
Describe the bug
After ffmpeg exists 0, it is restarted, but exits 1. In this case, there is no attempt to restart again and earhorn continues to run without actually running ffmpeg. Logs are:
Environment