I've been following this thread a bit a decided to give timidity a try, but 
I'm having a bit of a problem.  I configured timidity with the following 
options:
--localstatedir=/var/state/timidity++ --with-elf --enable-audio=arts,alsa 
--enable-server --enable-network --enable-dynamic --enable-vt100 
--enable-spline=cubic --with-default-output-alsa --enable-alsaseq

I used these since I was trying to copy the way that gentoo builds timidity.  
Anyway, I have everything built, and if I enter something like:
timidity foo.mid
It plays just fine.  If I start it in server mode, it seems to work okay:

[EMAIL PROTECTED] ~ $ timidity -iA -B4,11 -Os
Requested buffer size 32768, fragment size 8192
ALSA pcm 'default' set buffer size 33868, period size 3760 bytes
TiMidity starting in ALSA server mode
Opening sequencer port: 128:0 128:1 128:2 128:3

The next thing I do is fire up kmid (the KDE midi player).  Kmid is able to 
detect the MIDI port (or whatever you call it).  I open up a midi file and 
tell it to start playing.  Timidity spits out:

Requested buffer size 32768, fragment size 8192
ALSA pcm 'default' set buffer size 33868, period size 3760 bytes

So clearly kmid managed to interface with the server.  From the application, 
everything seems to be playing normal, but nothing comes out (i.e. I can't 
hear it playing).  I don't think its an issue of volume since playing the 
file with timidity directly works.  Any ideas?

Gabe
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to