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 01/13] 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
From 63a624414b80284f3591cbd476cf0a7f0085e909 Mon Sep 17 00:00:00 2001
From: Jonathan Moore Liles
-The focused strip can be moved in the display order via the [ and ] keys. Delete removes a strip (with confirmation dialog). n and w set the focused strip's width to narrow or wide, 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). +The focused strip can be moved in the display order via the [ and ] keys. Delete removes a strip (with confirmation dialog). n and w set the focused strip's width to narrow or wide, 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).
@@ -305,9 +307,25 @@ If same module/plugin is used twice in a signal chain (e.g. multiple Gain stages 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 specify an OSC URL.
-+Automatic translation between MIDI and Non's OSC Signals can be achieved by adding the headless program non-midi-mapper (included in the Non-Mixer distribution) to an NSM session. +
++Non-MIDI-Mapper provides JACK MIDI input and output ports that can be connected to a suitable controller device. +
++In Non-Mixer, the Remote Control/Start Learning menu item enters learning mode in which Non Mixer can be taught which controls to associated with which MIDI messages by clicking a control in Non-Mixer and moving the desired control on the MIDI device. Remote Control/End Learning ends the learning session. +
++The mapping will be saved with the NSM session. +
+Left-clicking on a module brings up a Module Parameter Editor window for the selected module.
@@ -323,7 +341,7 @@ Control+Right-clicking on a module causes it to be removed from the chain (modulThe focused module may also be controlled via the keyboard. Menu brings up the context menu for the focused module. Space opens the module parameter editor, b toggles the bypassed state, and Delete removes the module from the chain (without confirmation!). Control-X, Control-C and Control-V, cut, copy, and paste modules, respectively. Modules may be copied within or across chain boundaries. The normal module I/O constraints also apply to pasted modules.
-The control voltage concept should be familiar to anyone who has experience with analog modular synthesizers. MIDI, while having definite advantages in many respects, multiplexes control data in such a way as to make connecting one MIDI control to a parameter involve a significant inconvenience, usually requiring the adjustment of settings on both ends of the connection in order to separate the control data streams.
@@ -375,8 +393,8 @@ of parameter automation, as LADSPA plugins are incapable of processing Control Voltage signals at full audio resolution anyway.A Spatializer Module fed stereo input will perform stereo encoding and will present a Width control.
-The Spatializer module is intended to work with an external reverb engine having Ambisonics B-Format inputs for early reflections and a Mono input for reverb tail (and, of course, B-Format outputs).
@@ -420,7 +438,7 @@ I have crafted several jconvolver config files that meet these specifications. TThe main outputs of the strip should go to a master bus, into which the output of the reverb engine is also fed.
-There are several Ambisonics panners/encoders released as LADSPA plugins. When one of these plugins is added to a strip, Non Mixer will detect its parameter signature and create a Spatialization Control for it just as with the Spatializer Module.
diff --git a/mixer/doc/MANUAL.mu b/mixer/doc/MANUAL.mu index fd4012a..b4a6918 100644 --- a/mixer/doc/MANUAL.mu +++ b/mixer/doc/MANUAL.mu @@ -216,18 +216,6 @@ 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 The signal chain view of a mixer strip provides a way to view and @@ -317,6 +305,23 @@ controlled via Control Sequences in Non-DAW without the need to specify an OSC URL. + +::::: MIDI Control + + Automatic translation between MIDI and Non's OSC Signals can be + achieved by adding the headless program `non-midi-mapper` (included in the + Non-Mixer distribution) to an NSM session. + + Non-MIDI-Mapper provides JACK MIDI input and output ports that can be + connected to a suitable controller device. + + In Non-Mixer, the `Remote Control\/Start Learning` menu item enters learning + mode in which Non Mixer can be taught which controls to associated with which + MIDI messages by clicking a control in Non-Mixer and moving the desired control + on the MIDI device. `Remote Control\/End Learning` ends the learning session. + + The mapping will be saved with the NSM session. + ::::: Manipulation Left-clicking on a module brings up a Module Parameter Editor window From 5ae43bb27c42387052a73e5ffc5d33efb9d946a9 Mon Sep 17 00:00:00 2001 From: Jonathan Moore LilesK@smQ%jLpl{oqMp1X7q{rm3b
z%e11q#qA1AifVBH3hVDE*#-j1acVh`L8rFWe(Q`8)c-~8u2@*rISM{*GFq0I^h*q+
zUj`RQit@eJ^>ST$>J43vx_-cAdCF?q_Tom-Rbe5gBjnGULm(VgCjhSy^k>aLc)#OvXHR
zL9iEF4e2(=Yzo)$A3O%rxunFxnaM^>EAeIjUw^*HWAl#)Niyce*v@Dh{ih{tFO0On
zE3q~ha$~n7ymoI*Y?SQymuHpb0G+_T9ginytgikH9G1l1O77M)R8A0$!?ee!6Rz}5
zF?+@!KDXm<%G@k^W