Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in / Register
Toggle navigation
F
ffmpeg.wasm-core
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Linshizhi
ffmpeg.wasm-core
Commits
7028c9f4
Commit
7028c9f4
authored
Dec 21, 2011
by
Tim Nicholson
Committed by
Clément Bœsch
Dec 21, 2011
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clearer explanation of audio channel mapping restrictions
parent
1f797a58
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
3 deletions
+7
-3
ffmpeg.texi
doc/ffmpeg.texi
+7
-3
No files found.
doc/ffmpeg.texi
View file @
7028c9f4
...
...
@@ -825,9 +825,13 @@ The following example split the channels of a stereo input into streams:
ffmpeg -i stereo.wav -map 0:0 -map 0:0 -map
_
channel 0.0.0:0.0 -map
_
channel 0.0.1:0.1 -y out.ogg
@end example
Note that "-map
_
channel" is currently limited to the scope of one input for
each output; you can't for example use it to pick multiple input audio files
and mix them into one single output.
Note that currently each output stream can only contain channels from a single
input stream; you can't for example use "-map
_
channel" to pick multiple input
audio channels contained in different streams (from the same or different files)
and merge them into a single output stream. It is therefore not currently
possible, for example, to turn two separate mono streams into a single stereo
stream. However spliting a stereo stream into two single channel mono streams
is possible.
@item -map
_
metadata[:@var
{
metadata
_
type
}
][:@var
{
index
}
] @var
{
infile
}
[:@var
{
metadata
_
type
}
][:@var
{
index
}
] (@emph
{
output,per-metadata
}
)
Set metadata information of the next output file from @var
{
infile
}
. Note that
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment