10% cpu usage by pulseaudio when a UI is loaded

[hamoid]

Hi! I see a 10% CPU usage when loading a page with the Nexus UI. I can also hear the soundcard being activated and deactivated (a small click) when opening and closing such a web page.

Why is that the case? Is the audiocontext used for timing? Would it be possible to have an alternative method? Or maybe only activate it when using the sequencer? I'm just using a bunch of knobs, so no need for timing...

If I play an mp3 in cmus the CPU usage is around 0%. If I play audio on a web page the CPU usage is about 2%. Is maybe Nexus UI using a very tiny buffer that produces a high CPU usage?

[taylorbf]

This is the second request for a way to use NexusUI that does not rely on the web audio context. It's a good point.

A context really is necessary for part of the library and for timing, however it seems like it would be ideal to design the library so that a web audio context is created only if an interface necessitates it -- i.e. an interval, a sequencer, or an audio analyzer. This should be possible with a little extra logic. I will take a look at this as soon as I can.

[taylorbf]

That said, it is also possible that other elements of the library are creating the spike in CPU usage. When a NexusUI page loads, it can create a great number of SVG elements, depending on the interface. However it sounds like your interface should not involve any heavy processing and it very well may be the audio context.