Managing alsa scenarios and possible issues

[Nicola Mfb]

On Thu, Jul 15, 2010 at 8:13 AM, Al Johnson <alastair at truebox.co.uk> wrote:
[...]
> I believe this is correct, and I think it was encountered by someone testing
> my simplemixer. The symptom fitted, and neither of us managed to reproduce it,
> so that was my best guess as to the cause.
>
> I'm sure I proposed an API modification to get around this, but I can't find
> it now :-/ Essentially I wanted to add SaveCurrentScenario() as that's what an
> app usually wants to do anyway. In the race case we lose the scenario we
> wanted to save, but we don't overwrite another scenario. It would probably be
> good to have some feedback as to which scenario was saved so that we know if
> we lost what we wanted. Keeping SaveScenario(s) means we don't break legacy
> apps, and we still have the option of saving to named scenarios if we really
> need to.

Did you get feedbacks about that? was a bug filed?

Thanks

    Niko