xob is kinda broken after latest update

[ghost]

Hello to the developer of xob! I find your creation really useful, but the recent update has made it "misbehave".

Using the volume script on this repo and piping it to xob, on volume change I notice few artifacts and flashing throughout xob. Could this be an issue in my part? Let me know if there's a fix for this.

Thanks in advance!

[HolographicX]

I'm getting the same problem too

[florentc]

Hello,

I am sorry to hear about your issue.

The change in 0.3 that is most likely to trigger the issue is the switch to another rendering library by default: the xrender X library extension to handle transparency.

Unfortunately I have no idea for now as to what might be the reason. I am not personally running into this issue on 0.3. For the record, the compositor I use is picom with the following configuration in .config/picom.conf:

backend = "glx";
vsync = true;
shadow = false;
fading = false;

I suggest that you play around with the settings of your compositor or try to disable it temporarily to check if your are able to find a situation where the issue does not occur.

As a last resort you can compile xob without transparency support (see the build instruction). This will fallback on the old xlib only rendering just like in 0.2 and before.

I am of course leaving this open to other users' feedback and suggestions about the issue.

[jrvgr]

Hello,

I too am facing this issue but changing the Picom backend seems to make it worse

[cdown]

I'm experiencing this problem too, and bisected it to ff4911e.

Even compiling with enable_alpha=no does not improve things after this point -- the bar flickers uncontrollably on new input.

[florentc]

The commit you identified is based on some squashed commits from the original pull request for transparency. You may be able to narrow the search for the issue down by exploring those original commits here: https://github.com/florentc/xob/pull/19/commits