"ALSA is useless" "HW mixing fixes that" "HW mixing is useless" Wat?!
You posed a problem. A solution was offered. You rejected it without justification.
Also, the dmix buffer size can be adjusted.
Printable View
"ALSA is useless" "HW mixing fixes that" "HW mixing is useless" Wat?!
You posed a problem. A solution was offered. You rejected it without justification.
Also, the dmix buffer size can be adjusted.
Where exactly did you see "ALSA is useless" being said?
Justification was given. If you want more: this "solution" requires me to buy a new sound card. I already have one for which I paid good money for. If that's what it would take for gaming on Linux, no thanks. I'll keep using Windows for this, since it works awesome there without hardware mixing (which just proves how useless it is).Quote:
You posed a problem. A solution was offered. You rejected it without justification.
Is there a "defaults.pcm.dmix.*" option for this? I'd like to try it and see whether audio skipping becomes a problem with smaller buffers.Quote:
Also, the dmix buffer size can be adjusted.
+1
Gaming software always has a very high CPU usage.
For software mixing problem, high CPU load always means bad latency for software mixing solution.
Having a dedicated hardware for sound mixing is always a good idea.
Take a look on Windows:
Windows XP: hardware mixing
Windows 7: change to software mixing which cause serious latency problem http://www.youtube.com/watch?v=iujDVsg_2xY
Windows 8: http://msdn.microsoft.com/en-us/libr.../br259116.aspx they realize their mistake and go back to hardware mixing again :p
I wonder those PA developers will follow the stupid Microsoft again?:mad:
Mixing can run at high priority. Load doesn't affect it much.
No, it's not.Quote:
Having a dedicated hardware for sound mixing is always a good idea.
That happens when you try to monitor the output from the card; it raises latency.Quote:
Take a look on Windows:
Windows XP: hardware mixing
Windows 7: change to software mixing which cause serious latency problem http://www.youtube.com/watch?v=iujDVsg_2xY
Hi,
I'm the author of the current SDL pulse-audio backend (not the original author, but I rewrote it to fix several issues with the original), see:
http://hg.libsdl.org/SDL/rev/5b99971a27b4
The numbers posted in this article seem completely made up to me. In my experience (back when I was working on this), When using SDL
based games (I did most of my testing with ioquake3) one could set the latency lower when using the pulse-audio backend then when
using the alsa backend (with pulseaudio disabled of course). This is due to pulseaudio using high res timers to schedule sending data
to the cards buffers rather then relying on the often somewhat "crude" (wrt granularity) interrupts from the soundcard.
Now if you look at the patch you will notice it is using the new (back in 2009) PA_STREAM_ADJUST_LATENCY flag, if their testing did
not include this flag, and instead was relying on pulseaudio's defaults, or if they were going something -> alsa -> alsa-plugin-pulseaudio
rather then directly talking to pulse, then yes 25 ms makes a lot of sense. But then they have just been doing it wrong.
Back in 2009 I good get excellent latencies using SDL with its pulse-audio backend, provided the game *actually asked* SDL for such a
low latency ...
Regards,
Hans
If running at high priority can solve the problem, then ubuntu developer will not "Desires" Lower Audio Latency For Gaming.
and this post will not exist at all.:p
Besides, software mixing running at high priority will probably preempt the game unexpectedly. The "jitter" will be transferred from the sound to the game - network packet drop, video frame skipping.
Why don't you try to watch a HD movie when your CPU is under full load by low priority programs? Is the movie still ok?
If linux kernel's scheduler is good at realtime, you should not be affected, right?
Try to archive low latency with cheap card+user level software mixing is very difficult. There is no free lunch.
The miserable history of linux audio proves that kernel mixing/hardware mixing are superior solution (low cpu usage and good latency)
try googling yourself about Windows 7 audio latency, this is not the only post
you are talking about OSS. With ALSA multiple programs can access the sound card.
I never understood that soundserver idea anyway. You've to configure more for the same solution. Softwaredevelopers have to code more and add special cases for every friggin soundserver. And to top it off, you get 0 advantage from it over direct ALSA. Nada. In fact, you now have a high latency aswell. Well done.
Also, now you can't even remove PulseAudio anymore without losing the sound control in Ubuntu anymore. (alsamixer is nice, but you always need to open a terminal for it, instead of just using a slider in the top menu bar like it should be)
And you introduced another level of error into the system.
Isn't Klang supposed to fix the latency issue?
http://www.phoronix.com/scan.php?pag...tem&px=MTE1MDc
And loose all the benefits of PulseAudio? I don't get why people still hate PA, it's a great bit of software that does really cool stuff - it's perfect for gamers. Sure, it could do with some latency reduction, apparently, but that doesn't mean it's bad as a thing to have. PA can do stuff like assign certain audio streams to certain output devices really easily - for example, send chat to my headphones and game audio to my speakers - that is really useful for gamers.
You know sound is a considerable slower media than light. Your brain can't even tell apart single pictures if they are shown within 16ms, most people can't even at 40ms. If you have a really trained ear you'll be able to tell apart sounds with 10ms latency, but I doubt [b]you[/] are able to do so. Just remember 25ms is the latency of the sound from a piano standing 10m away from you. Can you really tell the latency between the pianist triggering the string and you hearing it?
Bringing down latency to the technical minimum is just a waste of energy for the sake of some retards that use the latency numbers as a kind of benchmark.