Sound error with Sauerbraten

by sirjavabean on 12/16/2007 17:34, 12 messages, last message: 12/19/2007 17:20, 1216 views, last view: 04/21/2024 04:21

Hi, I'm having problems getting sound to work with Sauer. Everything else works perfectly and sound is fine with other programs on my computer (I'm running Kubuntu 7.10 btw). Here's the output when I start Sauer:

init: sdl
init: enet
init: video: mode
init: video: misc
init: gl
Renderer: GeForce 6200 LE/PCI/SSE2 (NVIDIA Corporation)
Driver: 2.1.1 NVIDIA 100.14.19
Rendering using the OpenGL 1.5 GLSL shader path.
init: console
init: world
init: sound
sound init failed (SDL_mixer): No available audio device

I believe it could be a problem with SDL and sound? Though other SDL apps seem to do sound fine. I have Googled this already and although lots of people seem to have the same problem, I can't find any fixes.

Just so you know I compiled Sauer myself but I don't think that's relevant here.

   Board Index   

#1: ..

by Hirato Kirata on 12/17/2007 00:17

KDE is probably using the sound card.

Can you open the menu, go to system settings, then on sound system.

In that menu, you should see a slider on the bottom, if KDE plays a sound, that'll say how long it has exclusive access to your sound card (as the description says). Just lower it to 5 seconds maximum.

btw, I use kubuntu as well, with binaries I compiled myself. And I have that exact issue sometimes for the reason I stated above :).

~Hirato Kirata

reply to this message

#2: ..

by Quin on 12/17/2007 03:45

As it says 'No available audio device' instead of 'Unable to open audio device', I would assume it's looking for the wrong output method.

Make sure the 'sdl-mixer' package you install is for your current sound system, while it used to default to OSS, the standard is now ALSA. The package should be called 'libsdl-mixer-alsa' or something similar.

Failing that, look up the 'SDL_MIXER' environment variable for some hints on other methods to try.

reply to this message

#3: ..

by Q009 on 12/17/2007 11:07

Try with other operating system... Maybe Windowns XP.

reply to this message

#4: ..

by Q009 on 12/17/2007 11:08

Windows* not Windowns! xD

reply to this message

#5: Re: ..

by Quin on 12/17/2007 11:32, refers to #3

That's hardly an answer or solution to the problem. Please.

reply to this message

#6: Re: ..

by SheeEttin on 12/17/2007 21:53, refers to #2

Perhaps the settings under System Settings > Sound System > Hardware should be checked.
Also go through the settings in KMix.

I don't know if anything there will affect Sauer, though...

Kubuntu here, and it works fine.

reply to this message

#7: ..

by Julius on 12/17/2007 22:35

Yeah, works fine on kubuntu here too. Tried disabling the ARTS sound manager? (called sound-system in kubuntu) It is pretty useless anyways.

reply to this message

#8: Re: ..

by Quin on 12/18/2007 12:09, refers to #7

If you're using KDE (sorry, I didn't see you were using kubuntu) go to the place SheeEttin was talking about and reduce the "delay before sound server stops" (or something similar).

Also, in "notifications for events", turn off the sound for "open program", as this will start up the sound server again and cut your access to the wave out device.

I had the same problem initially, but I like some sounds in my windowing environment, and didn't want to disable them completely.

reply to this message

#9: Re: ..

by Quin on 12/18/2007 12:34, refers to #7

If you're using KDE (sorry, I didn't see you were using kubuntu) go to the place SheeEttin was talking about and reduce the "delay before sound server stops" (or something similar).

Also, in "notifications for events", turn off the sound for "open program", as this will start up the sound server again and cut your access to the wave out device.

I had the same problem initially, but I like some sounds in my windowing environment, and didn't want to disable them completely.

reply to this message

#10: ..

by Quin on 12/18/2007 12:36

Bah, internet cut out mid post. My first double post :(

reply to this message

#11: Re: ..

by Hirato Kirata on 12/18/2007 13:51, refers to #10

You mean triple post :P
anyways, I made the first post, suggesting to reduce the delay KDE has to give up it's access to the sound system.

It's probably just me, but I've noticed on my system, even after KDE plays a system sound through the speakers. I can still launch several instances of sauer (each with sound), even with the auto-suspend delay at 60 seconds. So SDL adn the KDE sound system may be completely unrelated.

sirjavabean, which variant of the debian SDL library are you using (like X11 + ALSA, or X11 + OSS) are you using. just look in adept or synaptic or something. and look for sdl1.2 . Can you make sure the ALSA variant is installed, or one of the other sound systems which you know is enabled on your system. ( apt-get install libsdl1.2debian-alsa will also work). That's if reducing the delay fails

~Hriato Kirata

reply to this message

#12: Re: ..

by sirjavabean on 12/19/2007 17:20

Thanks so much Hriato Kirata, I had the wrong version of SDL installed. Installing libsdl1.2debian-alsa did the trick. Silly me!

By the way I'm loving the Cube 2/Sauerbraten engine, especially now I can hear what's going on!

Thanks

sirjavabean

reply to this message

   Board Index