summaryrefslogtreecommitdiffstats
path: root/thesis
diff options
context:
space:
mode:
Diffstat (limited to 'thesis')
-rw-r--r--thesis/thesis.tex23
1 files changed, 22 insertions, 1 deletions
diff --git a/thesis/thesis.tex b/thesis/thesis.tex
index a596240..d049da9 100644
--- a/thesis/thesis.tex
+++ b/thesis/thesis.tex
@@ -112,6 +112,10 @@ parskip=never]{paper}
description={A programming language, \gls{ide} and synthesis server for
realtime audio processing and synthesis}
}
+\newglossaryentry{python}{
+ name={Python},
+ description={An multi-purpose, object-oriented programming language}
+}
\newglossaryentry{qt4}{
name={Qt4},
description={Version 4 (legacy) of the cross-platform application framework
@@ -888,7 +892,7 @@ parskip=never]{paper}
Harris and is now actively maintained by Stephen Sinclair.\\
The library, written in C, offers a C++ abstraction layer and is
released under the \gls{lgpl} v2.1 or greater. Additionally there are
- wrappers for the Perl and Python programming languages.\\
+ wrappers for the Perl and \gls{python} programming languages.\\
Due to its long standing availability and usage in many small and
large-scale software projects, alongside its fairly straight forward
implementability, it was chosen as the candidate for establishing a
@@ -1976,6 +1980,23 @@ ssr-aap -N “server” -C “127.0.0.1:50002”
\subsubsection{Status messages}
\label{subsubsec:status_messages}
+ When reflecting about different use-cases for networking setups
+ involving the \gls{ssr}, it became apparent, that in certain
+ situations it would be desirable to be able to poll instances for
+ information, involving sources, scenes and the like.\\
+ One example is the implementation of a light-weight, single-purpose
+ \gls{gui} (e.g.\ non-interactive display of source positions) in
+ another programming language, such as \gls{python}, \gls{pd}, or
+ \gls{supercollider}, while only relying on \gls{osc} for communication
+ between the parts. Another would be the case, where certain aspects of
+ a client or server instance should be monitored (e.g.\ \gls{cpu}
+ usage). Both examples should allow a (\gls{gui}) process to be
+ subscribed, after the active \gls{ssr} instances started rendering.\\
+ To be able to retrieve information from a \gls{ssr} instance, its
+ \gls{pubsub} interface has to be extended and \mintinline{c++}{get}
+ functions implemented - where applicable - to return the desired
+ information. A special case of this feature is described
+ in~\ref{subsubsec:scene_transfer}.
\subsubsection{Scene transfer}
\label{subsubsec:scene_transfer}