Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose capital pitch change value in the Voice Settings dialog #255

Closed
nvaccessAuto opened this issue Jan 1, 2010 · 6 comments
Closed

Comments

@nvaccessAuto
Copy link

Reported by jteh on 2008-12-17 23:25
There is a hidden configuration option called capPitchChange which specifies a value to be added to the pitch when capitals are encountered. However, it is not currently exposed in the Voice Settings dialog. This option should be exposed in that dialog.

@nvaccessAuto
Copy link
Author

Comment 1 by Bernd on 2009-07-16 09:57
It would great to see this in Release 0.6.

@nvaccessAuto
Copy link
Author

Comment 2 by ragb on 2011-07-02 17:24
Hi,

This request ccame again today in the portuguese users mailling-list. Is it possible to implement it for 2011.2?

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2011-07-04 02:50
Sorry. 2011.3.
Changes:
Milestone changed from None to 2011.3

@nvaccessAuto
Copy link
Author

Comment 4 by mdcurran on 2011-09-09 07:14
Implemented in 99c83b2.
Changes:
State: closed

@nvaccessAuto
Copy link
Author

Comment 5 by kevinchao89 on 2011-09-09 13:37
Thanks! This is working as expected in Snapshot main 4568 and is great, but I think for purposes of a great UI and UX, it should not be an edit box, but instead a slider. This would serve two purposes: it would be consistent with all the other voice settings, EG: rate, pitch, inflection, and volume are all sliders. It would save the user from knowing that the range is between -100 and 100, 30 is default, and 0 is no pitch change. With it being a slider, 50% would be 0, 65% would be default, and one can adjust above/below 50% to increase/decrease pitch change.

@nvaccessAuto
Copy link
Author

Comment 6 by jteh on 2011-09-09 22:58
We actually had this idea as well. However, we felt that it wouldn't be intuitive to users that 50% meant no change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant