client:sound:sound_howto
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
client:sound:sound_howto [2018/03/10 06:15] – Fix internal link to sounds.conf karl | client:sound:sound_howto [2025/04/18 13:09] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 20: | Line 20: | ||
These sound.raw files are named like // | These sound.raw files are named like // | ||
- | To make these event sounds working inside the client, the client | + | ===== Technical ===== |
- | When the client | + | The Crossfire |
- | + | When the client | |
+ | The default | ||
+ | - very legacy //alsa 0.5// | ||
+ | - legacy OSS | ||
+ | - SGI | ||
+ | - SUN | ||
+ | - SDL since v1.60.0 , needs SDL_mixer later than at least v1.2.9 | ||
+ | |||
+ | Most people will very likely have the OSS version of the cfsndserv, since the legacy ALSA code does not compile with recent 1.x ASLA libraries and their headers, and the SDL music is not enabled by default while configuring the client before compiling it: | ||
+ | >>> | ||
===== Configuration File sounds ===== | ===== Configuration File sounds ===== | ||
:!: For recent 1.71+ versions of the client, see [[# | :!: For recent 1.71+ versions of the client, see [[# | ||
+ | |||
+ | To make these event sounds working inside the client, the client has to know, where these event files are located on the system . \\ | ||
+ | When the client starts, it checks for two sound related configuration files in the HOME directory [[: | ||
From the // | From the // |
client/sound/sound_howto.1520684129.txt.gz · Last modified: (external edit)