"buffer queue overflow, dropping" error in ffmpeg on windows

Support
1

As per this discussion we have updated the Animator to match the encodings used in Screen Capture module. However, this resulted in a repeatable error in ffmpeg encoding (see video below). Same happens in Screen Capture when the number of images are set to maximum.

Curiously this only happens on windows, mac’s doesn’t seem to be affected.

ffmpeg standard output:
ffmpeg error output: ffmpeg version 3.2.4 Copyright (c) 2000-2017 the FFmpeg developers
built with gcc 6.3.0 (GCC)
configuration: --enable-gpl --enable-version3 --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-zlib
libavutil 55. 34.101 / 55. 34.101
libavcodec 57. 64.101 / 57. 64.101
libavformat 57. 56.101 / 57. 56.101
libavdevice 57. 1.100 / 57. 1.100
libavfilter 6. 65.100 / 6. 65.100
libswscale 4. 2.100 / 4. 2.100
libswresample 2. 3.100 / 2. 3.100
libpostproc 54. 1.100 / 54. 1.100
Input #0, image2, from 'C:/Users/amaga/AppData/Local/Temp/Slicer-zwrdHG\Slicer-%04d.png':
Duration: 00:00:12.00, start: 0.000000, bitrate: N/A
Stream #0:0: Video: png, rgb24(pc), 640x480, 25 fps, 25 tbr, 25 tbn, 25 tbc
Output #0, gif, to 'C:/Users/amaga/Desktop/after.gif':
Metadata:
encoder : Lavf57.56.101
Stream #0:0: Video: gif, pal8, 640x480, q=2-31, 200 kb/s, 60 fps, 100 tbn, 60 tbc (default)
Metadata:
encoder : Lavc57.64.101 gif
Stream mapping:
Stream #0:0 (png) -> palettegen
Stream #0:0 (png) -> paletteuse:default
paletteuse -> Stream #0:0 (gif)
[Parsed_paletteuse_1 @ 0000000000e1e020] [framesync @ 00000000029300a8] Buffer queue overflow, dropping.
Last message repeated 71 times
frame= 0 fps=0.0 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= 0x
[Parsed_paletteuse_1 @ 0000000000e1e020] [framesync @ 00000000029300a8] Buffer queue overflow, dropping.
Last message repeated 162 times
[Parsed_palettegen_0 @ 0000000000e1dee0] 255(+1) colors generated out of 88442 colors; ratio=0.002883
frame= 4 fps=4.0 q=-0.0 size= 137kB time=00:00:00.06 bitrate=18711.6kbits/s speed=0.0596x
frame= 42 fps= 28 q=-0.0 size= 2095kB time=00:00:00.69 bitrate=24870.0kbits/s speed=0.456x
frame= 65 fps= 35 q=-0.0 Lsize= 3504kB time=00:00:04.99 bitrate=5752.4kbits/s speed=2.71x
video:3503kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.036830%
Export to video...
Start ffmpeg:
C:\Users\amaga\AppData\Roaming\NA-MIC\ffmpeg\ffmpeg-3.2.4-win64-static\bin\ffmpeg.exe -nostdin -y -r 60 -start_number 0 -i C:/Users/amaga/AppData/Local/Temp/Slicer-zwrdHG\Slicer-%04d.png -filter_complex palettegen,[v]paletteuse C:/Users/amaga/Desktop/after.gif

Video export succeeded to file: C:/Users/amaga/Desktop/after.gif

after

2

I have never seen this error. How many frames did you use? What is the size of one frame?

You can search for this error on the web and if nothing useful comes up then report it to ffmpeg developers.

3

Dunno if this helps, but an answer on stack overflow suggests inserting a fifo for this error (not exactly same params as yours, but similar error):

4

640x480, 300 frames…

5

I was able to reproduce the problem with the ffmpeg version that ScreenCapture module installs by default. I’ve downloaded the latest version from here and that build did not have this problem. We could update the download link to get a more recent ffmpeg version.

However, the resulting gif was 55MB. If you put a few of such animations in a slide deck then you can get into trouble. The same animation saved as H.265 mp4 file is 950KB. I would recommend to go with mp4 if storing if gif file size is more than a few MB.

6

That will be great, thank you.

7

Please test if the essential build is sufficient or if we need the full build (https://www.gyan.dev/ffmpeg/builds/). Also, please check if we can delete ffplay.exe and ffprobe.exe from the package to reduce download time.

8

I downloaded the essential build, removed the ffplay and ffprobe from bin folder, reconfigured the screen capture to use this ffmpeg, and it seemed to work fine (no stutter, no error, and no complains about ffplay or ffprobe).

This is with the latest stable.

1 Like
9

I’ve updated the download link: ENH: Update ffmpeg download link for Windows to allow creating large … · Slicer/Slicer@7b60eed · GitHub

Existing ffmpeg installations will not be modified. Users who wants to upgrade need to clear their (usersetting)/ffmpeg folder to force update. The folder location can be printed by copying this command into the Python console:

import os
print(os.path.dirname(slicer.app.slicerUserSettingsFilePath)+'/ffmpeg')
1 Like