blackteay/ffmpeg-python
1
0
Fork 0
mirror of https://github.com/kkroening/ffmpeg-python.git synced 2025-04-05 04:22:51 +08:00
Code Issues Projects Releases Wiki Activity

Update doc

Browse Source
This commit is contained in:
Karl Kroening 2017-05-13 19:37:09 -10:00
parent 7db10ccf98
commit 350f30dcba
2 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -3,11 +3,17 @@
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.
Take for example a signal graph that looks like this:
![Signal graph](https://raw.githubusercontent.com/kkroening/ffmpeg-python/master/doc/graph1.png)
![Signal graph](https://raw.githubusercontent.com/kkroening/ffmpeg-python/master/doc/graph1.png|width=300)
The corresponding command-line arguments are pretty gnarly:
```
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
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
```
Maybe this looks great to you, but if you haven't worked with FFmpeg before, this probably looks pretty alien.

BIN
doc/graph1.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 29 KiB

After

Width:  |  Height:  |  Size: 43 KiB