We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi.
I'm having a issue with ffmpeg and bmdplay.
The command line is:
ffmpeg -i "udp://@239.50.53.9:5501?buffer_size=262144?fifo_size=4525000&overrun_nonfatal=1" -c:v rawvideo -s:v hd1080 -c:a pcm_s16le -ar 48000 -f nut -write_index 0 - | bmdplay -m 7 -C 0 -b 4000 -f pipe:0
I have 4 processes like this, each reading a multicast stream and sending it to a Blackmagic Decklink Duo 2 output.
After some time, one or two of the processes starts eating all the RAM, and I get this message over and over, until the machine hangs:
5526 storing 0x6063a0, videoqueue - is the input faster than realtime?
Any idea on what is causing this?
Thanks in advance for any help you can give me.
mjrduarte
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi.
I'm having a issue with ffmpeg and bmdplay.
The command line is:
ffmpeg -i "udp://@239.50.53.9:5501?buffer_size=262144?fifo_size=4525000&overrun_nonfatal=1" -c:v rawvideo -s:v hd1080 -c:a pcm_s16le -ar 48000 -f nut -write_index 0 - | bmdplay -m 7 -C 0 -b 4000 -f pipe:0
I have 4 processes like this, each reading a multicast stream and sending it to a Blackmagic Decklink Duo 2 output.
After some time, one or two of the processes starts eating all the RAM, and I get this message over and over, until the machine hangs:
5526 storing 0x6063a0, videoqueue - is the input faster than realtime?
Any idea on what is causing this?
Thanks in advance for any help you can give me.
mjrduarte
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: