portaudio VS Waybar

Thank you. I actually already did and no bites. Did in a couple facebook groups and also no bites. Its a rather complex issue as it appears to be something on a code level. https://github.com/PortAudio/portaudio/issues/523

For sound, there's PortAudio for C and C++, and Windows, Mac, and Linux; FMOD comes in C++.

However, PyAudio depends on another library called portaudio, which is not part of the default Linux dependencies. To install it on your machine, you need to issue the following command on your terminal:

I am trying to build a portable sound synthesiser using the cross-platform library portaudio. The library has it's own CMake file to be built with. I think I have managed to build it as part of my project (build finishes with exit code 0) but I can't figure how to actually use it's imports. Any #include I try to use results in cannot open source file.

The bug fix will be included in the imminent PortAudio release: https://github.com/PortAudio/portaudio/pull/504

In my testing with Mixxx, PipeWire works better with the JACK API than PulseAudio. With PulseAudio I got frequent crackles with Mixxx using this PortAudio branch. Using PipeWire via the JACK API, I get the same performance at low latencies as JACK.

Here's a code example: https://github.com/PortAudio/portaudio/blob/master/examples/paex_saw.c

If I understand https://github.com/Alexays/Waybar/wiki/Configuration correctly, what is to be displayed is defined in a JSON file that can be located in one of the directories mentioned.

GNU calls their extensions "equivalent to" things I'd have suggested trying ($_I or $-l), but I'm not sure if the equivalents are themselves GNU extensions, too. Regardless, reading this Waybar Github issue about %OI, I get the impression there was a regression at some point, in any case on March 27th 2022 someone says it "used to work fine until recently".

hope it helps. source btw: https://github.com/Alexays/Waybar/issues/2177

{ config, pkgs, ... }: { wayland.windowManager.sway = let patchedWaybar = pkgs.waybar.overrideAttrs(prev: final: { patches = [ (pkgs.fetchpatch { url = "https://github.com/Alexays/Waybar/pull/2134.diff"; sha256 = "1hzdv3b8zzps50pdcb8pj9cxwaix4q2d4gsqb9dl9vflgl429hq3"; }) ]; }); in { enable = true; config.bars = [{ statusCommand = "${patchedWaybar}/bin/waybar"; }]; };

See this issue. CSS and only new properties in config are reloaded when SIGUSR2 is triggered.

I think this has just been added to waybar (wlr/workspaces) to work in a similar manner to how it is in sway/workspaces. No need for fake empty terminals. Something was merged for wwlr/workspaces in the waybar github. See - https://github.com/Alexays/Waybar/pull/2089.

Ah, well in looking at their git, it appears some do have fallback font issues. See here - https://github.com/Alexays/Waybar/issues/215