ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
cyberpear has quit [Server closed connection]
cyberpear has joined #wayland
jmdaemon has joined #wayland
danvet has quit [Ping timeout: 480 seconds]
c7s has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
colordrops has quit [Ping timeout: 480 seconds]
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
ahartmetz has quit [Quit: Konversation terminated!]
maxzor has quit [Remote host closed the connection]
<tm512>
are there any tiling compositors aside from sway that swaymsg will work with? I want to make a transition over to wayland, but the biggest blocker I've run into is being able to capture video from a window
<tm512>
it seems like swaymsg is the only way to actually get a window's position and size
<tm512>
not being able to record a single window is going to be a non-starter since I have a single-monitor setup and I can't run games fullscreen if I want to monitor stuff like the twitch dashboard
<Arnavion>
If you're using OBS, you can crop the pipewire capture of the whole screen to whatever region you want
shankaru has joined #wayland
<i509VCB>
I believe compositors which support xdg-desktop-portal allow requesting the content of specific windows. In the case of wlroots based compositors see xdg-desktop-portal-wlr
<tm512>
I'd prefer to stick with ffmpeg if possible. screen space is really cramped for me
<tm512>
it's not possible to grab a single window with wlroots
<i509VCB>
ah didn't realize that about xdpw, I guess using kde confused me there
<tm512>
I don't mind having the full screen capture as an input, but if I do that then I really need something like xwininfo to get window position/size to pass into ffmpeg's crop filter
<Arnavion>
And swaymsg will give you that
<tm512>
only on compositors that implement sway IPC, that apparently excludes dwl :/
<Arnavion>
Sure. You didn't say not using sway was a requirement.
<tm512>
I asked "are there any tiling compositors aside from sway that swaymsg will work with?"
<Arnavion>
And you justified it with "but the biggest blocker I've run into is being able to capture video from a window", and as we've discussed this is not a blocker for using sway
<tm512>
I've been using dwm for nearly a decade, and I'd prefer to use something as close as possible to dwm
<tm512>
ideally, I wouldn't even be switching to wayland yet, I'd be giving it several more years to mature, but I've been getting plagued by issues here on X11 for the past month or so that I've never had in the past, like stuttering in games seemingly associated with using picom,
<tm512>
also, unfortunately I've got an nvidia card currently. I do have the 510 driver, but afaict there's still a good chance that the proprietary driver will be practically unusable with wayland
<i509VCB>
would copying the sway ipc or reimplementing it (it appears to be json via a socket) be an option for you?
<i509VCB>
short term it would be fine but I imagine you want something more stable
<tm512>
I've considered the possibility of hacking dwl to output this information about a window to something like a tmpfile
<tm512>
if it's possible to set a window at a specific position and possibly resize it as well, then I could sidestep needing to query this information, since I'd already know the coordinates and dimensions, but I'm not sure even that is possible
<tm512>
seems like so much about wayland is really unstandardized and that really sucks for people like me who don't want to go with a big DE like GNOME or KDE. sounds like pipewire can capture video from a specific window just fine on those
nielsdg has quit [Server closed connection]
nielsdg has joined #wayland
<tm512>
does the slurp -o flag print the name of the selected window, or is it talking about screens?
blue_penquin has quit [Server closed connection]
blue_penquin has joined #wayland
pavan has joined #wayland
doras[m] has quit [Server closed connection]
doras[m] has joined #wayland
gnustomp[m] has quit [Server closed connection]
gnustomp[m] has joined #wayland
halfline[m] has quit [Server closed connection]
halfline[m] has joined #wayland
shankaru has quit [Quit: Leaving.]
pavan has quit [Ping timeout: 480 seconds]
shankaru has joined #wayland
<tm512>
kinda seeming like slurp -o just predefines a rectangle for every screen. meh.
<tm512>
would it be possible to do something like run a dwl instance in a dwl window, that way I could fullscreen the application inside the nested instance, and just do a fullscreen capture of that instance?
<i509VCB>
short answer yes, long answer you'll probably want to ask for more info on the dwl discord or github
<tm512>
I did mention something about it on their discord a bit ago, haven't gotten a response yet, but we'll see. I'm also looking into hacking dwl to give a list of all clients and their position/size. might be able to extend my streaming script to provide an interactive selection for which client's geometry to use
<tm512>
hoping this is something the wlroots project can add first-class support for sooner than later. there are tickets on their tracker for capturing specific windows so it is on their radar
rv1sr has joined #wayland
eroux has joined #wayland
zebrag has quit [Quit: Konversation terminated!]
jgrulich has joined #wayland
<tm512>
skimming through dwl's source code and storing a list with info about every window, like name and geometry, seems very doable. could maybe even use something dmenu-like to provide a selector
<soreau>
wf-recorder works with wlroots compositors supporting wlr-screencopy
<tm512>
just getting the screen capture isn't the problem, the problem is recording a specific window. there appears to be no standardized way of querying a window's position and size
danvet has joined #wayland
<tm512>
I'm hoping I can just resolve the issues I've been having with X11, but I don't have much hope of accomplishing that. seems like these more minimalist compositors really need more time to mature though
<whot>
davidre: fwiw, you're maintainer status on libei now so you can merge too (or should be able to)
pnowack has joined #wayland
<tm512>
sounds like the nvidia driver needs more time wrt wayland support as well but I'll use nouveau or fall back to my iGPU if I really have to
<tm512>
I'm probably going to lose my mind if I do go through all the effort of switching over to wayland and I just end up having the same stuttering issues that I'm having here on X11
<soreau>
tm512: what about your fullscreen nested idea with wf-recorder?
spstarr has joined #wayland
<tm512>
I'm still gonna have to look into how that could be accomplished, and whether or not a nested wayland compositor would even get its own surface that something like pipewire could grab
<tm512>
would a nested wayland compositor hurt performance at all in any regard?
<tm512>
I'm gonna be using it to play games, so preferably it won't hurt graphical performance or add any additional input lag
dcz_ has joined #wayland
hardening has joined #wayland
jgrulich has quit [Remote host closed the connection]
jgrulich has joined #wayland
MajorBiscuit has joined #wayland
kenny has quit [Ping timeout: 480 seconds]
jgrulich has quit [Remote host closed the connection]
ahartmetz has quit [Quit: Konversation terminated!]
ahartmetz has joined #wayland
c7s has quit [Quit: c7s]
eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
c7s has joined #wayland
eroux has joined #wayland
pounce has quit [Ping timeout: 480 seconds]
kenny has joined #wayland
<tm512>
so at this point, how well does nvidia's proprietary driver support wlroots-based compositors? I'm on the 510 driver here, on void linux
<tm512>
I do have a card that nouveau can reclock, so it's not the end of the world if the proprietary driver isn't gonna work. I'd definitely rather be using FOSS drivers in the first place but I want to make efficient use of this card
<tm512>
I know at this point the nvidia driver has support for both GBM and DMABUF, but I don't know how good that support actually is
<dottedmag>
There is a wlroots-eglstreams fork that adds support for nvidia proprietary drivers. No idea how well it works
<tm512>
the nvidia driver isn't limited to eglstreams anymore, though
jgrulich has quit [Remote host closed the connection]
<LaserEyess>
tm512: I've heard various reports that it works, with sometimes incomprehensible (and un-debuggable) bugs
<LaserEyess>
it should work OOTB though, if you're lucky
<LaserEyess>
so just try it?
jgrulich has joined #wayland
<tm512>
I'll probably be giving it a try. I'm thinking of falling back to nouveau or my iGPU while setting things up though, and only switch back over to nvidia after I've got a working setup
trepatudo has quit [Server closed connection]
trepatudo has joined #wayland
<bl4ckb0ne>
wlroots doesnt recommend the eglstreams fork, plus it has been abandonned not too long ago
<bl4ckb0ne>
we fixed a small issue recently regarding the nvidia proprietary driver, it "works" but we don't give any support
zubzub_ has left #wayland [#wayland]
zubzub has joined #wayland
<zubzub>
how well does does the nvidia gbm driver work these days?
<bl4ckb0ne>
it works
<zubzub>
driver 510 or 495?
<bl4ckb0ne>
495 and over, the higher the better i guess
<zubzub>
ok cool
devilhorns has joined #wayland
tzimmermann has joined #wayland
manuel1985 has joined #wayland
ppascher has quit [Quit: Gateway shutdown]
shankaru has quit [Quit: Leaving.]
eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ppascher has joined #wayland
jgrulich has quit [Ping timeout: 480 seconds]
duxsco has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
pavan has joined #wayland
duxsco has quit [Remote host closed the connection]
Azem has quit [Remote host closed the connection]
spstarr has quit [Remote host closed the connection]
spstarr has joined #wayland
cvmn has joined #wayland
zebrag has joined #wayland
duxsco has joined #wayland
cvmn has quit [Remote host closed the connection]
<zebrag>
with kde debian sid / wayland as pure as possible, my Cherry g84-4400 keyboard integrated trackball is randomly lagging very badly
<zebrag>
it doesn't happen so often, like 5% of the time or less
<zebrag>
I really don't think it's any hardware related
<zebrag>
and I was wondering if as a workaround it was possible to "reboot" the libinput thing?
<zebrag>
Also, libinput seems like an x11 thing
colordrops has joined #wayland
duxsco has quit [Remote host closed the connection]
duxsco has joined #wayland
fmuellner has joined #wayland
___nick___ has joined #wayland
cvmn has joined #wayland
cvmn has quit []
<zebrag>
the device is listed as "HID 046a:0008", both for the keyboard and for the pointer.
colordro1 has joined #wayland
colordrops has quit [Ping timeout: 480 seconds]
___nick___ has quit []
___nick___ has joined #wayland
devilhorns has quit []
___nick___ has quit []
___nick___ has joined #wayland
sychill has quit []
sychill has joined #wayland
r00tobo has quit [Quit: Quit]
manuel1985 has quit []
colordrops has joined #wayland
colordro1 has quit [Ping timeout: 480 seconds]
cabal704 has joined #wayland
r00tobo has joined #wayland
cabal704 has quit [Ping timeout: 480 seconds]
cabal704 has joined #wayland
tzimmermann has quit [Quit: Leaving]
zebrag has quit [Quit: Konversation terminated!]
MajorBiscuit has quit [Ping timeout: 480 seconds]
d3x0r has joined #wayland
<d3x0r>
how am I suppsoed to get any work done when there's no choice but to block in wayland? like... calling just wl_display_roundtrip_queue() twice in a row blocks?
fmuellner has quit [Ping timeout: 480 seconds]
dcz_ has quit [Ping timeout: 480 seconds]
<emersion>
plenty of libwayland users are purely non-blocking
<emersion>
blocking is a no-go when integrating with another event loop
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
<kennylevinsen>
d3x0r: don't call roundtrip if you do not want to block?
zebrag has joined #wayland
cabal704 has quit [Remote host closed the connection]
___nick___ has quit [Ping timeout: 480 seconds]
cabal704 has joined #wayland
duxsco has quit [Remote host closed the connection]
rasterman has quit [Quit: Gettin' stinky!]
mvlad has quit [Remote host closed the connection]