RtCW sound without direct access to soundcard?

(zivs) #1

Hi,

Was just wondering if there are any possible workarounds for RtCW using only direct access to soundcard?

At the moment to run game with sound I have to do echo ‘wolf.x86 0 0 direct’ > /proc/asound/card0/pcm0p/oss which means that all other sources gets cut off from soundcard using, including newly released Ventrilo client for linux - Mangler, which uses PulseAudio for input/output stuff.

Naturally, If I run the game while Mangler is open, rtcw “steals” the soundcard and Mangler becomes basically muted.

So, I was just wondering - is there actually any way to trick RtCW (and Q3, and ET) to use some sort of different access to soundcard, just not the direct one?

(ailmanki) #2

http://nullkey.ath.cx/et-sdl-sound/

(zivs) #3

Now that was a fast reply! Many thanks for that! :slight_smile:

EDIT:
Tried to run both of methods, but in both cases I get no sound anyway:

In the beginning I get this:
ERROR: ld.so: object ‘/<path’ from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object ‘to>/et-sdl-sound.so’ from LD_PRELOAD cannot be preloaded: ignored.

Then game loads the sound and I get:
------- sound initialization -------
/dev/dsp: Device or resource busy
Could not open /dev/dsp
------------------------------------

Happens with both et-sdl-sound.gz and specific wolf launcher and with old method (that script) :o

EDIT2:
Bah, that was because didn’t show where that .so file was. Now I get this:

[i]Read /home/zivs/.rtcw/wolf.x86 (1493964 bytes)
You are not running a recognized version of Enemy Territory or RTCW (CRC32 = 0xe5f17aa4)

…

------- sound initialization -------
/dev/dsp: Input/output error
Could not mmap /dev/dsp

[/i]

That is 1.4 version of the game.

(zivs) #4

Ah, everything worked fine - didn’t have 1.41, but 1.4 installed, lol. Thanks for the link to sdl-sound!