diff options
Diffstat (limited to 'AudioManagerDaemon/docx')
| -rw-r--r-- | AudioManagerDaemon/docx/04_y_audiomanager_and_sources.dox | 4 | ||||
| -rw-r--r-- | AudioManagerDaemon/docx/06_classification.dox | 4 | ||||
| -rw-r--r-- | AudioManagerDaemon/docx/14_misc.dox | 2 |
3 files changed, 5 insertions, 5 deletions
diff --git a/AudioManagerDaemon/docx/04_y_audiomanager_and_sources.dox b/AudioManagerDaemon/docx/04_y_audiomanager_and_sources.dox index 113cf6b..fd0f1e3 100644 --- a/AudioManagerDaemon/docx/04_y_audiomanager_and_sources.dox +++ b/AudioManagerDaemon/docx/04_y_audiomanager_and_sources.dox @@ -30,7 +30,7 @@ sources and sinks since the routing adaptor will take care of handling some of t Here are some informations that is believed to be actually communicated to the sources and sinks: \section conFormats Connection Formats - The am::am_ConnectionFormat_e formats for a connection are chosen when the connection is build up. So if there are more than one possbilities + The am::am_CustomAvailabilityReason_t formats for a connection are chosen when the connection is build up. So if there are more than one possbilities that can be used for a connection (am::am_Sink_s::listConnectionFormats and am::am_Source_s::listConnectionFormats) the correct one is chosen upon a connect. If this is relevant to the sources and sinks, the routingAdaptor must communicate to the sources and sinks accordingly. \image html SettingConnectionFormats.png @@ -43,7 +43,7 @@ Here are some informations that is believed to be actually communicated to the s \section avail Availability This diagram shows the sequence that is used to communicate the availability am::am_Availability_s. from the sources. Please note that the availability reasons - am::am_AvailabilityReason_e are product specific. + am::am_CustomAvailabilityReason_t are product specific. \image html AvailabilityofSources.png Here is the same for the sinks: \image html AvailabilityofSinks.png diff --git a/AudioManagerDaemon/docx/06_classification.dox b/AudioManagerDaemon/docx/06_classification.dox index ccedffc..0fb72cd 100644 --- a/AudioManagerDaemon/docx/06_classification.dox +++ b/AudioManagerDaemon/docx/06_classification.dox @@ -23,8 +23,8 @@ but the parameters of the Classes itself are product specific and have to be interpreted by the AudioManagerController. This concept allows for very individual implementations of system behaviors.\n Since Classes are held in the database, Classes can be registered and deregistered during runtime, it is recommended that the AudioManagerController enters - all source & sink classes at start-up into the database.A ClassProperty exists out of an enumeration (am_ClassProperty_e, project specific) and a corresponding - value (integer) that is interpreted by the AudioManagerController according to am_ClassProperty_e.\n + all source & sink classes at start-up into the database.A ClassProperty exists out of an enumeration (am_CustomClassProperty_t, project specific) and a corresponding + value (integer) that is interpreted by the AudioManagerController according to am_CustomClassProperty_t.\n There is no restriction to the number of properties a class can have and how many classes can exist in a system.\n \section attributes Attributes - am::am_SourceClass_s describes the attributes of a source class\n diff --git a/AudioManagerDaemon/docx/14_misc.dox b/AudioManagerDaemon/docx/14_misc.dox index 7b3f950..8ae15c2 100644 --- a/AudioManagerDaemon/docx/14_misc.dox +++ b/AudioManagerDaemon/docx/14_misc.dox @@ -22,7 +22,7 @@ Every flow of audio is using a format to exchange data. The format that the sour experience. It is common that sources and sinks are capable of supporting more than one audioformat.\n So all sources and sinks register with a list of connectionFormats that they support and for each connection a format must be chosen that is then used to transport the audio data. Gateways (and Soundconverters) have the information which connectionFormat can be transformed into another one. -am::am_ConnectionFormat_e has all formats listed.\n +am::am_CustomAvailabilityReason_t has all formats listed.\n There is a special usecase that is worth showing as an example in this regard: the change of a connectionFormat when switching from one song to another. Here is an example of how the project specific parts could handle this: \image html ChangeofAudioformatduringplaytime.png |