summaryrefslogtreecommitdiff
path: root/posts
diff options
context:
space:
mode:
authorrekado <rekado@elephly.net>2013-10-31 22:45:44 +0800
committerrekado <rekado@elephly.net>2013-10-31 22:45:44 +0800
commite2436fa75cd2a16e19308886f17625818ff07e51 (patch)
tree0879d8873208216a3e02e68c44696ed6aa3ab81a /posts
parent4fcad21455a57847d13442d0a18408ea5d0af47a (diff)
correct error: WD2_PROG.BOR instead of PROG.BOR
Diffstat (limited to 'posts')
-rw-r--r--posts/2013-08-11-hacking-the-wavedrum.markdown6
1 files changed, 3 insertions, 3 deletions
diff --git a/posts/2013-08-11-hacking-the-wavedrum.markdown b/posts/2013-08-11-hacking-the-wavedrum.markdown
index 5a0066a..2b1ed0c 100644
--- a/posts/2013-08-11-hacking-the-wavedrum.markdown
+++ b/posts/2013-08-11-hacking-the-wavedrum.markdown
@@ -1,6 +1,6 @@
---
title: Hacking the Wavedrum
-tags: DIY,electronics,music,hacking
+tags: DIY,electronics,music,hacking,wavedrum
---
The Wavedrum Oriental is a wonderful electronic instrument. Unlike an
@@ -171,7 +171,7 @@ When a factory reset is performed, the customised versions of these
files in the root directory are overwritten with the versions
contained in the `Factory` directory. All initial programmes that
come with the Wavedrum are stored in `Factory/F_PROG.BOR`; once
-programmes have been edited `PROG.BOR` in the root directory will
+programmes have been edited `WD2_PROG.BOR` in the root directory will
differ from `Factory/F_PROG.BOR`. (More about the nature of these
differences later.) `PRE_PROG.BOR` is the same as
`Factory/F_PROG.BOR` and is probably used to make the original factory
@@ -299,7 +299,7 @@ pattern?).
# The programme format
-Looking at the hexdump of the file `PROG.BOR` which holds all custom
+Looking at the hexdump of the file `WD2_PROG.BOR` which holds all custom
presets, I couldn't find any obvious patterns in the file, so I
resorted to editing a single programme, setting particular consecutive
parameters to easily recognisable sequences of values (such as 100,