I there,
Im havin a sad issue since i have installed the latest ubuntu release. The sound will not work at all in the glx version. It works good in sdl but i dont want to use sdl because some buttons of my mouse dont work with it and there are some graphical artefacts that shows up . Sound is working in anything else i could think of testing (mp3s, movies, streaming )

when i start nexuiz-glx the folowing sequence of error shows up in the console:

[URL=http://g.imageshack.us/img11

really hoping someone knows the solution as i have a couples of incoming day off..and i wanted to play so much D:

Try as root:
chmod 777 /dev/dsp
chmod 777 /dev/mixer

ok i tried issuing those too command preceded by sudo , and after that ,started nexuiz. but still no sound and same error messages.
tx anyways for helping me

edit: after speaking with some other players , it seem im not the only one having this problem

Do you have esd, arts, pulseaudio, coreaudio or any other sound mixing thing running?
Other thing, would be to check whether you have .asoundrc in your home or /etc/asound.conf

hmm idk, how can i check that ?

Gnome has a process viewer or smth as a graphical interface.
You can also use ps in terminal.

ok after checking,
i dont have .asond in my home nor asound.conf in /etc

and the only process running in those that u listed that i have is pulseaudio

Can you try to close it and start nexuiz again?

OMG it works when i kill pulseaudio

u are my hero , im gonna go drink all the beer i have here in your honour

seriously u are the man, now what does that mean ? what is pulseaudio ?

Cheers. Alien also takes a large pint of strong dark beer (he likes dark one much more).

Pulseaudio is one of the thousand software mixers available for linux (I always try to stay away from them cause alsa can mix natively). If you intend to use it you need to route nexuiz through it somehow. I don't know how to do it for pulseaudio but it should have some help/manual. I suppose you can configure it somewhere in administration>sound or similar place.

ok thanks for the explanation alien,
I tried to uninstall pulseaudio by issuing the fallowing command:

Code: Select all

sudo apt-get autoremove pulseaudio

but doing that tell me that it will also remove the package ubuntu-desktop and something tell me that i dont want this to happen.
im actively looking for a clean solution to fix this issue, i will post results as soon as i have found it.

thanks again Alien for your help, it was extremely appreciated

Take a look at this:
http://www.pulseaudio.org/wiki/PerfectS ... plications

Sorry, I can't help you more cause I don't use Ubuntu. Div, z or any other ubuntu user might give better help.

OT, personally I use dmix on Linux and asio4all on windows due to the lower sound latency.

well ive spend all my day looking for a clean fix to that issue, and i could not find one.
so the solution of adding an item in the session startup manager that consist of a killall pulseaudio command seem to be how to do it for now. Doing that make everthing work like it should.

I've had the same problem, and killing pulseaudio indeed works... But then Audacious won't play anything... Even though I set it to use ALSA...

Muh!


EDIT: nevermind, restarting audacious makes it work again.


Waird!

additonal info :
tested teamspeak at the same time than nexuiz, all is good

liolak-mtl wrote:I tried to uninstall pulseaudio by issuing the fallowing command:

Code: Select all

sudo apt-get autoremove pulseaudio

but doing that tell me that it will also remove the package ubuntu-desktop and something tell me that i dont want this to happen.

ubuntu-desktop is a meta-package that just pulls in other packages and removing it doesn't cause harm directly.

But it is possible that the package that it pulls in (pulseaudio) is required by other apps.

Also on an update new packages that are required (and pulled in by ubuntu-desktop) would not be installed anymore, possibly breaking your installation. So it could be a good idea to reinstall ubuntu-desktop before updating.

Someone correct me if I'm wrong.

http://ph.ubuntuforums.com/showthread.php?p=6078456

there's your answer, i had same problem in intrepid ibex 8.10

i too wanted to stop having to manually kill the process after every boot

Unfortunately Ubuntu has tried to make a total conversion to Pulseaudio with the most recent releases and across the board it's pretty much broken.

It only shows Ubuntu is getting dumber with each release then.

Alien wrote:It only shows Ubuntu is getting dumber with each release then.

Aha. I think Pulseaudio does make sense (no, applications shouldn't directly interact with sound devices - most recent hardware has no hardware mixer, there is a *reason* why sound servers exist) and even if there are some transition problems (nasty and annoying) it doesn't make it "dumb". Fedora is also using Pulseaudio and I'm pretty sure SuSE will, too.

Talking about "dumb": There's a lot of pointless Ubuntu bashing around, so it seems.

What however is dumb is breaking support for non-pulseaudio applications that way at a time when pulseaudio is far from supported by every application. It's basically repeating the artsd mistake again.

Also, I doubt Nexuiz will get pulseaudio support anytime soon. I looked at the pulseaudio API, and the simple API always blocks and thus is unsuitable, while the asynchronous API requires the main loop to be replaced by pulseaudio's, which would need quite large changes in the design of darkplaces. If anyone manages to do this, the patch may get applied, but until then DP will support ALSA and OSS only.

Also, we cannot make pulseaudio the default sound system of DP until it is in ALL distributions, as there can be only one compiled in sound system.

Hmmm... I think ALSA can talk to Pulseaudio.

http://hg-mirror.alsa-project.org/alsa- ... ADME-pulse

This mostly looks like a configuration-challenge, not an API challenge.

Feel free to correct me.

Alsa has own mixer, no need for another loop:
alsa -> pulseaudio-> alsa.
Just because pulseaudio replaces esd and esd is used in gnome, no need to push another sound processing layer. What's wrong with sticking with alsa? Why not any other api like phonon?

I bash Ubuntu not without reason. In version 7 whatever it's name is, Ubuntu made old versions of radeon graphic cards useless, because it has upgraded to the newer Xorg and ATI drivers didn't work with it because of hardcoded version name. What do they expect? That average Joe knows that he needs to hexedit the driver to get it working.

Well, apparently it is not set up that way in Ubuntu, but should be by default to make the transition easy. If that method works, it clearly is a Ubuntu bug and not Pulseaudio stupidity then

Alien wrote:Alsa has own mixer, no need for another loop:
alsa -> pulseaudio-> alsa.
Just because pulseaudio replaces esd and esd is used in gnome, no need to push another sound processing layer. What's wrong with sticking with alsa? Why not any other api like phonon?

ALSA is two parts: The library and the hardware drivers. What's wrong with libalsa -> pulseaudio -> hardware-driver?

At least Pulseaudio is not just Linux-only like ALSA, so in my book ALSA perhaps was a great step forwards when it comes to drivers, but not so great an API for applications to use.

Alien wrote:I bash Ubuntu not without reason. In version 7 whatever it's name is, Ubuntu made old versions of radeon graphic cards useless, because it has upgraded to the newer Xorg and ATI drivers didn't work with it because of hardcoded version name. What do they expect? That average Joe knows that he needs to hexedit the driver to get it working.

Version 7? Do you refer to the current version, which is 8.10 and *did* ship with a pretty new X? That one ships with a fitting fglrx in the repository - or is actually the Xorg "radeon" driver broken? In the latter case I'd soundly say "ooops, but shit happens" and I assume a fixed package would be pushed via updates. (writing this on an Ubuntu 8.10 system with Radeon 9x00-something with free drivers. At home: Ubuntu 8.10 Radeon 3850 with fglrx. All up and fine - this of course and sadly doesn't mean things are as smooth for other people)

If the proprietary drivers from Nvidia/ATI break - well, I guess this merely demonstrates how weak the driver support from those parties is. It's not like new X releases suddenly fall from the sky, but still Nvidia/ATI seem to need a couple of releases to catch on.

Again, Fedora had the same problem. They're even more cutting-edge than Ubuntu.

OSS is also not linux only, but it was thrown away.
Adding additional layers increases sound latency.
Ok, the main alsa criticism is its api. But it's better to fix the api then to write another layer on top of that. Do you really think that macos (coreaudio) and windows (dsound/coreaudio(meh)) will use pulseaudio instead? Each OS has it's own API and that's ok.

7 version of Ubuntu is v7.0 and might have been called hardy, iirc. The problem was not ATI/Nvidia in that case. The problem was that older ATI drivers for older cards didn't work with newer X cause ATI stopped the drivers development for older cards. So instead of testing whether that X works with all cards, Ubuntu team pushed the release and left some of their users with crashing X if they installed "tested" proprietary drivers from Ubuntu rep. And because Ubuntu is meant for new linux users, do you really expect that they would know what to do with crashing X except reinstalling windows?

pulseaudio indeed cannot be used with darkplaces when using the ALSA pulseaudio layer. No idea why, it is working fine with mplayer.

Ah, the cause is fixed now. Someone in the ALSA team did something very weird in the "pulse" plugin. Please try a current engine compile and report if it works by default in ubuntu now.

Alien wrote:OSS is also not linux only, but it was thrown away.
Adding additional layers increases sound latency.
Ok, the main alsa criticism is its api. But it's better to fix the api then to write another layer on top of that. Do you really think that macos (coreaudio) and windows (dsound/coreaudio(meh)) will use pulseaudio instead? Each OS has it's own API and that's ok.

Pulseaudio isn't a layer on top of ALSA (the API) but a layer over the hardware driver. ALSA (the API) directly supports using Pulseaudio (not the other way round).

I was more thinking of Solaris and BSD. Those have mostly OSS and Pulseaudio available and not ALSA. This basically means that one has to support OSS anyway to have cross-platform support, making it weird that Linux has its own seperate API.

Alien wrote:7 version of Ubuntu is v7.0 and might have been called hardy, iirc. The problem was not ATI/Nvidia in that case. The problem was that older ATI drivers for older cards didn't work with newer X cause ATI stopped the drivers development for older cards. So instead of testing whether that X works with all cards, Ubuntu team pushed the release and left some of their users with crashing X if they installed "tested" proprietary drivers from Ubuntu rep. And because Ubuntu is meant for new linux users, do you really expect that they would know what to do with crashing X except reinstalling windows?

You are saying that it's not ATI/Nvidia's fault but write "cause ATI stopped the drivers development for older cards." The reasoning behind them (=ATI) stopping fglrx-development was that there are open-source drivers available already (with 3D support), so why not let user use those free drivers?

ATI stopped support for the older cards, some setups broke. This was ATI's decision. Perhaps Ubuntu could have had some logic inside "aha, this is an old card and it's trying to use fglrx - so lets force it down to the Xorg radeon driver instead" - that would have been a nice neato. However, forever shipping an old Xorg is simply not an option. Again, I don't see where Ubuntu made a "dumb" decision, even if the transition could have been more smooth.

Dumb decision was providing unpatched drivers.