FR: AudioParameterBool/Choice/Int/Float -> public getText/getValueForText

Well yes, just for flexibility. For example getValueForText() could be used to evaluate the right value from a text, even when its uses a different unit

“2k” -> 2000 -> 0…1
"2ms" -> 0.002 -> 0…1
"violet" -> purple -> 3 -> 0…1

getText()
0…1 -> 1000 (kg) -> tonne
0…1 -> 60 (s) -> 1 minute

(i’m aware that getText/getValueForText() expect the normalised value as parameter/return value, may be this should be added to the documentation)