aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Phillips <dbphillipsnz@gmail.com>2016-05-09 11:59:58 +1200
committerDavid Phillips <dbphillipsnz@gmail.com>2016-05-10 00:01:50 +1200
commit6daa87961ed8035085d11300073ee183b8db8391 (patch)
tree9dce6483553ebdeb52edf1519649de164709a3ac
parentf7c93efb48bb804717eb70b06d1f4c70a0dbd146 (diff)
downloadpgm-interlace-6daa87961ed8035085d11300073ee183b8db8391.tar.xz
Remove old example from readme
-rw-r--r--README.md24
1 files changed, 0 insertions, 24 deletions
diff --git a/README.md b/README.md
index 58b0ab2..2240874 100644
--- a/README.md
+++ b/README.md
@@ -2,30 +2,6 @@
Vertically interlace *n* PGM frames, each one *height/n* pixels in width into
one square image with a width the same as the height.
-By example, it would take two 2x4 images:
-
- Image A:
- 0 1
- 1 A B
- 2 C D
- 3 E F
- 4 G H
-
- Image B:
- 0 1
- 1 I J
- 2 K L
- 3 M N
- 4 O P
-
-combining them into one single 4x4 image from the command `pgm-interlace imageA imageB`
-
- 0 1 2 3
- 0 A I B J
- 1 C K D L
- 2 E M F N
- 3 G O H P
-
The order in which the frames are specified on the command line is critical for
the reconstruction of the image. pgm-interlace has no way of telling in which
order a handful of pgm frames should be interlaced unless you tell it how to