SoundSense

Discussion: http://www.bay12forums.com/smf/index.php?topic=60287.0 Homepage: http://df.zweistein.cz/soundsense/

Installation

Installing and configuring software can be intimidating if you are not an IT nerd. And this is no exception with SoundSense. But bear with me and it can actually be pretty easy.

Non-scary instructions:

Install the java runtime
Download and extract SoundSense (It does not matter where.)
Download soundpack.zip and extract the "packs" folder to SoundSense directory
Run soundsense.cmd or soundsense.exe

First, you need to have the java runtime installed. It can be downloaded from the java homepage. To determine if your computer already has the correct installation of java, go to the Start button, left click "Run..." from the bottom of the menu, type in "cmd" in the dialog that opens, and press the [OK] button. A dark windows pops up and you will be at a command prompt. Type in "java -version" and press [Enter].

A few lines starting with [java version "1.6.0_14"] or something similar should apear. If that case is the case, you are good to go. But if you see [java version "1.5.x_xx" or an earlier version (lower number), you will need to download and install the latest java.

If something similar to ['java' is not recognized as an internal or external command] appears, either java has not been installed yet or it was not installed correctly. If your case is the latter, it may be possible to work around the problem by editing the soundSense.cmd (in your SoundSense directory). Open it with Notepad and find line line starting with "java -Dja..." and replace the "java" part with the full path for your java installation. For example: "C:\Program Files\Java\jdk1.6.0_20\bin\java.exe"

That was the hard part.

Now, where to install it? SoundSense expects to be in a sub-directory that is inside your Dwarf Fortress directory. So, for example, if you have Dwarf Fortress in F:/df_31_18_win/, you should unpack the contents of SoundSense zip to F:/df_31_18_win/soundsense/. By default, you want to make sure that the .cmd file you use to launch SoundSense is inside a sub-directory of (i.e., below) the DF folder where gamelog.txt is located.

If you want to install to a different location, you need to edit configuration.xml and edit the <gamelog path="../gamelog.txt"/> line. Replace "../gamelog.txt" with the path to where Dwarf Fortress is located. For example: "F:/df_31_18_win/gamelog.txt"

SoundSense is now all set up and ready to run. But you still need the actual sounds and music that it will play. So download soundpack.zip and unzip the "packs" directory and all the contents inside that to the SoundSense directory.

You can start SoundSense by launching (double left-clicking) either soundSense.cmd or soundSenseExe.cmd. (Using the latter should give you clearer error messages regarding a bad java installation.) If you like, you can create a shortcut to soundSense.cmd, rename it "SoundSense" and move it to your desktop for easy access.

Finally, remember that SoundSense needs to run in the background. Ideally, you should start SoundSense BEFORE you start Dwarf Fortress.

Known Issues

Moments of Silence

Occationally, the music in SoundSense will stop for a short period (10, 20, or 30 seconds) before resuming. This is not a bug - it is intentional. This was done to let ears rest a bit between tracks. (Research shows that ears which get a rest have time to recover and are less likely to be damaged.) Also, a few tracks have a silent start and, at low volume, may take a minute or longer to become audible. If in doubt, you can see what is currently playing in GUI under the volume slider. During periods of silence, this will typically show "10s silence" or similar.

Game Loads and the Music is Random

When a game is loaded, SoundSense picks a random seasonal music track to play. This is not a bug - it is intentional. There is no way for SoundSense to detect what season it is when a game is loaded, so a random soundtrack is chosen. But when the season next changes, it will choose the correct soundtrack.

Adventure Mode - A Bit Lacking

Adventure Mode kind of works. The battle sounds function quite well because they are mostly the same as those in Fortress Mode. But SoundSense is still a bit lacking in other adventure sounds. The problem is that Adventure Mode does not log many other usefull events. For example, encountering a megabeast or a quest mob is resolved in chat, leaving no message in the game log to trigger SoundSense.

Improvements in how DF handles logging could benfit both SoundSense and DF as a whole. Such suggestions have already been posted in the official Dwarf Fortress forums: http://www.bay12forums.com/smf/index.php?topic=64834.0

Event Detection: Better Late Than Never?

In some cases, by the time SoundSense detects conditions to trigger an alert, it may be too late to react to the situation. For example, a "Tantrum Spiral" might already be over before the player can be alerted.

Part of this is a balance between detecting too many false positives and ignoring events until it is too late to do anything. For example, a soldier might lose a pet and report feeling like blowing off some steam... but instead of throwing a tantrum they calm down.

Another problem is FPS sensitivity. A specific sequence of events may trigger certain alert sounds in a high FPS situation, but it might not trigger with low FPS. The sequence of events might "time out". Also, pausing the game could cause similar problems.

Compatible With DF Mods - Should Work, But NO PROMISES

SoundSense was mainly designed for "vanilla" (unmodified) Dwarf Fortress. It should work fine with most mods. However, I can not guarantee compatibility. Some mods, especially "major" or "full conversions", may create unusual behavior and involve dangerous events that SoundSense was not designed to detect.

Another words, SoundSense may lack sounds for certain mod-specific events. (E.g.; you should NOT expect SoundSense to include gunshot sounds for mods that add guns! But you CAN modify SoundSense yourself to do this.) Conversely, some events that work normally in vanilla DF may trigger so frequently with a mod as to be very annoying.

On some Linux

Error on 'soundSense.sh' call: "/bin/sh^M : wrong interpret"

File "soundSense.sh" has CR+LF characters at lines ending. Convert these characters to a more suitable form, with a tool like "dos2unix":

 dos2unix soundSense.sh

Shell script should then be run without previous error.

Also using sed you can try this:

 # IN UNIX ENVIRONMENT: convert DOS newlines (CR/LF) to Unix format.
 sed -i -e 's/\r$//' ./soundSense.sh

IF launching .sh file after that, says that something is wrong on the last line, when you try to launch sh. Just check, if "fi" is present there instead of "f" or smth like that.

Error at playing any MP3 file: "javax.sound.sampled.UnsupportedAudioFileException: could not get audio input stream from input file: could not get audio input stream from input file"

Your Java virtual machine failed at reading MP3 files as audio stream. This could fix by adding to JVM an extra plugin: JMF MP3 Plugin. Download plugin, and put *.jar files into your JVM "lib/ext/" directory.

Error at playing any MP3 file: "javax.sound.sampled.LineUnavailableException: Audio Device Unavailable"

Whereas your JVM succeeded in reading MP3 file as audio stream, it failed to access to an audio device. If your audio system uses Alsa, you could install "aoss" utility, and "soundSense.sh" will call it. On Debian, package "alsa-oss" provides this utility. Note: if you are on Ubuntu see below. Ubuntu uses PulseAudio backend, therefore toying with aoss is a waste of time.

Goddammit I'm using PulseAudio and I still can't hear anything!

First, be sure that you are using OpenJDK 7; you can't use OpenJDK 6 as it has quiet a serious bug in its ALSA backend[1]. You can check what java you have installed by typing

 java -version

in the terminal. You can install OpenJDK like this in Ubuntu:

 sudo apt-get install openjdk-7-jdk
 sudo update-alternatives --set java /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java

(The "update-alternatives" command will only work on 64bit Ubuntu; for 32bit version you need to replace the "amd64" with "i386" or something like that.)

Now, check the

 /etc/java-7-openjdk/sound.properties

file for this:

 # OpenJDK on Ubuntu is configured to use PulseAudio by default
 javax.sound.sampled.Clip=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider
 javax.sound.sampled.Port=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider
 javax.sound.sampled.SourceDataLine=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider
 javax.sound.sampled.TargetDataLine=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider
 
 # PulseAudio not running? Please give feedback on LP: #407299.
 #javax.sound.sampled.Clip=com.sun.media.sound.DirectAudioDeviceProvider
 #javax.sound.sampled.Port=com.sun.media.sound.PortMixerProvider
 #javax.sound.sampled.SourceDataLine=com.sun.media.sound.DirectAudioDeviceProvider
 #javax.sound.sampled.TargetDataLine=com.sun.media.sound.DirectAudioDeviceProvider

This will not work, as OpenJDK's PulseAudio backend is buggy as hell. What you need to do is to comment out the PulseAudio and turn back on the old backend:

 # OpenJDK on Ubuntu is configured to use PulseAudio by default
 #javax.sound.sampled.Clip=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider
 #javax.sound.sampled.Port=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider
 #javax.sound.sampled.SourceDataLine=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider
 #javax.sound.sampled.TargetDataLine=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider
 
 # PulseAudio not running? Please give feedback on LP: #407299.
 javax.sound.sampled.Clip=com.sun.media.sound.DirectAudioDeviceProvider
 javax.sound.sampled.Port=com.sun.media.sound.PortMixerProvider
 javax.sound.sampled.SourceDataLine=com.sun.media.sound.DirectAudioDeviceProvider
 javax.sound.sampled.TargetDataLine=com.sun.media.sound.DirectAudioDeviceProvider

This should make the sound work. (If you don't know how to edit this then try typing "sudo nano /etc/java-7-openjdk/sound.properties" in the terminal.)

If you're using Sun/Oracle's JRE then switch to OpenJDK. If you don't want to do that (not recommended) then you might try to use the padsp wrapper or install osspd. If the padsp wrapper will not work properly for you then osspd daemon might just do the trick. (Archlinux Pulseaudio user)

Any Other Issues? Post Feedback

There is a thread at the official Dwarf Fortress forums. Feel free to post any issues, suggestions, and contributions there: http://www.bay12forums.com/smf/index.php?topic=60287.0

When providing feedback about your experience with SoundSense, please specify which mods (if any) you are using. If SoundSense seems to behave weirdly only for you, it just might be from using certain mods.

Customization

You can insert additional sounds and music into SoundSense by adding entries to an .xml configuration file. logPattern="regexp" is a regular expression which, if matched, will cause a random soundFile from a list to be played. (Details on how java uses regular expressions: http://download.oracle.com/javase/1.4.2/docs/api/java/util/regex/Pattern.html )

Sound element attributes:

logPattern - regular expression matching log line (see link above)
channel - string; Specifies a channel on which sound is played. Sounds played on a channel can be looped or stopped prematurely.
loop - string; Specifying "start" will start looping a sound on a channel until an expression with "stop" is triggered or until a different loop sound is played on the same channel. (If a non-looped sound is triggered on the same channel, this loop will resume when the non-looped is done playing.)
concurency - number; The number of concurrent (i.e., simultaneous) sounds allowed to be played besides this sound. If SoundSense is currently playing more than this, the sound is ignored. The default is unlimited.
timeout - number; This initiates a time out during which this particular sound is prevented from playing again. This is measured in milliseconds and the default is 0.
delay - number; Adds a delay before the sound is played. This is measured in milliseconds and the default is 0.
haltOnMatch - boolean; If this is set to True and more than one equivalent logPattern exists, SoundSense will only process the first logPattern expression. If it is False, it will continue to process matching (e.g., identical) logPatterns. The default is True.
speech - boolean; If this is set to True, SoundSense will echo the gamelog text line (containing the logPattern) with a speech synthesizer instead of playing a sound. The default is False.
playbackThreshhold - number, 0-4, defines level of filter which is applied to this sound.

SoundFile element attributes:

fileName - the path to and name of the sound/music file
weight - number; This controls the likelihood of a sound being chosen. Default is 100.
volumeAdjustment - number; This can be used to adjust the volume of the sample. The value can range from -40 to +6 decibles and the default is 0.
randomBalance - boolean, if set to true will randomply distribute sound betweem stereo channels.
balanceAdjustment - number, adjusts stereo channel, can range for -1 (full left) to 1 (full right).

SoundSense supports these audio formats for soundFiles:

mp3 (SoundSense can normalize the sound volume with this format)
ogg (works, but SoundSense can not normalize the sound volume)
wav (See note below. SoundSense only supports "Windows PCM" encoded .wav files)
aiff
au

Note: Not all .wav files are supported...

SoundSense supports .wav encoded in the "Windows PCM" format. However, some files with the .wav extention are actually encoded in some other proprietary format. A sound format conversion utility (such as FormatFactory) could be used to fix them.

Some Tips:

Control of Randomness: Each logPattern expression can contain several soundFile elements. When it is triggered, one of them is randomly chosen to play. You can control the probability of each sound being chosen by adding the weight="number" attribute.
Simultaneous Sounds: By default, only one sound will play for a given logPattern, even if there are several expression using identical logPatterns. (Only the first expression is processed.) But you can allow more than one sound to be played for same pattern by giving the first one the haltOnMatch="false" attribute. They will all start at same time (unless one or more of them also has a delay). An example is in Seasons.
Sequential Sounds: Two (or more) sounds can be played sequentially (one after the other) for the same logPattern by using the haltOnMatch="false" tip above and including a delay attribute for one of them with a delay that surpasses the length of the other.

Helpful files:

packSkeletons.zip ( http://df.zweistein.cz/soundsense/packSkeletons.zip ) - This contains .xml files for all known gamelog lines currently without sounds. You can use this as a starting point to expand SoundSense.
missingMessages.cmd - Run this program to parse your gamelog.txt file and output all lines your sound packs will not recognize.
logging.properties - Edit this file to enable more debug messages from SoundSense. Set ".level = ALL" to view a very verbose output.

Sources of sound & music:

The following are some sites of interest, should you want additional sounds/music. (Websites with free, creative commons, public domain, and/or GNU GPL licensed audio):

Utility:SoundSense

Contents