updated documentation

.gitignore

@@ -1,5 +1,6 @@
 *~
 .*~
 *.pyc
+auto/
 Desktop.ini
 Thumbs.db

doc/PythonMcu.tex

@@ -45,27 +45,27 @@ \chapter{Mackie Control}
 space (or you have a controller that is simply too good to be
 exchanged for an MCU), you might have found just the application you
 need.  It might not support your MIDI hardware controller yet, but if
-you know a bit of \textbf{Python} (or a programmer who does) it's
-pretty easy to change that.
+you know a bit of \textbf{Python} (or a programmer who does) it should
+be pretty easy to change that.
 
 
 \chapter{Installation}
 \label{chap:python_mcu}
 
 Download and install the latest version of
 \href{http://www.python.org/}{Python 2.6} on your computer.  As of
-August 2011, there is no installer of Python 2.6.7 for Microsoft
-Windows yet, so you could try.  Users of this operating system may
-download \href{http://www.python.org/download/releases/2.6.6/}{Python
-  2.6.6}, instead.
+December 2011, there is no Python 2.6.7 installer for Microsoft
+Windows.  Users of this operating system should download
+\href{http://www.python.org/download/releases/2.6.6/}{Python 2.6.6},
+instead.
 
 Please also download and install these libraries:
 
 \begin{compactitem}
 \item \href{http://www.pyside.org//}{PySide} (version 1.0.5 or above)
 \item \href{http://www.pygame.org/}{pygame} (version 1.9.1 or above;
   please note that pygame's MIDI implementation is still in its
-  infancy and may occasionally crash \application{Python MCU})
+  infancy and may thus occasionally crash \application{Python MCU})
 \end{compactitem}
 
 You'll also need virtual MIDI ports or cables to connect
@@ -79,6 +79,113 @@ \chapter{Installation}
 Microsoft Windows, try double-clicking on \path{PythonMcu.pyw},
 instead.
 
+\chapter{Running Python MCU}
+\label{chap:runnint_python_mcu}
+
+Here's a word of warning.  Although I have taken precautionary steps,
+there is some inherent risk that your controller might be destroyed by
+running \application{Python MCU} (mine was, once, when I was trying to
+change a lot of code at once).  So please read the license in
+\ref{chap:gpl} before you run \application{Python MCU}, especially the
+sections \emph{Disclaimer of Warranty} and \emph{Limitation of
+  Liability}.
+
+That being said, here's how to set up \application{Python MCU}\dots
+
+\begin{center}
+  \includegraphics[scale=\screenshotscale,clip]{include/images/python_mcu.png}
+\end{center}
+
+
+\begin{description}
+\item[Emulation:] Choose between ``Logic Control'' and ``Mackie
+  Control''.  The latter should be fine for most current DAWs.  The
+  extension units ``Logic Control XT'' and ``Mackie Control XT'' have
+  been added for completeness, but I don't think you'll ever need
+  them.
+
+\item[Connection:] Defaults to ``Challenge / Response'' for ``Logic
+  Control'' and ``Wait for MIDI data'' for ``Mackie Control''.  If
+  you're having trouble connecting to your DAW, try changing this
+  setting.
+
+\item[MIDI In/Out:] The virtual MIDI cables that connect
+  \application{Python MCU} to your DAW.  I freely admit that it's not
+  easy to understand the routing of virtual MIDI cables, so I
+  recommend using the first cable to send data from
+  \application{Python MCU} to your DAW and the second one to send data
+  from your DAW to \application{Python MCU}:
+
+  \includegraphics[scale=\screenshotscale,clip]{include/images/virtual_midi_cables.png}
+
+  This way, you can simply look at the screen-shots in this document
+  and set up \application{Python MCU} and your DAW accordingly.
+
+\item[Controller:] Select your hardware controller and the MIDI ports
+  it provides or is connected to.  There is a text field directly
+  below which might give you some hints on connecting your controller
+  to \application{Python MCU}.
+
+\end{description}
+
+\chapter{Hardware controllers}
+\label{chap:controller_setup}
+
+For the controller assignments of your hardware, please have a look at
+\path{doc/Controllers.pdf}.
+
+\section{Novation ZeRO SL MkII}
+
+This adaption makes good use of preset \#32 (Ableton Live Automap), so
+you either have to select this preset whenever you want to use
+\application{Python MCU} or set it up as your default preset.
+
+Whenever you press the \textbf{Automap} button, \application{Python
+  MCU} temporarily stops to let you do your thing in \textbf{Automap}.
+When you're done, simply press the \textbf{Automap} button again.
+
+You may also connect a sustain pedal to the ``control pedal'' input
+and use it to alternately start and stop playback in your DAW.  If it
+doesn't work, you'll have to change the preset: Edit $\rightarrow{}$
+Sustain Pedal $\rightarrow{}$ Ports: \textbf{ComnPORT} and MidiChan:
+\textbf{ComnCHAN.}  Don't forget to save your changes\dots
+
+\chapter{Digital Audio Workstations}
+\label{chap:daw_setup}
+
+\section{Ableton Live}
+
+\begin{description}
+\item[Emulation:] Mackie Control (Wait for MIDI data)
+\end{description}
+
+\includegraphics[scale=\screenshotscale,clip]{include/images/live_8.png}
+
+\section{Cockos Reaper}
+
+\begin{description}
+\item[Emulation:] Mackie Control (Wait for MIDI data)
+\end{description}
+
+\includegraphics[scale=\screenshotscale,clip]{include/images/reaper_4.png}
+
+\section{Emagic Logic}
+
+\begin{description}
+\item[Emulation:] Logic Control (Challenge / Response)
+\end{description}
+
+\includegraphics[scale=\screenshotscale,clip]{include/images/logic_5.png}
+
+\section{Image-Line FL Studio}
+
+\begin{description}
+\item[Emulation:] Mackie Control (Wait for MIDI data)
+\end{description}
+
+\includegraphics[scale=\screenshotscale,clip]{include/images/fl_studio_10.png}
+
+
 \chapter{Tested configurations}
 \label{chap:tested_configurations}
 
@@ -93,7 +200,8 @@ \section{Microsoft Windows XP}
 \begin{compactitem}
 \item Ableton Live 8
 \item Cockos Reaper 4
-\item Emagic Logic 5
+\item Emagic Logic Platinum 5
+\item Image-Line FL Studio Pro 10
 \end{compactitem}
 
 \section{Apple Mac}
@@ -104,7 +212,7 @@ \section{Apple Mac}
 \section{GNU/Linux}
 
 \begin{compactitem}
-\item ardour 2 \emph{(skipped a lot of commands, though)}
+\item ardour 2 (\emph{skipped a lot of commands, though})
 \end{compactitem}
 
 \chapter{Extending Python MCU}