Back

Added quite a number of things into the compositor since then. It's at the point where I can somewhat-comfortably use it for working or (Wayland-only) gaming sessions.

Today I figured out how to make it run as a proper session, launched from GDM, with systemd integration and all. It even mostly works!

Also finally implemented the ability to take screenshots—this one is from a real session.

Kinda want to try my hand at the screencast portal for OBS. How hard can it be, right?

Almost done adding touchpad gesture support to Smithay!

Here you can see the pinch zoom/rotate gesture visually in gtk4-demo, then the swipe gesture only in WAYLAND_DEBUG on the right, then the hold gesture by stopping the kinetic scrolling by putting a finger on the touchpad.

After adding dmabuf feedbacks to niri, I stumbled upon an extremely strange performance problem when using overlay planes. One specific animation, with a GTK 4 window open, stutters, but only when going into one direction.

Spent half a day debugging it with Smithay developers. Couldn't crack it yet; for some reason an AMDGPU kernel worker just... takes a while under those specific conditions, causing delayed frames. Seems to be doing the same thing as in the normal case, just... slower somehow.

Aaand my touchpad gesture support has been merged into Smithay!

I'm quite enjoying playing with the Tracy profiler. Turns out when you run the program with sudo, it records a ton of extra useful info, like CPU core scheduling, monitor VSync events, kernel context switches, what your process is blocked on.

I also annotated my compositor with Tracy Frame events for monitor VBlank cycles. I can then set a target FPS in Tracy and instantly see which frames were too slow! Both in the bar at the top, and in the main area highlighted in red.

lol a few days ago someone posted niri on the orange site and now it surpassed all my other projects by star count

aaaaaaaaahhhhhhhhhhh these two days were a grind but I somehow got monitor streaming working! with pipewire and dmabufs and dbus and screencast portal and everything! and it wooorkssssssssss woooooooooooooo

I just streamed for an hour from this and nothing crashed??

Dmabuf screencasting is crazy good. Here's a histogram of the screencasting overhead on my 2560×1600@165 screen—the median is 300 microseconds, and the worst across 12,669 frames was just below 1 ms. Most of that time is spent rendering the frame, perhaps something could even be further optimized in Smithay.

And yeah, if you look at the profiling timeline, I zoomed it in such a way that almost the entire width is taken by one frame, that is 6.05 ms long. Most of it is completely empty!

Today in Wayland compositor profiling! Turns out closing a shm pool file descriptor can result in a fat stall of up to like 6 ms with the kernel waiting on some spinlocks. Which is extra fun when you realize it covers the entire frame budget of your 165 Hz screen, and some clients are sometimes doing it every frame!

I'm trying a "dropping thread" workaround where the fd closing happens on a separate thread. Appears to work at the first glance.

new main loop stall dropped

and it is, uhhhhh, epoll_wait doing blocking disk decryption for solid 8 ms? is that a thing that it does?

seems to have happened once over a long period but still

Found the same disc decryption during rendering. Does it just randomly decide to do it or something?

Aside from this and some other weirdness, not a single dropped frame on my slower laptop! (which is admittedly just 60 Hz)

Thought of another thing to plot in Tracy: target presentation time offset! This is the difference between when a frame was shown on screen and the target time that we were rendering for.

Here you can see data across 17 seconds of runtime while recording with OBS. Offset on both monitors fluctuates within a few microseconds around zero, which means that our rendering lands right on time.

It's also common to see one frame worth of offset like on this zoomed-out screenshot. This happens when the compositor wakes up from idling too late into the monitor refresh cycle and doesn't manage to render a new frame in time.

I'm still working on niri btw (and using it myself too). Today I finally finished a window layout refactor that was due from very early on.

Now the layout always works correctly, with all the paddings, struts, fullscreen windows and animations. It's tricky because while most of the logic operates only on the "working area" (view excluding struts), fullscreen windows in particular must cover the entire view area, while otherwise acting as just another regular window column.

niri development is ongoing, getting a lot of help from kchibisov too.

Today I implemented an interactive area screenshot capture tool. Almost like a mini screenshot UI

Decided to make a new demo video for niri, finally. The last one was so old that niri didn't even have cursors implemented, it showed an orange rectangle instead.

Here's the link again for the curious: https://github.com/YaLTeR/niri

Very happy I've come this far writing my own compositor from scratch. Honestly thought my motivation would only last for two weeks max, but here we are.

Learned a ton in the process, and now this experience helps me with Mutter & Shell profiling.

The development pace had slowed down a little, so I've tagged an alpha release for niri: https://github.com/YaLTeR/niri/releases/tag/v0.1.0-alpha.1

Also made a COPR for the occasion, if you're on Fedora: https://copr.fedorainfracloud.org/coprs/yalter/niri/

