-
Notifications
You must be signed in to change notification settings - Fork 316
Error "Process ffmpeg hasn't written in 2 seconds, publishing periodic update" #563
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
That usually means the server is not powerful enough to process the data at realtime speed. |
@saghul repeated stream launches without restarting the recorder no longer cause this error. The error occurs only the first time |
Is the error fatal? |
@saghul logs are not recorded for the first time and this is bad, we want to understand the reason |
All it means is that ffmpeg didn't make progress in 2 seconds. Startup could be slower so unless you see an actual problem this should be harmless. If you do see it while the stream is running, it could imply a performance problem. |
@saghul If logs are not written, then I see the problem that the stream is interrupted. If I start the stream a second and subsequent times, it does not interrupt. |
After starting the container with a replaced ffmpeg, the first run always results in no logs being written to ffmpeg0.txt, and after 3 minutes, it crashes completely. |
Hello.
We use Kinescope a streaming platform, not YouTube, and we created a script for this:
This script run default ffmpeg named ffmpeg1.
At the first launch, logs are not written and an error occurs "Process ffmpeg hasn't written in 2 seconds, publishing periodic update".
When I restart the stream, everything works fine, but sometimes the CPU loads 100%.
What could be the reason?
The text was updated successfully, but these errors were encountered: