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