From f131a9a3f94f07317a9d5638e909fcc8d7bc7fe3 Mon Sep 17 00:00:00 2001
From: Karl Kroening <karlk@kralnet.us>
Date: Sat, 13 May 2017 19:47:24 -1000
Subject: [PATCH] Update doc

---
 README.md | 27 +++++++++++++++++++++++++--
 1 file changed, 25 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 0d4d253..0722e2e 100644
--- a/README.md
+++ b/README.md
@@ -1,9 +1,32 @@
 # ffmpeg-python: Powerfully simple A/V routing with Python
 
-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.
+## Overview
+
+There are tons of Python FFmpeg wrappers out there but they seem to lack complex filter support - useless for anything but trivial examples.  `ffmpeg-python` works well for simple as well as complicated signal graphs.
+
+## Quickstart
+
+```
+import ffmpeg
+ffmpeg \
+    .file_input('input.mp4') \
+    .file_output('output.mp4') \
+    .run()
+```
+
+Or if you dislike fluent-style APIs:
+```
+import ffmpeg
+in = ffmpeg.file_input('input.mp4')
+out = ffmpeg.file_output(in)
+ffmpeg.run(out)
+```
+
+## Complex filter graphs
+FFmpeg is extremely powerful, but it's 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|width=300)
+<img src="https://raw.githubusercontent.com/kkroening/ffmpeg-python/master/doc/graph1.png" alt="Signal graph" width="50%" />
 
 The corresponding command-line arguments are pretty gnarly:
 ```