Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

roarsin(1) [debian man page]

roartestclients(1)					  System Manager's Manual: roard					roartestclients(1)

NAME
roarcat2sock, roarcatad, roarsin, roarsockconnect - RoarAudio sound server test clients SYNOPSIS
roarcat2sock [OPTIONS]... roarcatad [OPTIONS]... roarsin roarsockconnect HOST PORT DESCRIPTION
This clients are primary for test perpose but may be useful for someone or can be used as examples. roarcat2sock This is the same as roarcat(1) but uses roar_simple_new_stream(3) to open the audio stream. roarcatad This is also the same as roarcat(1) but uses roar_stream_add_data(3) to fill the server's input buffer. roarsin This is the complete version of the sinus generator from roartut(7). It plays a 5 second middle C (523.2Hz) sine. roarsockconnect This is just a test tool connecting somewhere via roar_socket_connect(3). First the data of stdin is copied to the socket than the data from the socket to stdout. It's a very simlple semi-bi-directional version of netcat(1). GENERAL OPTIONS
NOTE: This list is incomplete! --help Print some help text. AUDIO OPTIONS
--rate RATE, -R RATE Set server sample rate. --bits BITS, -B BITS Set server bits. --chans CHANNELS, -C CHANNELS Set server channels. NETWORK OPTIONS
--server SERVER The server to connect to ENVIRONMENT VARIABLES
Bellow only the basic environment varibales are listend. For a complete list see libroar(7). HOME The users home directory. ROAR_SERVER The address of the listening server. This may be in form of host:port for TCP/IP connections and /path/to/sock for UNIX Domain Sock- ets. See roartips(7) for a full list. This is the same as the --server option. BUGS
There are a lot of bugs... SEE ALSO
roarctl(1), roarvorbis(1), roarfish(1), roarbaseclients(1), roartips(7), libroar(7), RoarAudio(7). HISTORY
For history information see RoarAudio(7). RoarAudio July 2008 roartestclients(1)

Check Out this Related Man Page

roartips(7)						System Manager's Manual: RoarAuido					       roartips(7)

NAME
roartips - Tips for RoarAudio users SYNOPSIS
roard [OPTIONS...] ... roarclient [OPTIONS...] ... DESCRIPTION
This manpage lists some tips for intermedia to advanced users of RoarAudio. CONTROLLING ROARD
RoarAudio supports a lot of things you can change on the fly. This includes the volume for each stream as you may allready noticed: If you cange the volume within a player only this stream is changed, other streams keep there loudness. There a a lot other things that can be changed on the fly. To do this there is a tool called roarctl(1). You may want to play around a bit with it. A good start are to try those two commands: roarctl --help roarctl allinfo The later one will show you all information current available of the server it self, the clients and the streams. This may include a lot of information. SERVER ADDRESS
There a serverel types of server addresses based on the protocol used to communicate. This lists the corrently implemented types in order of importance: /path/to/sock Path to UNIX Domain Socket. Example: /tmp/roar host, host:port This is used for connections over TCP/IP. If port is omitted the default port is used. Examples: audio.homeserver.local localhost:7564 node::, node::object, ::object, :: This is the way to specify a DECnet connection to node node's object object. Both may be omitted to use defaults. Default node name is local hosts node name. Examples: mynode:: ::roar yournode::yourroard +fork This starts a new roard for every roar_connect(3). This is used internaly by the lib to emulate EsounD's fallback. ENVIRONMENT
ROAR_SERVER This varibale contains the default server address. If some client does not allow a user to set a server address or to set a default value this one come into play. Examples: ROAR_SERVER=some.host ROAR_SERVER=another.host:port ROAR_SERVER=node:: ROAR_SERVER=/tmp/roar SEE ALSO
roarcat(1), roarctl(1), roarfilt(1), roarfish(1), roarmon(1), roarvorbis(1), roard(1), libroar(7). RoarAudio August 2008 roartips(7)
Man Page