[02:52] <Eickmeyer> OvenWerks: The Launchpad team was more than happy to raise the limit on both our autobuilds and the backports.
[05:43] <OvenWerks> cool
[05:45] <OvenWerks> It was more work that I thought to make pulse bridges able to be more than one :) Still have to test though
[06:50] <OvenWerks> only the first bridge auto connects to a device if specified. (need to check what happens if none is)
[07:20] <m_ad[m]> great, i read about the space issue the other day
[17:19] <OvenWerks> found another bug on the way to pulse bridge number... I think it is fixed now :)
[17:22] <Eickmeyer> Sweet. Is there any way we could allow custom naming for the pulse bridge(s)? Like, on a separate tab? That way, whatever application is assigned to whatever bridge could be named by the user to make routing in Jack easier.
[17:24]  * Eickmeyer noticed a new Calf release right around the same time as 19.04, will be looking at upgrading the package, putting it in the backports, and notifying Ross for upload to Debian/sync to Ubuntu.
[19:12] <OvenWerks> So does that mean you have tried the new -controls?
[19:16] <OvenWerks> I am not sure how many pulse bridges you expect people to use ;) I allow up to 9 and already think that is overkill. I expect one set for skype and one set for all the rest of the desktop will be all that anyone ever uses.
[19:16] <Eickmeyer> I agree, 9 is overkill. Where I'm at is to help people with knowing which pulse bridge is which without too much thought.
[19:17] <OvenWerks> The problem I see with naming, is that in order to to rename, all ports get deleted and remade. So if someone gets everything set up and then changes a name, all of there connections get lost.
[19:17] <Eickmeyer> Ohhhh... I see. Yeah, that could be bad.
[19:18] <OvenWerks> I picked 9 because that is the limit for one digit ;)
[19:18] <Eickmeyer> hehe
[19:18] <OvenWerks> disconnecting ports would get called a bug by at least some people
[19:21] <Eickmeyer> Just tried it. Selected 6 bridges. Only came back with 1.
[19:21] <OvenWerks> Right now I am not saving any info about bridges (other than number) and rely on system calls to clear all of them. With pulse it is hard to remove a single jack sourse/sink as you have to read through all of them and find out what the record number of that module is rather than just removing by name.
[19:21] <Eickmeyer> 1 stereo, that is.
[19:22] <OvenWerks> you have to logout/in or do: dbus-send --type=signal / org.ubuntustudio.control.event.quit_signal
[19:22] <OvenWerks> other wise the autojack you are running is the old one.
[19:23] <Eickmeyer> Oh yes.
[19:24] <OvenWerks> We can't do this from install because it is running as the user not the system and the install is done as the system.
[19:25] <Eickmeyer> Ah, I see. Something to add to ubuntustudio-system --fix?
[19:25] <OvenWerks> We could have the ping back changed from "pong_signal" to "V2_signal"
[19:26] <Eickmeyer> I have no idea what that does.
[19:28] <OvenWerks> I look for the pong signal in -controls to tell that autojack is running, if I look for a v2 signal the old version will not send that and so will send a quite_signal and then restart autojack.
[19:28] <Eickmeyer> Oh, that's not a bad idea.
[19:28] <Eickmeyer> A little hacky, but it gets the job done.
[19:28] <OvenWerks> So every time I change autojack I can up the version in both autojack and -controls
[19:29] <Eickmeyer> Yeah, that works.
[19:30] <OvenWerks> Next question.... the mixer start button... where should it be placed? on the bottom with the other buttons? (start, stop and apply)
[19:30] <OvenWerks> or under the jack status
[19:31] <OvenWerks> Or have a drop down that allows starting the mixer with whatever device they choose?
[19:33] <OvenWerks> yet another question: (or statement) It seems there are some devices (or subdevices) that jack can not start.
[19:34] <Eickmeyer> The start, stop, and apply buttons look fine where they are.
[19:34] <OvenWerks> For example, I have an AuodioPCI (Early 90s?) where AudioPCI,0,0 works fine but AudioPCI,1,0 is not accessable.
[19:35] <OvenWerks> Yes they look fine where they are should I add a 4th button to start the QASmixer in the same row?
[19:35] <Eickmeyer> Add two buttons below: one for QASmixer, the other vor PAVUcontrol.
[19:35] <Eickmeyer> *for
[19:36] <Eickmeyer> Because, if we're going to have multiple Jack bridges, people are going to want to route their applications.
[19:37] <Eickmeyer> By that same token, having one for Carla wouldn't be a bad idea either since that gives them access to their audio rack and patchbay for Jack.
[22:10] <OvenWerks> I will see what I can do...
[22:10] <OvenWerks> Maybe two rows then.
[22:29] <Eickmeyer> Cool
[22:30] <OvenWerks> Two rows means that one row controls Controls and the other starts extra stuff
[22:30] <Eickmeyer> Yeah.
[22:30] <Eickmeyer> Of course, by that same token, jack-mixer, but this can become a slippery slope.
[22:30] <OvenWerks> It does mean adding things to the depends...
[22:31] <Eickmeyer> Not hard.
[22:31] <OvenWerks> Well no but that means installing installer installs at least 4 extra applications
[22:32] <Eickmeyer> True. Can we have -controls look for if the applications are installed and then add the buttons dynamically?
[22:32] <Eickmeyer> Seeing if the file exists in /usr/bin would be one way.
[22:32] <OvenWerks> right.
[22:33] <OvenWerks> I don't know, I have been unable to make a button invisible so far.
[22:33] <Eickmeyer> Then what if it was simply disabled unless the corresponding application was in /usr/bin?
[22:34] <OvenWerks> How can we make the problem obvious to the user?
[22:34] <OvenWerks> If file not exist, open installer instead :P
[22:34] <Eickmeyer> If the button is disabled, the text should be gray. A help button would be one way to figure that out.
[22:35] <Eickmeyer> Another idea is to add apturl and point to a website with icons that, when clicked-on, open an "apt://" url that installs the application using apturl.
[22:36] <Eickmeyer> Xubuntu has something like that.
[22:36] <OvenWerks> I think one step at a time.
[22:37] <Eickmeyer> Gotcha. I'm going too fast. 
[22:37]  * Eickmeyer hits the brakes
[22:37] <OvenWerks>  I will add the three buttons and depends for now. In the Studio they will just work.
[22:37] <Eickmeyer> True.
[22:38] <Eickmeyer> back in a bit
[23:16] <Eickmeyer> Okay, I'm back.