I'm having difficulty getting timidity++ to provide transparent MIDI support with OpenTTD.
I've tried both the music set available via in-game download as well as the AUR package openttd-openmsx; in both cases, timidity++ can play individual files on the command line, even if another program is playing back audio, so it is unlikely that Pulse is monopolizing output.
I've experimented with setting default_driver=pulse in /etc/libao.conf as recommended in PulseAudio's PerfectSetup, as well as preserving the default settings (which means playback through pulseaudio-alsa). In both cases, Timidity shows up in the GNOME sound applet, unmuted, and timidity++ does not display any startup errors. Enabling the timidity systemd service mutes the speakers, and once they're unmuted through the GNOME applet, OpenTTD still does not play music.
Any help is appreciated.
$ timidity -iA -OO & TiMidity starting in ALSA server mode Opening sequencer port: 128:0 128:1 128:2 128:3
$ cat /etc/libao.conf default_driver=pulse
# lspci -v 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) Subsystem: Samsung Electronics Co Ltd Device c708 Flags: bus master, fast devsel, latency 0, IRQ 43 Memory at f0700000 (64-bit, non-prefetchable) [size=16K] Capabilities:  Power Management version 2 Capabilities:  MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities:  Express Root Complex Integrated Endpoint, MSI 00 Capabilities:  Virtual Channel Capabilities:  Root Complex Link Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel
Update: On my Debian 7 machine, installing the 1.4.1 version of the package from the openttd.org website also muted music, both from ingame content download and from the Debian openttd-openmsx package. As such, this could be an OpenTTD bug, but no such issues exist in the OpenTTD bug tracker or the OpenMSX tracker.
Last edited by Ascanius (2014-06-25 10:32:02)