<html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">Tanu Kaskinen wrote: </div> <blockquote cite="mid:1471446676.9375.61.camel@iki.fi" type="cite"> <pre wrap="">All these use cases seem like they deal only with the descriptions. You made earlier a distinction between card names and card descriptions, and it's unclear where you'd need to care about the card name.</pre> </blockquote> Thanks as ever for your time and insights Tanu. Deeply appreciated. Forgive the confusion. I had not intention of alluding to a change in card name per se. I mentioned the idea of a localname only (not meaning to replace a name or id or any other property that already has meaning and function in some context but as a place to store a name that can be edited by the system admin to read meaningfully for a given card/port to users of the current system). It seems that description is intended to fill that need, so totally no need for another property like localname. It seems from what your saying that: a) providing such descriptions from the lowest level not the highest,is desirable so that consistent descriptions reach all apps and efforts are not duplicated. b) pulseaudio already has the infrastructure for saving and remembering such descriptions and ALSA probably not. So pulseaudio may be sensible place to see it implemented. Such features may even be a feather in the cap of pulse. c) at the pulseaudio level there are already description properties available (on sinks, cards and ports) and all it would take to allow tweaking them is an interface of sorts (update-sink-description, update-card-description, update-port-description?). Not sure if these stored descriptions survive the unplug, plug scenario mind or if they are overwritten when replugged. It seems to me that on MINT at least the Sound settings and the System tray sound app list output devices differently (superficially it looks like one lists ports the other sinks). Either way, I'm curious if pulse publishes a document or spec which stipulates what the expected (planned for) manner of describing sinks, cards and ports in apps is, in order to promote consistency? Bernd. <pre wrap=""> </pre> </body> </html>