On Wed, Jun 04, 2008 at 10:03:06PM +0000, Jacob Meuser wrote: > On Wed, Jun 04, 2008 at 06:22:09AM -0700, Alexander.Pavlyutin wrote: > > > > artsplayer works fine. esdplay works fine. > > esd running with options "-noterminate -nobeeps" > > artsd running with options "-a esd" > > I'm not useing kde, and i don't need /tmp/ksocket-$USER. > > artsd only need manualy created ~/.kde/socket-`hostname` if directory not > > exists
either directory works. > > Besause timidity not installed as depend not for arts, sdl, sdl-sound I > > think it's not need. > > sdl-sound has it's own copy of timidity. > > anyway, I'm pretty sure that's not what's causing the problem. exactly > what is, I don't know yet. for example: $ echo $SDL_AUDIODRIVER arts $ playsound test.wav Couldn't open audio device! reason: [Couldn't open /usr/local/lib/timidity/timidity.cfg]. $ sudo mkdir -p /usr/local/lib/timidity $ sudo touch /usr/local/lib/timidity/timidity.cfg $ playsound test.wav Couldn't open audio device! reason: [Couldn't open /etc/timidity.cfg]. $ sudo touch /etc/timidity.cfg $ playsound test.wav Couldn't open audio device! reason: [Couldn't open timidity.cfg]. $ touch timidity.cfg $ playsound test.wav Couldn't open audio device! reason: [No available audio device]. as I said, this is just the last error message in SDL's message buffer (the last SDL_SetError(msg)). > do other sdl apps work? I usually use oilwar for testing, and it doesn't > work for me in such a setup. but it does when running under kde, which is what I don't understand. I've never noticed SDL to behave differently under different window managers. > > -- > > View this message in context: > > http://www.nabble.com/problem-with-sdl-sound-on--current-tp17592197p17646617.html > > Sent from the openbsd user - ports mailing list archive at Nabble.com. > > > > -- > [EMAIL PROTECTED] > SDF Public Access UNIX System - http://sdf.lonestar.org > -- [EMAIL PROTECTED] SDF Public Access UNIX System - http://sdf.lonestar.org
