If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

What? Sorry, but low-latency server is JACK. Pulse is much more latent and high-latency & high perfomance vs low-latency vs low-perfomance are not related to Pulse. Its either faster reacting(but doing less work) and consuming more or slower reacting(and doing more work) and consuming less. Same reason why RT linux kernel is slower in server(ie constant load) environiment.

Pulse clicking is ubuntu issue.
If application uses a library to output the sound, gstreamer, sdl, openal, doesntmatter what. And this library is wrongly configured to output sound to ALSA. But Pulse is installed and alsa.conf points to pulse. This thing happens:
Some game>>libsdl>>alsa(reroutes to pulse)>>pulse>>alsa you hear clicky-noise

Where if that lib attaches itself to pulse correctly:
Some game>>libsdl>>pulse>>alsa

I have no clicks or anything with pulse. I also do not really care for ubuntu not doing their homework. Gentoo and PA perfect setup describes pretty much clearly how to link PA with libs, apps and soundsystems.

Didnt check on 70% issue, so I believe you. But again, not single desktop app working wrong with PA+Alsa up to date.

Not a single problem.
Of course this isnt major industrial-level testing and I cannot speak for PA as whole. However applications SHOULD use either libSDL or libopenAL or if they require more features gstreamer, xine or even managin whole sound pipeline themself by using alsa/oss and codecs/libs directly. This is however has issues. Because you required close-to-system calls, you should support it. Higher level libs do not offer the features which arent generic or cannot be emulated. But if you program this way, your app has pretty much in similar with DOS era. Writing your own drivers, mixer etc. You asked for it.

Of course there may be driver problems within ALSA. There may be problems within SDL and Pulse(especially in case I described above; just install SDL-pulse version only, not of all-in-one). But system is there, frameworks are there and they work!

Now dont tell me DirectX(Directsound, -music or however it is called now) is consequent and API and sound model was never changed
It did, devs pushed new versions, everything worked to some degree, then got broken again and again etc. I dont see how linux is "not ready" here. In fact linux is more ready than windows; you just put sound chip manufacturer publishing specs for new chips and game publishers updating their software(regardless foss or proprietary) and it works.