[11:07] What's the current situation with Wayland on Ubuntu Studio? KDE itself used to say it's experimental, and afaik essential features such as color profiles are still WIP, is there anything else I should be aware of? [14:23] justJanne[m]: I use wayland on only one of my machines and only because I need it for waydroid. I do not know how well it works for 23.04 but on 22.10 I find the scaling is off (everything comes out tiny). I have heard that is not as bad in later versions. On the other hand almost all software is still written on top of the X11 libs. [14:24] OvenWerks: Well, Electron, Qt and Gtk work fine on Wayland, and pretty much all software uses these frameworks, so that should be fine [14:24] > <@OvenWerks:libera.chat> justJanne: I use wayland on only one of my machines and only because I need it for waydroid. I do not know how well it works for 23.04 but on 22.10 I find the scaling is off (everything comes out tiny). I have heard that is not as bad in later versions. On the other hand almost all software is still written on top of the X11 libs. [14:24] * Well, Electron, Qt and Gtk work fine on Wayland, and all software I use uses these frameworks, so that should be fine [16:34] a lot of plugins use X11 pretty directly. None of the plugins (that are stable) use electron, qt or gtk. I personally avoid electron based sw as much as possible. Ardour, which is gtk-ish based, is based on older versions and may not be wayland native either. That said, wayland does provide an X11 interface. [16:48] So, I installed it on another drive for testing, it works really well. Loving it already. Time to make the switch on my main system as well. [17:31] Hi all. [17:31] Has anyone else had the problem of using google meet or microsoft teams or any conferencing software really - the mic works but the audio in the room doesn't - when i look at speakers in the conferencing software it's set to default, when i try to change it it says jack sink - pulse out, when i cliick test i get no audio [17:31] i'm on ubuntu studio 22.04 and have a usb audio interface - behringer um2 [17:31] i can record and hear audio in mixbus etc. [17:31] it's just conferencing software this is an issue on [17:31] anyone else have this problem? [17:55] guitarman: Conferencing software will be using pulseaudio as opposed to mixbus which is likely using jack, therefore it will have to be patched differently. [17:55] Eickmeyer: thanks for chiming in - youtube works for instance [17:55] Eickmeyer: do you think I need to change something in the studio controls app [17:56] guitarman: More like you'll need to change something in a patchbay like carla's patchbay. [17:56] You'll need to set your pulse in/out to your UM2. [17:56] hmmm [17:57] lo9oking in carla, i have capture 1 and 2 going to pulse_in left and right [17:57] i have pulse out going to system playback [17:57] And the videoconferencing software will also be needed to be set to the pulse-in and pulse-out. [17:58] System playback would be whatever your master is set to in studio controls. [17:59] i'm in studio controls now [18:02] in jack master settings it has the usb device that should be master set [18:03] main output ports system:playback1 [18:07] Ok, perfect. [18:08] Then in the video conferencing software, it should be set to pulseaudio source and pulseaudio sinc. [18:08] *sink. [18:08] *Jack source and Jack sink [18:09] yeah so in the conference software I have: jack source and jack sink [18:09] pulse in and pulse out [18:09] yet still no audio [18:10] And everything is routed correctly in carla? [18:14] yes [18:14] syhstem captures 1 and 2 go to pulse in l and r, pulse out l and r go to playback 1 and 2 [18:14] that's why it's a mystery [18:15] youtube works which uses pulse sink to jack i think [18:15] open qasmixer and make sure your levels are up. [18:15] master is 100% [18:15] What video conferencing software is this that you're testing on? [18:16] Google Meet in this case [18:16] Ok, that explains it. You might have to close every browser tab/window and reopen to get it to use it correctly after making any changes. It's finicky. [18:17] Basically, you can't have a browser window open while starting jack. [18:17] still no go [18:17] closed and reopened browser [18:18] Then you still have a hung browser process. [18:18] Which browser? [18:18] google chrome [18:18] ok, open a terminal, type "pkill -9 chrome". [18:19] (Chrome is probably set to stay open in the background) [18:19] Then try it. [18:23] so here's something odd [18:24] it works in firefox but not chrome now [18:24] So I guess that's progress. [18:24] I wonder why it fails in chrome but works in firefox [18:24] Not sure. [18:25] Like I said, Google Meet is very finicky when it comes to audio and detecting stuff. Basically, it won't detect anything new if there's a previous browser process open. [18:31] Eickmeyer: thanks for your help. I'll call being able to use firefox for meetings good enough. [18:31] counter intuitive though, you would think the google stuff would work in chrome vs firefox [18:32] guitarman: If that works for you, awesome. Glad to hear it. But yeah, Chrome can be a pain sometimes. [18:50] Any chance of some more help just now with my Carla problem? I did the backports thing as advised, it still won't launch. [18:54] tedthetrumpet: can you show me the output of `sudo apt-cache policy carla` ? [18:54] hang on [18:54] carla:... (full message at ) [18:55] Hmmmm.... [18:55] !info carla lunar [18:55] carla (2.5.4-0ubuntu2, lunar): audio plugin host. In component universe, is optional. Built by carla. Size 4,520 kB / 29,135 kB. (Only available for amd64, i386.) [18:55] Give me a few hours, I'll give you the latest bugfix release. Sorry, that one might be on me. [18:56] Ok, no major hurry right now, I'll probably be in bed by then :) would be good to get it working by the end of this week though [18:57] Well, if this doesn't work then you might have something else that's pretty broken on your system. [18:57] Ok, be good to find out!