=== housecat is now known as dax [14:41] @Eickmeyer [@teward001 When you come back to us, critical fix for Ardour at https://code.lau …], if i recall this was fixed already [14:41] thank you to others for handling the upload yesterday :0 [14:42] @teward001 [if i recall this was fixed already], That's correct. [14:43] We're looking at two packages that need to be accepted at this point: ardour and rapid-photo-downloader, with ardour being the more critical of the two. [14:44] @teward001 Do you think I should incessently pester #ubuntu-release to get that done? ^ [14:44] i'm already pestering them for an nginx FFe to get done [14:45] if you want to pester them that's your call [14:45] given it's a Critical I would [14:45] because IIRC Final Freeze is today [14:45] Final Freeze is tomorrow, but yes. [14:45] meh whatever [14:45] *yawns* [14:45] @teward001 just pretend you are Simon [14:45] I am still waking up [14:45] hahahahahaha [14:45] yeah no i'm better than Simon lol [14:45] Simon actually owes me cash lol [14:46] or rather, Lubuntu Foundation probably will if they want faster SLA to their infra issues xD [20:10] Rapid Photo Downloader update is accepted, we are good to go, pending no other mejor issues hit us. [20:28] Ardour is through too? [20:29] Eickmeyer: ^^ [20:29] Yep. [20:29] when will the ISO be ready? [20:30] Next daily will probably be tomorrow, and they'll probably start making final RCs starting tomorrow. [20:59] I just noticed while doing some cleanup that my wife has a BT speaker sitting around. I may try to see if it is possible to auto connect from script... [21:02] I'm pretty sure the only way to do that is through Pulse. Not even ALSA connect directly to BT speakers [21:14] Yeah, but going from jack to pulse to BT is not straight forward [21:14] Oh, absolutely true. [21:15] It would be nice to be able to create a jack->pulse bridge called BT-speaker or something and send a command to pulse that connects it to the BT speaker [21:16] I just hope nobody would expect it to be low latency. [21:16] not even Intel lowlatency (30ms) I would guess [21:17] Bluetooth is notoriously latent. [21:17] I know (from the LAU mail list) that there are at least some people who have figured it out [21:18] The best solution would be to use the zita SRC lib to create a BT-out jack client [21:19] I think the pulse solution is best for now. The jack client may become redundent if pipewire replaces pulse soon [21:20] I have pipewire installed (but not activated) by default in Fedora Jam. [21:21] doesn't show up in ubuntu (at least not 18.04) [21:22] !info pipewire focal [21:22] pipewire (source: pipewire): PipeWire multimedia server. In component universe, is optional. Version 0.2.7-1 (focal), package size 217 kB, installed size 1408 kB [21:22] It's in Focal. [21:22] disco even [21:22] https://packages.ubuntu.com/search?keywords=pipewire [21:22] !info pipewire disco [21:22] pipewire (source: pipewire): PipeWire multimedia server. In component universe, is optional. Version 0.2.5-1 (disco), package size 211 kB, installed size 1345 kB [21:23] Yep, slightly older version. [21:23] good [21:23] one hopes the versions are going up quickly at this point of development [21:24] Might be fun to play around with. I know the version in Fedora 32 uses the Jack API. [21:24] Not yet pulse though. [21:25] I think they offer a pseudo default device like pulse though [21:26] The idea is that it will use the Jack and Pulse APIs, therefore eliminating the need for a bridge. [21:27] yeah, I am guessing that a jack to jack bridge will just show up :) [21:28] There are a lot of people who are not ready to trust PW over jack even with the API [21:28] Won't be necessary. Jack applications won't know any different. [21:29] I wouldn't expect anyone to trust PW yet. [21:29] It's still real early. [21:29] may not be needed for our use (someone who wants to work around it is welcome to do so... on their own [21:29] Experimental, even, though Fedora does want to move to it as default by Fedora 34. [21:30] 34... what is current? and how often do the numbers move? [21:31] Current is 31, 32 is in release candidate, and 33 will be in October/November. Fedora does delay if they feel it's necessary unlike Ubuntu which sticks to very strict release dates +/- 1 day or so. [21:31] so around next year at this time [21:32] (within a couple months) [21:32] Roughly, yes, unless they feel there's blockers. PipeWire has a lot of Red Hat backing. [21:32] yeah, a lot of things get in that way [21:32] if the pulse-jack bridging is better with pw I am all for it [21:33] that is, basically if they use jack as the backend for pulse as we do [21:34] Well, the bridge would be PW itself. In theory, if you look at a Carla patchbay, each application, whether it uses pulse or jack, would show-up in the patchbay. [21:35] Of course, they would auto-patch to primary system out, but you get the idea. [21:35] So, you'd have Firefox in there, or anything else with an audio in/out. [21:35] The question in may mind is: with multiple devices, where do they show up? [21:36] In theory, yes. [21:37] I mean, each device would show up in the patchbay as well, kinda like we have with zita-ajbridge. [21:37] If a jack application gets it's device from the pw backend rather than alsa, many people may not be very happy [21:37] I'm not sure PW overrides alsa. [21:37] I think it's more like a replacement for Pulse and Jack. [21:38] So if pw uses the jack part as the backend that is fine and makes sense, but if jack then goes through pw then through alsa not so good [21:38] No, you don't understand. Jack wouldn't actually run. PW would essentially *be* both jack and pulse. [21:39] now I guess pw essenially rewrites jack in anycase, so it may be that the jack api works directly with the pw backend [21:39] Exactly. [21:40] so one might say pw is a rewrite of jack that features a pulse front end... and video streaming [21:40] Something like that. [21:40] I wonder if there will also be a pw front end that applications can access directly. [21:41] Well, browsers can access different devices separately via pulse, so I'm sure that will be the case. Applications won't have to be rewritten for their audio backend, it'll be transparent. [21:42] I'd say PW is more like a rewrite of both jack and pulse that combines the two. [21:42] ...and video streaming. [21:43] how does the video streaming affect X and or wacom? (and vulcan?) [21:43] Nooo clue, but I know it's all on their radar. [21:48] So have you played with pw at all? [21:49] How does one set SR, buffers etc? [21:49] Not yet. Been too busy with getting our stuff fixed. [21:49] That and homeschooling. [21:49] I might play with it soon though. [21:50] my son is "leave me alone, i've got it" [21:50] My son it 8. [21:50] mine's 14 [21:50] Yeah. If he were older, then yeah, he could do it, but he doesn't stay motivated on his own. [21:51] I'm not sure how motivated Tim is either, but he does seem to do better without help [21:57] Mine would never even do his school work if I weren't motivating him. He's on spring break now, but we have a schedule of subjects we follow. [21:58] our spring breat was the last two weeks of March... he never went back :)