AUSCOPE(1)

πŸ“¦ version 1.9.5, in fedora 43, fedora 44

πŸŽ€ AUSCOPE β€” the Network Audio System Protocol Filter πŸŽ€

okay bestie, sit down, because auscope is genuinely one of those little tools that's giving main character energy for anyone trying to figure out what their audio app is actually saying to the server πŸ’–


✨ NAME ✨

auscope β€” the Network Audio System Protocol Filter, no cap πŸ¦‹


🌸 SYNOPSIS 🌸

auscope [ option ] ...

πŸ’… DESCRIPTION πŸ’…

so auscope is an audio protocol filter, and its whole vibe is letting you watch the network packets flying back and forth between an audio application and an audio server πŸ‘€βœ¨ like a little gossip channel but for packets, and honestly? iconic.

auscope is written in Perl, so you literally must have Perl installed on your machine to run it, fr fr. And listen β€” if your Perl executable is not installed as /usr/local/bin/perl, you're gonna want to go edit the first line of the auscope script so it points at wherever your Perl actually lives. Or, alternatively, you can just invoke auscope like this:

perl auscope [ option ] ...

...assuming the Perl executable is in your path 🫢 easy.

Now, to actually operate, auscope needs to know three things, periodt:

  • 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 the input port (client) are automatically biased by 8000. The output port defaults to 0 and the input port defaults to 1. lowkey important, don't forget it πŸ’œ


πŸ”₯ ARGUMENTS πŸ”₯

  • -i<input-port> β€” picks the port that auscope will use to take requests from clients πŸ’«
  • -o<output-port> β€” decides the port that auscope will use to connect to the audio server 🌈
  • -h<audio server name> β€” sets the desktop machine name that auscope will use to find the audio server πŸ‘‘
  • -v<print-level> β€” controls the level of printing that auscope will provide. The print-level can be 0 or 1. The larger numbers provide greater output detail πŸ” (yes bestie, more number = more tea β˜•)

πŸ¦‹ EXAMPLES πŸ¦‹

In this first 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 next one, 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 1994 Network Computing Devices, Inc.


πŸŽ€ AUTHOR πŸŽ€

Greg Renda, Network Computing Devices, Inc.


okay that's the whole thing bestie, you ate that πŸ“βœ¨ this was AUSCOPE(1), version 1.9.5, and it's a General Commands Manual moment β€” go forth and watch those packets, ily, bye πŸ’œπŸ¦‹πŸ’…

πŸ“¦ where this page comes from