[04:37] <Eickmeyer[m]> OvenWerks: Any opinions on bug 1884472? 
[04:39] <OvenWerks> I suspect qjackctl had been run before controls or before upgrading the os.
[04:40] <OvenWerks> I say this because neither of us have had this problem with fresh install.
[04:42] <OvenWerks> however, I will add something that forces midi to none in controls.... I suppose we could force all settings to something sane. (even back to default)
[04:43] <OvenWerks> For example qjackctl also sets port maximum to 256 instead of default (2048)
[04:44] <OvenWerks> that made sense when memory was often 500Mb, but everyone is past 2Gb by now even over 10 year old machines
[04:46] <OvenWerks> I suspose we could just delete ~/.config/jack/conf.xml just before starting jackdbus. (which would overwrite the file anyway.
[04:47] <OvenWerks> So killall -9 jackd jackdbus, then rm ~/.config/jack/conf.xml, then start setting jackdbus to start.
[04:48] <Eickmeyer[m]> Could you write something to that effect in the bug report?
[04:51] <OvenWerks> ok
[05:56] <OvenWerks> Eickmeyer[m]: looking at my version of the same file, it only includes things that have been changed away from default. So the fact that this person even found that midi was set to raw proves it was not default. Removing that file seems the best thing so that other things don't crop up. I was already unsetting input device and output device so that using device will work as expected
[05:57] <OvenWerks> But I realize a user who has been using some other jack starter may have put who knows what junk in there and rather than setting _everything_ sanely, rm the file and start from default.
[05:58] <OvenWerks> This person upgraded from 19.10 where qjackctl was in plain view to 20.04 where qjackctl is hidden and -controls is in plain view :)
[05:59] <OvenWerks> upgrade from 19.10 to 20.04 will not reset that file. as I noted in the bug report.
[06:00] <OvenWerks> yes, qjackctl sets both input and output devices every time even if they are the same device.
[06:09] <OvenWerks> Eickmeyer[m]: should studio-controls have an install script in the repo?
[06:09] <OvenWerks> Eickmeyer[m]: like make install or something?
[06:10] <OvenWerks> Does that make it harder or easier to package?
[06:10] <Eickmeyer[m]> OvenWerks: I was considering just writing a simple "install.sh" script for you. It would be a good idea for more distros, and make things easier for Fedora, but I don't know if that would have any more advantages over what we already have.
[06:10] <Eickmeyer[m]> A makefile would be super universal, though.
[06:11] <OvenWerks> I am noticing that the build of mcpdisp it uses the install
[06:11] <OvenWerks> so is sh
[06:11] <Eickmeyer[m]> Yep, that seems about right.
[06:11] <OvenWerks> -controls is linux specific... dbus/logind/systemd for that matter
[06:12] <Eickmeyer[m]> Yep.
[06:13] <OvenWerks> ok, if you are writing a tool to do that.... I have other things to do
[06:13] <Eickmeyer[m]> Sure, that would be a pretty easy thing for me to write.
[06:13] <OvenWerks> I am looking at what I did in Ardour and about to change it again :P
[06:13] <Eickmeyer[m]> Just a simple install.sh would do the trick.
[06:33] <OvenWerks> Hmm, It would be nice to have the install script so I couold work on things without hand copying everything. but I also already have three or four files not in master :)
[06:34] <OvenWerks> I can't test on this machine (18.04 32 bit) anyway. so I will maybe hand install downstairs tomorow.
[06:36] <OvenWerks> I think I am almost done the Ardour patch. Once I patched it one place I realize I have another to do almost the same. Then I realized it is not quite right anyway.
[06:37] <Eickmeyer[m]> Oof, hate it when that happens.
[06:39] <OvenWerks> basically, I realized that the pan type can change after feedback is set up so I have to monitor pan type and remove monitoring of any controls not in use. Like width. (this all started with someone wanting width feedback)
[06:44] <Eickmeyer[m]> Ohhhhh, dang.
[06:44] <Eickmeyer[m]> So, complete rewrite then?
[06:45]  * Eickmeyer[m] needs to head to bed.
[06:49] <OvenWerks> night
[18:19] <OvenWerks> Eickmeyer[m]: the indicator we use for audio that assume does the kb vol+/- as well. Is there a setup for that? is there a way we can move what device it controls?
[22:00] <Eickmeyer[m]> OvenWerks: In Plasma, it always controls the default PulseAudio device. In Xfce, I think it's the same, but in that case it's a plugin as opposed to in Plasma where it's part of the system.