This update for ffmpeg-4 fixes the following issues:
{ "binaries": [ { "ffmpeg-4-libavutil-devel": "4.4-150400.3.8.1", "libavdevice58_13-32bit": "4.4-150400.3.8.1", "ffmpeg-4-private-devel": "4.4-150400.3.8.1", "libswscale5_9-32bit": "4.4-150400.3.8.1", "libavfilter7_110": "4.4-150400.3.8.1", "libavresample4_0-32bit": "4.4-150400.3.8.1", "ffmpeg-4-libavfilter-devel": "4.4-150400.3.8.1", "libavdevice58_13": "4.4-150400.3.8.1", "ffmpeg-4": "4.4-150400.3.8.1", "ffmpeg-4-libavcodec-devel": "4.4-150400.3.8.1", "libavcodec58_134": "4.4-150400.3.8.1", "ffmpeg-4-libavresample-devel": "4.4-150400.3.8.1", "libswresample3_9": "4.4-150400.3.8.1", "libavcodec58_134-32bit": "4.4-150400.3.8.1", "ffmpeg-4-libswscale-devel": "4.4-150400.3.8.1", "ffmpeg-4-libavformat-devel": "4.4-150400.3.8.1", "libavutil56_70-32bit": "4.4-150400.3.8.1", "libavfilter7_110-32bit": "4.4-150400.3.8.1", "libpostproc55_9-32bit": "4.4-150400.3.8.1", "libswresample3_9-32bit": "4.4-150400.3.8.1", "libswscale5_9": "4.4-150400.3.8.1", "ffmpeg-4-libpostproc-devel": "4.4-150400.3.8.1", "ffmpeg-4-libavdevice-devel": "4.4-150400.3.8.1", "libavformat58_76-32bit": "4.4-150400.3.8.1", "libavformat58_76": "4.4-150400.3.8.1", "libavresample4_0": "4.4-150400.3.8.1", "libpostproc55_9": "4.4-150400.3.8.1", "libavutil56_70": "4.4-150400.3.8.1", "ffmpeg-4-libswresample-devel": "4.4-150400.3.8.1" } ] }