On 7/20/2020 9:57 AM, Simon Roberts wrote:
Splitting this into five separate commands, generating five separate
output files, running them in background simultaneously, works without
any overruns, dropped frames, or any other complaints.
This more suggests either a threading/process management issue within ffmpeg
or that the underlying OS is starving the ffmpeg process for resources.
(IIRC, some codecs/etc are single-threaded.)
Which OS?
What are the CPU/memory usages in each running scenario?
Try capturing uncompressed video to the null device; then try encoded to a
null device; that should show if there's an issue with the encoder or
elsewhere. Try using a different encoder, too, for test.
And please give us the cmd output (again)- at least with the headers, stream
info, and a few error messages.
Later,
z!
_______________________________________________
ffmpeg-user mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
