Re: [FFmpeg-user] Muxing multiple files and concatenating those outputs

2020-04-22 Thread Greg Oliver
On Tue, Apr 21, 2020 at 9:40 PM Edward Park wrote: > Hi, > > > I ended up just keeping it as a script and getting the developers to > > incorporate it into our code. Thanks though! Since it is a script, a > > single bash call is not too intrusive. If we had some C programmers, I > > would

Re: [FFmpeg-user] Muxing multiple files and concatenating those outputs

2020-04-21 Thread Edward Park
Hi, > I ended up just keeping it as a script and getting the developers to > incorporate it into our code. Thanks though! Since it is a script, a > single bash call is not too intrusive. If we had some C programmers, I > would have them use the ffmpeg libraries directly, but they are all just

Re: [FFmpeg-user] Muxing multiple files and concatenating those outputs

2020-04-21 Thread Greg Oliver
On Thu, Apr 16, 2020 at 10:19 AM Nicolas George wrote: > Greg Oliver (12020-04-14): > > We currently use ffmpeg to combine 2 streams (telephony codecs) into > > mp3/wav/flac, etc.. This is no problem - we use: > > > > ffmpeg -ar 8000 -y -f mulaw -i calls/example.g711a.ulaw -ar 8000 -f mulaw > >

Re: [FFmpeg-user] Muxing multiple files and concatenating those outputs

2020-04-16 Thread Nicolas George
Greg Oliver (12020-04-14): > We currently use ffmpeg to combine 2 streams (telephony codecs) into > mp3/wav/flac, etc.. This is no problem - we use: > > ffmpeg -ar 8000 -y -f mulaw -i calls/example.g711a.ulaw -ar 8000 -f mulaw > -i calls/example.g711b.ulaw -filter_complex

Re: [FFmpeg-user] Muxing multiple files and concatenating those outputs

2020-04-15 Thread Greg Oliver
On Wed, Apr 15, 2020 at 5:43 AM Ted Park wrote: > Hi, > > > Yeah, when we record the calls, the directory structure preceeding those > > names is /MM/DD/HH and the filenames are MIN_SEC_MSEC.codec(side) > > > I mean some phones specifically put g729a, and I assume it's the same for > g729b.

Re: [FFmpeg-user] Muxing multiple files and concatenating those outputs

2020-04-15 Thread Ted Park
Hi, > Yeah, when we record the calls, the directory structure preceeding those > names is /MM/DD/HH and the filenames are MIN_SEC_MSEC.codec(side) I mean some phones specifically put g729a, and I assume it's the same for g729b. So I started imagining files ending all over the place

Re: [FFmpeg-user] Muxing multiple files and concatenating those outputs

2020-04-14 Thread Greg Oliver
On Tue, Apr 14, 2020 at 3:30 PM Ted Park wrote: > Hi, > > > Example using these files (suffix denotes codec - a and b are each side > of > > a call): > > > > 18_17_248.g729a > > 18_17_248.g729b > > 19_18_440.g711a > > 19_18_440.g711b > > 20_01_886.g729a > > 20_01_886.g729b > > > That is really

Re: [FFmpeg-user] Muxing multiple files and concatenating those outputs

2020-04-14 Thread Ted Park
Hi, > Example using these files (suffix denotes codec - a and b are each side of > a call): > > 18_17_248.g729a > 18_17_248.g729b > 19_18_440.g711a > 19_18_440.g711b > 20_01_886.g729a > 20_01_886.g729b > That is really confusing... > Current method to concatenate and transcode to wav putting

[FFmpeg-user] Muxing multiple files and concatenating those outputs

2020-04-14 Thread Greg Oliver
Hi, We currently use ffmpeg to combine 2 streams (telephony codecs) into mp3/wav/flac, etc.. This is no problem - we use: ffmpeg -ar 8000 -y -f mulaw -i calls/example.g711a.ulaw -ar 8000 -f mulaw -i calls/example.g711b.ulaw -filter_complex "[0:a][1:a]amerge[aout]" -map "[aout]" output.wav If