[16:44] <Eickmeyer> OvenWerks: Do we have anything to add to the release notes? https://wiki.ubuntu.com/DiscoDingo/ReleaseNotes/UbuntuStudio
[17:16] <OvenWerks> Eickmeyer: I don't know if it is worth mentioning that -controls is now the prefered method of starting jack or not.
[17:16] <Eickmeyer> OvenWerks: That might be good, and I thought we did that for 18.10, but it's not bad to reiterate.
[17:16] <OvenWerks> Eickmeyer: people may question the line: "If you need Long Term Support, it is recommended you use Ubuntu Studio Bionic 18.04 instead."
[17:17] <OvenWerks> As 18.04 was not released as LTS
[17:17] <OvenWerks> I think it is right though
[17:17] <OvenWerks> because the repos are lts
[17:18] <Eickmeyer> OvenWerks: Maybe modify it to be "If you need Long Term Support, it is recommended you use Ubuntu Studio Bionic 18.04 with the Ubuntu Studio Backports PPA."
[17:19] <OvenWerks> Sure. Speaking of which, if jackd2.0 comes out any time soon, it should be there too
[17:19] <Eickmeyer> Agreed. I think if it gets synced for EE, then we can backport it, but I hope we don't end up in dependency hell for that.
[17:19] <OvenWerks> (I can't remember if Falktx has released it or not)
[17:20] <Eickmeyer> Something like jackd2.0 would end up in Debian first.
[17:20] <OvenWerks> Jackd 2.0 is supposed to add any bits jackd1 has to jackd 2
[17:20] <Eickmeyer> Interesting, so backwards compatibility (finally).
[17:21] <OvenWerks> meta data, zita-ajbridge internally, etc
[17:21] <Eickmeyer> That would be good to have that running under one process as opposed to a cluster of external bridges.
[17:21] <OvenWerks> I don't think the internal zita-ajbridge will really help us... maybe.
[17:22] <OvenWerks> A plugged in USB device would still need an external bridge I think
[17:22] <Eickmeyer> You mean if hotplugged?
[17:23] <OvenWerks> jackd1 needs the bridge to be a part of the command line. maybe jackd2 will allow loading it after startup
[17:24] <OvenWerks> yes if hotplugged... even if not hotplugged, we want jack to keep running if the USB mic is unplugged
[17:24] <OvenWerks> Internal devices that can't be hot (un)plugged are ok.
[17:33] <Eickmeyer> Ok
[17:34]  * Eickmeyer is keeping a close eye on #ubuntu-release for the RC.
[17:41]  * OvenWerks has had more trouble with USB unplugging than the plugin.
[17:42] <OvenWerks> it seems unplugging a USB device freezes/zommbifys/whatever jackd before I can change the master device.
[17:43] <OvenWerks> So I have to kill -9 jackd before changing devices in that case
[17:44] <OvenWerks> In fact changing master devices on the fly has become less stable in the last jackd release.
[17:45] <OvenWerks> Even with the devices plugged in and running, switching from one to the other only works one or two times and then mucks jack up.
[17:47] <Eickmeyer> Yikes. Should we put that in the release notes (which I just updated big-time, btw): https://wiki.ubuntu.com/DiscoDingo/ReleaseNotes/UbuntuStudio
[17:47] <OvenWerks> Eickmeyer: I don't think so. SM is not something a lot of people use ;)
[17:49] <OvenWerks> https://wiki.ubuntu.com/DiscoDingo/ReleaseNotes/UbuntuStudio seems to be confused as to what release 19.02 is C or D
[17:50] <OvenWerks> It says "Getting Ubuntu Studio Cosmic Cuttlefish (19.04)"
[17:51] <Eickmeyer> Thanks for that catch. Fixed.
[17:51] <OvenWerks> right after it says: "Release Notes for Ubuntu Studio 19.04 Disco Dingo"
[17:51] <OvenWerks> looks good.
[17:53] <Eickmeyer> Cool. I'll probably be able to put a strikethru on the part about Ubiquity real soon since Ross and I fixed that, with Carlos Lobrano and the upstream developer's help.
[17:54] <OvenWerks> for: "NOTE: Derivitives of Ubuntu (Linux Mint, Kali Linux, etc.) are not supported." does that mean they are known not to work? That they have not been tried? That they likely work but don't ask help? ;)
[17:55] <Eickmeyer> They haven't been tested, and don't ask for help.
[17:55] <Eickmeyer> Basically, you're welcome to try it, but you're on your own.
[17:56] <OvenWerks> About what I thought. I expect it would for the  most part work with vanilla debian too.
[18:00] <OvenWerks> derivitives should just work but are often one or more cycles behind, sometime based on the last LTS plus one cycle
[18:06] <Eickmeyer> I just don't think it's something we have the resources to handle.
[19:04] <OvenWerks> right. I am not saying we should support it at all... though if someone asked about one of the dirivitives simply says the backports are valid starting based on ubuntustudio lts life
[19:05] <OvenWerks> they can figure out what they are using and do as they wish.
[19:06] <OvenWerks> but the statement "Not supported" is correct.
[23:56] <OvenWerks> krytarik: FYI, "Boost" is not turned off by default, but can be turned off (for better low latency performance) with -controls.
[23:57] <OvenWerks> krytarik: however, the boost speed will generally not show up unless the cpu is pushed quite hard.
[23:59] <krytarik> So there is switch for it in Controls too but they've overlooked it?