1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
|
# 4a-tools
4a-tools is a set of simple scripts that can be used to test and troubleshoot 4a framework.
## 4a-status
4a-status gives a diagnostic whether 4a-framework is supposed to be working or not.
```bash
user@machine$ 4a-status
---- Audio cards detected ----
card 0: Loopback
card 1: Intel
---- snd-aloop driver availability ----
SUCCESS: Built into the kernel
---- 4a service status ----
SUCCESS: Service is currently running!
```
If any error is shown then there is no way that 4a-framework can work.
Not running services do trigger only a warning because you may have started the service's binding manually and the script cannot detect this.
If you don't, this must be considered as an error, because 4a-framework obviously cannot work when binding are not running.
```bash
---- Audio cards detected ----
card 0: Loopback
card 1: Intel
---- snd-aloop driver availability ----
SUCCESS: Built into the kernel
---- 4a service status ----
WARNING: Service is not currently running!
It can be started using the following command:
systemctl restart *agl-service-audio-4a*.service
```
## 4a-api
This script let you call 4a's APIs to test bindings and get some infos.
### Ping API
Pinging an API let you know that the binding providing this API is running and ready.
```bash
user@machine$ 4a-api api smixer ping
Detected systemd unit file!
Port detected: 1025
ON-REPLY 1:smixer/ping: OK
{
"response":3,
"jtype":"afb-reply",
"request":{
"status":"success"
}
}
```
### List HALs
You can list availables HALs using the following command:
```bash
user@machine$ 4a-api hals
Detected systemd unit file!
Port detected: 1025
ON-REPLY 1:4a-hal-manager/loaded: OK
{
"response":[
"4a-hal-intel-qemu"
],
"jtype":"afb-reply",
"request":{
"status":"success",
"info":"Requested data"
}
}
```
If the returned list is empty, this mean that no HAL is loaded and ready. In such a case you won't be able to use 4a-framework because this mean that there is no device to play audio on.
To get more information about a HAL, you can call it's **info** verb:
```bash
user@machine$ 4a-api api 4a-hal-intel-qemu info
Detected systemd unit file!
Port detected: 1025
ON-REPLY 1:4a-hal-intel-qemu/info: OK
{
"response":{
"streams":[
{
"name":"multimedia",
"cardId":"hw:0,0,2"
},
{
"name":"navigation",
"cardId":"hw:0,0,3"
},
{
"name":"emergency",
"cardId":"hw:0,0,4"
}
],
"playbacks":[
{
"name":"playback",
"mixer-name":"INTEL-QEMU:playback"
}
],
"captures":[
{
"name":"capture",
"mixer-name":"INTEL-QEMU:capture"
}
]
},
"jtype":"afb-reply",
"request":{
"status":"success",
"info":"Requested data"
}
}
```
This allows you to get which device is bounded to which stream.
Please note these are stream names, not roles name.
In addition, multiples HALs can provide the same stream.
Nowadays, it result in a race condition: 4a-framework using the first HAL providing the stream.
### List roles
This let you get the list of available audio roles.
Only roles with a bounded device are listed here, because roles without a devices are pretty much unusable.
```bash
user@machine$ 4a-api roles
Detected systemd unit file!
Port detected: 1025
ON-REPLY 1:ahl-4a/get_roles: OK
{
"response":[
"radio",
"multimedia",
"emergency",
"navigation"
],
"jtype":"afb-reply",
"request": {
"status":"success"
}
}
```
## 4a-play
4a-play let you play some audio file on a specified device, with an optional audio role.
```bash
4a-play <file> <device> [role]
```
Where *file* is the path to the file to play, *device* is the device to play on and and *role* is the 4a audio role to open (multimedia for example).
The specified role should be the one that is bounded to the specified device, however the script is not able to detect it so there is no control about this. The role is opened before playing the audio file, and closed after playing is over.
So for example:
```bash
4a-play Happy_MBB_75.ogg hw:2,0,0 multimedia
```
>**NOTE**: For now you have to specify the device and the role. Future version of this script may detect devices and roles relations so that you will be able to omit either role or device.
>
>The device that usually match "multimedia" is "hw:0,0,2" (for more details please read the [HALs](HALs.md) section).
|
