[00:11] John122: I am not sure what you are asking, the ports would get connected just like any other ports. Or do you mean how to do it on the commandline? [00:12] John122: must be middle of the night there :) 4pm-ish here. Anyway, jack_lsp -c will show all jack ports and what they are connected to. [00:14] John122: jack_connect source-port sink-port will connect two ports. [00:19] John122: remember there are two ports for stereo, so two connections. I would suggest calling zita-n2j on your master with --jname pi_name so that the portnames are always the same. Otherwise, you will end up with zita-n2j and zita-n2j_1 etc. [00:22] John122: thank you for your support BTW. [06:43] OvenWerks: ah yes, of course. As I said I was trying this yesterday and I used that command then. For some reason when I was trying it last night (and yes, it was late!) I totally forgot. My fault for trying to work in bed with the laptop rather than sleep! And my pleasure, thanks so much for the app and your help. === Iamahuman is now known as Iamahuman4 [15:06] Is this the appropriate channel for help installing LXQt on Ubuntu Studio (if this is even compatible) or is that considered software mixing? [15:11] its feasbile, but not specific to -studio, the usual ubuntu channels should suffice. what issues are you having? [15:11] s/specific/unique/ [15:12] kveremitz: you having trouble installing it? [15:12] sirriffsalot: ^ maxFlexGuest [15:13] I use xfce a lot, but haven't popped my lxqt 'cherry' yet [15:13] I did have lxde once [15:14] kveremitz: I see the metapackage as available, no adding repositories needed [15:14] kveremitz: yeah sorry [15:14] I guess he figured it out lol [15:15] heh [15:27] OvenWerks: Morning... Really sorry, spent all day trying to get the audio from the 3 RPis to the Master one. With help from someone in #jack I managed to check zita bridge was working using a test sine wave, but it seems to be a problem getting pulseaudio from chromium to jack out to j2n that is the problem. I've put studio controls on hoping that can help me get the chromium output to j2n but really struggling : [15:27] ( [15:27] OvenWerks: If I'm taking the piss asking too much, just say (well, say you are busy rather than I am taking the piss maybe ;) ) [16:12] John122: is chromium using pulse? Does chromium show in pavucontrol? [16:12] OvenWerks: Hi, yes it is. And yes, Chromium shows but the playback devices are the standard RPi audio interface. I've tried just about every combination I can think of and getting nowhere slowly [16:13] John122: but yes, using zita-njbridge, studio-controls would be an option. [16:13] does pavucontrol show a jack sink? [16:13] OvenWerks: no [16:13] that would be a show stopper :) [16:14] yes ;) It has been. I've done so many things today [16:14] John122: if you have started jackd from commandline, you need to manually create pulse-jack bridge [16:14] OvenWerks: testing with te sine wave, I had the settings in qjackctl to dummy. should I be using the inbuilt soundcard? I was having problems getting jack to start with that [16:15] also seems pointless [16:15] dummy is fine [16:15] great, I thought it should be [16:15] ok at the moment here's where i am. using studio controls alone, jack doesn't start [16:17] OvenWerks: https://markuphero.com/share/Un8pnZrIM2C6zqM7o4SR [16:17] OvenWerks: https://markuphero.com/share/DcWJIzYDwn5vtxtlnLg7 [16:18] so you have a total of 4 R-Pi? anyway, each of them need to have pulse, and the pulse_jack module [16:18] (as well as zita-njbridge) [16:20] OvenWerks: yes, but at the moment just trying to get one to work. the zita bridge is working, as proven with the sine wive sample client app [16:20] if jack is stopped the second screen has no effect. Though system:playback_1 seems wrong [16:20] I presume I've messed something up in qjackctl. shall I just delete the config files? [16:21] no need... controls deletes the jackdbus config files on start [16:21] :) [16:21] ah ok [16:21] well i've just closed studio controls, and killed autojack and jackdbus [16:21] So you have the master Pi working and now we are starting to deal with the slave Pis [16:22] if I'm using dummy, shall I go back to my original setup of disabling the inbuilt audio? [16:22] yes, master is fine [16:22] it's working with pulse/jack etc and it's getting the sine wave over the network via zita [16:22] it's getting pulse to jack on the slave so I connect it to zita that is the problem (as I understand it) [16:23] Ok, but because you are using features controls does not have yet, you are using a script in the Slave to get things going? [16:24] OvenWerks: you mean zita etc? all that is stopped at the moment. just trying to get pulse into jack [16:24] I am guessing that you are using a script started in ~/.config/autostart/ [16:24] on the main one yes (well, in the LXDE folder but yes) [16:25] John122: well it depends on how you wish to start jack [16:25] slave nothing yet. been testing by hand to get things working using multiple terminals (i should try tmux one day...) [16:25] OvenWerks: I just want the slaves to autostart and always pipe the chromium audio to jack (and then to the master via zita njbridge) [16:25] you need to find out how pulse connects to the Pi audio [16:26] if you do aplay -l [16:26] on a slave, do you see the Pi audio device? [16:26] sorry, just rebooted after having disabled it on the basis I was going to use dummy... just restarting [16:27] John122: how would you disable it? [16:27] ok, back up and now no sound cards found [16:27] in /boot/config.txt [16:27] good [16:28] you may wish to use a custom script [16:28] I gather it makes sense to disable it? not going to be using it surely? just dummy [16:28] yes, I'll put it in a script as I have on the master once I get it working but for now... ;) [16:28] ok, so fresh reboot. no sound cards. no jack running [16:29] yes it makes sense. In general if pulse can't see a device it will direct the audio where it can find a device or to it's own dummy. [16:29] pauvcontrol shows dummy [16:29] so you want to make the jacksink the only "device" [16:29] yes [16:29] this machine will do one thing only [16:30] how are you most comfortable starting jack? [16:30] OvenWerks: I really don't mind as long as it autostarts [16:30] on the master I am starting autojack [16:30] if yuo remember we had problems otherwise [16:30] the gui wasn't working on restart [16:30] yes :) [16:31] If you have the jackd command line worked out we can use that. [16:32] I don't. That's the problem. I'm been trying qjackctl and sound controls but wasn't 100% sure on using dummy vs alsa etc. [16:32] at the moment i have /usr/bin/jackd -v -ddummy -r48000 -p1024 [16:32] the rubix is 48000 [16:33] 48k is the best SR to use in my opinion [16:33] i know zita njbridge resamples but presumably makes sense to set to the same [16:33] my digital mixer is "only" 48k anyway so no point going higher [16:34] (and it's speech - even music is pretty pointless higher) [16:34] normally I kill pulse when I restart because it respawns in a known state but because you are starting from boot that is already the case. [16:34] ok [16:34] any audio we listen to is pointless higher [16:34] yes [16:34] quite [16:35] i believe latency can be lower at 96k ? but ... [16:36] latency is lower for any given buffer size but you find you have to use twice the buffer anyway so the latency ends up the same [16:36] actually, the rubix does 192khz but ... [16:36] right [16:38] anyway, what autojack does after it figures pulse is back running, it removes three pulse modules: [16:39] /usr/bin/pactl unload-module module-jackdbus-detect [16:40] /usr/bin/pactl unload-module module-udev-detect [16:40] /usr/bin/pactl unload-module module-alsa-card [16:41] If you are using jackd to start and you have disabled any alsa device (or any audio device) tis should not be needed [16:41] ok [16:42] I would suggest a sleep 2 or sleep 3 to make sure pulse is fully running before starting jackd but that would be the next thing [16:43] as your commandline works (I am guessing) just use that [16:46] Then you want to set up you zita-j2n --jname Master-Pi 192.*.*.* 8500 [16:50] OvenWerks: yes, got that set up on both ends and connected [16:51] then you want a pulse-jack bridge: /usr/bin/pactl load-module module-jack-sink client_name=pulse-out channels=2 connect=no [16:51] then you want to connect them up [16:52] in controls? [16:52] By the way, in a script I would put at least a sleep 1 between each [16:52] ok [16:52] I am assuming for your slaves not using controls but using a script instead [16:53] yes sure , but just to test [16:53] (this may be the best in your master too) [16:55] anyway connect your ports: /usr/bin/jack_connect pulse-out:front-left Master-Pi:playback_1 [16:56] and /usr/bin/jack_connect [16:56] opps [16:56] OvenWerks: sorry, something not right with the master now. It's playing to the sinks (1 to 4 depending on what I set in pavucontrol for chromium) and I can see the levels. but my mixer isn't playing any sound. ffs what have I done now [16:56] /usr/bin/jack_connect pulse-out:front-right Master-Pi:playback_2 [16:59] just unplugged the rubix 24, left a min, put it back, then restared autojack. as it was starting audio blasted out of the mixer, then went silent again and autojack reported [16:59] File "/usr/local/bin/autojack", line 597, in check_jack_status [16:59] new_l = phone_port [17:00] NameError: name 'phone_port' is not defined [17:04] maybe change headphones to none [17:06] I think shouldn't have to it should be set to system:playback_1 [17:06] but none should be safe [17:06] I can't see a none option? [17:07] 0,0,0 Capture... ? [17:07] or No Action? [17:07] no action [17:08] * OvenWerks will add a none option to HP devices next version [17:08] but PCH,0,0 will not work for you [17:09] 0,0,0 should be ok... but this is something I have not checked as well as should be [17:10] I have not tested no device by default which is what you have [17:11] this is because you have dissabled the Pi device [17:11] ok, rebooted. and now the sinks appear on boot [17:11] master [17:11] but for some reason, sound is not going out to the rubix [17:12] jack_lsp -c |pastebinit [17:12] when i stop autojack, pulse is using it as the default sound card and outputting on all 4 channels (that's what happened before when I restarted autojack) [17:12] Oh you may not have pastebinit [17:13] OvenWerks: http://paste.debian.net/1188273/ [17:13] no I do now, didn't have at first and it was throwing an error and not working, but now it throws and error but works [17:13] how come they are all pulse in? [17:14] are you trying to get audio to pulse? Obs or something? [17:14] they are coming from chromium. if i can get rid of pulse, fine [17:14] there are also no connections [17:14] yes, i just spotted that. somehow they have been wiped. God knows how [17:14] they should be pulse-outs then [17:15] they should all be output bridges I think [17:16] anyway, I need to go see my wife for a bit... maybe breakfast [17:16] sure no worries [17:16] sorry about this [17:16] you have been VERY patient [17:16] I amy write up two scripts one for remotes and one for master. [17:18] that would be amazing. I'm losing the will to live! searched for something before and found a thread called "I could cry..." and thought, yeah, not the only one! [17:44] OvenWerks: ok, manually connecting in qjackctl makes it work, but restarting and launching with autojack fails. It doesn't seem to persist the no switch option either, although it runs without complaint like this config but has no sound output because no connections are actually made - http://paste.debian.net/1188277/ [17:55] OvenWerks: Ok, fixed the master problem... Ugh... I had left a connection to zita in the input bridge section [18:04] OvenWerks: gone back to trying to connect "/usr/bin/jack_connect pulse-out:front-left guest1:playback_1 " (guest1 is the jname of the master) and no apparent error but no audio either [18:11] OvenWerks: sorry no, there is an error, guest1:playback_1 not a valid port. the master name is set to guest1 though. [18:12] OvenWerks: and both ends are connected for sure. master is --jname guest1 and sender is --jname guest3 [18:41] John122: http://www.ovenwerks.net/paste/pi-net/master [18:41] John122: this should replace autojack [18:42] it can be named master.sh or whatever. it will need chmod +x to work [18:44] the lines with 1 to 3 where you say not sure if right, they are the other 3 pis coming in? as master will be outputting on 1, I should change these to 2, 3, 4 ? [18:49] OvenWerks: ok, just to let you know i've renamed all the guests 1 , 2 and 3 to 2, 3 and 4 in both places. master is called guest1 (confusing I know) [19:02] OvenWerks: ok, on top of that you'd repeated _2 3 times instead of _2 _3 _4 but sorted now. just taking a pizza of of the oven then testing the sending. (thanks for this btw!) [19:11] OvenWerks: ok, this is what I've got in master.sh now and it boots on reboot - http://paste.debian.net/1188306/ === Iamahuman4 is now known as Iamahuman === Iamahuman is now known as Iamahuman4 [19:28] OvenWerks: ok, on the sender side (guest3) this is the output of jack_lsp -c http://paste.debian.net/1188309/ I gather I should connect something now but nothing works [19:32] yes I repeated _1 three times on purpose [19:34] John122: if you look at jack_lsp you should find the same as each bridge only has a _1 [19:35] That last paste is not jack_lps -c but rather the jackd log I think. [19:36] this line? /usr/bin/pactl load-module module-jack-sink client_name=pulse-out2 channels=1 connect=no [19:36] there was three of those, first was 1, then 3 x 3? [19:37] John122: I was following what your autojack config was that you posted. [19:37] http://paste.debian.net/1188310/ - i've got verbose logging on [19:38] OvenWerks: not sure if when I posted that it was broken. think so. I've fixed it now and it is working on master [19:39] OvenWerks: http://paste.debian.net/1188311/ [19:40] what am I supposed to see in this paste? [19:41] The file I sent should modify pulse, start jack then [19:42] sorry, i was just showing you the last working autojack.json [19:42] are my changes in http://paste.debian.net/1188306/ right? [19:43] create three mono zita bridges waiting for the other end. create 4 mono pulse->jack bridges, create 2 mono jack->pulse bridges [19:44] yes that looks right [19:45] then it should connect lots of stuff [19:45] great. so what about the sending end? I can't get jack_connect to work there [19:45] I have not yet got to the sending yet :) [19:45] i need to connect the dummmy output to jack so it .... [19:46] ah ok sorry! didn't mean to rush you! [19:46] doing family stuff at the same time :) [19:46] you have no idea how much I appreciate this! [19:46] sort of same, except not doing and in my wife's bad books.... [20:03] John122: http://www.ovenwerks.net/paste/pi-net/slave [20:03] this the one for the three slaves [20:04] there are three lines two are commented out. This one is set up for the first slave. [20:04] for the second and third slaves commentout the first line and uncomment the right line :) [20:06] John122: http://www.ovenwerks.net/paste/pi-net/master should match your now too. [20:13] OvenWerks: hmm, something not working on guest3. just rebooting (never rebooted a linux based computer like the RPi ;) ) [20:13] I mean as much as... [20:23] Hello! Since there's no direct upgrade path for Ubuntu Studio 20.04 to 20.10, is there any recommended way to port all customizations from XFCE to Plasma? I had to do a lot of things, including a manual change to one of JACK's config files to work with my quadrophonic speaker set. [20:24] OvenWerks: ok, doesn't seem to be working? http://paste.debian.net/1188319/ [20:44] OvenWerks: it's not starting anything after starting after it starts jackd by the look of i t. doing it manually on the cli, all seems ok until "/usr/bin/jack_connect pulse-out1:mono master:playback_1 " . looking at the connections in master, I only have master:in_1 [20:45] I've connected it to that, but still doesn't seem to send the sound [20:47] OvenWerks: http://paste.debian.net/1188322/ [21:08] John122: just back, the scripts I gave have a mistake. [21:08] OvenWerks: no worries [21:09] John122: I pulled command lines from the python script but there is no backgrounding of things [21:12] John122: try the new http://www.ovenwerks.net/paste/pi-net/master and http://www.ovenwerks.net/paste/pi-net/slave [21:12] be sure to refresh [21:12] note the adition of the & at the end of some lines [21:13] other wise we will never get past the jackd line [21:13] sorry about that. [21:17] no worries, this is the output of master run on cli manually after a fresh boot - http://paste.debian.net/1188327/ [21:19] "/usr/bin/jackd -d alsa -d: Rubix24,0,0 & - second -d be hw: ?" [21:20] Kraus: xfce and plasma store their settings in a totally different manner. What you could do though, is to save your home directory Or at least the ~/.config/ directory and then install xubuntu, ubuntustudio-installer and run ub ubuntustudio-installer and install the rest of studio from there. Adding the .config back (or restoring youor home directory) should allow the same settings and continue [21:20] to use xfce [21:21] John122: it should just be /usr/bin/jackd -d alsa -d: Rubix24,0,0 & [21:21] John122: the last char should be & on that line [21:21] default is 48000/1024/2 [21:22] Not to add to the endless workload of wonderful volunteers, but perhaps in the future it might be a good idea to offer different UI options for adopters of Studio, the way Mint does? [21:22] yes sorry, i didn't mean for - second -d ... to be inside the quotes [21:22] but is it not hw:Rubix24,0,0 not -d Rubix24,0,0 ? [21:23] ignore me [21:23] sorry [21:23] John122: right hw: should be there... been a while since I have used jackd to start jack [21:24] i wasn't used to -d it's normally -dhw:... so it looked very wrong to me when actually it was more right than I was wrong dropping the -d ;) [21:25] http://www.ovenwerks.net/paste/pi-net/master is updated if you don't want to just edit the one you have [21:27] Kraus: I think the idea was floated at one point. but with only two of us and each of us being part of other projects as well, there is just not the manpower. That is where ubuntustudio-installer came from. Install whichever ubuntu flavour you wish and put studio on top of it. [21:27] OvenWerks: thanks, just done it and rebooted though (seriously, never rebooted so much in my life, so lazy...) flipping between desktop with new spanish keyboard that i'm still getting used to, and macbook with spanish keyboard, and vnc'ing and ssh'ing into remote pi's and also into a virtualbox ubuntu where the keys are different again. so I am all over the place at the moment! [21:29] John122: I am not on my dev machine either right now so a do a ssh -Y to the dev machine run latte-dock and use that as my menu on the dev machine [21:29] rather than VNC [21:30] OvenWerks: When I was on straight Ubuntu 18.04, (then having switched to 19, then 20), when I attempted to use the ubuntustudio-installer and switched to XFCE, there were several points where things did not integrate well. That could have been due to the switch from Gnome to XFCE, but I was never able to put my finger on the causes. When I did a fresh install of Ubuntu Studio, all those problems went away. Everything worked out of [21:30] the box wonderfully. [21:30] OvenWerks: I'll look at that. Getting closer - http://paste.debian.net/1188330/ [21:30] timing problem ? [21:31] this irc is on yet another machine (web server) where I use the screen session manger to run alpine irssi etc [21:31] OvenWerks: yes, I've been doing that (actually it's on my mac desktop and I've been connecting to that from my laptop using Chrome Remote Desktop - screen is much bigger too so hard to see. On my desktop at the moment) [21:32] so yes, forgot about chrome remote desktop, as well as vnc, and ssh, and ssh into virtualbox VM, and new spanish keyboards and two different layouts and at least 4 keyboard mappings. no wonder I'm losing it [21:32] I'm currently backing everything up that I can remember. I guess in the future I'm going to keep a log of all the manual config tweaks I do, and maybe even keep a backup of the files in a backup folder.. Other than that I really don't see an easier way to port this stuff. Not your guys' fault. Just hours and hours of work to rebuild a system for a simple upgrade. [21:33] John122: it looks like autojack is still running on that [21:33] OvenWerks: and half of that because I wanted to not displease my wife too much by being up here, but still managed to piss her off anyway, so I may as well have made life easier for myself and stayed up here all day instead of being doing with them most of the day! [21:33] i could be wrong [21:33] OvenWerks: hmm. shouldn't be. let me check [21:34] OvenWerks: no, it's commented out [21:35] yeah my mistake [21:37] ah ip is wrong [21:37] 66 instead of 61 [21:37] Kraus: gnome screen is (insert favourite term here) in many ways. The menu is broken and the last time I looked was not fixable. [21:38] John122: the ip in all cases should be the master machbine's ip [21:38] Yeah, I hate gnome. :P [21:39] Kraus: getting studio to work on gnome has been a trial for a while now. [21:40] most audio applications work best on xorg rather than wayland [21:41] wayland it seems is also broken or at least insists that the way linux apps has been doing things forever is wrong. [21:42] Oh well. I'm still waiting for Adobe to port CS to Linux. Been 24 years. I'm a patient man. [21:46] John122: are you using static or dynamic ips in your network? [21:46] OvenWerks: static for anything that matters [21:47] John122: ok, just wondering if your master ip had changed from dynamic [21:47] OvenWerks: no. And just successfully run master.sh [21:47] had to change capture to out as well [21:52] OvenWerks: got it working. sound is a bit dodgy though although actually, it seems to have settled down now. was a bit robotic at first [21:53] OvenWerks: the ports weren't working being so close to each other. I tried them 2 apart (even though only 1 channel) but ended up having to go 11 about (8902, 8913, 8924) [21:53] OvenWerks: hmm gone robotic again [21:53] john wick trailer on youtube and someone sounds like a dalek ;) but at least we have sound going from one to the other! === OU812 is now known as OU812[] === OU812[] is now known as OU812[-] [21:55] OvenWerks: this is the master (I added a sleep in between the n2j lines before fixing it with the ports so may not need them) - http://paste.debian.net/1188336/ [21:57] Ovenworks: and this is the slave http://paste.debian.net/1188337/ [21:58] John122: thank you good to know I did not see that in the zita man page but they obviously use more than one port :) [21:59] OvenWerks: no need to thank me, thank you! I've just got to work out why it's going crackly / robotic now [21:59] OvenWerks: just to clarify I went 11 to keep 2, 3, 4 for simplicity [22:00] John122: is part of the robot-ness from them running the same program material on four machines? [22:00] OvenWerks: no, sorry, only. testing one machine at the moment [22:00] John122: I would have done 10, 20, 30 :) [22:00] what is the cpu load on master? [22:00] OvenWerks: ha, yes, that would make more sense! I just started with 02 and I was being lazy [22:00] Master is 2 to 4% [22:01] you may need to upsize your udp buffer on master at least but maybe slaves too. [22:01] Slave is around 45% [22:01] playing youtube video at 720p [22:02] ouch! [22:02] yep ,) [22:02] OvenWerks: want a real laugh? [22:02] what is master when playing the same yt vid [22:03] whats that? [22:04] OvenWerks: I got the RPI 4 on the basis that it was 4k output. I was hoping I could capture that with a 4k hdmi capture card, and then take one 4k with 4 1080p images on into Ecamm and manipulate it from there. Turns out Ecamm can't crop like that they way I needed it, so went to the idea of a 1080p per screen (they have 2 x 4k outputs...)... no go. too slow for that. 1080p on one screen is bad enough on the 4 (3 [22:04] is fine!). So at the moment going for 720, can worry about 1080 in the future. So ended up with 4 RPis doing 720p each! [22:06] OvenWerks: so far master is 30 to 40%. master is 8gb (although not all used properly on 32 bit os), and guest 2 is 4gb, guest 3 and 4 are 2gb [22:06] OvenWerks: actually, don't forget sorry both are running VNC server which I'm viewing it over so unfair % [22:06] right. [22:07] well, I can't work around that I don't think. I do think the SRC is done at the master. [22:07] (I think it has to be to work) [22:08] I don't know if the dummy backend uses more cpu (I don't think so... system timer) [22:14] OvenWerks: I won't be using VNC once set up [22:15] OvenWerks: apart from the odd time, but not while using the system, it will be headless [22:16] OvenWerks: hmm, changing the buffer to 20 - which should be 20ms - has caused the message "Waiting for 10.0 seconds... " to be repeated . will try other values [22:25] OvenWerks: mono is fine btw, because it's for speech, but any reason for that? [22:29] John122: I was copying what you were doing in the autojack config [22:30] feel free to do two channels everywhere [22:30] OvenWerks: ah ok, yes, will be mono anyway. put the buffer up to 35ms and playing a test of high quality speech and it's PERFECT ;) just about to start the other 2 [22:30] remember that you will need to connect left and right separately [22:31] yes. won't be doing stereo for this but good to know this for other uses [22:40] OvenWerks: ok, got 2 of the 3 remotes working. 3rd isn't coming in but it could be the cabling or mixing desk. I'll check it tomorrow. Thank you again SO much. I'd have stuck with pulse audio networking after going through this had I been on my own! [22:43] John122: hope this really is better. if the load it too much to can reduce the bit depth zita sends [22:44] John122: there is 32float, 24bit int (default) and 16bit int. [22:45] OvenWerks: yes, it sounds good now. but I can experiment with depth and buffer. someone worried me before with the idea that pulse to jack may still drift ... hopefully not! [22:45] it may be that 24bit takes as much bandwidth as 32bit in mono but shares stuff in stearo [22:46] but even if it did, I would imagine it would be massively less than the drift using pulseaudio over the network where, as I understand it, it could buffer and pause for a bit then restart delayed etc [22:46] jack tends to force pulse to stay in sync [22:46] perfect! [22:46] switched cables around and it's not the cable or mixing desk for guest 4! never mind, it'll be something silly. will fix it in the morning when not absolutely shattered. [22:47] it certainly forces pulse to the same latency [22:48] o/ [22:48] OvenWerks: oh, one funny thing I realised... this is great, and I will keep it this way because it takes more load off my mac which I am doing as much as possible with this whole podcasting/video setup. But my mac is connected to the x32 digital mixer. it is also a 32/32 sound card. now I know about zita njdbridge, I could have sent the audio directly from the RPis to the mac and then to the mixing desk and back [22:48] ;) No real benefit, I have all the hardware any way and this takes more load off, but just made me laugh when I realised! [22:48] OvenWerks: consistent latency is the main thing [22:51] OvenWerks: now I have one final piece of the jigsaw to do (well, actually, apart from guest 4 will I'll fix in the morning, I could use this now) but I have 4 "guest" video captures in my jitsi meeting to capture the video of up to 4 guests/co-hosts (my camera/mic is local here). And these 4 guests - written using the jitsi api - currently show up in the conference. No big deal. Not on the output, but there is a [22:51] way to hide them so want to get that nailed and then I have a system perfectly meets what I aimed for over a month ago and thought "Oh, this will be easy with webrtc!" [22:53] Right got to fall into bed and sleep. School run in the morning and she is going as a surgeon for "uniform" day...! Thanks again OvenWerks - you are a gem, one of the rare people who remind me what the internet was like back in the 90s! I don't use IRC massively but I will certainly keep in touch with this group when I do and I'll show you the result of this once we do our first proper video with it. [22:54] OvenWerks: have a good rest of your sunday and have a good week ahead! night!