aboutsummaryrefslogtreecommitdiff
path: root/backends/midi/alsa.cpp
diff options
context:
space:
mode:
authorTorbjörn Andersson2010-07-19 05:30:40 +0000
committerTorbjörn Andersson2010-07-19 05:30:40 +0000
commit75dd75a73767319b2797a140f985dfc356462862 (patch)
tree9226fbcbe1f8f8420e56758aecccd3a1e724c77f /backends/midi/alsa.cpp
parentefbac08e6b5de96436b32ee5e8a79ba7f2b9cb88 (diff)
downloadscummvm-rg350-75dd75a73767319b2797a140f985dfc356462862.tar.gz
scummvm-rg350-75dd75a73767319b2797a140f985dfc356462862.tar.bz2
scummvm-rg350-75dd75a73767319b2797a140f985dfc356462862.zip
SUBSYSTEM: ALSA music driver
We should probably open the sequencer the exact same way, both when opening the driver and when asking it for available MIDI devices. Not that I've been able to figure out the difference between "hw" and "default" from the fine ALSA manual... And I'm not sure we really need to try and keep compatibility with ancient (pre-0.9.0?) ALSA any longer... svn-id: r51014
Diffstat (limited to 'backends/midi/alsa.cpp')
-rw-r--r--backends/midi/alsa.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/backends/midi/alsa.cpp b/backends/midi/alsa.cpp
index 6a1a8e88ae..a3f4b149d1 100644
--- a/backends/midi/alsa.cpp
+++ b/backends/midi/alsa.cpp
@@ -290,7 +290,7 @@ MusicDevices AlsaMusicPlugin::getDevices() const {
MusicDevices devices;
snd_seq_t *seq;
- if (snd_seq_open(&seq, "default", SND_SEQ_OPEN_DUPLEX, 0) < 0)
+ if (my_snd_seq_open(&seq) < 0)
return devices; // can't open sequencer
snd_seq_client_info_t *cinfo;