Bottom post...please. Ryan wrote:
>The docs for that wrapper say that its only used for 4.x. I've been >able to use sound in 4.x just by using artsdsp or esddsp in the past >(although it wasnt the best, it did work) but I am now using 5.0. I >gave it a whirl and still it didnt work. It still says there is no >/dev/dsp device. Both artsplay and esdplay are currently working. KDE >uses arts, so I know thats working. NWN works great with artsdsp and >some of my media players use esddsp. > >Is there some command that will tell me which /dev device that artsd or >esd is using? I am pretty sure its /dev/dsp, but with absolutly nothing >working that I have tried with VMWare and /dev/dsp, there is a chance >that they could be using something else. > > > I can only speak to artsd, which if you have configured to use ALSA, will not use /dev/dsp at all. /dev/dsp is the (obsolete) OSS API, so an application using ALSA will not use it at all. esd should be similar. FYI, the wrappers work by overloading the file operation functions such as open(), read(), write(), close(), etc. When the replacement function in the wrapper sees an attempt to open "/dev/dsp", it instead opens the appropriate sound library/server. So it doesn't matter whether you have /dev/dsp or not if you are using a wrapper. The current artsdsp and esddsp will not work (at least on a 32-bit system) with VMWare, because VMWare is a large-file aware application and thus uses open64(), read64(), write64(), etc.. That is why you need vmwaredsp. You may want to turn on debugging in vmwaredsp: 1. Change "#define VMDSP_DEBUG (0)" to "#define VMDSP_DEBUG (1)" in vmdsp.c, and rebuild/re-install vmwaredsp. 2. Modify the startup script vmwarearts (or vmwareesd) to add "VMDSP_DEBUG=1" to the command line. When you run VMWare after these steps it should create a /tmp/vmdsp.log file with some info about what the wrapper is doing. -Richard -- [email protected] mailing list
