[FFmpeg-user] Please help confirm if this hard, system crash is reproducible

Ted Park kumowoon1025 at gmail.com
Mon Apr 6 20:27:10 EEST 2020

>> ffplay -f lavfi -i "anoisesrc[a1];sine,[a1]amix"
>> ffplay version 4.2.2 Copyright (c) 2003-2019 the FFmpeg developers
> Apart from "is the issue reproducible with current FFmpeg git head?"
> The problem with ffplay-specific issues is that ffplay depends on an
> external library that can easily be the issue for such (hard to debug)
> crashes.
> That being said: valgrind shows nothing unusual for above command line.
> Carl Eugen

I mean, it was kind of stale, the build I encountered it on was one commit behind on master I think.
I switched to the default binary installation in homebrew just to see if it’s my build configuration, but anyway, you’re probably right, I’m starting to think it’s probably some hardware or the mess I’ve made of my sdl2 installation, I don’t think there’s anything that could cause this kind of failure reliably with any typical build of ffmpeg.

> is this a correct syntax if you specify only one input for amix? I'm not sure. Does it mean amix gets [a1] as the first input and sine as the second input, or vice versa? Did you try
> "anoisesrc[a1];sine[a2];[a1][a2]amix”
> Michael

I did, and nope, nothing happened. This was on OSX 10.14 (first machine was running 10.15.5) so I might try on yet another machine but I’ll leave that for later if I end up not being able to fix the issue on this machine.

If anyone has ffmpeg on 10.15.3~5 frameworks try it out, I think it’s just me and not a bug at this point.

Ted Park

More information about the ffmpeg-user mailing list