The features shown off in theis video are available in the main picom repo but you'll have to build the latest commits of the repo not the master branch
The old blur kernel that comes default with predefined `NxNbox/gaussian` is way too sharp. Even with 11x11, the weight matrix mainly focuses on the center 3x3 pixels, which is basically no blur at all. I managed to get the blur with kernel generated with the compton-convgen.py script and it worked.
hey, great video! btw as you metioned in the end, picom already offers the rounded edges feture. What i normaly do if i want to use that is set biger borders, so it doesnt eat part of my applications
do you happen, or could you please PLEASE make a tutorial on getting picom installed with qtile? I've followed everything but i cannot seem to get it installed and or running even using the aur. I'm about 8 days in on this and it's driving me nuts. thank you!
I'd advise against doing transparency like this. Picom will make the window and all its contents transparent. This makes reading the text in your terminal a bit harder and imo it looks worse. Most terminal emulators support background transparency. E.g. with alacritty you can set "background_opacity: 0.85" in the config and only the background will be transparent (and blurred), with URxvt you have to set the alpha of the background color by adding percentage opacity in brackets before the color code "[85]#242D54". I'm not sure about kitty or st, the latter probably has a patch for this.
whenever i try to run picom, i always get an error like this: [ (time and date) parse_config_libconfig FATAL ERROR ] Invalid blur method dual_kawase how do i fix this?
My advice? Ditch I3, sway, and bspwm and use KDE Plasma with kohnkite. Sway hates nvidia, and picom is way too unstable. The kwin compositor is super fast, stable, has awesome blur, transparancy and other effects. Krohkite + plasma keybinds let you do all the important tiling functions.
I tried using GLX weeks ago but it was causing weird flickering issues with my Nvidia 1060 card so had to switch to Xrender which worked fine it might of been because the Linux and Nvidia incompatibly issues several weeks ago Arch reported.
If you're using Intel integrated graphics, you typically want xrender backend because it requires less processing power from your GPU and intel integrated graphics is not the fastest thing in the town.
I am kind of new to Linux. What is that program that lets you navigate the filesystem graphically in the terminal? You typed 'lf' to open it. It looks really useful :D
@@BrodieRobertson Ah, thank you very much. I thought it was soe kind of macro with how short the name was. Must say, your videos are really informative and to the point
Sway is a tiling Wayland compositor and a drop-in replacement for the i3 window manager for X11. Display servers using the Wayland protocol are called compositors because they also act as compositing window managers. From swaywm.org and archwiki. But yes. It is a window manager.
Hi all i'm new , I installed Picom two days ago but using dual_kawase it says me that this is not supported. So i read i have to build the last commit of the repo. Can someone please explain me how to do that? I have to build all by myself or can i just copy the compiled files?
glx does not work for me on nvidia. I get multiple seconds long delay on every action I do, its unusable with glx. Currently using xrender. If anyone can give me a hint what to do, I would be more than happy. When I was on KDE Plasma, glx worked fine, so I don't know what the issue is here.
Please mention the version you are using next time. I was wondering, why blur didn't work for me, even though I had the latest version installed. Turns out, blur was added after the last release.
could you upload your config to your github please? just tried it and i cant get it to work with glx as backend. id love to use picom instead of open gl because then i could blur rofi and possibly wouldnt have the blur sticking out of rounded corners like i have it now (awesome wm on kde backend).
Maybe it is time suckless.org makes its own fork of picom and move all of the configuration inside config.h. Only marginally tongue in cheek. By the way, thank you for this type of video.
After seeing all these videos about picom and the trivially different forks that fall behind master... Screw that nonsense, just install picom main. Talk about trial and error.
@@mentalpatient2324 Compositors aren't just for transparency, so I'm not against them. It's annoying to read text where the transparency makes it ambiguous.
The features shown off in theis video are available in the main picom repo but you'll have to build the latest commits of the repo not the master branch
My screen gets blurred after a few shots of cheap whiskey. I don't even need a compositor for that.
You've got to optimize your solution, get yourself some cheap boxed wine
@@BrodieRobertson that would be an upgrade 🤣
Clearly you're not Irish or Russian. We have to drink just to see clearly.
@@Bagginsess We just drink to forget we're a prison colony
@@BrodieRobertson I'll toast to that laddy!
I wish all linux tutorials were like this, subbed
Zoomer: "Everything looks better with picom blur"
Boomer: "Hold my camera lens and vaseline"
😂😂😂😂
Now we only have for the rounded corners, because the fork has a lot of performance issues for me
The old blur kernel that comes default with predefined `NxNbox/gaussian` is way too sharp. Even with 11x11, the weight matrix mainly focuses on the center 3x3 pixels, which is basically no blur at all. I managed to get the blur with kernel generated with the compton-convgen.py script and it worked.
It's broken, can you update the link?
hey, great video! btw as you metioned in the end, picom already offers the rounded edges feture. What i normaly do if i want to use that is set biger borders, so it doesnt eat part of my applications
do you happen, or could you please PLEASE make a tutorial on getting picom installed with qtile? I've followed everything but i cannot seem to get it installed and or running even using the aur. I'm about 8 days in on this and it's driving me nuts. thank you!
I'd advise against doing transparency like this. Picom will make the window and all its contents transparent. This makes reading the text in your terminal a bit harder and imo it looks worse. Most terminal emulators support background transparency. E.g. with alacritty you can set "background_opacity: 0.85" in the config and only the background will be transparent (and blurred), with URxvt you have to set the alpha of the background color by adding percentage opacity in brackets before the color code "[85]#242D54". I'm not sure about kitty or st, the latter probably has a patch for this.
That's why I Iike running high contrast themes but in a lot of situations like browsers it's a mess
@@BrodieRobertson yeah... maybe I should also consider giving up on my use pywal everywhere mission
How about blurring everything in background and let the foreground window be focused. Is that possible?
whenever i try to run picom, i always get an error like this:
[ (time and date) parse_config_libconfig FATAL ERROR ] Invalid blur method dual_kawase
how do i fix this?
Does picom work properly in virtual box ..? Or it only works fine on physical machine..,
for some reason my config file doesn't look at all like yours
can you share that wallpaper?
This is why I haven't switched to Sway yet. It doesn't have any nice effects like this.
I'm sure I've heard someone talk about something similiar for Wayland
My advice? Ditch I3, sway, and bspwm and use KDE Plasma with kohnkite. Sway hates nvidia, and picom is way too unstable. The kwin compositor is super fast, stable, has awesome blur, transparancy and other effects. Krohkite + plasma keybinds let you do all the important tiling functions.
If it works for you that's awesome
I tried using GLX weeks ago but it was causing weird flickering issues with my Nvidia 1060 card so had to switch to Xrender which worked fine it might of been because the Linux and Nvidia incompatibly issues several weeks ago Arch reported.
I have issues going glx on my Nvidia 1070 too. But on KDE Plasma on same installation does work perfectly fine. BTW, I use Manjaro.
If you're using Intel integrated graphics, you typically want xrender backend because it requires less processing power from your GPU and intel integrated graphics is not the fastest thing in the town.
I am kind of new to Linux. What is that program that lets you navigate the filesystem graphically in the terminal? You typed 'lf' to open it. It looks really useful :D
If you search for gokcehan/lf you'll find the Github page
@@BrodieRobertson Ah, thank you very much. I thought it was soe kind of macro with how short the name was. Must say, your videos are really informative and to the point
I want blur effects on sway (Wayland compositor). Is there a way to get it?
I thought sway was a window manager, not a compositor?
Sway is a tiling Wayland compositor and a drop-in replacement for the i3 window manager for X11. Display servers using the Wayland protocol are called compositors because they also act as compositing window managers. From swaywm.org and archwiki. But yes. It is a window manager.
Hi all i'm new , I installed Picom two days ago but using dual_kawase it says me that this is not supported. So i read i have to build the last commit of the repo. Can someone please explain me how to do that? I have to build all by myself or can i just copy the compiled files?
what is file manager name ?
How i can set i3wm on 60 Hz or 60 FPS
glx does not work for me on nvidia. I get multiple seconds long delay on every action I do, its unusable with glx. Currently using xrender. If anyone can give me a hint what to do, I would be more than happy.
When I was on KDE Plasma, glx worked fine, so I don't know what the issue is here.
Please mention the version you are using next time. I was wondering, why blur didn't work for me, even though I had the latest version installed. Turns out, blur was added after the last release.
That's a fair point, it's in the latest version of the code base but hasn't made it to master just yet
could you upload your config to your github please? just tried it and i cant get it to work with glx as backend. id love to use picom instead of open gl because then i could blur rofi and possibly wouldnt have the blur sticking out of rounded corners like i have it now (awesome wm on kde backend).
I've added the lastest version to github, it's still named compton.conf
@@BrodieRobertson thx. dont have much hope, but ill give it a shot
One question: does anyone know how should rounded window work well with window borders (the corners of the border will be cut off)?
They will be cut off. They'd have to be implemented at the wm-level for it to be otherwise.
Is this in master? I had a hard time getting it to work. I had to manually build the next branch for this to work?
It'll be in master soon
thank youu 😍
Maybe it is time suckless.org makes its own fork of picom and move all of the configuration inside config.h. Only marginally tongue in cheek. By the way, thank you for this type of video.
thanks a lot !
After seeing all these videos about picom and the trivially different forks that fall behind master... Screw that nonsense, just install picom main. Talk about trial and error.
IMHO blur is just a waste of brain cycles.
I've got plenty of those to spare
@@mentalpatient2324 But they look cool
@@mentalpatient2324 Compositors aren't just for transparency, so I'm not against them. It's annoying to read text where the transparency makes it ambiguous.