NASD.CONF(5)

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

🌸 NASD.CONF(5) β€” the config file for NAS servers, bestie 🌸

(that's the NASD.CONF(5) manual page, filed under *File Formats Manual β€” yes we're in the file formats section, stay with me 🫢)*

πŸ’– NAME πŸ’–

nasd.conf β€” the config file for NAS servers. that's it. that's the whole name. iconic.


✨ DESCRIPTION ✨

okay so nasd.conf is the file you use to configure how your NAS server behaves πŸ’… and like, it does a LOT:

  • which devices it's gonna try to use
  • the minimum & maximum frequencies
  • whether the device runs in 8bit or 16bit mode
  • what fragment size and how many fragments to use (super handy for tuning the server's latency, fr)
  • whether the server should be verbose when starting up, or dump debugging info

ngl though β€” not all options are supported for all servers. so before you go feral in the config, peek at the /etc/nas/nasd.conf.eg file, it literally tells you which options work for which servers πŸŽ€


πŸ¦‹ THE CONFIG FILE SYNTAX πŸ¦‹

there are up to three sections in the config file, periodt:

  1. the first section is all about global options β€” some of them just turn on verbose messages while parsing the config, and some turn on debug messages.
  2. the remaining two sections, if present, adjust various parameters of the input and output devices β€” but only for the servers that actually understand them.

here's every single one, no skips, no cap πŸ’–

  • verbose β€” sets a flag telling the server to report what it's trying to do with each setting in the config file. this one is off by default.
  • debug <number> β€” sets the debug flag, which gives you a whole trace of the server's activities on stderr. set <number> to 0 to disable debug messages, or 99 for alot of debug messages. defaults to 0.
  • ReleaseDevice YES | NO β€” set to YES or NO. defines whether the server should release the audio device when it's finished playing or recording a sound. defaults to YES. (voxware, hpux, sun)
  • KeepMixer YES | NO β€” set to YES or NO. defines whether the server should keep the mixer open when releasing the audio device. and listen β€” without an open mixer device, the server will always report the default gain and line mode, and cannot change them either 😭 defaults to YES. (voxware)
  • MixerInit YES | NO β€” set to YES or NO. defines whether the server will init the mixer device on startup. later changes of gain or input mode will change the mixer settings. defaults to NO. (voxware)
  • ReInitMixer YES | NO β€” set to YES or NO. defines whether the server will re-init the mixer device on every audio device open. heads up tho: the mixer is re-initialized only if it is initialized at startup (see the MixerInit option above πŸ‘€). defaults to NO. (voxware)
  • OutDevType EXT | INT β€” for HPUX servers: define it to EXT to use the external output device (headphone/speakers) or INT for the internal output device (internal speaker). defaults to EXT.
  • outputsection β€” marks the beginning of the output section, which lets you set up various parameters of the output device ✨
  • inputsection β€” marks the beginning of the input section, which lets you set up various parameters of the input device ✨
  • end β€” marks the end of the input section or output section. the closer. the periodt of sections.
  • device <devname> β€” specifies what device is used. example: device "/dev/dsp". with the voxware server you can use the empty string "" to disable the device entirely πŸ™ˆ
  • mixer <mixername> β€” specifies what mixer device is used. example: mixer "/dev/mixer". if <mixername> is set to the empty string "", no mixer is used in this section.
  • gain <number> β€” specifies the default volume (0-100). default is 50.
  • gainscale <number> β€” this factor (expressed as a percentage) gets applied to all volume-setting requests. it lets the server transparently limit the actual maximum volume clients can set πŸ‘‘ default is 100.
  • maxrate <number> β€” the maximum number of samples per second that we'll drive the card at.
  • minrate <number> β€” the minimum number of samples per second that the card will be driven at.
  • maxfrags <number> β€” the maximum number of kernel buffers that will be used for the device. the number is dynamically adjusted as the sampling frequency varies.
  • minfrags <number> β€” the minimum number of kernel buffers that will be used.
  • fragsize <number> β€” the size of each buffer. note that the size must be a power of 2 ⚠️
  • wordsize <number> β€” the number of bits per sample. allowable values are 8 and 16.
  • numchans <number> β€” used to decide if the card is run in stereo or mono mode. allowable values are 1 or 2.
  • forcerate no | yes β€” forces the output rate to the current rate. default is no.
  • autoOpen no | yes β€” whether to open the device at init time (if ReleaseDevice = no). default is yes.
  • readwrite no | yes β€” whether or not to open the device read-write. default is no. if set to yes, then the device will be opened read-write. there should be no need to set this to yes, but... πŸ’€

🌈 SEE ALSO 🌈

nas(1), nasd(1), auinfo(1), auplay(1), auctl(1)

go read those too, bestie, they're part of the lore πŸ“š


πŸ’€ BUGS πŸ’€

Absolutely none.

(i know. i know. iconic behaviour. we love a flawless queen πŸ‘‘)


πŸŽ€ AUTHORS πŸŽ€

  • Stephen Hocking (sysseh@devetir.qld.gov.au)
  • Jon Trulson (jon@radscan.com)

give them their flowers, they built this πŸ’


πŸ’– and that's the whole page!! this came to you from the NAS source, and yeah, it lives at NASD.CONF(5). slay, go edit that config, and remember: power of 2 for fragsize or it's over for you 🧚✨
πŸ“¦ where this page comes from