8000 Update doc · Powercoder64/ffmpeg-python@350f30d · GitHub
[go: up one dir, main page]
Skip to content

Commit 350f30d

Browse files
kkroeningkkroening
committed
Update doc
1 parent 7db10cc commit 350f30d

File tree

2 files changed

+8
-2
lines changed

2 files changed

+8
-2
lines changed

‎README.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,17 @@
33
FFmpeg is extremely powerful, but its command-line interface gets really complicated really quickly - especially when working with signal graphs and doing anything more than trivial.
44

55
Take for example a signal graph that looks like this:
6-
![Signal graph](https://raw.githubusercontent.com/kkroening/ffmpeg-python/master/doc/graph1.png)
6+
![Signal graph](https://raw.githubusercontent.com/kkroening/ffmpeg-python/master/doc/graph1.png|width=300)
77

88
The corresponding command-line arguments are pretty gnarly:
99
```
10-
ffmpeg -i input.mp4 -filter_complex "[0]trim=start_frame=10:end_frame=20,setpts=PTS-STARTPTS[v0];[0]trim=start_frame=30:end_frame=40,setpts=PTS-STARTPTS[v1];[0]trim=start_frame=50:end_frame=60,setpts=PTS-STARTPTS[v2];[v0][v1][v2]concat=n=3[v3]" -map [v3] output.mp4
10+
ffmpeg -i input.mp4 \
11+
-filter_complex "\
12+
[0]trim=start_frame=10:end_frame=20,setpts=PTS-STARTPTS[v0];\
13+
[0]trim=start_frame=30:end_frame=40,setpts=PTS-STARTPTS[v1];\
14+
[0]trim=start_frame=50:end_frame=60,setpts=PTS-STARTPTS[v2];\
15+
[v0][v1][v2]concat=n=3[v3]"\
16+
-map [v3] output.mp4
1117
```
1218

1319
Maybe this looks great to you, but if you haven't worked with FFmpeg before, this probably looks pretty alien.

‎doc/graph1.png

14.2 KB
Loading

0 commit comments

Comments
 (0)
0