From 7f42caf789144a8ef8df8180e9372f886278a0c4 Mon Sep 17 00:00:00 2001
From: non25 <19non91@gmail.com>
Date: Mon, 24 Apr 2017 15:53:08 +0300
Subject: [PATCH] Additional info

Added info about MIDI controller usage, and info on getting OSC paths for Module controls.
---
 mixer/doc/MANUAL.mu | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/mixer/doc/MANUAL.mu b/mixer/doc/MANUAL.mu
index 9b78e8b..fd4012a 100644
--- a/mixer/doc/MANUAL.mu
+++ b/mixer/doc/MANUAL.mu
@@ -215,6 +215,18 @@
   respectively, and `f` and `s` switch between /fader/ and /signal/
   views. The strip's context menu can be invoked without the mouse by
   hitting the `Menu` key (assuming your keyboard has one).
+  
+::: MIDI Controllers
+
+  Usual Midi bindings can be achieved by launching both non-mixer
+  and non-midi-mapper through non-session-manager.
+  non-midi mapper is usually included in non-mixer package.
+  
+  After launching them through non-session-manager connect JACK-Midi
+  output to Non-MIDI-Mapper input.
+  
+  Then you can use 'Start learning', which is accesible through Remote
+  Control menu of the Mixer. Select desirable control and use MIDI device.
 
 ::: Signal Chain
 
@@ -294,6 +306,12 @@
 
   For the second instance of the Gain module on the strip named 'Foo'.
 
+  There's a possibility to get exact OSC path for module controls.
+  For this you need to switch strip mode to 'Signl', right click a
+  module, for example 'Gain', and open 'Edit parameters' dialog. OSC
+  path will be shown in a statusbar of the main window when you
+  hover a parameter.
+
   Non-DAW accesses these same signals via a more advanced signal
   routing layer on top of OSC. Any module parameter is easily
   controlled via Control Sequences in Non-DAW without the need to