![]() You can try to build something with their internal compositor libraries (libmutter or kwayland) but they probably won't be as nice. I don't think so, GNOME and KDE have never had the goal of making a reusable and generic compositor library like wlroots. ![]() >I'm actually more concerned about the fact that wlroots has/had to duplicate work done by Gnome and KDE With wayland, tough luck, the most you can get is a better editor/annotation tool. In X, if you don't like Gnome's screenshto tool, you have a handful of other options. And a tool like flameshot becomes awkward if the compositor opens it's own dialog. So on wlroots, currently, an app can only get a full screen screenshot. Yeah, the problem is that each compositor has to implement it's own screenshot dialog, and you _have_ to go through that dialog for that compositor. Unfortunately the wlr portal is still not done yet and doesn't implement this. What's supposed to happen is that the portal daemon (NOT the application) pops up a dialog asking the user to choose which one they want. I'm actually more concerned about the fact that wlroots has/had to duplicate work done by Gnome and KDE (wlroots is more recent than much of gnome and kde's wayland support). If those projects want to create extra work for themselves, that's on them. > I am not sure how this is relevant if you're trying to write your own compositor. I also use X forwarding pretty extensively, but I'm probably a small minority these days. I'm definitely not looking forward to reworking my entire workflow for minor benefits although I suppose I'll have to one day. I remember being fairly optimistic when I first heard about Wayland and Mir, the prospect of ditching X11 was enticing.īut now? I haven't really had to wrestle with X in a long time. Xorg was sometimes a bit of a pig too resource-wise, but that's when I was running a PC with 256MB of RAM. In the specific case of Xorg I find the situation strange because I'd gladly have made the switch 15 years ago back when messing with nf was a common occurrence for me and it kept getting in the way (although a big portion of the blame was with the proprietary drivers, especially AMD's). People who were dealing just fine with previous solutions then start complaining about breaking things for the sake of breaking things and not being able to do things the way they were used to. Same reason systemd exists, the previous solutions were old and clunky and some people got fed up and decided to update. Luckily, we didn't say anything too embarrassing, but it was embarrassing nonetheless. We didn't see the green audio level animation or even the listing for that input either, because it was at the bottom of the list of audio input sources where you have to scroll down within that box to see it. Little did I know that OBS includes -all- audio sources on every scene, by default, unmuted.Īnd though I had muted our regular mic, the webcam's built-in mic was on and transmitting. ![]() We then proceeded to chat and get things ready for the presentation, etc. We started the live stream and then muted the mic on the audio inputs and then, for good measure, muted the physical mic. We have an Intro screen scene that just displays our logo and some background movement with a message that we will begin soon. Or at the very least, audio sources should be muted by default in new scenes. Tldr There needs to be a master audio level display or at least some sort of master indication whether a stream is getting an audio signal or not. But I have one suggestion that would save a lot of embarrassment for a lot of people. I love being able to switch scenes on the fly. I've posted a bounty of $10k recently to make this a native feature and it's getting lots of traction. On windows its reasonably easy to output OBS to a virtual camera for video conferencing software through a plugin. As one of our coaches recently said "Video quality is the new presence in 1:1s". Even simple things like adding a compressor to an audio stream can make a huge difference to the quality. OBS is an amazing tool and its worth learning. I use its video record feature to react to figma prototypes and post the MP4s in the respective channel for discussion. I've done townhall with live on-screen Q/A voting, hosted podcast discussions, done PIP product reviews. I run a 6,000 people company during the day and have OBS setup to push into Google Meet. I randomly learned OBS a while ago for doing some twitch streams in the evenings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |