User Tools

Site Tools


client:sound:sound_howto

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
client:sound:sound_howto [2018/03/10 06:15] – Fix internal link to sounds.conf karlclient: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 //Teeswing.raw// .\\ These sound.raw files are named like //Teeswing.raw// .\\
  
-To make these event sounds working inside the client, the client has to know, where these event files are located on the system . \\ +===== Technical ===== 
-When the client starts, it checks for two sound related configuration files in the HOME directory [[:client:crossfire|.crossfire]] //sndconfig// and //sounds// . \\ +The Crossfire client uses a helper binary to play sounds. \\ 
- +When the client compiles, it usually creates two different sound server binaries named //cfsndserv// and //cfsndserv_alsa9// . By default, the client uses the //cfsndserv// , the //cfsndserv_alsa9// can be switched on by the commandline parameter [[:client:optional_parameters#-sound_server <path>]] </absolute/path/to/cfsndserv> . \\ 
 +The default //cfsndserv// server can be divided into several sound systemsThese sound systems are switched on when the client is getting compiled. Either : 
 +  - 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: 
 +>>>--enable-sdl_mixer      Enable use of the SDL_mixer library, default is not to use it 
 ===== Configuration File sounds ===== ===== Configuration File sounds =====
 :!: For recent 1.71+ versions of the client, see [[#Configuration File sounds.conf]] .  :!: For recent 1.71+ versions of the client, see [[#Configuration File sounds.conf]] . 
 +
 +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 [[:client:crossfire|.crossfire]] : //sndconfig// and //sounds// . \\
  
 From the //client/sound-src/common.c// : From the //client/sound-src/common.c// :
client/sound/sound_howto.1520684129.txt.gz · Last modified: (external edit)

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki