You are not logged in.

#1 2009-06-21 18:15:15

b4283
Member
Registered: 2008-11-26
Posts: 123

ALSA Errors from Timidity++

I've been using Timidity++ with dosbox and it worked nicely until recently updates (dunno caused by what)
that dosbox no longer MIDI-operational with Timidity++, while on the command-line playing MIDI files with timidty works okay, and vkeybd --addr 128:0 works fine too.

the work around seems to be start dosbox with aoss.

here's the error message:

$> timidity -iA
Requested buffer size 32768, fragment size 8192
ALSA pcm 'default' set buffer size 30104, period size 3760 bytes
TiMidity starting in ALSA server mode
Opening sequencer port: 128:0 128:1 128:2 128:3
[i](start dosbox)[/i]
ALSA lib pcm_dmix.c:1008:(snd_pcm_dmix_open) unable to open slave
Can't open pcm device 'default'.
Couldn't open ALSA pcm device (`s')

looks pretty much like a problem from ALSA

I've looked up the forum and found somebody has some problems too, with newer kernels.
that 2.6.30 uses a newer alsa library, but falling back to 2.6.29 doesn't help either.

Last edited by b4283 (2009-06-21 18:16:55)

Offline

#2 2009-06-23 22:51:22

xyrico
Member
Registered: 2009-06-11
Posts: 13

Re: ALSA Errors from Timidity++

I can confirm that I have this exact same problem with 2.6.30. Not sure what to do about it, other than a workaround, since it's been about a month since I've tried to run dosbox and there have been many updates since then.

EDIT: As an alternative workaround, replacing timidity++ with fluidsynth allows dosbox to run properly without aoss.

Last edited by xyrico (2009-06-23 23:54:17)

Offline

#3 2009-06-28 14:04:00

b4283
Member
Registered: 2008-11-26
Posts: 123

Re: ALSA Errors from Timidity++

thanks for the fluidsynth infomation.
it works perfect! i guess we can get rid of timidity now

Offline

Board footer

Powered by FluxBB