Sebastian Krzyszkowiak @dos@librem.one

@pavel @datenwolf @dcz @martijnbraam @NekoCWD Both, including chromatic shading. They're not that bad in still photos, but I find them very distracting when in movement.

I've got a song for you, but you'll have to translate it yourself 😁 https://www.youtube.com/watch?v=FdIid5IJEds

I'm relying on kernel changes, so I need to put everything in place first. It also took some time for me to get reasonably confident that what I'm doing is correct. I'm pretty much done though, just some cleanups left to do.

@ireneista Depends what exactly you mean. When it comes to PureOS (not exactly a "big" org though 😜), we have only actively worked on GTK / GNOME / Phosh, but all the other stuff was still flowing in from Debian. We had set qtwayland up in the default config for Librem 5 to let Qt apps run well, but that was pretty much it. Ultimately it's just a matter of focus and resources, as we're all spreading ourselves thin and the community is still very tiny.

@Oleksii ...and thanks to your post I've noticed that some apps are missing: https://github.com/flathub-infra/website/issues/5335

@janvlug Can be much nicer as long as you don't care about the framerate 😂 #shotonlibrem5

@pavel @datenwolf @dcz @martijnbraam @NekoCWD You could encode to YUV444 or even RGB, but lack of lens corrections is much more visible than chroma subsampling:)

chillout #shotonlibrem5

@aeva From a quick search, Framework's touchpad (PixArt PIXA3854) should be handled by hid_multitouch just fine, so if it shows up as a mouse you may have something misconfigured or some kernel modules missing.

@aeva > (which linux sees as a mouse)

Awful. What kind of laptop is that? Only seen that with shitty USB touchpads in lapdocks (...and Pinebooks), presumably done for compatibility with Android(?)

@pavel Outputting AYUV is trivial and makes encoding slightly faster, but then you lose the viewfinder for free as that's not a format that can be passed to the compositor.

Ideally we would output planar YUV (perhaps with multiple render targets?) as that can be sampled from with recent etnaviv: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3418

For now I'm limiting myself to what's possible on bookworm/crimson though :)

@SpookyDoom @maxleibman As if the current incentives actually worked 😄

@pavel Displaying the viewfinder is free with (gl)waylandsink, as the dmabuf gets passed directly to the compositor in a subsurface, so the resolution is not important - it goes straight to the GPU for compositing. It's important for encoding and that's where uncached buffers can bite you, but since my shader is currently too heavy to handle higher res anyway it's not a thing I concern myself with right now.

And the code is basic, it just takes time to get familiar with the problem space 😜

@pavel So I was just adding autofocus to my toy code and I wanted to be able to trigger it by tapping on the viewfinder. Just replaced waylandsink with gtkwaylandsink, grabbed its GtkWidget and added it to my GtkWindow and it works 😛

@maxleibman This is actually unironically one of the rare use cases where it does make some sense, especially when you keep waiting for your PDF reader to search through thousands pages of reference manual just to find out that you need to come up with yet another synonym as a search phrase.

Well, at least theoretically. Most AI integrations I've seen so far looked like they were put together with sticks and mud, probably written by that AI itself 😂

@pavel Doing it via GStreamer makes buffer queue management easier, but of course it can be done either way. With SDL you get GL context already, so you just do it the way I showed you some time ago. You skip the context creation part and you're done.