Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

prototyper(1) [debian man page]

Prototyper(1)							   User Commands						     Prototyper(1)

NAME
Prototyper - Runs CLAM networks with a Qt interface SYNOPSIS
Prototyper [Network.clamnetwork [Interface.ui]] [-o] [-d backend1 [-d backend2]...] DESCRIPTION
The Prototyper runs audio processing networks created by the CLAM NetworkEditor (.clamnetwork) which can be controlled using a Qt user interface (.ui) created by the Qt Designer to control it. Qt widget names on the interface will be used to connect the widgets the proper network elements. See the CLAM NetworkEditor tutorial for more detailed explanation. on how to specify such binding. If no interface is provided on the command line, the Prototyper will look for an interface with the same name than the network and the proper extension. If anything else fails then a minimalistic default interface will be used. You can also provide a list of audio backends to try. Most common backends are 'alsa', 'jack', 'portaudio'... They will be probed in order and the first one working will be selected. If none of the selected works then the default list of backends for the platform will be tried. The -o option executes the network without any interface AUTHOR
CLAM development team (clam (at) iua.upf.es) SEE ALSO
NetworkEditor(1), designer-qt4(1), QtSMSTools(1), Annotator(1) http://clam-project.org/wiki/Network_Editor_tutorial (Network Editor Tutorial) version 0.1.2 August 24, 2005 Prototyper(1)

Check Out this Related Man Page

AUSCOPE(1)						      General Commands Manual							AUSCOPE(1)

NAME
auscope - Network Audio System Protocol Filter SYNOPSIS
auscope [ option ] ... DESCRIPTION
auscope is an audio protocol filter that can be used to view the network packets being sent between an audio application and an audio server. auscope is written in Perl, so you must have Perl installed on your machine in order to run auscope. If your Perl executable is not installed as /usr/local/bin/perl, you should modify the first line of the auscope script to reflect the Perl executable's location. Or, you can invoke auscope as perl auscope [ option ] ... assuming the Perl executable is in your path. To operate, auscope must know the port on which it should listen for audio clients, the name of the desktop machine on which the audio server is running and the port to use to connect to the audio server. Both the output port (server) and input port (client) are automati- cally biased by 8000. The output port defaults to 0 and the input port defaults to 1. ARGUMENTS
-i<input-port> Specify the port that auscope will use to take requests from clients. -o<output-port> Determines the port that auscope will use to connect to the audio server. -h<audio server name> Determines the desktop machine name that auscope will use to find the audio server. -v<print-level> Determines the level of printing which auscope will provide. The print-level can be 0 or 1. The larger numbers provide greater output detail. EXAMPLES
In the following example, mcxterm is the name of the desktop machine running the audio server, which is connected to the TCP/IP network host tcphost. auscope uses the desktop machine with the -h command line option, will listen for client requests on port 8001 and connect to the audio server on port 8000. Ports (file descriptors) on the network host are used to read and write the audio protocol. The audio client auplay will connect to the audio server via the TCP/IP network host tcphost and port 8001: auscope -i1 -o0 -hmcxterm auplay -audio tcp/tcphost:8001 dial.snd In the following example, the auscope verbosity is increased to 1, and the audio client autool will connect to the audio server via the network host tcphost, while displaying its graphical interface on another server labmcx: auscope -i1 -o0 -hmcxterm -v1 autool -audio tcp/tcphost:8001 -display labmcx:0.0 SEE ALSO
nas(1), perl(1) COPYRIGHT
Copyright 1994 Network Computing Devices, Inc. AUTHOR
Greg Renda, Network Computing Devices, Inc. 1.9.3 AUSCOPE(1)
Man Page