Merge branch 'refs/heads/t/rm_oaep'
[paraslash.git] / web /
1 **Paraslash user manual**
3 This document describes how to install, configure and use the paraslash
4 network audio streaming system. Most chapters start with a chapter
5 overview and conclude with an example section. We try to focus on
6 general concepts and on the interaction of the various pieces of the
7 paraslash package. Hence this user manual is not meant as a replacement
8 for the manual pages that describe all command line options of each
9 paraslash executable.
11 ============
12 Introduction
13 ============
15 In this chapter we give an [overview](#Overview) of the interactions of
16 the two main programs contained in the paraslash package, followed by
17 [brief descriptions](#The.paraslash.executables) of all executables.
19 Overview
20 --------
22 The core functionality of the para suite is provided by two main
23 executables, para_server and para_audiod. The former maintains a
24 database of audio files and streams these files to para_audiod which
25 receives and plays the stream.
27 In a typical setting, both para_server and para_audiod act as
28 background daemons whose functionality is controlled by client
29 programs: the para_audioc client controls para_audiod over a local
30 socket while the para_client program connects to para_server over a
31 local or remote networking connection.
33 Typically, these two daemons run on different hosts but a local setup
34 is also possible.
36 A simplified picture of a typical setup is as follows
38 server_host client_host
39 ~~~~~~~~~~~ ~~~~~~~~~~~
41 +-----------+ audio stream +-----------+
42 |para_server| -----------------------------> |para_audiod|
43 +-----------+ +-----------+
44 ^ ^
45 | |
46 | | connect
47 | |
48 | |
49 | +-----------+
50 | |para_audioc|
51 | +-----------+
52 |
53 |
54 | connect +-----------+
55 +-------------------------------------- |para_client|
56 +-----------+
57 The paraslash executables
58 -------------------------
60 ### para_server ###
62 para_server streams binary audio data (MP3, ...) over local and/or
63 remote networks. It listens on a TCP port and accepts commands such
64 as play, stop, pause, next from authenticated clients. There are
65 many more commands though, see the man page of para_server for a
66 description of all commands.
68 It supports three built-in network streaming protocols
69 (senders/receivers): HTTP, DCCP, or UDP. This is explained in more
70 detail in the section on [networking](#Networking).
72 The built-in audio file selector of paraslash is used to manage your
73 audio files. It maintains statistics on the usage of all available
74 audio files such as last-played time, and the number of times each
75 file was selected.
77 Additional information may be added to the database to allow
78 fine-grained selection based on various properties of the audio file,
79 including information found in (ID3) tags. However, old-fashioned
80 playlists are also supported.
82 It is also possible to store images (album covers) and lyrics in the
83 database and associate these to the corresponding audio files.
85 The section on the [audio file selector](
86 discusses this topic.
89 ### para_client ###
91 The client program to connect to para_server. paraslash commands
92 are sent to para_server and the response is dumped to STDOUT. This
93 can be used by any scripting language to produce user interfaces with
94 little programming effort.
96 All connections between para_server and para_client are encrypted
97 with a symmetric session key. For each user of paraslash you must
98 create a public/secret RSA key pair for authentication.
100 If para_client is started without non-option arguments, an interactive
101 session (shell) is started. Command history and command completion are
102 supported through libreadline.
104 ### para_audiod ###
106 The local daemon that collects information from para_server.
108 It runs on the client side and connects to para_server. As soon as
109 para_server announces the availability of an audio stream, para_audiod
110 starts an appropriate receiver, any number of filters and a paraslash
111 writer to play the stream.
113 Moreover, para_audiod listens on a local socket and sends status
114 information about para_server and para_audiod to local clients on
115 request. Access via this local socket may be restricted by using Unix
116 socket credentials, if available.
119 ### para_audioc ###
121 The client program which talks to para_audiod. Used to control
122 para_audiod, to receive status info, or to grab the stream at any
123 point of the decoding process. Like para_client, para_audioc supports
124 interactive sessions on systems with libreadline.
126 ### para_recv ###
128 A command line HTTP/DCCP/UDP stream grabber. The http mode is
129 compatible with arbitrary HTTP streaming sources (e.g. icecast).
130 In addition to the three network streaming modes, para_recv can also
131 operate in local (afh) mode. In this mode it writes the content of
132 an audio file on the local file system in complete chunks to stdout,
133 optionally 'just in time'. This allows to cut an audio file without
134 first decoding it, and it enables third-party software which is unaware
135 of the particular audio format to send complete frames in real time.
137 ### para_filter ###
139 A filter program that reads from STDIN and writes to STDOUT.
140 Like para_recv, this is an atomic building block which can be used to
141 assemble higher-level audio receiving facilities. It combines several
142 different functionalities in one tool: decoders for multiple audio
143 formats and a number of processing filters, among these a normalizer
144 for audio volume.
146 ### para_afh ###
148 A small stand-alone program that prints tech info about the given
149 audio file to STDOUT. It can be instructed to print a "chunk table",
150 an array of offsets within the audio file.
152 ### para_write ###
154 A modular audio stream writer. It supports a simple file writer
155 output plug-in and optional WAV/raw players for ALSA (Linux) and OSS.
156 para_write can also be used as a stand-alone WAV or raw audio player.
158 ### para_play ###
160 A command line audio player.
162 ### para_gui ###
164 Curses-based gui that presents status information obtained in a curses
165 window. Appearance can be customized via themes. para_gui provides
166 key-bindings for the most common server commands and new key-bindings
167 can be added easily.
169 ### para_fade ###
171 An alarm clock and volume-fader for OSS and ALSA.
173 ===========
174 Quick start
175 ===========
177 This chapter lists the [necessary software](#Requirements)
178 that must be installed to compile the paraslash package, describes
179 how to [compile and install](#Installation) the paraslash
180 source code and the steps that have to be performed in order to
181 [set up](#Configuration) a typical server and client.
183 Requirements
184 ------------
185 ### For the impatient ###
187 git clone git://
188 cd osl && make && sudo make install && sudo ldconfig
189 sudo apt-get install autoconf libssl-dev help2man gengetopt m4 \
190 libmad0-dev libid3tag0-dev libasound2-dev libvorbis-dev \
191 libfaad-dev libspeex-dev libFLAC-dev libsamplerate-dev realpath \
192 libasound2-dev libao-dev libreadline-dev libncurses-dev \
193 libopus-dev
195 ### Detailed description ###
197 In any case you will need
199 - [libosl]( The _object
200 storage layer_ library is used by para_server. To clone the source
201 code repository, execute
203 git clone git://
205 - [gcc]( or
206 [clang]( All gcc versions >= 4.2 are currently
207 supported. Clang version 1.1 or newer should work as well.
209 - [gnu make]( is also shipped with the
210 disto. On BSD systems the gnu make executable is often called gmake.
212 - [bash]( Some scripts which run
213 during compilation require the _Bourne again shell_. It is most
214 likely already installed.
216 - [gengetopt]( is needed to
217 generate the C code for the command line parsers of all paraslash
218 executables.
220 - [help2man]( is used to create
221 the man pages.
223 - [m4]( Some source files are generated
224 from templates by the m4 macro processor.
226 Optional:
228 - [openssl]( or
229 [libgcrypt]( At least one
230 of these two libraries is needed as the backend for cryptographic
231 routines on both the server and the client side. Both openssl and
232 libgcrypt are usually shipped with the distro, but you might have
233 to install the development package (`libssl-dev` or `libgcrypt-dev`
234 on debian systems) as well.
236 - [libmad]( To compile in MP3
237 support for paraslash, the development package must be installed. It
238 is called `libmad0-dev` on debian-based systems. Note that libmad is
239 not necessary on the server side, i.e., for sending MP3 files.
241 - [libid3tag]( For version-2
242 ID3 tag support, you willl need the libid3tag development package
243 `libid3tag0-dev`. Without libid3tag, only version-1 tags are
244 recognized. The mp3 tagger also needs this library for modifying
245 (id3v1 and id3v2) tags.
247 - [ogg vorbis]( For ogg vorbis streams
248 you need libogg, libvorbis, libvorbisfile. The corresponding Debian
249 packages are called `libogg-dev` and `libvorbis-dev`.
251 - [libfaad]( For aac files (m4a) you
252 need libfaad (`libfaad-dev`).
254 - [speex]( In order to stream or decode speex
255 files, libspeex (`libspeex-dev`) is required.
257 - [flac]( To stream or decode files
258 encoded with the _Free Lossless Audio Codec_, libFLAC (`libFLAC-dev`)
259 must be installed.
261 - [libsamplerate]( The
262 resample filter will only be compiled if this library is
263 installed. Debian package: `libsamplerate-dev`.
265 - [alsa-lib]( On Linux, you will
266 need to have the ALSA development package `libasound2-dev` installed.
268 - [libao]( Needed to build
269 the ao writer (ESD, PulseAudio,...). Debian package: `libao-dev`.
271 - [curses]( Needed for
272 para_gui. Debian package: `libncurses-dev`.
274 - [GNU
275 Readline]( If
276 this library (`libreadline-dev`) is installed, para_client, para_audioc
277 and para_play support interactive sessions.
279 Installation
280 ------------
281 To build the sources from a tarball, execute
283 ./configure && make
285 To build from git or a gitweb snapshot, run this command instead:
287 ./
289 There should be no errors but probably some warnings about missing
290 packages which usually implies that not all audio formats will be
291 supported. If headers or libs are installed at unusual locations you
292 might need to tell the configure script where to find them. Try
294 ./configure --help
296 to see a list of options. If the paraslash package was compiled
297 successfully, execute (optionally)
299 make test
301 to run the paraslash test suite. If all tests pass, execute as root
303 make install
305 to install executables under /usr/local/bin and the man pages under
306 /usr/local/man.
308 Configuration
309 -------------
311 ### Create a paraslash user ###
313 In order to control para_server at runtime you must create a paraslash
314 user. As authentication is based on the RSA crypto system you'll have
315 to create an RSA key pair. If you already have a user and an RSA key
316 pair, you may skip this step.
318 In this section we'll assume a typical setup: You would like to run
319 para_server on some host called server_host as user foo, and you want
320 to connect to para_server from another machine called client_host as
321 user bar.
323 As foo@server_host, create ~/.paraslash/server.users by typing the
324 following commands:
326 user=bar
327 target=~/.paraslash/server.users
328 key=~/.paraslash/$user
330 mkdir -p ~/.paraslash
331 echo "user $user $key $perms" >> $target
333 Next, change to the "bar" account on client_host and generate the
334 key pair with the commands
336 ssh-keygen -q -t rsa -b 2048 -N '' -f $key
338 This generates the two files id_rsa and in ~/.ssh. Note
339 that para_server won't accept keys shorter than 2048 bits. Moreover,
340 para_client rejects private keys which are world-readable.
342 para_server only needs to know the public key of the key pair just
343 created. Copy this public key to server_host:
345 src=~/.ssh/
346 dest=.paraslash/$LOGNAME
347 scp $src foo@server_host:$dest
349 Finally, tell para_client to connect to server_host:
351 conf=~/.paraslash/client.conf
352 echo 'hostname server_host' > $conf
355 ### Start para_server ###
357 For this first try, we'll use the info loglevel to make the output
358 of para_server more verbose.
360 para_server -l info
362 Now you can use para_client to connect to the server and issue
363 commands. Open a new shell as bar@client_host and try
365 para_client help
366 para_client si
368 to retrieve the list of available commands and some server info.
369 Don't proceed if this doesn't work.
371 ### Create and populate the database ###
373 An empty database is created with
375 para_client init
377 This initializes a couple of empty tables under
378 ~/.paraslash/afs_database-0.4. You normally don't need to look at these
379 tables, but it's good to know that you can start from scratch with
381 rm -rf ~/.paraslash/afs_database-0.4
383 in case something went wrong.
385 Next, you need to add some audio files to that database so that
386 para_server knows about them. Choose an absolute path to a directory
387 containing some audio files and add them to the audio file table:
389 para_client add /my/mp3/dir
391 This might take a while, so it is a good idea to start with a directory
392 containing not too many files. Note that the table only contains data
393 about the audio files found, not the files themselves.
395 You may print the list of all known audio files with
397 para_client ls
399 ### Configure para_audiod ###
401 We will have to tell para_audiod that it should receive the audio
402 stream from server_host via http:
404 para_audiod -l info -r '.:http -i server_host'
406 You should now be able to listen to the audio stream once para_server
407 starts streaming. To activate streaming, execute
409 para_client play
411 Since no playlist has been specified yet, the "dummy" mode which
412 selects all known audio files is activated automatically. See the
413 section on the [audio file selector]( for how
414 to use playlists and moods to specify which files should be streamed
415 in which order.
417 Troubleshooting
418 ---------------
420 If you receive a socket related error on server or audiod startup,
421 make sure you have write permissions to the /var/paraslash directory:
423 sudo chown $LOGNAME /var/paraslash
425 Alternatively, use the --afs-socket (para_server) or --socket
426 (para_audiod) option to specify a different socket pathname.
428 To identify streaming problems try to receive, decode and play the
429 stream manually using para_recv, para_filter and para_write as follows.
430 For simplicity we assume that you're running Linux/ALSA and that only
431 MP3 files have been added to the database.
433 para_recv -r 'http -i server_host' > file.mp3
434 # (interrupt with CTRL+C after a few seconds)
435 ls -l file.mp3 # should not be empty
436 para_filter -f mp3dec -f wav < file.mp3 > file.wav
437 ls -l file.wav # should be much bigger than file.mp3
438 para_write -w alsa < file.wav
440 Double check what is logged by para_server and use the --loglevel
441 option of para_recv, para_filter and para_write to increase verbosity.
443 ===============
444 User management
445 ===============
447 para_server uses a challenge-response mechanism to authenticate
448 requests from incoming connections, similar to ssh's public key
449 authentication method. Authenticated connections are encrypted using
450 a stream cipher, either RC4 or AES in integer counter mode.
452 In this chapter we briefly describe RSA, RC4 and AES, and sketch the
453 [authentication handshake](#Client-server.authentication)
454 between para_client and para_server. User management is discussed
455 in the section on [the user_list file](#The.user_list.file).
456 These sections are all about communication between the client and the
457 server. Connecting para_audiod is a different matter and is described
458 in a [separate section](#Connecting.para_audiod).
460 RSA, RC4, AES
461 -------------
463 RSA is an asymmetric block cipher which is used in many applications,
464 including ssh and gpg. An RSA key consists in fact of two keys,
465 called the public key and the private key. A message can be encrypted
466 with either key and only the counterpart of that key can decrypt
467 the message. While RSA can be used for both signing and encrypting
468 a message, paraslash uses RSA only for the latter purpose. The
469 RSA public key encryption and signatures algorithms are defined in
470 detail in RFC 2437.
472 RC4 is a stream cipher, i.e. the input is XORed with a pseudo-random
473 key stream to produce the output. Decryption uses the same function
474 calls as encryption. While RC4 supports variable key lengths,
475 paraslash uses a fixed length of 256 bits, which is considered a
476 strong encryption by today's standards. Since the same key must never
477 be used twice, a different, randomly-generated key is used for every
478 new connection.
480 AES, the advanced encryption standard, is a well-known symmetric block
481 cipher, i.e. a transformation operating on fixed-length blocks which
482 is determined by a single key for both encryption and decryption. Any
483 block cipher can be turned into a stream cipher by generating
484 a pseudo-random key stream by encrypting successive values of a
485 counter. The AES_CTR128 stream cipher used in paraslash is obtained
486 in this way from the AES block cipher with a 128 bit block size.
488 Client-server authentication
489 ----------------------------
491 The authentication handshake between para_client and para_server goes
492 as follows:
494 - para_client connects to para_server and sends an authentication
495 request for a user. It does so by connecting to TCP port 2990 of the
496 server host. This port is called the para_server _control port_.
498 - para_server accepts the connection and forks a child process which
499 handles the incoming request. The parent process keeps listening on the
500 control port while the child process (also called para_server below)
501 continues as follows.
503 - para_server loads the RSA public key of that user, fills a
504 fixed-length buffer with random bytes, encrypts that buffer using the
505 public key and sends the encrypted buffer to the client. The first
506 part of the buffer is the challenge which is used for authentication
507 while the second part is the session key.
509 - para_client receives the encrypted buffer and decrypts it with the
510 user's private key, thereby obtaining the challenge buffer and the
511 session key. It sends the SHA1 hash value of the challenge back to
512 para_server and stores the session key for further use.
514 - para_server also computes the SHA1 hash of the challenge and compares
515 it against what was sent back by the client.
517 - If the two hashes do not match, the authentication has failed and
518 para_server closes the connection.
520 - Otherwise the user is considered authenticated and the client is
521 allowed to proceed by sending a command to be executed. From this
522 point on the communication is encrypted using the stream cipher with
523 the session key known to both peers.
525 paraslash relies on the quality of the pseudo-random bytes provided
526 by the crypto library (openssl or libgcrypt), on the security of the
527 implementation of the RSA, RC4 and AES crypto routines and on the
528 infeasibility to invert the SHA1 function.
530 Neither para_server or para_client create RSA keys on their
531 own. This has to be done once for each user as sketched in
532 [Quick start](#Quick.start) and discussed in more detail
533 [below](#The.user_list.file).
535 The user_list file
536 ------------------
538 At startup para_server reads the user list file which contains one
539 line per user. The default location of the user list file may be
540 changed with the --user-list option.
542 There should be at least one user in this file. Each user must have
543 an RSA key pair. The public part of the key is needed by para_server
544 while the private key is needed by para_client. Each line of the
545 user list file must be of the form
547 user <username> <key> <perms>
549 where _username_ is an arbitrary string (usually the user's login
550 name), _key_ is the full path to that user's public RSA key, and
551 _perms_ is a comma-separated list of zero or more of the following
552 permission bits:
554 +---------------------------------------------------------+
555 | AFS_READ | read the contents of the databases |
556 +-----------+---------------------------------------------+
557 | AFS_WRITE | change database contents |
558 +-----------+---------------------------------------------+
559 | VSS_READ | obtain information about the current stream |
560 +-----------+---------------------------------------------+
561 | VSS_WRITE | change the current stream |
562 +---------------------------------------------------------+
564 The permission bits specify which commands the user is allowed to
565 execute. The output of
567 para_client help
569 contains in the third column the permissions needed to execute the
570 command.
572 It is possible to make para_server reread the user_list file by
573 executing the paraslash "hup" command or by sending SIGHUP to the
574 PID of para_server.
576 Connecting para_audiod
577 ----------------------
579 para_audiod listens on a Unix domain socket. Those sockets are
580 for local communication only, so only local users can connect to
581 para_audiod. The default is to let any user connect but this can be
582 restricted on platforms that support UNIX socket credentials which
583 allow para_audiod to obtain the Unix credentials of the connecting
584 process.
586 Use para_audiod's --user-allow option to allow connections only for
587 a limited set of users.
589 =======================
590 The audio file selector
591 =======================
593 paraslash comes with a sophisticated audio file selector (AFS),
594 whose main task is to determine which file to stream next, based on
595 information on the audio files stored in a database. It communicates
596 also with para_client whenever an AFS command is executed, for example
597 to answer a database query.
599 Besides the traditional playlists, AFS supports audio file selection
600 based on _moods_ which act as a filter that limits the set of all
601 known audio files to those which satisfy certain criteria. It also
602 maintains tables containing images (e.g. album cover art) and lyrics
603 that can be associated with one or more audio files.
605 AFS employs [libosl](, the
606 object storage layer library, as the backend library for storing
607 information on audio files, playlists, etc. This library offers
608 functionality similar to a relational database, but is much more
609 lightweight than a full database backend.
611 In this chapter we sketch the setup of the [AFS
612 process](#The.AFS.process) during server startup and proceed with the
613 description of the [layout](#Database.layout) of the various database
614 tables. The section on [playlists and moods](#Playlists.and.moods)
615 explains these two audio file selection mechanisms in detail
616 and contains pratical examples. The way [file renames and content
617 changes](#File.renames.and.content.changes) are detected is discussed
618 briefly before the [Troubleshooting](#Troubleshooting) section
619 concludes the chapter.
621 The AFS process
622 ---------------
624 On startup, para_server forks to create the AFS process which opens
625 the OSL database tables. The server process communicates with the
626 AFS process via pipes and shared memory. Usually, the AFS process
627 awakes only briefly whenever the current audio file changes. The AFS
628 process determines the next audio file, opens it, verifies it has
629 not been changed since it was added to the database and passes the
630 open file descriptor to the server process, along with audio file
631 meta-data such as file name, duration, audio format and so on. The
632 server process then starts to stream the audio file.
634 The AFS process also accepts connections from local clients via
635 a well-known socket. However, only child processes of para_server
636 may connect through this socket. All server commands that have the
637 AFS_READ or AFS_WRITE permission bits use this mechanism to query or
638 change the database.
640 Database layout
641 ---------------
643 ### The audio file table ###
645 This is the most important and usually also the largest table of the
646 AFS database. It contains the information needed to stream each audio
647 file. In particular the following data is stored for each audio file.
649 - SHA1 hash value of the audio file contents. This is computed once
650 when the file is added to the database. Whenever AFS selects this
651 audio file for streaming the hash value is recomputed and checked
652 against the value stored in the database to detect content changes.
654 - The time when this audio file was last played.
656 - The number of times the file has been played so far.
658 - The attribute bitmask.
660 - The image id which describes the image associated with this audio
661 file.
663 - The lyrics id which describes the lyrics associated with this
664 audio file.
666 - The audio format id (MP3, OGG, ...).
668 - An amplification value that can be used by the amplification filter
669 to pre-amplify the decoded audio stream.
671 - The chunk table. It describes the location and the timing of the
672 building blocks of the audio file. This is used by para_server to
673 send chunks of the file at appropriate times.
675 - The duration of the audio file.
677 - Tag information contained in the audio file (ID3 tags, Vorbis
680 - The number of channels
682 - The encoding bitrate.
684 - The sampling frequency.
686 To add or refresh the data contained in the audio file table, the _add_
687 command is used. It takes the full path of either an audio file or a
688 directory. In the latter case, the directory is traversed recursively
689 and all files which are recognized as valid audio files are added to
690 the database.
692 ### The attribute table ###
694 The attribute table contains two columns, _name_ and _bitnum_. An
695 attribute is simply a name for a certain bit number in the attribute
696 bitmask of the audio file table.
698 Each of the 64 bits of the attribute bitmask can be set for each
699 audio file individually. Hence up to 64 different attributes may be
700 defined. For example, "pop", "rock", "blues", "jazz", "instrumental",
701 "german_lyrics", "speech", whatever. You are free to choose as
702 many attributes as you like and there are no naming restrictions
703 for attributes.
705 A new attribute "test" is created by
707 para_client addatt test
708 and
709 para_client lsatt
711 lists all available attributes. You can set the "test" attribute for
712 an audio file by executing
714 para_client setatt test+ /path/to/the/audio/file
716 Similarly, the "test" bit can be removed from an audio file with
718 para_client setatt test- /path/to/the/audio/file
720 Instead of a path you may use a shell wildcard pattern. The attribute
721 is applied to all audio files matching this pattern:
723 para_client setatt test+ '/test/directory/*'
725 The command
727 para_client -- ls -l=v
729 gives you a verbose listing of your audio files also showing which
730 attributes are set.
732 In case you wonder why the double-dash in the above command is needed:
733 It tells para_client to not interpret the options after the dashes. If
734 you find this annoying, just say
736 alias para='para_client --'
738 and be happy. In what follows we shall use this alias.
740 The "test" attribute can be dropped from the database with
742 para rmatt test
744 Read the output of
746 para help ls
747 para help setatt
749 for more information and a complete list of command line options to
750 these commands.
752 ### Blob tables ###
754 The image, lyrics, moods and playlists tables are all blob tables.
755 Blob tables consist of three columns each: The identifier which is
756 a positive number that is auto-incremented, the name (an arbitrary
757 string) and the content (the blob).
759 All blob tables support the same set of actions: cat, ls, mv, rm
760 and add. Of course, _add_ is used for adding new blobs to the table
761 while the other actions have the same meaning as the corresponding
762 Unix commands. The paraslash commands to perform these actions are
763 constructed as the concatenation of the table name and the action. For
764 example addimg, catimg, lsimg, mvimg, rmimg are the commands that
765 manipulate or query the image table.
767 The add variant of these commands is special as these commands read
768 the blob contents from stdin. To add an image to the image table the
769 command
771 para addimg image_name < file.jpg
773 can be used.
775 Note that the images and lyrics are not interpreted at all, and also
776 the playlist and the mood blobs are only investigated when the mood
777 or playlist is activated with the select command.
779 ### The score table ###
781 The score table describes those audio files which are admissible for
782 the current mood or playlist (see below). The table has two columns:
783 a pointer to a row of the audio file table and a score value.
785 Unlike all other tables of the database, the score table remains in
786 memory and is never stored on disk. It is initialized at startup and
787 recomputed when the select command loads a new mood or playlist.
789 When the audio file selector is asked to open the next audio file,
790 it picks the row with the highest score, opens the corresponding
791 file and passes the file descriptor to the virtual streaming system.
792 At this point the last_played and the num_played fields of the selected
793 file are updated and the score is recomputed.
795 Playlists and moods
796 -------------------
798 Playlists and moods offer two different ways of specifying the set of
799 admissible files. A playlist in itself describes a set of admissible
800 files. A mood, in contrast, describes the set of admissible files in
801 terms of attributes and other type of information available in the
802 audio file table. As an example, a mood can define a filename pattern,
803 which is then matched against the names of audio files in the table.
805 ### Playlists ###
807 Playlists are accommodated in the playlist table of the afs database,
808 using the aforementioned blob format for tables. A new playlist is
809 created with the addpl command by specifying the full (absolute)
810 paths of all desired audio files, separated by newlines. Example:
812 find /my/mp3/dir -name "*.mp3" | para addpl my_playlist
814 If _my_playlist_ already exists it is overwritten. To activate the
815 new playlist, execute
817 para select p/my_playlist
819 The audio file selector will assign scores to each entry of the list,
820 in descending order so that files will be selected in order. If a
821 file could not be opened for streaming, its entry is removed from
822 the score table (but not from the playlist).
824 ### Moods ###
826 A mood consists of a unique name and its *mood definition*, which is
827 a set of *mood lines* containing expressions in terms of attributes
828 and other data contained in the database.
830 At any time at most one mood can be *active* which means that
831 para_server is going to select only files from that subset of
832 admissible files.
834 So in order to create a mood definition one has to write a set of
835 mood lines. Mood lines come in three flavours: Accept lines, deny
836 lines and score lines.
838 The general syntax of the three types of mood lines is
841 accept [with score <score>] [if] [not] <mood_method> [options]
842 deny [with score <score>] [if] [not] <mood_method> [options]
843 score <score> [if] [not] <mood_method> [options]
846 Here <score> is either an integer or the string "random" which assigns
847 a random score to all matching files. The score value changes the
848 order in which admissible files are going to be selected, but is of
849 minor importance for this introduction.
851 So we concentrate on the first two forms, i.e. accept and deny
852 lines. As usual, everything in square brackets is optional, i.e.
853 accept/deny lines take the following form when ignoring scores:
855 accept [if] [not] <mood_method> [options]
857 and analogously for the deny case. The "if" keyword is only syntactic
858 sugar and has no function. The "not" keyword just inverts the result,
859 so the essence of a mood line is the mood method part and the options
860 following thereafter.
862 A *mood method* is realized as a function which takes an audio file
863 and computes a number from the data contained in the database.
864 If this number is non-negative, we say the file *matches* the mood
865 method. The file matches the full mood line if it either
867 - matches the mood method and the "not" keyword is not given,
868 or
869 - does not match the mood method, but the "not" keyword is given.
871 The set of admissible files for the whole mood is now defined as those
872 files which match at least one accept mood line, but no deny mood line.
873 More formally, an audio file F is admissible if and only if
875 (F ~ AL1 or F ~ AL2...) and not (F ~ DL1 or F ~ DN2 ...)
877 where AL1, AL2... are the accept lines, DL1, DL2... are the deny
878 lines and "~" means "matches".
880 The cases where no mood lines of accept/deny type are defined need
881 special treatment:
883 - Neither accept nor deny lines: This treats all files as
884 admissible (in fact, that is the definition of the dummy mood
885 which is activated automatically if no moods are available).
887 - Only accept lines: A file is admissible iff it matches at
888 least one accept line:
890 F ~ AL1 or F ~ AL2 or ...
892 - Only deny lines: A file is admissible iff it matches no
893 deny line:
895 not (F ~ DL1 or F ~ DN2 ...)
899 ### List of mood_methods ###
901 no_attributes_set
903 Takes no arguments and matches an audio file if and only if no
904 attributes are set.
906 is_set <attribute_name>
908 Takes the name of an attribute and matches iff that attribute is set.
910 path_matches <pattern>
912 Takes a filename pattern and matches iff the path of the audio file
913 matches the pattern.
915 artist_matches <pattern>
916 album_matches <pattern>
917 title_matches <pattern>
918 comment_matches <pattern>
920 Takes an extended regular expression and matches iff the text of the
921 corresponding tag of the audio file matches the pattern. If the tag
922 is not set, the empty string is matched against the pattern.
924 year ~ <num>
925 bitrate ~ <num>
926 frequency ~ <num>
927 channels ~ <num>
928 num_played ~ <num>
929 image_id ~ <num>
930 lyrics_id ~ <num>
932 Takes a comparator ~ of the set {<, =, <=, >, >=, !=} and a number
933 <num>. Matches an audio file iff the condition <val> ~ <num> is
934 satisfied where val is the corresponding value of the audio file
935 (value of the year tag, bitrate in kbit/s, etc.).
937 The year tag is special as its value is undefined if the audio file
938 has no year tag or the content of the year tag is not a number. Such
939 audio files never match. Another difference is the special treatment
940 if the year tag is a two-digit number. In this case either 1900 or
941 2000 is added to the tag value, depending on whether the number is
942 greater than 2000 plus the current year.
945 ### Mood usage ###
947 To create a new mood called "my_mood", write its definition into
948 some temporary file, say "tmpfile", and add it to the mood table
949 by executing
951 para addmood my_mood < tmpfile
953 If the mood definition is really short, you may just pipe it to the
954 client instead of using temporary files. Like this:
956 echo "$MOOD_DEFINITION" | para addmood my_mood
958 There is no need to keep the temporary file since you can always use
959 the catmood command to get it back:
961 para catmood my_mood
963 A mood can be activated by executing
965 para select m/my_mood
967 Once active, the list of admissible files is shown by the ls command
968 if the "-a" switch is given:
970 para ls -a
973 ### Example mood definition ###
975 Suppose you have defined attributes "punk" and "rock" and want to define
976 a mood containing only Punk-Rock songs. That is, an audio file should be
977 admissible if and only if both attributes are set. Since
979 punk and rock
981 is obviously the same as
983 not (not punk or not rock)
985 (de Morgan's rule), a mood definition that selects only Punk-Rock
986 songs is
988 deny if not is_set punk
989 deny if not is_set rock
993 File renames and content changes
994 --------------------------------
996 Since the audio file selector knows the SHA1 of each audio file that
997 has been added to the afs database, it recognizes if the content of
998 a file has changed, e.g. because an ID3 tag was added or modified.
999 Also, if a file has been renamed or moved to a different location,
1000 afs will detect that an entry with the same hash value already exists
1001 in the audio file table.
1003 In both cases it is enough to just re-add the new file. In the
1004 first case (file content changed), the audio table is updated, while
1005 metadata such as the num_played and last_played fields, as well as
1006 the attributes, remain unchanged. In the other case, when the file
1007 is moved or renamed, only the path information is updated, all other
1008 data remains as before.
1010 It is possible to change the behaviour of the add command by using the
1011 "-l" (lazy add) or the "-f" (force add) option.
1013 Troubleshooting
1014 ---------------
1016 Use the debug loglevel (-l debug) to show debugging info. All paraslash
1017 executables have a brief online help which is displayed when -h is
1018 given. The --detailed-help option prints the full help text.
1020 If para_server crashed or was killed by SIGKILL (signal 9), it
1021 may refuse to start again because of "dirty osl tables". In this
1022 case you'll have to run the oslfsck program of libosl to fix your
1023 database:
1025 oslfsck -fd ~/.paraslash/afs_database-0.4
1027 However, make sure para_server isn't running before executing oslfsck.
1029 If you don't mind to recreate your database you can start
1030 from scratch by removing the entire database directory, i.e.
1032 rm -rf ~/.paraslash/afs_database-0.4
1034 Be aware that this removes all attribute definitions, all playlists
1035 and all mood definitions and requires to re-initialize the tables.
1037 Although oslfsck fixes inconsistencies in database tables it doesn't
1038 care about the table contents. To check for invalid table contents, use
1040 para_client check
1042 This prints out references to missing audio files as well as invalid
1043 playlists and mood definitions.
1045 Similarly, para_audiod refuses to start if its socket file exists, since
1046 this indicates that another instance of para_audiod is running. After
1047 a crash a stale socket file might remain and you must run
1049 para_audiod --force
1051 once to fix it up.
1053 =======================================
1054 Audio formats and audio format handlers
1055 =======================================
1057 Audio formats
1058 -------------
1060 The following audio formats are supported by paraslash:
1062 ### MP3 ###
1064 Mp3, MPEG-1 Audio Layer 3, is a common audio format for audio storage,
1065 designed as part of its MPEG-1 standard. An MP3 file is made up of
1066 multiple MP3 frames, which consist of a header and a data block. The
1067 size of an MP3 frame depends on the bit rate and on the number
1068 of channels. For a typical CD-audio file (sample rate of 44.1 kHz
1069 stereo), encoded with a bit rate of 128 kbit, an MP3 frame is about
1070 400 bytes large.
1072 ### OGG/Vorbis ###
1074 OGG is a standardized audio container format, while Vorbis is an
1075 open source codec for lossy audio compression. Since Vorbis is most
1076 commonly made available via the OGG container format, it is often
1077 referred to as OGG/Vorbis. The OGG container format divides data into
1078 chunks called OGG pages. A typical OGG page is about 4KB large. The
1079 Vorbis codec creates variable-bitrate (VBR) data, where the bitrate
1080 may vary considerably.
1082 ### OGG/Speex ###
1084 Speex is an open-source speech codec that is based on CELP (Code
1085 Excited Linear Prediction) coding. It is designed for voice
1086 over IP applications, has modest complexity and a small memory
1087 footprint. Wideband and narrowband (telephone quality) speech are
1088 supported. As for Vorbis audio, Speex bit-streams are often stored
1089 in OGG files. As of 2012 this codec is considered obsolete since the
1090 Oppus codec, described below, surpasses its performance in all areas.
1092 ### OGG/Opus ###
1094 Opus is a lossy audio compression format standardized through RFC
1095 6716 in 2012. It combines the speech-oriented SILK codec and the
1096 low-latency CELT (Constrained Energy Lapped Transform) codec. Like
1097 OGG/Vorbis and OGG/Speex, Opus data is usually encapsulated in OGG
1098 containers. All known software patents which cover Opus are licensed
1099 under royalty-free terms.
1101 ### AAC ###
1103 Advanced Audio Coding (AAC) is a standardized, lossy compression
1104 and encoding scheme for digital audio which is the default audio
1105 format for Apple's iPhone, iPod, iTunes. Usually MPEG-4 is used as
1106 the container format and audio files encoded with AAC have the .m4a
1107 extension. A typical AAC frame is about 700 bytes large.
1109 ### WMA ###
1111 Windows Media Audio (WMA) is an audio data compression technology
1112 developed by Microsoft. A WMA file is usually encapsulated in the
1113 Advanced Systems Format (ASF) container format, which also specifies
1114 how meta data about the file is to be encoded. The bit stream of WMA
1115 is composed of superframes, each containing one or more frames of
1116 2048 samples. For 16 bit stereo a WMA superframe is about 8K large.
1118 ### FLAC ###
1120 The Free Lossless Audio Codec (FLAC) compresses audio without quality
1121 loss. It gives better compression ratios than a general purpose
1122 compressor like zip or bzip2 because FLAC is designed specifically
1123 for audio. A FLAC-encoded file consists of frames of varying size, up
1124 to 16K. Each frame starts with a header that contains all information
1125 necessary to decode the frame.
1127 Meta data
1128 ---------
1130 Unfortunately, each audio format has its own conventions how meta
1131 data is added as tags to the audio file.
1133 For MP3 files, ID3, version 1 and 2 are widely used. ID3 version 1
1134 is rather simple but also very limited as it supports only artist,
1135 title, album, year and comment tags. Each of these can only be at most
1136 32 characters long. ID3, version 2 is much more flexible but requires
1137 a separate library being installed for paraslash to support it.
1139 Ogg vorbis, ogg speex and flac files contain meta data as Vorbis
1140 comments, which are typically implemented as strings of the form
1141 "[TAG]=[VALUE]". Unlike ID3 version 1 tags, one may use whichever
1142 tags are appropriate for the content.
1144 AAC files usually use the MPEG-4 container format for storing meta
1145 data while WMA files wrap meta data as special objects within the
1146 ASF container format.
1148 paraslash only tracks the most common tags that are supported by
1149 all tag variants: artist, title, year, album, comment. When a file
1150 is added to the AFS database, the meta data of the file is extracted
1151 and stored in the audio file table.
1153 Chunks and chunk tables
1154 -----------------------
1156 paraslash uses the word "chunk" as common term for the building blocks
1157 of an audio file. For MP3 files, a chunk is the same as an MP3 frame,
1158 while for OGG files a chunk is an OGG page, etc. Therefore the chunk
1159 size varies considerably between audio formats, from a few hundred
1160 bytes (MP3) up to 16K (FLAC).
1162 The chunk table contains the offsets within the audio file that
1163 correspond to the chunk boundaries of the file. Like the meta data,
1164 the chunk table is computed and stored in the database whenever an
1165 audio file is added.
1167 The paraslash senders (see below) always send complete chunks. The
1168 granularity for seeking is therefore determined by the chunk size.
1170 Audio format handlers
1171 ---------------------
1173 For each audio format paraslash contains an audio format handler whose
1174 first task is to tell whether a given file is a valid audio file of
1175 this type. If so, the audio file handler extracts some technical data
1176 (duration, sampling rate, number of channels etc.), computes the
1177 chunk table and reads the meta data.
1179 The audio format handler code is linked into para_server and executed
1180 via the _add_ command. The same code is also available as a stand-alone
1181 tool, para_afh, which prints the technical data, the chunk table
1182 and the meta data of a file. Moreover, all audio format handlers are
1183 combined in the afh receiver which is part of para_recv and para_play.
1185 ==========
1186 Networking
1187 ==========
1189 Paraslash uses different network connections for control and data.
1190 para_client communicates with para_server over a dedicated TCP control
1191 connection. To transport audio data, separate data connections are
1192 used. For these data connections, a variety of transports (UDP, DCCP,
1193 HTTP) can be chosen.
1195 The chapter starts with the [control
1196 service](#The.paraslash.control.service), followed by a section
1197 on the various [streaming protocols](#Streaming.protocols)
1198 in which the data connections are described. The way
1199 audio file headers are embedded into the stream is discussed
1200 [briefly](#Streams.with.headers.and.headerless.streams) before the
1201 [example section](#Networking.examples) which illustrates typical
1202 commands for real-life scenarios.
1204 Both IPv4 and IPv6 are supported.
1206 The paraslash control service
1207 -----------------------------
1209 para_server is controlled at runtime via the paraslash control
1210 connection. This connection is used for server commands (play, stop,
1211 ...) as well as for afs commands (ls, select, ...).
1213 The server listens on a TCP port and accepts connections from clients
1214 that connect the open port. Each connection causes the server to fork
1215 off a client process which inherits the connection and deals with that
1216 client only. In this classical accept/fork approach the server process
1217 is unaffected if the child dies or goes crazy for whatever reason. In
1218 fact, the child process can not change address space of server process.
1220 The section on [client-server
1221 authentication](#Client-server.authentication) above described the
1222 early connection establishment from the crypto point of view. Here
1223 it is described what happens after the connection (including crypto
1224 setup) has been established. There are four processes involved during
1225 command dispatch as sketched in the following diagram.
1227 server_host client_host
1228 ~~~~~~~~~~~ ~~~~~~~~~~~
1230 +-----------+ connect +-----------+
1231 |para_server|<------------------------------ |para_client|
1232 +-----------+ +-----------+
1233 | ^
1234 | fork +---+ |
1235 +----------> |AFS| |
1236 | +---+ |
1237 | ^ |
1238 | | |
1239 | | connect (cookie) |
1240 | | |
1241 | | |
1242 | fork +-----+ inherited connection |
1243 +---------->|child|<--------------------------+
1244 +-----+
1246 Note that the child process is not a child of the afs process,
1247 so communication of these two processes has to happen via local
1248 sockets. In order to avoid abuse of the local socket by unrelated
1249 processes, a magic cookie is created once at server startup time just
1250 before the server process forks off the AFS process. This cookie is
1251 known to the server, AFS and the child, but not to unrelated processes.
1253 There are two different kinds of commands: First there are commands
1254 that cause the server to respond with some answer such as the list
1255 of all audio files. All but the addblob commands (addimg, addlyr,
1256 addpl, addmood) are of this kind. The addblob commands add contents
1257 to the database, so they need to transfer data the other way round,
1258 from the client to the server.
1260 There is no knowledge about the server commands built into para_client,
1261 so it does not know about addblob commands. Instead, the server sends
1262 a special "awaiting data" packet for these commands. If the client
1263 receives this packet, it sends STDIN to the server, otherwise it
1264 dumps data from the server to STDOUT.
1266 Streaming protocols
1267 -------------------
1269 A network (audio) stream usually consists of one streaming source,
1270 the _sender_, and one or more _receivers_ which read data over the
1271 network from the streaming source.
1273 Senders are thus part of para_server while receivers are part of
1274 para_audiod. Moreover, there is the stand-alone tool para_recv which
1275 can be used to manually download a stream, either from para_server
1276 or from a web-based audio streaming service.
1278 The following three streaming protocols are supported by paraslash:
1280 - HTTP. Recommended for public streams that can be played by any
1281 player like mpg123, xmms, itunes, winamp, etc. The HTTP sender is
1282 supported on all operating systems and all platforms.
1284 - DCCP. Recommended for LAN streaming. DCCP is currently available
1285 only for Linux.
1287 - UDP. Recommended for multicast LAN streaming.
1289 See the Appendix on [network protocols](/#Network.protocols)
1290 for brief descriptions of the various protocols relevant for network
1291 audio streaming with paraslash.
1293 It is possible to activate more than one sender simultaneously.
1294 Senders can be controlled at run time and via config file and command
1295 line options.
1297 Note that audio connections are _not_ encrypted. Transport or Internet
1298 layer encryption should be used if encrypted data connections are
1299 needed.
1301 Since DCCP and TCP are both connection-oriented protocols, connection
1302 establishment/teardown and access control are very similar between
1303 these two streaming protocols. UDP is the most lightweight option,
1304 since in contrast to TCP/DCCP it is connectionless. It is also the
1305 only protocol supporting IP multicast.
1307 The HTTP and the DCCP sender listen on a (TCP/DCCP) port waiting for
1308 clients to connect and establish a connection via some protocol-defined
1309 handshake mechanism. Both senders maintain two linked lists each:
1310 The list of all clients which are currently connected, and the list
1311 of access control entries which determines who is allowed to connect.
1312 IP-based access control may be configured through config file and
1313 command line options and via the "allow" and "deny" sender subcommands.
1315 Upon receiving a GET request from the client, the HTTP sender sends
1316 back a status line and a message. The body of this message is the
1317 audio stream. This is common practice and is supported by many popular
1318 clients which can thus be used to play a stream offered by para_server.
1319 For DCCP things are a bit simpler: No messages are exchanged between
1320 the receiver and sender. The client simply connects and the sender
1321 starts to stream.
1323 DCCP is an experimental protocol which offers a number of new features
1324 not available for TCP. Both ends can negotiate these features using
1325 a built-in negotiation mechanism. In contrast to TCP/HTTP, DCCP is
1326 datagram-based (no retransmissions) and thus should not be used over
1327 lossy media (e.g. WiFi networks). One useful feature offered by DCCP
1328 is access to a variety of different congestion-control mechanisms
1329 called CCIDs. Two different CCIDs are available per default on Linux:
1332 - _CCID 2_. A Congestion Control mechanism similar to that of TCP. The
1333 sender maintains a congestion window and halves this window in response
1334 to congestion.
1337 - _CCID-3_. Designed to be fair when competing for bandwidth.
1338 It has lower variation of throughput over time compared with TCP,
1339 which makes it suitable for streaming media.
1341 Unlike the HTTP and DCCP senders, the UDP sender maintains only a
1342 single list, the _target list_. This list describes the set of clients
1343 to which the stream is sent. There is no list for access control and
1344 no "allow" and "deny" commands for the UDP sender. Instead, the "add"
1345 and "delete" commands can be used to modify the target list.
1347 Since both UDP and DCCP offer an unreliable datagram-based transport,
1348 additional measures are necessary to guard against disruptions over
1349 networks that are lossy or which may be subject to interference (as
1350 is for instance the case with WiFi). Paraslash uses FEC (Forward
1351 Error Correction) to guard against packet losses and reordering. The
1352 stream is FEC-encoded before it is sent through the UDP socket and
1353 must be decoded accordingly on the receiver side.
1355 The packet size and the amount of redundancy introduced by FEC can
1356 be configured via the FEC parameters which are dictated by server
1357 and may also be configured through the "sender" command. The FEC
1358 parameters are encoded in the header of each network packet, so no
1359 configuration is necessary on the receiver side. See the section on
1360 [FEC](#Forward.error.correction) below.
1362 Streams with headers and headerless streams
1363 -------------------------------------------
1365 For OGG/Vorbis, OGG/Speex and wma streams, some of the information
1366 needed to decode the stream is only contained in the audio file
1367 header of the container format but not in each data chunk. Clients
1368 must be able to obtain this information in case streaming starts in
1369 the middle of the file or if para_audiod is started while para_server
1370 is already sending a stream.
1372 This is accomplished in different ways, depending on the streaming
1373 protocol. For connection-oriented streams (HTTP, DCCP) the audio file
1374 header is sent prior to audio file data. This technique however does
1375 not work for the connectionless UDP transport. Hence the audio file
1376 header is periodically being embedded into the UDP audio data stream.
1377 By default, the header is resent after five seconds. The receiver has
1378 to wait until the next header arrives before it can start decoding
1379 the stream.
1381 Networking examples
1382 -------------------
1384 The "si" (server info) command lists some information about the
1385 currently running server process.
1387 -> Show PIDs, number of connected clients, uptime, and more:
1389 para_client si
1391 The sender command of para_server prints information about senders,
1392 like the various access control lists, and it allows to (de-)activate
1393 senders and to change the access permissions at runtime.
1395 -> List all senders
1397 para_client sender
1399 -> Obtain general help for the sender command:
1401 para_client help sender
1403 -> Get help for a specific sender (contains further examples):
1405 s=http # or dccp or udp
1406 para_client sender $s help
1408 -> Show status of the http sender
1410 para_client sender http status
1412 By default para_server activates both the HTTP and th DCCP sender on
1413 startup. This can be changed via command line options or para_server's
1414 config file.
1416 -> List config file options for senders:
1418 para_server -h
1420 All senders share the "on" and "off" commands, so senders may be
1421 activated and deactivated independently of each other.
1423 -> Switch off the http sender:
1425 para_client sender http off
1427 -> Receive a DCCP stream using CCID2 and write the output into a file:
1429; ccid=2; filename=bar
1430 para_recv --receiver "dccp --host $host --ccid $ccid" > $filename
1432 Note the quotes around the arguments for the dccp receiver. Each
1433 receiver has its own set of command line options and its own command
1434 line parser, so arguments for the dccp receiver must be protected
1435 from being interpreted by para_recv.
1437 -> Start UDP multicast, using the default multicast address:
1439 para_client sender udp add
1441 -> Receive FEC-encoded multicast stream and write the output into a file:
1443 filename=foo
1444 para_recv -r udp > $filename
1446 -> Add an UDP unicast for a client to the target list of the UDP sender:
1449 para_client sender udp add $t
1451 -> Receive this (FEC-encoded) unicast stream:
1453 filename=foo
1454 para_recv -r 'udp -i' > $filename
1456 -> Create a minimal config for para_audiod for HTTP streams:
1458 c=$HOME/.paraslash/audiod.conf.min;
1459 echo receiver \".:http -i $s\" > $c
1460 para_audiod --config $c
1462 =======
1463 Filters
1464 =======
1466 A paraslash filter is a module which transforms an input stream into
1467 an output stream. Filters are included in the para_audiod executable
1468 and in the stand-alone tool para_filter which usually contains the
1469 same modules.
1471 While para_filter reads its input stream from STDIN and writes
1472 the output to STDOUT, the filter modules of para_audiod are always
1473 connected to a receiver which produces the input stream and a writer
1474 which absorbs the output stream.
1476 Some filters depend on a specific library and are not compiled in
1477 if this library was not found at compile time. To see the list of
1478 supported filters, run para_filter and para_audiod with the --help
1479 option. The output looks similar to the following:
1481 Available filters:
1482 compress wav amp fecdec wmadec prebuffer oggdec aacdec mp3dec
1484 Out of these filter modules, a chain of filters can be constructed,
1485 much in the way Unix pipes can be chained, and analogous to the use
1486 of modules in gstreamer: The output of the first filter becomes the
1487 input of the second filter. There is no limitation on the number of
1488 filters and the same filter may occur more than once.
1490 Like receivers, each filter has its own command line options which
1491 must be quoted to protect them from the command line options of
1492 the driving application (para_audiod or para_filter). Example:
1494 para_filter -f 'mp3dec --ignore-crc' -f 'compress --damp 1'
1496 For para_audiod, each audio format has its own set of filters. The
1497 name of the audio format for which the filter should be applied can
1498 be used as the prefix for the filter option. Example:
1500 para_audiod -f 'mp3:prebuffer --duration 300'
1502 The "mp3" prefix above is actually interpreted as a POSIX extended
1503 regular expression. Therefore
1505 para_audiod -f '.:prebuffer --duration 300'
1507 activates the prebuffer filter for all supported audio formats (because
1508 "." matches all audio formats) while
1510 para_audiod -f 'wma|ogg:prebuffer --duration 300'
1512 activates it only for wma and ogg streams.
1514 Decoders
1515 --------
1517 For each supported audio format there is a corresponding filter
1518 which decodes audio data in this format to 16 bit PCM data which
1519 can be directly sent to the sound device or any other software that
1520 operates on undecoded PCM data (visualizers, equalizers etc.). Such
1521 filters are called _decoders_ in general, and xxxdec is the name of
1522 the paraslash decoder for the audio format xxx. For example, the mp3
1523 decoder is called mp3dec.
1525 Note that the output of the decoder is about 10 times larger than
1526 its input. This means that filters that operate on the decoded audio
1527 stream have to deal with much more data than filters that transform
1528 the audio stream before it is fed to the decoder.
1530 Paraslash relies on external libraries for most decoders, so these
1531 libraries must be installed for the decoder to be included in the
1532 executables. For example, the mp3dec filter depends on the mad library.
1534 Forward error correction
1535 ------------------------
1537 As already mentioned [earlier](#Streaming.protocols), paraslash
1538 uses forward error correction (FEC) for the unreliable UDP and
1539 DCCP transports. FEC is a technique which was invented already in
1540 1960 by Reed and Solomon and which is widely used for the parity
1541 calculations of storage devices (RAID arrays). It is based on the
1542 algebraic concept of finite fields, today called Galois fields, in
1543 honour of the mathematician Galois (1811-1832). The FEC implementation
1544 of paraslash is based on code by Luigi Rizzo.
1546 Although the details require a sound knowledge of the underlying
1547 mathematics, the basic idea is not hard to understand: For positive
1548 integers k and n with k < n it is possible to compute for any k given
1549 data bytes d_1, ..., d_k the corresponding r := n -k parity bytes p_1,
1550 ..., p_r such that all data bytes can be reconstructed from *any*
1551 k bytes of the set
1553 {d_1, ..., d_k, p_1, ..., p_r}.
1555 FEC-encoding for unreliable network transports boils down to slicing
1556 the audio stream into groups of k suitably sized pieces called _slices_
1557 and computing the r corresponding parity slices. This step is performed
1558 in para_server which then sends both the data and the parity slices
1559 over the unreliable network connection. If the client was able
1560 to receive at least k of the n = k + r slices, it can reconstruct
1561 (FEC-decode) the original audio stream.
1563 From these observations it is clear that there are three different
1564 FEC parameters: The slice size, the number of data slices k, and the
1565 total number of slices n. It is crucial to choose the slice size
1566 such that no fragmentation of network packets takes place because
1567 FEC only guards against losses and reordering but fails if slices are
1568 received partially.
1570 FEC decoding in paralash is performed through the fecdec filter which
1571 usually is the first filter (there can be other filters before fecdec
1572 if these do not alter the audio stream).
1574 Volume adjustment (amp and compress)
1575 ------------------------------------
1577 The amp and the compress filter both adjust the volume of the audio
1578 stream. These filters operate on uncompressed audio samples. Hence
1579 they are usually placed directly after the decoding filter. Each
1580 sample is multiplied with a scaling factor (>= 1) which makes amp
1581 and compress quite expensive in terms of computing power.
1583 ### amp ###
1585 The amp filter amplifies the audio stream by a fixed scaling factor
1586 that must be known in advance. For para_audiod this factor is derived
1587 from the amplification field of the audio file's entry in the audio
1588 file table while para_filter uses the value given at the command line.
1590 The optimal scaling factor F for an audio file is the largest real
1591 number F >= 1 such that after multiplication with F all samples still
1592 fit into the sample interval [-32768, 32767]. One can use para_filter
1593 in combination with the sox utility to compute F:
1595 para_filter -f mp3dec -f wav < file.mp3 | sox -t wav - -e stat -v
1597 The amplification value V which is stored in the audio file table,
1598 however, is an integer between 0 and 255 which is connected to F
1599 through the formula
1601 V = (F - 1) * 64.
1603 To store V in the audio file table, the command
1605 para_client -- touch -a=V file.mp3
1607 is used. The reader is encouraged to write a script that performs
1608 these computations :)
1610 ### compress ###
1612 Unlike the amplification filter, the compress filter adjusts the volume
1613 of the audio stream dynamically without prior knowledge about the peak
1614 value. It maintains the maximal volume of the last n samples of the
1615 audio stream and computes a suitable amplification factor based on that
1616 value and the various configuration options. It tries to chose this
1617 factor such that the adjusted volume meets the desired target level.
1619 Note that it makes sense to combine amp and compress.
1621 Misc filters (wav and prebuffer)
1622 --------------------------------
1624 These filters are rather simple and do not modify the audio stream at
1625 all. The wav filter is only useful with para_filter and in connection
1626 with a decoder. It asks the decoder for the number of channels and the
1627 sample rate of the stream and adds a Microsoft wave header containing
1628 this information at the beginning. This allows to write wav files
1629 rather than raw PCM files (which do not contain any information about
1630 the number of channels and the sample rate).
1632 The prebuffer filter simply delays the output until the given time has
1633 passed (starting from the time the first byte was available in its
1634 input queue) or until the given amount of data has accumulated. It
1635 is mainly useful for para_audiod if the standard parameters result
1636 in buffer underruns.
1638 Both filters require almost no additional computing time, even when
1639 operating on uncompressed audio streams, since data buffers are simply
1640 "pushed down" rather than copied.
1642 Examples
1643 --------
1645 -> Decode an mp3 file to wav format:
1647 para_filter -f mp3dec -f wav < file.mp3 > file.wav
1649 -> Amplify a raw audio file by a factor of 1.5:
1651 para_filter -f amp --amp 32 < foo.raw > bar.raw
1653 ======
1654 Output
1655 ======
1657 Once an audio stream has been received and decoded to PCM format,
1658 it can be sent to a sound device for playback. This part is performed
1659 by paraslash _writers_ which are described in this chapter.
1661 Writers
1662 -------
1664 A paraslash writer acts as a data sink that consumes but does not
1665 produce audio data. Paraslash writers operate on the client side and
1666 are contained in para_audiod and in the stand-alone tool para_write.
1668 The para_write program reads uncompressed audio data from STDIN. If
1669 this data starts with a wav header, sample rate, sample format and
1670 channel count are read from the header. Otherwise CD audio (44.1KHz
1671 16 bit little endian, stereo) is assumed but this can be overridden
1672 by command line options. para_audiod, on the other hand, obtains
1673 the sample rate and the number of channels from the decoder.
1675 Like receivers and filters, each writer has an individual set of
1676 command line options, and for para_audiod writers can be configured
1677 per audio format separately. It is possible to activate more than
1678 one writer for the same stream simultaneously.
1680 OS-dependent APIs
1681 -----------------
1683 Unfortunately, the various flavours of Unix on which paraslash
1684 runs on have different APIs for opening a sound device and starting
1685 playback. Hence for each such API there is a paraslash writer that
1686 can play the audio stream via this API.
1688 - *ALSA*. The _Advanced Linux Sound Architecture_ is only available on
1689 Linux systems. Although there are several mid-layer APIs in use by
1690 the various Linux distributions (ESD, Jack, PulseAudio), paraslash
1691 currently supports only the low-level ALSA API which is not supposed
1692 to be change. ALSA is very feature-rich, in particular it supports
1693 software mixing via its DMIX plugin. ALSA is the default writer on
1694 Linux systems.
1696 - *OSS*. The _Open Sound System_ is the only API on \*BSD Unixes and
1697 is also available on Linux systems, usually provided by ALSA as an
1698 emulation for backwards compatibility. This API is rather simple but
1699 also limited. For example only one application can open the device
1700 at any time. The OSS writer is activated by default on BSD Systems.
1702 - *FILE*. The file writer allows to capture the audio stream and
1703 write the PCM data to a file on the file system rather than playing
1704 it through a sound device. It is supported on all platforms and is
1705 always compiled in.
1707 - *AO*. _Libao_ is a cross-platform audio library which supports a wide
1708 variety of platforms including PulseAudio (gnome), ESD (Enlightened
1709 Sound Daemon), AIX, Solaris and IRIX. The ao writer plays audio
1710 through an output plugin of libao.
1712 Examples
1713 --------
1715 -> Use the OSS writer to play a wav file:
1717 para_write --writer oss < file.wav
1719 -> Enable ALSA software mixing for mp3 streams:
1721 para_audiod --writer 'mp3:alsa -d plug:swmix'
1724 ===
1725 Gui
1726 ===
1728 para_gui executes an arbitrary command which is supposed to print
1729 status information to STDOUT. It then displays this information in
1730 a curses window. By default the command
1732 para_audioc -- stat -p
1734 is executed, but this can be customized via the --stat-cmd option. In
1735 particular it possible to use
1737 para_client -- stat -p
1739 to make para_gui work on systems on which para_audiod is not running.
1741 Key bindings
1742 ------------
1744 It is possible to bind keys to arbitrary commands via custom
1745 key-bindings. Besides the internal keys which can not be changed (help,
1746 quit, loglevel, version...), the following flavours of key-bindings
1747 are supported:
1749 - external: Shutdown curses before launching the given command.
1750 Useful for starting other ncurses programs from within para_gui,
1751 e.g. aumix or dialog scripts. Or, use the mbox output format to write
1752 a mailbox containing one mail for each (admissible) file the audio
1753 file selector knows about. Then start mutt from within para_gui to
1754 browse your collection!
1756 - display: Launch the command and display its stdout in para_gui's
1757 bottom window.
1759 - para: Like display, but start "para_client <specified command>"
1760 instead of "<specified command>".
1762 The general form of a key binding is
1764 key_map k:m:c
1766 which maps key k to command c using mode m. Mode may be x, d or p
1767 for external, display and paraslash commands, respectively.
1769 Themes
1770 ------
1772 Currently there are only two themes for para_gui. It is easy, however,
1773 to add more themes. To create a new theme one has to define the
1774 position, color and geometry for for each status item that should be
1775 shown by this theme. See gui_theme.c for examples.
1777 The "." and "," keys are used to switch between themes.
1779 Examples
1780 --------
1782 -> Show server info:
1784 key_map "i:p:si"
1786 -> Jump to the middle of the current audio file by pressing F5:
1788 key_map "<F5>:p:jmp 50"
1790 -> vi-like bindings for jumping around:
1792 key_map "l:p:ff 10"
1793 key_map "h:p:ff 10-"
1794 key_map "w:p:ff 60"
1795 key_map "b:p:ff 60-"
1797 -> Print the current date and time:
1799 key_map "D:d:date"
1801 -> Call other curses programs:
1803 key_map "U:x:aumix"
1804 key_map "!:x:/bin/bash"
1805 key_map "^E:x:/bin/sh -c 'vi ~/.paraslash/gui.conf'"
1807 ===========
1808 Development
1809 ===========
1811 Contributing
1812 ------------
1814 Paraslash is an open source project and contributions are
1815 welcome. Here's a list of things you can do to help the project:
1817 - Report problems with building, installing or running the software.
1818 In particular, test the experimental git branches ("next" and "pu").
1819 This helps to identify and fix problems before the code gets merged
1820 and thus keeps the master branch as stable as possible.
1821 - Proofread the documentation (manual, web pages, man pages, source
1822 code documentation) and point out unclear or poorly written parts. If
1823 you are a native English speaker you will easily find a lot of text
1824 that could be improved.
1825 - Run analysis tools (coverity, afl, sparse, etc.) and report issues
1826 found by those tools.
1827 - Suggest new features you would like to see implemented.
1828 - Compile and test on your favorite architecture or operating
1829 system. The code is tested only on a limited set of systems, so you
1830 will probably encounter problems when building on different systems.
1831 - Post about about paraslash on your blog or on social networks.
1832 - Build and maintain Debian/RPM packages for your favorite distribution.
1834 Note that there is no mailing list, no bug tracker and no discussion
1835 forum for paraslash. If you'd like to contribute, or have questions
1836 about contributing, send email to Andre Noll <>.
1838 Tools
1839 -----
1841 In order to compile the sources from the git repository (rather than
1842 from tar balls) and for contributing non-trivial changes to the
1843 paraslash project, some additional tools should be installed on a
1844 developer machine.
1846 - [git]( As described in more detail
1847 [below](#Git.branches), the git source code management tool is used for
1848 paraslash development. It is necessary for cloning the git repository
1849 and for getting updates.
1851 - [autoconf]( GNU autoconf creates
1852 the configure file which is shipped in the tarballs but has to be
1853 generated when compiling from git.
1855 - [discount]( The
1856 HTML version of this manual and some of the paraslash web pages are
1857 written in the Markdown markup language and are translated into html
1858 with the converter of the *Discount* package.
1860 - [doxygen]( The documentation
1861 of paraslash's C sources uses the doxygen documentation system. The
1862 conventions for documenting the source code is described in the
1863 [Doxygen section](#Doxygen).
1865 - [global]( This is used to generate
1866 browsable HTML from the C sources. It is needed by doxygen.
1868 Git branches
1869 ------------
1871 Paraslash has been developed using the git source code management
1872 tool since 2006. Development is organized roughly in the same spirit
1873 as the git development itself, as described below.
1875 The following text passage is based on "A note from the maintainer",
1876 written by Junio C Hamano, the maintainer of git.
1878 There are four branches in the paraslash repository that track the
1879 source tree: "master", "maint", "next", and "pu".
1881 The "master" branch is meant to contain what is well tested and
1882 ready to be used in a production setting. There could occasionally be
1883 minor breakages or brown paper bag bugs but they are not expected to
1884 be anything major, and more importantly quickly and easily fixable.
1885 Every now and then, a "feature release" is cut from the tip of this
1886 branch, named with three dotted decimal digits, like 0.4.2.
1888 Whenever changes are about to be included that will eventually lead to
1889 a new major release (e.g. 0.5.0), a "maint" branch is forked off from
1890 "master" at that point. Obvious, safe and urgent fixes after the major
1891 release are applied to this branch and maintenance releases are cut
1892 from it. New features never go to this branch. This branch is also
1893 merged into "master" to propagate the fixes forward.
1895 A trivial and safe enhancement goes directly on top of "master".
1896 New development does not usually happen on "master", however.
1897 Instead, a separate topic branch is forked from the tip of "master",
1898 and it first is tested in isolation; Usually there are a handful such
1899 topic branches that are running ahead of "master". The tip of these
1900 branches is not published in the public repository to keep the number
1901 of branches that downstream developers need to worry about low.
1903 The quality of topic branches varies widely. Some of them start out as
1904 "good idea but obviously is broken in some areas" and then with some
1905 more work become "more or less done and can now be tested by wider
1906 audience". Luckily, most of them start out in the latter, better shape.
1908 The "next" branch is to merge and test topic branches in the latter
1909 category. In general, this branch always contains the tip of "master".
1910 It might not be quite rock-solid production ready, but is expected to
1911 work more or less without major breakage. The maintainer usually uses
1912 the "next" version of paraslash for his own pleasure, so it cannot
1913 be _that_ broken. The "next" branch is where new and exciting things
1914 take place.
1916 The two branches "master" and "maint" are never rewound, and "next"
1917 usually will not be either (this automatically means the topics that
1918 have been merged into "next" are usually not rebased, and you can find
1919 the tip of topic branches you are interested in from the output of
1920 "git log next"). You should be able to safely build on top of them.
1922 However, at times "next" will be rebuilt from the tip of "master" to
1923 get rid of merge commits that will never be in "master". The commit
1924 that replaces "next" will usually have the identical tree, but it
1925 will have different ancestry from the tip of "master".
1927 The "pu" (proposed updates) branch bundles the remainder of the
1928 topic branches. The "pu" branch, and topic branches that are only in
1929 "pu", are subject to rebasing in general. By the above definition
1930 of how "next" works, you can tell that this branch will contain quite
1931 experimental and obviously broken stuff.
1933 When a topic that was in "pu" proves to be in testable shape, it
1934 graduates to "next". This is done with
1936 git checkout next
1937 git merge that-topic-branch
1939 Sometimes, an idea that looked promising turns out to be not so good
1940 and the topic can be dropped from "pu" in such a case.
1942 A topic that is in "next" is expected to be polished to perfection
1943 before it is merged to "master". Similar to the above, this is
1944 done with
1946 git checkout master
1947 git merge that-topic-branch
1948 git branch -d that-topic-branch
1950 Note that being in "next" is not a guarantee to appear in the next
1951 release (being in "master" is such a guarantee, unless it is later
1952 found seriously broken and reverted), nor even in any future release.
1954 Coding Style
1955 ------------
1957 The preferred coding style for paraslash coincides more or less
1958 with the style of the Linux kernel. So rather than repeating what is
1959 written [there](,
1960 here are the most important points.
1962 - Burn the GNU coding standards.
1963 - Never use spaces for indentation.
1964 - Tabs are 8 characters, and thus indentations are also 8 characters.
1965 - Don't put multiple assignments on a single line.
1966 - Avoid tricky expressions.
1967 - Don't leave whitespace at the end of lines.
1968 - The limit on the length of lines is 80 columns.
1969 - Use K&R style for placing braces and spaces:
1971 if (x is true) {
1972 we do y
1973 }
1975 - Use a space after (most) keywords.
1976 - Do not add spaces around (inside) parenthesized expressions.
1977 - Use one space around (on each side of) most binary and ternary operators.
1978 - Do not use cute names like ThisVariableIsATemporaryCounter, call it tmp.
1979 - Mixed-case names are frowned upon.
1980 - Descriptive names for global variables are a must.
1981 - Avoid typedefs.
1982 - Functions should be short and sweet, and do just one thing.
1983 - The number of local variables shouldn't exceed 10.
1984 - Gotos are fine if they improve readability and reduce nesting.
1985 - Don't use C99-style "// ..." comments.
1986 - Names of macros defining constants and labels in enums are capitalized.
1987 - Enums are preferred when defining several related constants.
1988 - Always use the paraslash wrappers for allocating memory.
1989 - If the name of a function is an action or an imperative.
1990 command, the function should return an error-code integer
1991 (<0 means error, >=0 means success). If the name is a
1992 predicate, the function should return a "succeeded" boolean.
1994 Doxygen
1995 -------
1997 Doxygen is a documentation system for various programming
1998 languages. The API reference on the paraslash web page is generated
1999 by doxygen.
2001 It is more illustrative to look at the source code for examples than
2002 to describe the conventions in this manual, so we only describe which
2003 parts of the code need doxygen comments, but leave out details on
2004 documentation conventions.
2006 As a rule, only the public part of the C source is documented with
2007 Doxygen. This includes structures, defines and enumerations in header
2008 files as well as public (non-static) C functions. These should be
2009 documented completely. For example, each parameter and the return
2010 value of a public function should get a descriptive doxygen comment.
2012 No doxygen comments are necessary for static functions and for
2013 structures and enumerations in C files (which are used only within
2014 this file). This does not mean, however, that those entities need
2015 no documentation at all. Instead, common sense should be applied to
2016 document what is not obvious from reading the code.
2018 ========
2019 Appendix
2020 ========
2022 Network protocols
2023 -----------------
2025 ### IP ###
2027 The _Internet Protocol_ is the primary networking protocol used for
2028 the Internet. All protocols described below use IP as the underlying
2029 layer. Both the prevalent IPv4 and the next-generation IPv6 variant
2030 are being deployed actively worldwide.
2032 ### Connection-oriented and connectionless protocols ###
2034 Connectionless protocols differ from connection-oriented ones in
2035 that state associated with the sending/receiving endpoints is treated
2036 implicitly. Connectionless protocols maintain no internal knowledge
2037 about the state of the connection. Hence they are not capable of
2038 reacting to state changes, such as sudden loss or congestion on the
2039 connection medium. Connection-oriented protocols, in contrast, make
2040 this knowledge explicit. The connection is established only after
2041 a bidirectional handshake which requires both endpoints to agree
2042 on the state of the connection, and may also involve negotiating
2043 specific parameters for the particular connection. Maintaining an
2044 up-to-date internal state of the connection also in general means
2045 that the sending endpoints perform congestion control, adapting to
2046 qualitative changes of the connection medium.
2048 ### Reliability ###
2050 In IP networking, packets can be lost, duplicated, or delivered
2051 out of order, and different network protocols handle these
2052 problems in different ways. We call a transport-layer protocol
2053 _reliable_, if it turns the unreliable IP delivery into an ordered,
2054 duplicate- and loss-free delivery of packets. Sequence numbers
2055 are used to discard duplicates and re-arrange packets delivered
2056 out-of-order. Retransmission is used to guarantee loss-free
2057 delivery. Unreliable protocols, in contrast, do not guarantee ordering
2058 or data integrity.
2060 ### Classification ###
2062 With these definitions the protocols which are used by paraslash for
2063 steaming audio data may be classified as follows.
2065 - HTTP/TCP: connection-oriented, reliable,
2066 - UDP: connectionless, unreliable,
2067 - DCCP: connection-oriented, unreliable.
2069 Below we give a short descriptions of these protocols.
2071 ### TCP ###
2073 The _Transmission Control Protocol_ provides reliable, ordered delivery
2074 of a stream and a classic window-based congestion control. In contrast
2075 to UDP and DCCP (see below), TCP does not have record-oriented or
2076 datagram-based syntax, i.e. it provides a stream which is unaware
2077 and independent of any record (packet) boundaries. TCP is used
2078 extensively by many application layers. Besides HTTP (the Hypertext
2079 Transfer Protocol), also FTP (the File Transfer protocol), SMTP (Simple
2080 Mail Transfer Protocol), SSH (Secure Shell) all sit on top of TCP.
2082 ### UDP ###
2084 The _User Datagram Protocol_ is the simplest transport-layer protocol,
2085 built as a thin layer directly on top of IP. For this reason, it offers
2086 the same best-effort service as IP itself, i.e. there is no detection
2087 of duplicate or reordered packets. Being a connectionless protocol,
2088 only minimal internal state about the connection is maintained, which
2089 means that there is no protection against packet loss or network
2090 congestion. Error checking and correction (if at all) are performed
2091 in the application.
2093 ### DCCP ###
2095 The _Datagram Congestion Control Protocol_ combines the
2096 connection-oriented state maintenance known from TCP with the
2097 unreliable, datagram-based transport of UDP. This means that it
2098 is capable of reacting to changes in the connection by performing
2099 congestion control, offering multiple alternative approaches. But it
2100 is bound to datagram boundaries (the maximum packet size supported
2101 by a medium), and like UDP it lacks retransmission to protect
2102 against loss. Due to the use of sequence numbers, it is however
2103 able to react to loss (interpreted as a congestion indication) and
2104 to ignore out-of-order and duplicate packets. Unlike TCP it allows
2105 to negotiate specific, binding features for a connection, such as
2106 the choice of congestion control: classic, window-based congestion
2107 control known from TCP is available as CCID-2, rate-based, "smooth"
2108 congestion control is offered as CCID-3.
2110 ### HTTP ###
2112 The _Hypertext Transfer Protocol_ is an application layer protocol
2113 on top of TCP. It is spoken by web servers and is most often used
2114 for web services. However, as can be seen by the many Internet radio
2115 stations and YouTube/Flash videos, http is by far not limited to the
2116 delivery of web pages only. Being a simple request/response based
2117 protocol, the semantics of the protocol also allow the delivery of
2118 multimedia content, such as audio over http.
2120 ### Multicast ###
2122 IP multicast is not really a protocol but a technique for one-to-many
2123 communication over an IP network. The challenge is to deliver
2124 information to a group of destinations simultaneously using the
2125 most efficient strategy to send the messages over each link of the
2126 network only once. This has benefits for streaming multimedia: the
2127 standard one-to-one unicast offered by TCP/DCCP means that n clients
2128 listening to the same stream also consume n-times the resources,
2129 whereas multicast requires to send the stream just once, irrespective
2130 of the number of receivers. Since it would be costly to maintain state
2131 for each listening receiver, multicast often implies connectionless
2132 transport, which is the reason that it is currently only available
2133 via UDP.
2135 Abstract socket namespace
2136 -------------------------
2137 UNIX domain sockets are a traditional way to communicate between
2138 processes on the same machine. They are always reliable (see above)
2139 and don't reorder datagrams. Unlike TCP and UDP, UNIX domain sockets
2140 support passing open file descriptors or process credentials to
2141 other processes.
2143 The usual way to set up a UNIX domain socket (as obtained from
2144 socket(2)) for listening is to first bind the socket to a file system
2145 pathname and then call listen(2), then accept(2). Such sockets are
2146 called _pathname sockets_ because bind(2) creates a special socket
2147 file at the specified path. Pathname sockets allow unrelated processes
2148 to communicate with the listening process by binding to the same path
2149 and calling connect(2).
2151 There are two problems with pathname sockets:
2153 * The listing process must be able to (safely) create the
2154 socket special in a directory which is also accessible to
2155 the connecting process.
2157 * After an unclean shutdown of the listening process, a stale
2158 socket special may reside on the file system.
2160 The abstract socket namespace is a non-portable Linux feature which
2161 avoids these problems. Abstract sockets are still bound to a name,
2162 but the name has no connection with file system pathnames.
2164 License
2165 -------
2167 Paraslash is licensed under the GPL, version 2. Most of the code
2168 base has been written from scratch, and those parts are GPL V2
2169 throughout. Notable exceptions are FEC and the WMA decoder. See the
2170 corresponding source files for licencing details for these parts. Some
2171 code sniplets of several other third party software packages have
2172 been incorporated into the paraslash sources, for example log message
2173 coloring was taken from the git sources. These third party software
2174 packages are all published under the GPL or some other license
2175 compatible to the GPL.
2177 Acknowledgements
2178 ----------------
2180 Many thanks to Gerrit Renker who read an early draft of this manual
2181 and contributed significant improvements.
2183 ==========
2184 References
2185 ==========
2187 Articles
2188 --------
2189 - [Polynomial Codes over Certain Finite
2190 Fields]( by Reed, Irving
2191 S.; Solomon, Gustave (1960), Journal of the Society for Industrial
2192 and Applied Mathematics (SIAM) 8 (2): 300-304, doi:10.1137/0108018)
2194 RFCs
2195 ----
2197 - [RFC 768]( (1980): User Datagram
2198 Protocol
2200 - [RFC 791]( (1981): Internet
2201 Protocol
2203 - [RFC 2437]( (1998): RSA
2204 Cryptography Specifications
2206 - [RFC 4340]( (2006): Datagram
2207 Congestion Control Protocol (DCCP)
2209 - [RFC 4341]( (2006): Congestion
2210 Control ID 2: TCP-like Congestion Control
2212 - [RFC 4342]( (2006): Congestion
2213 Control ID 3: TCP-Friendly Rate Control (TFRC)
2215 - [RFC 6716]( (2012): Definition
2216 of the Opus Audio Codec
2218 Application web pages
2219 ---------------------
2221 - [paraslash](
2222 - [xmms](
2223 - [mpg123](
2224 - [gstreamer](
2225 - [icecast](
2226 - [Audio Compress](
2228 External documentation
2229 ----------------------
2231 - [The mathematics of
2232 Raid6](
2233 by H. Peter Anvin
2235 - [Effective Erasure Codes for reliable Computer Communication
2236 Protocols]( by Luigi
2237 Rizzo
2239 Code
2240 ----
2241 - [Original FEC
2242 implementation]( by
2243 Luigi Rizzo)