Hi,
if all volumes are max on module insert. the ftu is essentially unusable untill they're corrected
Yes, the current defaults for the FTUs are horrible.
But I don't know if I really like the "diagonal" state that you proposed as a default state. At least for my setup it's not more usable than the "all-volumes-maxed" state. I probably would prefer a "everything-muted" default. Then you only have to deal with the controls you actually need and don't have to bother with tons of other controls. (And, it's more in line with non-USB devices).
If there aren't any objections to the "everything-muted-by-default" approach, I will prepare a patch this weekend.
What about alsactl? Set the mixers once, then call "alsactl store". Does that help?
Yes, for sure. That's what I have been using for a long time. It would be desirable though if the state was stored on diconnect/shutdown of the device. Is this possible with a udev rule?
While we're at it I would even like to discuss the FTU's control naming scheme again. As someone (Grant?) was pointing out some time ago the capture volumes really are no capture volumes. It just came in handy to name them this way to easily switch between both groups of control in alsamixer etc.
Suggestions anyone?
Regards, Felix