[17:33] <Eickmeyer> teward: Have you spun-up a test for the new website theme? Eylul went over it and couldn't find anything obfuscated.
[18:18] <teward> Not yet but my code review turned up nothing either
[18:18] <teward> I’d say just use it
[18:18] <teward> I have a lot of crazy atm to deal with
[18:39] <Eickmeyer> teward: Ack.
[19:15] <OvenWerks> Eickmeyer: jack_mixer: has error messages on run. It does run. It complains about not having lash (yeah!) which is fine. It also complains about "Cannot load Python bindings for GConf"
[19:15] <OvenWerks> Which means preferences will be lost from run to run.
[19:16] <Eickmeyer> OvenWerks: Yeah, i noticed that. Did you save the mixer? Also, I noticed that jack-mixer is pretty much dead.
[19:17] <OvenWerks> I figured that may be true as well.
[19:17] <Eickmeyer> Honestly, the mixer functions in Ardour are far superior.
[19:17] <OvenWerks> but... it is written in python.
[19:18] <OvenWerks> If all someone wants is a jack output mixer, Ardour is a bit much to load
[19:19] <OvenWerks> but it does have a c componant it looks like
[19:20] <OvenWerks> but a c bit would probably not need to be kept up. The python will be 2 and the gtk is probably 2 as well
[19:21] <Eickmeyer> It's both python 2 and gtk2. Unless it can be upgraded to python3, it might be dead.
[19:21] <Eickmeyer> As in, we might have to remove it from the seed.
[19:22] <Eickmeyer> Last release was 2014.
[19:23]  * OvenWerks is getteing tired of loosing sw that works fine for these kinds of reasons.
[19:24] <Eickmeyer> Hmmm...
[19:24] <OvenWerks> if jack_mixer a separate package on it's own?
[19:24] <Eickmeyer> trebmuh: You had the last commit to jack-mixer. Got any thoughts?
[19:24] <OvenWerks> s/if/is/
[19:25] <Eickmeyer> Yes. It's jack-mixer, not jack_mixer.
[19:25] <Eickmeyer> https://salsa.debian.org/multimedia-team/jack-mixer/tree/master/debian
[19:25] <Eickmeyer> Rather... https://salsa.debian.org/multimedia-team/jack-mixer
[19:28] <OvenWerks> the question is if it is easier to fix this or package nonmixer
[19:28] <OvenWerks> or build a whole new one.
[19:53] <Eickmeyer> OvenWerks: That's the thing. In order to package NSM or Nonmixer, the entire non suite has to be packaged. BUT, it relies on git checkouts, which is non-ideal.
[20:19] <Eickmeyer> OvenWerks: Also, a deal-breaker for me is that Non Mixer doesn't take MIDI. OSC only.
[20:25] <OvenWerks> Eickmeyer: ya, jack-mixer is better that way, but doesn't load plugins... of course nonmixer is lv1 only.
[20:25] <Eickmeyer> OvenWerks: Yep, which makes no sense to me.
[20:25] <OvenWerks> The ideal thing IMO, would be a mixer that is integrated into the jack back end
[20:25] <Eickmeyer> Might be easier to update to Python 3 for jack-mixer, but that might require a fork.
[20:25] <OvenWerks> but that will not happen
[20:26] <OvenWerks> I am willing to do a fork for that purpose.
[20:26] <OvenWerks> the gtk could be updated to 3 as well
[20:27] <OvenWerks> I think glade will take the gtk file and hilite things that need to be changed
[20:29] <OvenWerks> Maybe I should revisit gtkmaster after that.
[20:31] <OvenWerks> Eickmeyer: If I feel u0p to it I will fork->fix->pr upstream as well
[20:34] <Eickmeyer> OvenWerks: Ok, sounds good. We can fork it to ubuntustudio-jack-mixer or something like that? nm, I'll leave it up to you.
[20:37] <OvenWerks> be nice if it could see keyboard vol-up/down as well :)