[FFmpeg-devel] [PATCH] doc: document amerge filter as an alternative for the -map_channel limitation.

[Clément Bœsch]

On Tue, Jan 24, 2012 at 08:03:04AM +0000, Tim Nicholson wrote:
> On 24/01/12 07:58, Tim Nicholson wrote:
> > On 23/01/12 22:43, Clément Bœsch wrote:
> >> On Mon, Jan 23, 2012 at 03:13:29PM +0100, Nicolas George wrote:
> >>> L'octidi 28 nivôse, an CCXX, Tim Nicholson a écrit :
> >>>> OK so after further testing I propose this amendment to Clément's patch:-
> >>>>
> >>>> was:-
> >>>> + at example
> >>>> +ffmpeg -i input.mkv -f lavfi -i "
> >>>> +amovie=input.mkv:si=1 [a1];
> >>>> +amovie=input.mkv:si=2 [a2];
> >>>> +[a1][a2] amerge" -c:a pcm_s16le -c:v copy output.mkv
> >>>> + at end example
> >>>> +
> >>>>
> >>>> becomes:-
> >>>> + at example
> >>>> +ffmpeg -i input.mkv -f lavfi -i "
> >>>> +amovie=input.mkv:si=1 [a1];
> >>>> +amovie=input.mkv:si=2 [a2];
> >>>> +[a1][a2] amerge, aformat=s16:stereo:all" -c:a pcm_s16le -c:v copy output.mkv
> >>>> + at end example
> >>>> +
> >>>>
> >>>>
> >
> [...]
> > 
> >>
> >> Sorry I almost forgot this patch. It seems there is still something to fix
> >> with the current patch; do you expect me to change something concerning
> >> the last version I sent or should I just push it?
> 
> Of course it may all be irrelevant if your new channel mapping patch works....
> 

Transparent channel merge with -map_channel depends on -af being in
ffmpeg. I have a WIP to build a filterchain based on the specified
-map_channel options, but in order to insert it properly, we need -af (and
maybe more tricky things).

[...]

-- 
Clément B.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20120202/d78a0f29/attachment.asc>