From c58f77910a45a400174b8f72a207d3f582af5e35 Mon Sep 17 00:00:00 2001 From: Giso Grimm Date: Thu, 31 Oct 2024 23:52:52 +0100 Subject: [PATCH] improve documentation --- manual/modmididispatch.tex | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/manual/modmididispatch.tex b/manual/modmididispatch.tex index 28456617..8024146a 100644 --- a/manual/modmididispatch.tex +++ b/manual/modmididispatch.tex @@ -1,4 +1,4 @@ -This plugins can dispatch OSC messages upon MIDI events (CC or note events). Event handlers can be registered via OSC or in the XML configuration, using the \elem{ccmsg} or \elem{notemsg} elements. Multiple event handlers for the same event can be registered. In that case all event handlers will be called. Event handler can be removed via OSC. The communication is bi-directional; MIDI events can be emitted by sending an OSC message to \verb!/mididispatch/send/cc! or \verb!/mididispatch/send/note!. +This plugins can dispatch OSC messages upon MIDI events (CC or note events). Event handlers can be registered via OSC or in the XML configuration, using the \elem{ccmsg} or \elem{notemsg} elements (see below). Parameters to the message can be added using the \elem{f v="1.234"}, \elem{i v="1"} or \elem{s v="string"} sub-elements. Multiple event handlers for the same event can be registered. In that case all event handlers will be called. Event handler can be removed via OSC. The communication is bi-directional; MIDI events can be emitted by sending an OSC message to \verb!/mididispatch/send/cc! or \verb!/mididispatch/send/note!. \begin{snugshade} {\footnotesize @@ -81,4 +81,14 @@ } \end{snugshade} +An example configuration can look like this: + +\begin{lstlisting} + + + + + +\end{lstlisting} + \input{oscdoc_tascarmod_mididispatch.tex}