A month has passed and a number of important additions have landed in niri, so here's a second alpha release: https://github.com/YaLTeR/niri/releases/tag/v0.1.0-alpha.2

Highlights include relative-pointer and pointer-constraints which let Xwayland masterfully handle 3D games mouse look, and popup unconstraining which prevents popups from opening off-screen. I actually made popups place within their window with some padding, which looks quite nice.

Aaahhhhhh another difficult refactor down and niri now does multi-GPU! By which I mean that monitors plugged into secondary GPUs will now light up and work. All the screenshot UI and screencast portal stuff also works just fine. Wouldn't be able to do this as quickly without Smithay's MultiRenderer support and lots of help from @drakulix

I went for the easier strat of always rendering on the primary GPU, but you can also pick render GPU dynamically, which apparently cosmic-comp does, cool!

Tagged niri v0.1.0-alpha.3 with multi-GPU support, borders and other improvements! Multi-GPU was one of the bigger things I wanted to get done before going out of alpha so I guess I'm slowly getting there.

https://github.com/YaLTeR/niri/releases/tag/v0.1.0-alpha.3

Turns out that if you implement xdg-decoration in your compositor but tell clients that you want CSD, then SDL2 + libdecor clients will break due to a bug. The bug is already fixed, but the fix hasn't made it to any SDL2 release yet, let alone all the runtimes and vendored copies.

Hiding xdg-decoration from clients it is then

I added text rendering to niri using pangocairo, which turned out to be surprisingly simple. It basically "just worked". This unlocks a lot of features, beginning with a hotkey overlay, which should help people get started (suggested by @ju).

I've tagged niri 0.1.0-beta.1 which includes the overlay along with many more improvements: https://github.com/YaLTeR/niri/releases/tag/v0.1.0-beta.1

I'm now happy enough with the feature set so in a week I'll release 0.1.0. Time to finally catch up on other projects I've been neglecting.

I'm pretty excited to finally be able to "release" niri soon but god I'm glad I set aside a beta week for bugfixes. We already stumbled upon and fixed several issues

A few latency tests before release confirm that niri's still doing good (at least on idle; I don't have any repaint scheduling yet but on idle it doesn't matter). The compositors are pretty much within the noise threshold from each other. Except some sway fullscreen bug and Shell losing one frame somewhere.

Well, I'm happy to release the first stable version of niri, my scrollable-tiling compositor: https://github.com/YaLTeR/niri/releases/tag/v0.1.0

Very satisfied with the current state, even though there's plenty left to do. Took a lot of time and work but I've certainly learned a lot, and I'm glad to have contributed a bit to Smithay too!

Before adding more animations into niri, I'm making a "visual tests" application. It shows a set of hardcoded scenarios which I can quickly go through and visually check that everything looks right.

It uses solid color rectangles as "windows", but otherwise this is the real niri layout code and real niri + Smithay rendering code, drawing to a GTK GL area.

For example, on the last test you can see that my offscreen code currently clips CSD shadows (during the open animation).

visual tests are such a lifesaver, so glad I stole that idea from osu!lazer

The window opening animation is now live as part of niri v0.1.2: https://github.com/YaLTeR/niri/releases/tag/v0.1.2

I'm really looking forward to more animations, but wow they sure do need a lot of care to get right in all the edge cases.

Also, I added a way to programmatically invoke compositor actions, and turns out that's quite useful for making video demos!

For a bit of fun I added gradient borders to niri. One of the visual tests for it turned out a bit mesmerizing to look at

Tagged niri v0.1.3: https://github.com/YaLTeR/niri/releases/tag/v0.1.3

This one has much improved touchpad gestures with inertia, springs, rubberbanding and everything else I copied from libadwaita, my primary source for things that feel good

Also thanks @alice for helping and giving feedback on the gestures and for giving a try to the touch support!

Just implemented something I've had in mind for a while: compositor-side blocking out of windows from screencasts! The compositor is the perfect place to do this since it can replace the window contents in the render tree, which will work fine with any kind of overlapping, transparency, etc. AND it will work with anything that records the screen through the portal, be it OBS or video meeting, or whatever.

There's actually an important edge case here: if you open the screenshot UI while recording the monitor, then the screenshot UI preview will show the window, and OBS, recording the screenshot UI preview, will hence also show the window. There are trade-offs here for how you want this to work; for now I put a big warning around the option, and added a stricter mode that blocks out the window from ANY screen capture (which means you can't screenshot it).

I think for the built-in screenshot UI this is solvable with one more layer of indirection (render the screenshot UI preview itself twice, once for screencasts, and once for the monitor). However, for third-party screenshot annotation tools, this will still be a problem.

Implemented this idea. It means rendering each monitor 3 times always for the screenshot but maybe it's fine? On this laptop 3 monitors × 3 renders takes 2 ms, and there's some unnecessary blocking I forgot to remove.

