Will a configuration change automatically stop the device, or must it be
stopped before the configuration change happens?

In the latter it looks to me like "moving" the handle between my
suggested "configurator" and "proesseor" objects. who both provide
different APIs.

Regards Peter

Timur Doumler wrote on 19.06.19 17:22:
> Oh, and there should also be an arrow from “configuring” to “doing
> nothing”, because obviously the device can become unavailable while
> you are in the configuring state.
>
> Cheers,
> Timur
>
>> On 19 Jun 2019, at 18:13, Timur Doumler via SG13
>> <sg13_at_[hidden] <mailto:sg13_at_[hidden]>> wrote:
>>
>> Hi again,
>>
>>> On 19 Jun 2019, at 15:55, Peter Sommerlad (CPP)
>>> <peter.cpp_at_[hidden] <mailto:peter.cpp_at_[hidden]>> wrote:
>>> Drawing the actual state diagram of the lifetime of a system audio
>>> device can help to figure out where to make the cut and figure out,
>>> if there are even more things lurking, such as the interdependency
>>> of sample rate and buffer size.
>>
>> Here’s my very crude attempt at a state machine diagram for the audio
>> device.
>>
>> Cheers,
>> Timur
>>
>> <audio_device_diagram.png>
>> --
>> SG13 mailing list
>> SG13_at_[hidden] <mailto:SG13_at_[hidden]>
>> http://lists.isocpp.org/mailman/listinfo.cgi/sg13
>