8000 Update README.md · Powercoder64/ffmpeg-python@bde72f4 · GitHub
[go: up one dir, main page]

Skip to content

Commit bde72f4

Browse files
authored
Update README.md
1 parent 411b0a1 commit bde72f4

File tree

1 file changed

+21
-13
lines changed

1 file changed

+21
-13
lines changed

README.md

Lines changed: 21 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ import ffmpeg
3232
)
3333
```
3434

35-
## [[API reference]](https://kkroening.github.io/ffmpeg-python/)
35+
## [API reference](https://kkroening.github.io/ffmpeg-python/)
3636

3737
## Complex filter graphs
3838
FFmpeg is extremely powerful, but its command-line interface gets really complicated rather quickly - especially when working with signal graphs and doing anything more than trivial.
@@ -51,7 +51,7 @@ ffmpeg -i input.mp4 -i overlay.png -filter_complex "[0]trim=start_frame=10:end_f
5151

5252
Maybe this looks great to you, but if you're not an FFmpeg command-line expert, it probably looks alien.
5353

54-
If you're like me and find Python to be powerful and readable, it's easy with `ffmpeg-python`:
54+
If you're like me and find Python to be powerful and readable, it's easier with `ffmpeg-python`:
5555
```python
5656
import ffmpeg
5757

@@ -70,28 +70,24 @@ overlay_file = ffmpeg.input('overlay.png')
7070
)
7171
```
7272

73-
`ffmpeg-python` takes care of running `ffmpeg` with the command-line arguments that correspond to the above filter diagram, and it's easy to see what's going on and make changes as needed.
73+
`ffmpeg-python` takes care of running `ffmpeg` with the command-line arguments that correspond to the above filter diagram, in familiar Python terms.
7474

7575
<img src="https://raw.githubusercontent.com/kkroening/ffmpeg-python/master/doc/screenshot.png" alt="Screenshot" align="middle" width="60%" />
7676

77-
Real-world signal graphs can get a heck of a lot more complex, but `ffmpeg-python` handles them with ease.
78-
77+
Real-world signal graphs can get a heck of a lot more complex, but `ffmpeg-python` handles arbitrarily large (directed-acyclic) signal graphs.
7978

8079
## Installation
8180

82-
The latest version of `ffmpeg-python` can be acquired via pip:
81+
The latest version of `ffmpeg-python` can be acquired via a typical pip install:
8382

8483
```
8584
pip install ffmpeg-python
8685
```
8786

88-
It's also possible to clone the source and put it on your python path (`$PYTHONPATH`, `sys.path`, etc.):
89-
87+
Or clone the source and install locally:
9088
```bash
91-
$ git clone git@github.com:kkroening/ffmpeg-python.git
92-
$ export PYTHONPATH=${PYTHONPATH}:ffmpeg-python
93-
$ python
94-
>>> import ffmpeg
89+
git clone git@github.com:kkroening/ffmpeg-python.git
90+
pip install -e ./ffmpeg-python
9591
```
9692

9793
## [Examples](https://github.com/kkroening/ffmpeg-python/tree/master/examples)
@@ -166,7 +162,7 @@ Some ffmpeg filters drop audio streams, and care must be taken to preserve the a
166162

167163
This dilemma is intrinsic to ffmpeg, and ffmpeg-python tries to stay out of the way while users may refer to the official ffmpeg documentation as to why certain filters drop audio.
168164

169-
As usual, take a look at the [Examples](https://github.com/kkroening/ffmpeg-python/tree/master/examples#audiovideo-pipeline) (the "Audio/video pipeline" example in particular).
165+
As usual, take a look at the [examples](https://github.com/kkroening/ffmpeg-python/tree/master/examples#audiovideo-pipeline) (*Audio/video pipeline* in particular).
170166

171167
## Contributing
172168

@@ -180,6 +176,18 @@ Pull requests are welcome as well, but it wouldn't hurt to touch base in the iss
180176

181177
Anyone who fixes any of the [open bugs](https://github.com/kkroening/ffmpeg-python/labels/bug) or implements [requested enhancements](https://github.com/kkroening/ffmpeg-python/labels/enhancement) is a hero, but changes should include passing tests.
182178

179+
### Running tests
180+
181+
```bash
182+
git clone git@github.com:kkroening/ffmpeg-python.git
183+
cd ffmpeg-python
184+
virtualenv venv
185+
. venv/bin/activate # (OS X / Linux)
186+
venv\bin\activate # (Windows)
187+
pip install -e .[dev]
188+
pytest
189+
```
190+
183191
<br />
184192

185193
### Special thanks

0 commit comments

Comments
 (0)
0