aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorcbdev <cb@cbcdn.com>2020-02-28 19:00:58 +0100
committercbdev <cb@cbcdn.com>2020-02-28 19:00:58 +0100
commitd574abf032da350f1208d9480d24c51187bc7c63 (patch)
treee9c9127cfa84a32270a89c24ba367f5dc2f53499
parentcff53b6fb1996a24dbdef3657e4fac6558913c33 (diff)
downloadmidimonster-d574abf032da350f1208d9480d24c51187bc7c63.tar.gz
midimonster-d574abf032da350f1208d9480d24c51187bc7c63.tar.bz2
midimonster-d574abf032da350f1208d9480d24c51187bc7c63.zip
Minor documentation fix
-rw-r--r--README.md6
-rw-r--r--backends/lua.md5
2 files changed, 5 insertions, 6 deletions
diff --git a/README.md b/README.md
index 2af26cf..7313415 100644
--- a/README.md
+++ b/README.md
@@ -24,10 +24,8 @@ Currently, the MIDIMonster supports the following protocols:
| Lua Scripting | Linux, Windows, OSX | | [`lua`](backends/lua.md) |
| Loopback | Linux, Windosw, OSX | | [`loopback`](backends/loopback.md) |
-with additional flexibility provided by a [Lua scripting environment](backends/lua.md).
-
-With these features, the MIDIMonster allows the user to translate any channel on one protocol into channel(s)
-on any other (or the same) supported protocol, for example to:
+With these features, the MIDIMonster allows users to control any channel on any of these protocols, and translate any channel on
+one protocol into channel(s) on any other (or the same) supported protocol, for example to:
* Translate MIDI Control Changes into MIDI Notes ([Example configuration](configs/unifest-17.cfg))
* Translate MIDI Notes into ArtNet or sACN ([Example configuration](configs/launchctl-sacn.cfg))
diff --git a/backends/lua.md b/backends/lua.md
index b936a99..d2552e0 100644
--- a/backends/lua.md
+++ b/backends/lua.md
@@ -65,9 +65,10 @@ Using these names as arguments to the output and value interface functions works
Output values will not trigger corresponding input event handlers unless the channel is mapped
back in the MIDIMonster configuration.
-To build (and run) the `lua` backend on Windows, a compiled version of the Lua library is required.
+To build (and run) the `lua` backend on Windows, a compiled version of the Lua 5.3 library is required.
For various reasons (legal, separations of concern, not wanting to ship binary data in the repository),
-you will need to acquire a copy of `lua53.dll` (for example by downloading it from the [luabinaries
+the MIDIMonster project can not provide this file within this repository.
+You will need to acquire a copy of `lua53.dll`, for example by downloading it from the [luabinaries
project](http://luabinaries.sourceforge.net/download.html).
To build the `lua` backend for Windows, place `lua53.dll` in a subdirectory `libs/` in the project root