[00:42] Eickmeyer[m]: https://lists.linuxaudio.org/archives/linux-audio-announce/2020-April/002798.html [00:44] Interesting. [00:44] pretty exciting that someone has put that together [00:45] it has been stock macos and ios for years now [00:46] Yeah. When I was at my last job, we pretty much had mac/windows environments and I was starting to work on MIDI-IP stuff. This would've brought Linux into that mix. [00:46] linux has had ipmidi for a while [00:47] Right, but not really zeroconf. [00:47] qmidinet we have [00:47] right [00:47] What I'm saying is that this would've made it braindead-simple what I was working on. [00:48] Might be something worth including in 20.10. [00:49] yes, though probably with the right glue. [00:49] I will have to see. [00:50] I have been working on documentation for Ardour for all the stuff I added since 5.12 [00:51] I thought I had been keeping up but didn't really think how my foldback stuff affected OSC [00:53] Do you think studio-controls could be that right glue? [00:54] I will need to try it out to really know [00:55] I don't know the protocol well enough to know how automated it already is [00:56] It could be that if another computer sets up a connection, it just shows up in alsa or jack [00:58] I would at some point like to create a patch bay similar to patchage or Carla but have it show "possible" connections that are not on the jack grid yet (or alsa) [00:59] Interesting concept. [00:59] I'm sure Filipe would be OK with copying the code from Catia. [01:00] not just for rtpmidi, but also for USB audio devices that are not yet connected using zizta-ajbridge (there is a new version BTW) and AVB or aes 67 end points that are available but not yet connected. [01:01] in other words the discovery info of possible connections [01:02] The patch pannel would start the connecting SW at the time the connection was asked for. [01:02] and then connect it [01:03] That's a really cool concept. [01:03] If anyone can pull it off, it's you. [01:04] I would probably use the patchbay method used by Ardour (and many other patch bays) rather than patchage or qjackctl connections [01:05] That's fair. It's not a bad patchbay method. Patchage/Carla connections are easier for my head to wrap-around, personally, because I think in terms of connecting devices together. [01:05] Eickmeyer[m]: they are both great for small numbers of ports [01:06] Eickmeyer[m]: have you tried to play with even a 10strip Ardour session using one of those patch bays? [01:06] That's true. When connecting a lot of ports at once, the Ardour method is better. [01:06] Hehe, I've done 32-strip. [01:08] Really, more like 36-strip after adding a few effects busses. [01:08] right, it is doable, but a lot of wires in patchage and a lot of scrolling in qjackctl [01:09] I don't touch qjackctl anymore. :P [01:12] but if you look at pretty much all of my sw, it is control stuff [01:13] I have not done any dsp for example [15:42] OvenWerks: Wishlist-item for Controls: a system tray indicator that shows Jack's state. [15:42] Came up while your client was dead. [15:45] :P [15:45] Eickmeyer: https://askubuntu.com/questions/1225047/ubuntu-studio-20-04-firewire-compatibility relevant [15:45] for your attention [15:45] (I'mma close as Offtopic because 20.04 but something you might wnat to look at) [15:45] systray stuff was already hard the indicator stuff (when I looked at it) was to new to find reasonable documentation on it [15:52] teward: We removed the non-ALSA firewire support, proved to be too problematic to support ancient, no-longer-being-produced devices. [15:52] ack i'll write that reply [15:53] @teward001 I am already writing something [15:53] How is the team, who are the people and their positions or responsebillities. Who else does marketing/social media/communication for Ubuntu Studio? [15:53] teward: Also, Ask Ubuntu is an official support channel for all flavors. [15:53] @OvenWerks Eickmeyer already got it [15:53] @Eickmeyer yes, I know. I'm a moderator there [15:53] *throws salt on you* [15:53] but it's a 20.04 question ;) [15:54] there's restrictions on those [15:54] @teward001: doesn't support means we can't help if you can't get it to work. [15:54] @OvenWerks [ @teward001: doesn't support means we can't help if you can't get it …], this is true, however that's also still irrelevant to MY point - an answer of "Firewire isn't supported anymore" is a valid answer in those cases [15:54] Christoffer[m]: Marketing/social media/communication is mostly myself and @azbutlutlu. [15:54] but it's a 20.04 question which is one we usually snipe :P [15:54] but in this case it's able to be answered [15:54] it showed up in the flags so :P [15:54] (again I'm a moderator on Ask Ubuntu - I SEE YOUR IPS!) [15:55] *shot* [15:55] Weird flex, but ok [15:57] * OvenWerks thinks he had a nicer answer.... but couldn't login [15:59] I see [15:59] I take it you are basically the community manager as well? [15:59] Christoffer: I'm the Project Leader. [16:00] In Ubuntu terms, I'm the flavor lead and point-of-contact. [16:00] That's mostly an intra-Ubuntu thing. [16:00] Eickmeyer [16:01] ....yes? [16:55] what eickmeyer is trying to say is that he is the communication with me trying to hold mastodon side upright and being second eyes on release notes or website related things when I can. [16:56] ^ Facts [16:56] that is pretty much the summary of the current situation on pr/communications [16:58] I also try to do or at least review art/design when I can. eickmeyer does leading and packaging he knows better than I who does what on technical side. (I only know owenwerks is basically THE ubuntustudio-controls. <3) [17:00] i'm sort of the support role, testing, helping with packaging, sponsoring package uploads when people in the team don't have upload rights, etc. [17:00] Christoffer: ^ [17:00] but i also bother the heck out of Eickmeyer just because ;) [17:00] I'd consider OvenWerks the development lead. [17:01] i agree with that [17:01] (Thomas thanks for graciously explaining that instead of laughing at me for still not having caught up to what is happening here) [17:02] oh i'm laughing at you [17:02] i'm just not making it known xD [17:03] fair enough xD [17:03] Don't take it personally, @azbulutlu . @teward001 laughs at everytone and everything. [17:03] *everyone [17:03] and sometimes I just rage at everyone too [17:03] esp. on bad days :P [17:03] but that's just me [17:03] ^ Facts [17:03] in all fairness I am laughing at myself. and lol [17:03] <3 [17:06] ahh, that also does community management and social media [17:23] Christoffer: Does that help with what you need? [17:25] (also christoffer when you sort out the pgp thing do email me for the mastodon password.) [17:59] Ahh, I see [18:00] It's easier when one kind of know where people are at and stuff [18:00] I'll sort the email stuff soon^^ [18:01] Who is the media contact? [18:02] I'm guessing it's you Eickmeyer [18:02] ERR:DrAppt [18:03] huh? [18:03] Christoffer: Yes, that's correct. [18:03] I have a telephone doctor appointment right now. [18:04] Okay [18:21] * Christoffer[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/eOpUreunfudZVKFzbmspjBNX > [18:21] My conferance room tool of choice is Jitsi. [18:21] Well, I'm pretty much homeschoolilng my son at this point, so it's very difficult at this time. [18:22] Christoffer: for the Telegram bridge, you'll need to use a @ to ping them. [18:22] @azbulutlu ^ [18:23] ah! [18:23] Thanks! [18:23] Yeah, it doesn't need to be as soon as possible, but I rather get the question out of the way. [18:24] * Yeah, it doesn't need to be as soon as possible, just rather getting the question out of the way so I can move on. [18:26] If we can worry abou that stuff after the 20.04 release, I'd prefer it since we'll have some time between then and when GG opens. [18:26] Ah, i see [18:27] For now, do what you can on your own and present it to us then. Simply use good judgement. :) [18:31] Personally it would be the most superb to have it done before the release as the release is the biggest message to push and with a good strategy and plan one can enhance the engagement and reach. But I do acknowledge constraints and I trust in your judgement as the project leader. [18:31] also I just discovered I DO have a matrix account. trying very hard to get on devel channel via ther [18:31] there* [18:32] When it comes to what I can do on my own it's incredibly helpfull to have input from you guys to decide as i don't have a full picture and don't know what the team is going for. Like IDK if you guys think this and that group is something you want to go for. [18:33] @azbulutlu check your invite. :) [18:34] YAY! [18:34] Eyy [18:34] eylul, Christoffer : You can transfer the password via direct message, just make sure it's encrypted using the direct message properties. [18:35] Nice little Matrix feature. :) [18:35] 🥳 [18:36] Ok. Looks like you're not bridged? Something's not right. [18:37] eylul: ^ [18:37] You're not showing up on the IRC side. [18:37] I can invite you to a room to see why you're not bridging correctly. [18:42] I had joined as a guest that might be why [18:42] Ohhhh... yeah, maybe. [18:44] Doesn't look like it. [18:46] Can't see you in the IRC side. Can't see you on Telegram either. [18:46] I mean, I can see you on Telegram in IRC, just not your Matrix in IRC. [18:47] It might be because you have to authenticate to Freenode's nickserv. [18:48] Hehehe [18:50] shouldn't have any effect, since the IRC channel isn't +r [19:02] dax: That's probably right. [19:02] Nope, didn't work. [19:03] I think it might be broken in the IRC bridge. Happened to me once before. [19:03] gotta love the matrix bridge [19:03] but yeah, my guess would be their IRC ghost user either didn't connect or didn't try joining for some reason [19:04] dax: Most likely. I've had that happen and they had to fix it internally in the bridge. [19:04] * OvenWerks finds IRC just works ;) [19:04] OvenWerks: You say that repeatedly, but most of the general public has no idea it even exists. [19:05] *agrees with ovenwerks but needs to fix the logging with a solution that is not znc* [19:05] * OvenWerks also uses a text only client (irssi) which would confuse some people [19:08] @azbulutlu [*agrees with ovenwerks but needs to fix the logging with a solution that is not …], I find Quassel is quite easy. [19:09] I'm considering switching to weechat though, but it's not a priority. [19:17] eylul: Nope, didn't work. [19:17] eylul: can't read your message before you accept my verification request [19:17] 😠 [19:18] Eickmeyer: what's their MXID? [19:18] dax: eulul:matrix.org [19:18] *@eylul:matrix.org [19:19] Christoffer I accepted it about 5 minutes ago. [19:20] Says to me you haven't responded [19:20] dax: @rodericuus:matrix.org was having the same issue in #ubuntustudio-offtopic's Matrix equivalent. [19:20] today? [19:20] dax: Yes. Just earlier. [19:20] About 15 minutes ago. [19:20] *just gives up* can you send it again? [19:20] IDK what it's about. Could be a homeserver thing, matrix.org has a tendency to be slow [19:22] I'm trying to get Matrix staff to look at this now. [19:22] christoffer which device are you at? mobile or desktop? [19:22] #MatrixIsBroken heh 😜 [19:22] They're pretty responsive usually. [19:22] i just poked freenode staff to ask if matrix filled up their i-line again [19:22] I broke matrix [19:23] 'cause that's my current suspicion [19:23] dax: Sounds about right. [19:24] I'm on my pinebookpro 😎 using the webbrowser version of riot [19:25] on the privacytools.io matrix homeserver [19:25] Christoffer: Yeah, that doesn't really matter too much in this case. [19:29] eylul: Christoffer is showing up properly in IRC. [19:29] nice [19:29] yeah not sure why this is happening but I dont want to clog devel list with this anymore [19:30] It's OK. I'd rather we troubleshoot communication problems since that inhibits devel anyhow. [19:32] I actually did a legacy thing before. Tried to accept this one but took forever to confirm it [19:33] if you can see the contents now let me know? [19:34] I can't [19:35] Christoffer[m]: Do you use Telegram? [19:35] *starts laughing* [19:36] It kind of annoys me that the matrix.org server is the weak link (IDK if it is this time, but usually is) [19:36] They don't really to spread out the users like with joinmastodon.org either [19:37] No. I'm on Matrix and XMPP [19:37] Assuming it's the matrix<->IRC bridge, that's a single point of failure hosted by matrix.org. The current matrix bridging model doesn't allow for decentralized bridging. [19:37] https://send.firefox.com/ might be an idea. [19:37] And with email those are all my communication things [19:37] * It kind of annoys me that the matrix.org server is the weak link (IDK if it is this time, but usually is) [19:37] They don't really try to spread out the users like with joinmastodon.org either [19:38] dax: Yeah, it's a pain, but it's better than Telegram bridging in my experience. [19:38] we need a password solution [19:39] anyway. asked fn staff, the response i got was "looking at it now", dunno if i'll get further info [19:39] like I don't know nextcloud? [19:39] thanks dax [19:39] @azbulutlu [we need a password solution], Did you see the Firefox Send link I posted? That might be good for sending an encrypted file. [19:40] @azbulutlu [like I don't know nextcloud?], I have a nextcloud instance. [19:41] checking it now [19:41] doesn't nextcloud have a password management addon? [19:42] @azbulutlu [doesn't nextcloud have a password management addon?], It does and I use it. [19:44] Eickmeyer: apparently their i-line isn't full. If/when you get a response from matrix.org, I'd be interested to know what the reason ends up being. [19:50] dax: I'm still waiting for a response. [19:50] ok.. a few bytes of information finally got transmitted via matrix [19:50] \o/ [19:51] *headdesk* [19:52] Thanks are a-ok [19:52] * Things are a-ok [19:54] *is still laughing* [19:58] ok so basicaly current solution has been to manually post that there is a blog post on twitter and it being mirrored to mastodon. the mirror to mastodon is very recent. replies remains in each community and nothing else is cross posted. if you want to do both manually sure, but I know I missed posts before because I missed them on the b [19:58] log [19:58] :) [20:03] 👍️