Anukari now has nice-looking and functional master output level meters and a GPU meter. The GPU meter is actually just a measurement of the % of the latency budget being consumed while processing each block, which I believe is the same as the Ableton CPU meter. Which makes sense, because that's the thing the user actually cares about, in terms of how much headroom they have.

The meters use an exponential weighted moving average for the main display bar, and show the instantaneous peak as a little line, which hangs around for 1s (again, much like Ableton or any other number of DAWs). And of course if there's clipping, you get a red bar.

One thing I realized that I still need to incorporate into the master out level meter is the function of the master limiter. I was trying to test the clipping indicator and was confused about why I couldn't trigger it, and then I facepalmed -- with a master brickwall limiter at -1 dBFS, you're never going to clip! But of course this just pushes the clipping problem upstream to the limiter. So I will have the master level show an orange bar if the signal is hitting the master limiter, and a red bar if it still manages to clip after that, which I think will work quite well.