Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ (1) — SVR4 88k NCDware 3.1

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

ncdaudio(1)

auplay(1)

autool(1)



AUSCOPE(1)               USER COMMANDS                 AUSCOPE(1)



NAME
     auscope - NCDAudio Protocol Filter

SYNOPSIS
     auscope [ option ] ...

DESCRIPTION
     auscope is an audio protocol filter, based on  xscope,  that
     can  be  used to view the network packets being sent between
     an audio application and an audio server.

     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 automatically  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.

     -d<display>
             Defines the display number.  The display  number  is
             added  to  the  input  and  output  port to give the
             actual ports which are used by auscope.

     -q      Quiet output mode.  Prints only set up  and  connec-
             tion  information.  Does not display protocol infor-
             mation, or protocol requests, events, or errors.

     -v<print-level>
             Determines the level of printing which auscope  will
             provide.   The  print-level  can be 0 (same as quiet
             mode), 1, 2,  3,  4.   The  larger  numbers  provide
             greater output detail.

     -D<debug-level>
             Determines the level of debugging information  which
             auscope  will  provide.  The debug-level defaults to
             0.  The larger the number, the  greater  the  output
             detail provided.  Useful levels are 1 and 7.



NCDware 3.0                                                     1





AUSCOPE(1)               USER COMMANDS                 AUSCOPE(1)



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  4  (the highest level), 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 -v 4

          autool -audio tcp/tcphost:8001 -display labmcx:0.0

     In the following example, standard input is redirected  from
     /dev/null to prevent auscope from stopping when put into the
     background.  Output is redirected to a file in /tmp.   Since
     the  default input and output ports (1 and 0) are used, they
     are not required on the  command  line.   The  audio  client
     auctl connects in the manner previously described:

          auscope -hmcxterm < /dev/null > /tmp/auscope.out &

          auctl -audio tcp/tcphost:8001

SEE ALSO
     ncdaudio(1), auplay(1), autool(1)

COPYRIGHT
     Copyright 1993 Network Computing Devices, Inc.

AUTHOR
     Dave Lemke, Network Computing Devices, Inc.









NCDware 3.0                                                     2



Typewritten Software • bear@typewritten.org • Edmonds, WA 98026