[17:41] <OvenWerks> Eickmeyer[m]: Talking more with Rick about firewire... He tried again with everything stock. This works... sort of.
[17:41] <OvenWerks> Audacity can see the device and can use it.
[17:43] <OvenWerks> Then he did the most obvious thing and started ffado-mixer to turn the phantom power on which actually worked but then phantom turned itself off and he got the dying off audio as it did. The device then reset itself :)   :P
[17:44] <OvenWerks> I wish ffado-mixer would just not work at all when the firewire device is being used as an ALSA device.
[17:45] <OvenWerks> So anyway, the documentation needs to include a warning not to try using ffado-mixer!
[17:45] <Eickmeyer> Yeah, that's a pain.
[17:45] <Eickmeyer> So, then that begs the question as to if ffado-mixer needs to be removed from the seed.
[17:46] <OvenWerks> I have asked Rick to try again and see if alsamixer has all the controls needed to run the unit. (Phantom power etc.)
[17:46] <OvenWerks> I hope to find out if alsa is complete enough
[17:46] <Eickmeyer> Yeah. Otherwise, it might be back to the drawing board?
[17:47] <OvenWerks> However, if we set -controls up to enable ffado drivers we should also be able to disable the ffado-mixer menu item
[17:47] <Eickmeyer> True.
[17:48] <OvenWerks> or even make it run alsa-mixer in a terminal ;)
[17:48] <Eickmeyer> Nah, that'd be hacky.
[17:48] <Eickmeyer> There's also qasmixer, which is basically a gui for alsamixer.
[17:48] <OvenWerks> Yes.
[17:49] <OvenWerks> I wonder if it has a system default configure
[17:49] <Eickmeyer> I'd look, but I'm getting ready to test the latest daily.
[17:50] <OvenWerks> It defaults to Mixer device "default" which is pulse. I would like it to default to "hw:Card"
[17:50] <Eickmeyer> Right. That's par for the course for alsamixer.
[17:53] <OvenWerks> The man page gives no idea
[17:54] <OvenWerks> There are no files installed that look like a config
[17:58] <Eickmeyer> So, that means it's hard-coded. :/
[17:58] <OvenWerks> Anyway, at this point, I want to see the final outcome from Rick's experiments
[17:58] <OvenWerks> yes it is. The device can be set on the commandline
[17:59] <Eickmeyer> If that's the case, then maybe modify the .desktop file?
[17:59] <OvenWerks> But if we set it to hw:0 or card 0
[17:59] <OvenWerks> that means the user always has to change it to hw:2 or whatever.
[17:59] <Eickmeyer> Ah, yes. :/
[18:00] <OvenWerks> Right now it opens at the device layout from last time
[18:00] <Eickmeyer> Then a button that launches it from -controls set to whatever is master?
[18:00] <OvenWerks> That would be possible yes.
[18:01] <Eickmeyer> Seems like the best option we've got.
[18:02] <OvenWerks> qasmixer --device=hw:M66 works here.
[18:03] <Eickmeyer> Sweet. We have either a workaround or a solution.
[18:03] <OvenWerks> qasmixer has a real problem deciding if a control is an input or output
[18:05] <OvenWerks> All of my devices have at least some controls that show as both inputs and outputs and changing one changes the other.
[18:05] <Eickmeyer> That's not ideal.
[18:06] <OvenWerks> last update is end of 2016 so probably not quite dead.
[18:07] <Eickmeyer> It's definitely approaching senile, though.
[18:07] <OvenWerks> I would almost like to fork it...
[18:07] <Eickmeyer> Ubuntu Studio Mixer!!!
[18:07] <OvenWerks> It was upgraded to QT5 at least.
[18:10] <OvenWerks> Actually I would be better off to start over I think. It would take less time as I would not have to A)learn QT or B) figure out how they did things.
[18:10] <Eickmeyer> Oh, okay.
[18:10] <OvenWerks> It could be written in python or tcl/tk or whatever.
[18:11] <OvenWerks> But it does look like we need a good ALSA mixer
[18:12] <Eickmeyer> Agreed. alsamixer itself isn't ideal. ncurses interfaces aren't exactly intuitive anymore.
[18:13] <OvenWerks> It would be nice to do a jack router as well. Like patchage, but show unused alsa devices as well (in an off colour) that get auto connected to jack vai zita-ajbridge when connected on the GUI
[18:13] <OvenWerks> (and become an "On colour ;)
[18:14]  * OvenWerks has a longterm goal to show and end point on the network this way as well
[18:14] <OvenWerks> s/and/any/
[18:15] <Eickmeyer> That would be really cool.
[18:15] <Eickmeyer> Looks like there used to be a gnome-alsamixer, but it's long dead.
[18:16] <OvenWerks> most of the alsa mixer GUIs do not give _all_ the controls. That was what I liked about QASmixer
[18:26] <OvenWerks> QASmixer aslo lays tings out nicer. Most gui alsa mixers go for a minimum look that fits well with a popup/down from systray with just the controls the user needs for desktop use. QASmixer thinks like an Application and tries to lay things out like a HW mixer.
[18:29] <Eickmeyer> Yeah. Just tried "alsamixergui" and it's garbage.
[18:35] <OvenWerks> Ya, I went through everything I could find before we put QASmixer in
[20:06] <Eickmeyer> !ubuntustudio-installer | OvenWerks: I did another thing