[17:01] <Eickmeyer> OvenWerks: zita-alsa-pcmi (the source package) is at 0.5.1: https://launchpad.net/ubuntu/+source/zita-alsa-pcmi
[17:07] <OvenWerks> Eickmeyer: I was looking at the depends which are = or greater :P
[17:07] <Eickmeyer> Ah, that explains it.
[17:07] <Eickmeyer> 22.04 has it at 0.4.0
[17:07] <Eickmeyer> Kinetic is at 0.5.1
[17:07] <Eickmeyer> I can backport 0.5.1 to backports if you want.
[17:08] <Eickmeyer> I'm always wary of breakage from backporting libs though.
[17:08] <OvenWerks> to fix that problem we need 0.6.1
[17:08] <Eickmeyer> Looks like snd is the maintainer there.
[17:09] <Eickmeyer> (dunno if he's paying attention)
[17:10] <OvenWerks> It affects audio cards with 32 bit adc
[17:10] <snd> hello
[17:10] <Eickmeyer> Hey snd!
[17:10] <snd> 0.6.1 is out?
[17:10] <Eickmeyer> Looking at zita-alsa-pcmi.
[17:10] <Eickmeyer> Yep!
[17:11] <OvenWerks> 32 bit audio being about as useful as 96k audio or screen doors on submarines
[17:11] <Eickmeyer> Heh, not wrong.
[17:12] <OvenWerks> (unless one works in sales)
[17:12] <Eickmeyer> Or my 192k interface at 192k.
[17:13] <OvenWerks> for scientific studies of bats or doing RF manipulation for radio it might be useful
[17:14] <OvenWerks> 32 bit audio on the other hand, is beyond the capability of the analong input circuitry (even 24 bit is). So the last 9 or so bits would all be noise
[17:16] <Eickmeyer> Maybe that could be metadata? >_>
[17:17] <OvenWerks> Maybe for recording jet engines up close... or rockets?
[17:18] <OvenWerks> If one can find a mic that would handle it.
[17:19] <OvenWerks> Even then the dynamic range is unlikely to be that great.
[17:19] <snd> seems the upstream needs to release another release...
[17:19] <snd> g++ -Wl,-z,relro -Wl,-z,now -o alsa_loopback alsa_loopback.o pxthread.o ../source/libzita-alsa-pcmi.so.0.5.1 -lasound -lpthread -lrt
[17:19] <snd> /usr/bin/ld: cannot find ../source/libzita-alsa-pcmi.so.0.5.1: No such file or directory
[17:19] <snd> with the latest 0.6.1
[17:19] <snd> lol
[17:20] <snd> ah no wait
[17:20] <snd> its a patch
[17:21] <Eickmeyer> Heh
[17:22] <Eickmeyer> I was gonna say, that looks like a version mismatch.
[17:24]  * OvenWerks wonders why he has two resampler libs
[18:19] <snd> ill upload it and lsp-plugins 1.2.4 to debian unstable soon, but first i need something to eat
[18:20] <Eickmeyer> snd: Sounds good. I was just going to ping you about that, but you're ahead of me. Thanks!
[19:29] <snd> uploaded
[19:29] <snd> how do you guys see updates of software? do you use anything else than uscan aka watch files
[19:37] <Eickmeyer> snd: I watch the multimedia-team mailing list. Everything automatically syncs to the Ubuntu archive for the latest development release.
[19:38] <Eickmeyer> As for latest release from upstream, for instance lsp-plugins, I'm subscribed to their github release notifications.
[19:44] <snd> ah ok, but zita-* releases?
[19:46] <Eickmeyer> OvenWerks tends to keep track of that more than I do.
[19:46] <snd> the upstreams website suck a bit, because you cant sort releases for the latest ones
[19:52]  * OvenWerks is subscribed to the lau, laa, lad mailing lists
[19:53] <snd> aah
[19:53] <Eickmeyer> I'm subscribed to those lists too but they end up in my spam folders even though I have rules set.
[19:54] <snd> well i have my own mail server and sometimes too busy (or lazy) to update the whitelist for greylisting 
[19:54] <snd> heh
[19:54] <Eickmeyer> And I have the same problem with new-session-manager and agordejo which is why I have to periodically check if I miss the announcement.
[20:10] <arraybolt3> OvenWerks: Random humorous anecdote, someone one time set up a camera to capture a picture of a space shuttle during lift-off, and used noise to activate it. The first picture it took was of a really loud turkey buzzard :D (Was reminded of that with the mention of recording rockets)
[20:11] <OvenWerks> :)
[20:11] <OvenWerks> relative distance does funny things too
[20:33] <Eickmeyer> Wild goose chase. *facepalm*
[20:34] <OvenWerks> I did (backscroll) say you need to enable back ports in -installer and was told that is done.
[20:34] <Eickmeyer> Right. You did. Failure to follow instructions is one of my pet peeves with providing support.
[21:19] <Eickmeyer> OvenWerks: Line 181 has a space in the command where it doesn't belong. There is definitely a bug, I can patch it.
[21:22] <Eickmeyer> Nvm, didn't work, back to the drawing board.
[21:33] <OvenWerks> the space should not be there for sure. however from that point I start to wonder what the difference is.
[21:35] <Eickmeyer> Now he's having trouble with receive bridges.
[21:38] <OvenWerks> for some reason the network bridging does not have logging set up, does not keep the pid for shutdown.
[21:42] <OvenWerks> Actually, ajbridge doesn't capture logging either
[21:42] <OvenWerks> just the pid.
[21:45] <Eickmeyer> Does it not have stdout or stderr?
[21:45] <OvenWerks> I think the stdout buffer doesn't get flushed till exit so capturing stdout/err will block till exit. output shows up in terminal though
[21:46] <Eickmeyer> That's inconvenient.
[21:47] <OvenWerks> so if autojack is run from a terminal it might show.
[21:48] <OvenWerks> I don't have a machine I can play with it with though.
[21:48] <OvenWerks> I am just looking at the code on github.
[22:10] <Eickmeyer> I have the feeling it probably works, but while he was trying to make it work on 2.3.1 he probably bugged it up.
[22:25] <OvenWerks> The net bridging is probably one of the least tested parts of controls