You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I create this command to create a movie (mp4) with a frame rate of 60 and audio a file (I think that those are the key elements that causes the issue):
I similar issue appear to create a WEBM. In this case the files are different (with diff) but I can't see it.
Solution
In both cases, I only have to add -thread_queue_size 4096 in the ffmpeg comand to fix it. I can do it.
Doubt
My doubt is that I don't understand well what is going on, so I don't know if my solution may cause major problems later on or if there is no better solution.
I found an explanation here that it says "that your computer cannot keep up with encoding in real-time." I try the solution
-thread_queue_size size (input/output)
For input, this option sets the maximum number of queued packets when reading from the file or device. With low latency / high rate live streams, packets may be discarded if they are not read in a timely manner; setting this value can force ffmpeg to use a separate input thread and read packets as soon as they arrive. By default ffmpeg only does this if multiple inputs are specified.
For output, this option specified the maximum number of packets that may be queued to each muxing thread.
So, if someone has something to say, please let me know. I will start making the PR.
The text was updated successfully, but these errors were encountered:
Intro
I create this command to create a movie (mp4) with a frame rate of 60 and audio a file (I think that those are the key elements that causes the issue):
and I got the following message on the terminal:
[image2 @ 0x55e57165d400] Thread message queue blocking; consider raising the thread_queue_size option (current value: 8)
I similar issue appear to create a WEBM. In this case the files are different (with
diff
) but I can't see it.Solution
In both cases, I only have to add
-thread_queue_size 4096
in theffmpeg
comand to fix it. I can do it.Doubt
My doubt is that I don't understand well what is going on, so I don't know if my solution may cause major problems later on or if there is no better solution.
I found an explanation here that it says "that your computer cannot keep up with encoding in real-time." I try the solution
This is what the ffmpeg docs say:
So, if someone has something to say, please let me know. I will start making the PR.
The text was updated successfully, but these errors were encountered: