From 815a277189a2400226d34c90b63e57ab7e734ae9 Mon Sep 17 00:00:00 2001 From: Andre Noll Date: Mon, 2 Aug 2010 09:12:16 +0200 Subject: [PATCH] manual: Minor cleanups. - Mention that OGG/Speex also needs periodic audio file headers, reword this sentence. - para_write now understands formats != 16 bit, so remove this restriction also from the documentation. Also mention that the sample format is being read from the wav header, if present. - Typo fix. --- web/manual.m4 | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/web/manual.m4 b/web/manual.m4 index cd06cccd..14feb573 100644 --- a/web/manual.m4 +++ b/web/manual.m4 @@ -1347,12 +1347,12 @@ REFERENCE(Forward error correction, FEC) below. Streams with headers and headerless streams ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -For ogg vorbis and wma streams, not all information needed to decode -the stream is contained in each data chunk but only in the audio -file header of the container format. Therefore clients must be able -to obtain this information in case streaming starts in the middle of -the file or if para_audiod is started while para_server is already -sending a stream. +For OGG/Vorbis, OGG/Speex and wma streams, some of the information +needed to decode the stream is only contained in the audio file +header of the container format but not in each data chunk. Clients +must be able to obtain this information in case streaming starts in +the middle of the file or if para_audiod is started while para_server +is already sending a stream. This is accomplished in different ways, depending on the streaming protocol. For connection-oriented streams (HTTP, DCCP) the audio file @@ -1631,12 +1631,12 @@ A paraslash writer acts as a data sink that consumes but does not produce audio data. Paraslash writers operate on the client side and are contained in para_audiod and in the stand-alone tool para_write. -The para_write program reads uncompressed 16 bit audio data from -STDIN. If this data starts with a wav header, sample rate and channel -count are read from the header. Otherwise CD audio (44.1KHz stereo) -is assumed but this can be overridden by command line options. -para_audiod, on the other hand, obtains the sample rate and the number -of channels from the decoder. +The para_write program reads uncompressed audio data from STDIN. If +this data starts with a wav header, sample rate, sample format and +channel count are read from the header. Otherwise CD audio (44.1KHz +16 bit little endian, stereo) is assumed but this can be overridden +by command line options. para_audiod, on the other hand, obtains +the sample rate and the number of channels from the decoder. Like receivers and filters, each writer has an individual set of command line options, and for para_audiod writers can be configured @@ -1844,7 +1844,7 @@ New development does not usually happen on "master", however. Instead, a separate topic branch is forked from the tip of "master", and it first is tested in isolation; Usually there are a handful such topic branches that are running ahead of "master". The tip of these -branches is not published in the public repository, to keep the number +branches is not published in the public repository to keep the number of branches that downstream developers need to worry about low. The quality of topic branches varies widely. Some of them start out as -- 2.39.5