The Network Audio System (NAS) is a network-transparent, client/server audio system originally developed at Network Computing Devices (NCD) by Jim Fulton, Greg Renda, and Dave Lemke. The client software can also be used with several models of NCD X terminals as well as NCD's PCXware (an X server for PCs running Microsoft Windows). Key features of the Network Audio System include:
nas-1.4.2: description + notes
- Device-independent audio over the network
- Lots of audio file and data formats
- Can store sounds in server for rapid replay
- Extensive mixing, separating, and manipulation of audio data
- Simultaneous use of audio devices by multiple applications
- Use by a growing number of ISVs
- Small size
- Free! No obnoxious licensing terms
The Network Audio System (NAS) homepage has more information.NOTE: Because of conflicts with the standard IRIX audio headers and library this package has been modified to install headers under /usr/freeware/include/nas, and the library has been renamed libnas. You may either modify clients to use these names and paths, or follow the directions below.
NOTE: Developers intending to use this distribution of libaudio for application development should be sure to read the information below. Users installing libaudio for the runtime environment only need not read any further.
Developers intending to use this library for development of other freeware packages or their own software applications will need to be familiar with a few peculiarities due to the way that this library is packaged and installed. The reasons for this installation strategy are described further in the fw_common product release notes.
The header files and libraries in this package are installed into /usr/freeware. This means that when building software using this distribution of libaudio you should be sure to do the following:
This flag will cause your compilations to correctly find the library's header files at compile time.
- Include the following flag on your compile lines:
- -I/usr/freeware/nas/include -I/usr/freeware/include
Include the following flag on your link lines:
-L/usr/freeware/nas/lib (if using o32 ABI) -L/usr/freeware/nas/lib32 (if using n32 ABI) -L/usr/freeware/nas/lib64 (if using 64 ABI)This flag will cause the linker to correctly find the library's archive or shared object files at link time.
Additionally, include the following flag on your link lines:
-rpath /usr/freeware/lib (if using o32 ABI) -rpath /usr/freeware/lib32 (if using n32 ABI) -rpath /usr/freeware/lib64 (if using 64 ABI)This flag will allow the binary to locate the shared object library files when the application is run. This is required since the shared objects are stored in these /usr/freeware subdirectories which are not searched by the run-time linker by default.
Finally, if you are building an installable package for inst (contributing to freeware, for example) be sure to make your package depend upon this package. Add the following line to your spec file: prereq ( fw_nas.sw.lib 1230000000 1239999900 )Following these guidelines will allow your application to safely and easily use the software in this package.
To auto-install this package, go back and click on the respective install icon.