[04:03] <MauroGaspari[m]> uhh Eickmeyer remember that bug I was complaining about earlier? freeze after grub, when using lowlatency kernel?
[04:03] <MauroGaspari[m]> It seems to be fixed. I installed updates to 5.8.0-41-lowlatency on both Ubuntu studio 21.04 and Ubuntu Budgie (with studio tools) 21.04. and both are running great now. I did full shutdowns and reboots more than I can count, not a single hang.
[04:04] <MauroGaspari[m]> I don't know who to thank for that, but I am a happy geek today 😅🥳
[14:45]  * OvenWerks didn't notice this behaviour... but only booted a few times yesterday
[14:48] <OvenWerks> Eickmeyer[m]: (and anyone who cares) I did some testing yesterday in 21.04 of pipewire... I need to do a lot more as pw is installed in 21.04 by default and I think will end up being the only audio setup that will work with wayland properly (and flatpack which will likely replace snaps)
[14:51] <OvenWerks> From the docs, if Jack asks for a device from PW (assuming pw in jack mode) pw will give jack that device and create a jack-jack (or pw-jack) bridge which at least on the pw side, will be called by that device name.
[14:55] <OvenWerks> from my observations, this at least means that starting jack for the express purpose of using a firewire device as master does not auto create a pw-jack bridge because pw never gets to see the FW device because alsa can't load the module.
[14:55] <OvenWerks> therefor no bridge. I am sure such a bridge can be created though.
[14:56] <OvenWerks> manually that is.
[14:59] <OvenWerks> So I had two default jack servers running with completely different graphs.
[15:01] <OvenWerks> That is two instances of Carla running with the patch bay showing different devices and applications
[15:02] <OvenWerks> this testing so far has been using pw-jack carla to start an application to us pw-jack.
[15:05] <OvenWerks> However, normal use and probably as installed down the road, is to not have to do that but have libpw-jack replace libjack as the libjack applications will see.
[15:09] <OvenWerks> I think this would mean that jackd or jackdbus would not start at all unless the server name was set to !default and that any jack client would use the pw jack instance only. I think this is true even for applications that can set the jack server name.
[15:13] <OvenWerks> This means that jack would only be of use for loading backends that pw can't handle or that some switch or environment variables would have to be set when running non-pipewire jack clients.
[15:18] <Eickmeyer> OvenWerks: Good info.
[15:18] <OvenWerks> if pw can truely replace jack except for backends this is probably ok
[15:18]  * Eickmeyer is reading backscroll
[15:19] <Eickmeyer> Well, the version we have in our repos (synced from Debian) isn't as current as in Fedora, so I'm guessing there's still a little more left to trickle in.
[15:19] <OvenWerks> The other surprising thing was that pw opened my 12/10 i/o device as 4/2
[15:20] <Eickmeyer> Happy surprise there.
[15:20] <OvenWerks> our version is only a month old
[15:20] <Eickmeyer> I was understanding that PW was supposed to be a complete 1:1 replacement for Jack and Pulse, meaning neither of those engines running with PW doing all the work.
[15:21] <OvenWerks> and many of the problems I see are not likely to change
[15:21] <Eickmeyer> Well, probably not before release, but if wtay is kept up-to-date on these things, I'm sure it will get better.
[15:23] <OvenWerks> Eickmeyer: I understand that, however, with ALSA fw broken in the current kernels and the ffado drivers provide so much more stability (more than alsa with a good USB device) jack will be around for a while yet
[15:23] <Eickmeyer> That's fair. For 21.10 might be worth making some sort of switch in studio-controls to switch all backend to FW?
[15:23] <OvenWerks> Eickmeyer: fw may be considered outdated, but there is nothing out there that can replace it.
[15:23] <Eickmeyer> er.. PW?
[15:24] <OvenWerks> so there are a lot of people hanging on to their units
[15:24] <OvenWerks> Eickmeyer: my basic conclusion is that studio-controls or something like it will continue to be useful with PW
[15:24] <Eickmeyer> Yeah, I understand that. Keeping it around is a good idea. I don't mean we should throw the baby out with the bathwater, I'm just trying to figure out a way to make any PW transition easy.
[15:27] <OvenWerks> pw has some good things going for it for sure and desktop audio mixed with jack clients will work better
[15:28] <OvenWerks> Eickmeyer: in other news, is it possible in 21.04 to have system warning sounds turned off be default?
[15:28] <Eickmeyer> Hmmmm....
[15:28] <OvenWerks> I don't think we really addressed this since the switch to plasma
[15:29] <OvenWerks> certainly having a full volume bell in the middle of a recording is just really bad
[15:29] <Eickmeyer> I'm not 100% sure that's possible. That would take making some global config files. Some settings take for global, others don't. I'm not sure where the system sounds lie on that front. I'd have to experiement.
[15:30] <OvenWerks> ok
[15:30]  * OvenWerks was startled in the dark last night by a very loud bell
[15:32] <Eickmeyer> System Settings > Audio > Applications > Notification Sounds (to 0) would do the trick on a per-user basis, but I'm not sure it would take in a global default.
[15:35] <Eickmeyer> FYI, I'm in the process of moving, so somewhat incommunicado and unavailable for the most part throughout the day.
[16:02] <OvenWerks> Eickmeyer: I figured something. SO found your own place then.
[16:03] <Eickmeyer> Yeah, we ended up moving into an apartment. The banks wouldn't accept my income for a mortgage.
[16:06] <OvenWerks> saving time. once you have a big enoough down they don't care so much
[16:13] <Eickmeyer> Yep.
[17:14] <wonko> What's wrong with your income? not enough or self employed (i understand that's a pain in the ass)
[19:55] <Eickmeyer> wonko: It's considered self-employment even though I'm under an at-will contract. Really no difference except 1) no pay stub, 2) taxes get reported differently.