GNOME Bugzilla – Bug 150523
only rate can be set for a speaker using festival
Last modified: 2011-10-14 10:50:37 UTC
For a speaker using festival, the pitch and volume cannot be set. Start test-speech program from gnome-speech/test directory. Select festival driver and choose first voice. Select change parameter option. Only rate parameter will be displayed.
Created attachment 30740 [details] output from test-speech
why is this marked AP2? Is this such a serious issue?
This is a part of a bug marked as AP2. Probably is not an AP2. I agree with you to change the priority.
*** Bug 142839 has been marked as a duplicate of this bug. ***
Apologies for spam-- ensuring Sun a11y team are cc'ed on all current a11y bugs. Filter on "SUN A11Y SPAM" to ignore.
festival driver shouldn't report 'pitch' and 'volume' as changeable parameters if we don't actually implement them as editable. I'd be inclined to consider the reporting of 'volume' and 'pitch' in this driver as bugs, and the request for pitch and volume change support as an RFE.
Apologies for spam... ensuring Sun a11y folks are cc'ed on all current accessibility bugs.
The availability of voice parameters for festival voices is dependent upon the voice. After some experimentation, here's a way to modify the average pitch of the kal_diphone voice: festival> (set! int_lr_params '((target_f0_mean 185) (target_f0_std 14) (model_f((target_f0_mean 185)_std 34))) (target_f0_std 14) (model_f0_mean 170) (model_f0_std 34)) festival> (SayText 'hello) Since I believe "int_lr_params" is most likely a convention, experimentation with other voices will be necessary to see if it is more widely used. BTW, I checked with test-speech, and festival is only offering up "rate" as a parameter. I don't see pitch or volume appearing, so either the bug of presenting unsupported parameters never existed or it has been fixed.
gnome-speech development has been stalled and it has been replaced by speech-dispatcher [1]. Maintainers don't have future development plan so i am closing all the bugs as WONTFIX. [1] https://mail.gnome.org/archives/gnome-bugsquad/2011-October/msg00001.html