path: root/introduction.tex
diff options
authorMatthias P. Braendli <matthias.braendli@mpb.li>2019-09-23 19:00:45 +0200
committerMatthias P. Braendli <matthias.braendli@mpb.li>2019-09-23 19:00:45 +0200
commitb24baf8a1a59f87fae84a80115beaa73d3e5cd4f (patch)
treeaa876e7b939f893b0f6ad6767dbaac43e2f5dd1c /introduction.tex
parent8d60e3486dd6b0f2dc72223dc3f660d5d6ab8e00 (diff)
Rework to prefer EDI over ZeroMQ
Diffstat (limited to 'introduction.tex')
1 files changed, 3 insertions, 5 deletions
diff --git a/introduction.tex b/introduction.tex
index ff6357b..6a6658c 100644
--- a/introduction.tex
+++ b/introduction.tex
@@ -113,9 +113,7 @@ a real-time streaming scenario (e.g.~in a transmitter).
ODR-DabMux can read input audio or data from files (``.mp2'' for DAB, ``.dabp'' for
\dabplus), FIFOs (also called ``named pipes''), or from a network connection. This
-network connection can use UDP or ZeroMQ. The CURVE authentication mechanism
-from ZeroMQ can also be used to authenticate the encoder, in order to prevent
-third parties from disrupting or hijacking programmes.
+network connection can use UDP (STI-D) or EDI.
The configuration of the multiplexer is given in a configuration file, whose
format is defined in the example files in the \verb+doc/+ folder inside the
@@ -134,7 +132,7 @@ software-defined radio (SDR) devices using the
SoapySDR\footnoteurl{https://github.com/pothosware/SoapySDR/wiki} library.
The output of the modulator can also be sent to a GNURadio flow-graph for
-further processing, conversion or analysis using a ZeroMQ interface.
+further processing, conversion or analysis using a ZeroMQ network connection.
The ODR-AudioEnc encoder can be used to encode for DAB and \dabplus. It includes
@@ -147,7 +145,7 @@ Another encoder called twolame is not compatible with DAB even though it is more
recent than TooLAME, and cannot be used for our application.
The framing and error correction which are needed for \dabplus{}, as well as the
-programme-associated data (PAD) insertion, the output to the ZeroMQ interface,
+programme-associated data (PAD) insertion, the output EDI protocol,
and the input from Advanced Linux Sound Architecture (ALSA) were then added by
different parties.