FreeCalypso > hg > freecalypso-hwlab
comparison audio-tones/README @ 164:9336a48746d9
audio-tones: experimental tools and findings
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Sat, 13 Nov 2021 04:49:06 +0000 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
163:5f9dd4056420 | 164:9336a48746d9 |
---|---|
1 As of 2021-11, we are still far away from being able to clean up the | |
2 implementation of audio tones in our handset UI fw: before we can clean up the | |
3 implementation of audio tones, we will first need to detangle the wrong-minded | |
4 coupling between these audio tones and the buzzer, and that detangling will | |
5 require a development platform with a working buzzer, which means FC Venus. | |
6 | |
7 However, we can apply a band-aid fix to the current misdesigned Condat audio | |
8 driver that would allow keybeep tones to be re-enabled on FC Luna with FC-HDS4 | |
9 without being brutal on the developer-operator's ears: we can change the dBfs | |
10 amplitudes baked into F_xxx defined constants, and we can conditionalize this | |
11 change on CONFIG_TARGET_LUNA. With this method we are constrained to picking | |
12 just one amplitude for the 3 different tones based on F_425 (busy, CW and | |
13 ringing) and likewise the same amplitude between the half-tone of keybeep and | |
14 the low tone of DTMF - but we are not seeking fully optimal tuning here, only a | |
15 band-aid fix to protect the developer-operator's hearing. | |
16 | |
17 The set of shell scripts contained in this directory was put together to | |
18 facilitate easier experimentation with different amplitudes, easier than | |
19 entering full AT@TONE commands manually. | |
20 | |
21 Amplitude selections being made for now: | |
22 | |
23 Keybeep-half and DTMF-low: -26 dBfs | |
24 DTMF-high: -24 dBfs | |
25 F_425 tones: -21 dBfs |