On the video, note how for me the screenshot UI has Secrets visible, but on the recording afterwards it's always blocked out.

Amidst all the fires being put out, niri 0.1.4 which can block out windows from screencasts! https://github.com/YaLTeR/niri/releases/tag/v0.1.4

And also gamma control, focus follows mouse, warp mouse to focus, wheel and touchpad scroll bindings, xdp-gnome 46 support.

Also, every single config option is now documented on the wiki! Which took like an entire week of work (even though I was reusing a lot of my previously written docs in the config). Check it out here: https://github.com/YaLTeR/niri/wiki/Configuration:-Overview

Today: horizontal column movement is now animated!

Took the whole yesterday and a bit of today, but I've got window closing animations working! These turned out to be tricky because they need storing a snapshot of the surface render tree to draw once the app is gone.

Some apps may start destroying their subsurfaces before the main surface, like alacritty with its sctk CSD, making it very easy to miss parts of the window in the snapshot, and therefore in the closing animation.

Also, windows closing to the left no longer shift the view!

..i can't even enjoy these properly because my brain already stopped noticing them since now things act *as they should* (and also the settings are as usual copied from gnome shell)

I have this monitor connected through HDMI, and if I enable VRR then it starts modesetting every frame (lol). Guessing some AMDGPU issue.

But today I finally found a DisplayPort → USB C dongle, and this way VRR works perfectly, yay! Even bumped the refresh rate from 144 Hz to 170 Hz, which this monitor supports only through DP.

Anyway, #niri has VRR now

I also have smoother magic trackpad gestures now since it reports at 100 Hz, and before I had to deal with framerate aliasing. Too bad I don't use it much because mouse more convenient

All the animations, plus VRR, today in niri 0.1.5: https://github.com/YaLTeR/niri/releases/tag/v0.1.5

I also remade the demo video to showcase the animations and some of the newer features!

We've reached 1000 commits with an a bit of an anticlimactic one though

@huilong

> please make dialogs and popups float

There's no floating layer yet, I have an issue at https://github.com/YaLTeR/niri/issues/122

> it takes over thirty minutes to compile niri

Uh oh, which system is that?

> please provide precompiled niri bin

Fedora COPR is pre-compiled, there's also an AUR niri-bin package. I can't really provide a distro-independent one.

@YaLTeR im on #voidlinux . maybe because of 4gb ram.but it is much faster to build #Hyprland , #labwc, #SwayFX and #waybar etc..

@huilong 30 min must be a clean build? Recompiling after changes should be much faster

@YaLTeR you are right. clean built 0.1.2 and then 0.1.3.

@YaLTeR AMD PRO A4-4350B R4 5 COMPUTE CORES 2C+3G

@rmader why would it be a bug? Also, it's destroying the surfaces, there are no commits involved. All in one go; just that the subsurface destroy messages arrive first, so if you don't snapshot at that point, then by the time the toplevel surface is destroyed, there already is no subsurfaces to render.

@rmader fwiw in Mutter it looks fine, but I haven't looked deep into what exactly Mutter is doing to solve this.

@YaLTeR "Destroying a sub-surface takes effect immediately.", see https://wayland.freedesktop.org/docs/html/apa.html#protocol-spec-wl_subsurface

If a client wants to ensure the content gets destroyed in sync it shouldn't start with destroying a subsurface as compositors may schedule a frame directly after that step. Depending on the architecture, it would be good if the client unmapped (by attaching a NULL buffer) or destroyed the toplevel first (no need to wait for anything after either of these steps).

@rmader yeah, I see, that makes sense

@rmader it's getting fixed in winit: https://github.com/rust-windowing/winit/pull/3625

@nano looks even better at 144 Hz

@su quite real and usable :)

@YaLTeR im gonna try it out on my laptop

@tbernard hmm, the pill backgrounds give some weight to the area. Otherwise it looks even more like empty space that uncenters the windows

@YaLTeR Not sure, I think the bigger factor there is that the padding around the windows is so tight in comparison to the height of the top bar. Increasing the outer padding a bit might help with that.

@tbernard @YaLTeR Well, besides the fullcolor icons

@tbernard There's no way to adjust the top margin specifically AFAIK but I may be wrong? @YaLTeR

@kramo @tbernard you can increase it with https://github.com/YaLTeR/niri/wiki/Configuration:-Layout#struts and decrease in the Waybar config

@YaLTeR @tbernard Ah, I didn't notice struts, thanks

@CleoMenezesJr but Mutter already does a crossfade on keyboard resize? I.e. Super+Left/Right/Up. Should be pretty similar to what I've got

@etrigan63 you still need to use rootful, same as before

@YaLTeR it was cage, last time I tried.

@etrigan63 we have instructions on the wiki: https://github.com/YaLTeR/niri/wiki/Xwayland