Hi Moritz
> On 24 Jun 2017, at 17:18, Moritz Barsnick <[email protected]> wrote: > > On Sat, Jun 24, 2017 at 16:41:09 +0200, Bouke / VideoToolShed wrote: >> Can someone please tell me what I’m doing wrong here? > > A segmentation fault should usually not be your fault. It could be > ffmpeg, it could be libmp3lame, or it could be some unfortunate > exchange of libraries. > > Did you build this ffmpeg yourself? Do you have access to the version Nope, I did not, I can’t :-) (I’m mortal…) > with debug symbols (ffmpeg_g)? Only then can this issue be debugged. > How to use gdb (and report the issue) is described here: > https://ffmpeg.org/bugreports.html > I don't know whether Mac OSX uses gdb though. > >> [...] -filter_complex "[0:0][0:0] amix=inputs=2,pan=mono|c0=c0+c1" -ac 1 > > I wasn't aware you could use an input ([0:0]) twice, and it seems > you're doing something in a more complicated way than you should - but > that shouldn't lead to a crash. ;-) This is a result of my front end that has to do a lot of stuff and be as versatile as possible. It ‘should’ work (and it does, except for this audio codec, change it to pcm_s16le it works just fine…) strange thing is, I did not notice this before, so there is ‘something’ strange with the input file. No clue yet, and it only seems to happen on Mac. I’ll dive into it tomorrow and try to pinpoint it more exactly. (That will probably mean get other FFmpeg binaries) As always, thanks for your help! Bouke > > Moritz > _______________________________________________ > ffmpeg-user mailing list > [email protected] > http://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe". _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
