On Sun, 25 Nov 2007, admin@xxxxxxx wrote:
[root]# whereis nasd nasd: /usr/bin/nasd /usr/share/man/man1/nasd.1x.gz
Ahh, so it's moved.
[root]# /usr/bin/nasd -aa -v -d 99 Network Audio System Release 1.9.1 Network Audio System Release 1.9.1 AuInitPhysicalDevices(); Init: will close device when finished with stream. Init: will keep mixer device open. Init: Leaving the mixer device options alone at startup. Init: openDevice OUT /dev/dsp mode 1 Init: Output open(/dev/dsp) failed: No such file or directory Fatal server error: could not create audio connection block info [root]# No dsp device! Now how can that be?Does nas create a virtual DSP device accessed through a port or do you have to have hardware installed on the server?
Yes - I had thought Paul explained that - basically nas is a sound server - ie: it provides network access to sound hardware. The nasd server runs on the machine(s) that have the audio devices installed in them. nas clients connect (locally or over the network) to the nasd server to play sounds. It works very much like an Xserver (and in fact is based on X11), where the X server runs on the device with the display hardware (video card/monitor, mouse, etc) and X clients connect to it to display their thang.
Jon Trulson wrote:On Sun, 25 Nov 2007, admin@xxxxxxx wrote:I can confirm it works with Ubuntu (Ubuntu Breezy on Mac Mini ppc) root@ /etc/init.d]# ./nas start Starting the Network Audio System @(#)Network Audio System Release 1.7 root@ /etc/init.d]# While on FC7 it is ambiguous. [init.d]# ./nasd start Network Audio System Release 1.9.1 [ OK ]^^^ crap, I only noticed the upper one (v1.7), sorry. Really, try starting nasd as described in my previous post, it should provide a lot more info. [...]
-- Happy cheese in fear | Jon Trulson against oppressor, rebel! | mailto:jon@xxxxxxxxxxx Brocolli, hostage. -Unknown | #include <std/disclaimer.h>