On 8 June 2016 at 17:13, Jim Lesurf <jcgl@audiomisc.co.uk> wrote:
In article
<CAOnWdogzYmCLi2FN2NfTtp54EwNe8H00V4HMwQEkUbMnZaH3HA@mail.gmail.com>,
Reuben Thomas <rrt@sc3d.org> wrote:
> Using rpcemu 0.8.14, emulating an SA-RPC running RISC OS 3.71, I notice
> that pulseaudio is running with a constant appreciable load (~20% of a
> core on my machine), which stops when I quit rpcemu.
> This would be less than ideal even if I had sound switched on, but it's
> off!
I can't advise on the reasons why the above occurs. TBH one of the first
things I do with any new Linux install is to try and beat Pulseaudio to
death with a big stick as I find it a real PITA! If I can't kill it, I do
what I can to isolate and bypass it.
I had trouble with Pulseaudio the first time I tried using it, but for years now it has been stable and reliable out of the box, and provides functionality (such as audio I/O sharing between apps and per-app volume controls) unmatched by ALSA, along with non-mind-numbing configuration (which I hardly ever have to use). I can't speak for those who are doing live sound processing, where low-level considerations may apply.
I suspect the bug here is in some Allegro/Pulseaudio interaction, though obviously it could still be in rpcemu. As it happens, sparing ⅛ of ¼ of my cores while running rpcemu isn't a big deal, but if this isn't a known bug I guess I should file one.
No comments:
Post a Comment