<<
<a href="REQUIREMENTS.html"> REQUIREMENTS </a>
>>
-for a list of required software. You don't need everything listed
-there. In particular, mp3, ogg vorbis and aac, ortp support is
-optional. Autoconf will detect what is installed on your system
-and will only try to build those executables that can be built with
-your setup.
+for a list of required software. You don't need everything listed there. In
+particular, mp3, ogg vorbis and aac support are all optional. Autoconf will
+detect what is installed on your system and will only try to build those
+executables that can be built with your setup.
Note that no special library (not even the mp3 decoding library libmad)
is needed for para_server if you only want to stream mp3 files.
Alternatively, use the --afs_socket Option to specify a different
location for the afs command socket.
-For this first try, we'll use a debug level of two to make the
-output of para_server more verbose.
+For this first try, we'll use the info loglevel to make the output
+of para_server more verbose.
- para_server -l 2
+ para_server -l info
Now you can use para_client to connect to the server and issue
commands. Open a new shell (as "bar" on "client_host" in the above
will be described next. Try the following on client_host (assuming
Linux/ALSA and an mp3 stream):
- para_recv -l 2 -r 'http -i server_host' > file.mp3
+ para_recv -l info -r 'http -i server_host' > file.mp3
# (interrupt with CTRL+C after a few seconds)
ls -l file.mp3 # should not be empty
para_filter -f mp3dec -f wav < file.mp3 > file.wav
for help. Usually you have to specify only server_host as the receiver
specifier for each supported audio format, like this:
- para_audiod -l 2 -r 'mp3:http -i server_host'
+ para_audiod -l info -r 'mp3:http -i server_host'
The preferred way to use para_audiod is to run it once at system start
as an unprivileged user. para_audiod needs to create a "well-known"