So after the huge hype, I just managed to update an iPhone 14 Pro Max to iOS 17 Beta. My observations follow:
1. I'm using Alex as my default voice. As iOS 17 came up, I noticed that Alex is using a relatively lower speech rate. My rate was 57 with iOS 16 and it was still set to 57. So I had to increase it a bit to replicate the iOS 16 experience. 58 or 59 does it I'd say.
2. Now VoiceOver voices have an extra Rotor option upon landing on each voice name in the Speech window of VoiceOver settings. So, apart from "Speak sample" we now have the "Open per-voice settings" Rotor item. But the more remarkable point is that for Eloquence voices we can adjust more settings compared with, say, Alex. With Eloquence we can adjust roughness, breathiness, pitch, and, more crucially, utilize a higher sample rate.
3. Of course, since Eloquence should apparently keep bugging us one way or another, the higher sample rate setting, which is now the default option, generates a noticeable sibilant sound especially when Eloquence utters "s" and "z" sounds. This is the first time I've heard Eloquence so sibilant over the past 2 decades. Of course, reducing the sample rate gets rid of the sibilance but re-introduces the so called older muffled/boxiness. Moreover, it seems that this updated Eloquence doesn't support user community dictionaries! As such, words like "Gmail" and "assistive" are still mispronounced - quite sorely!
I'll keep this post updated in the comments section. What else have you, early beta testers, found?
By Amir Soleimani, 6 June, 2023
Share Your Bug Reports with AppleVis
If you experience a bug in Apple Beta Software, the most important thing you can do is to file a report in Feedback Assistant. Please do not assume that Apple is already aware of a bug or that your report won't make a difference; your report may provide crucial information, and submitting bug reports directly to Apple helps them reproduce and resolve the issue faster. The more reports they receive, the higher the priority Apple is likely to give to fixing the bug.
If you are using beta software, please use the Feedback Assistant on your device to submit feedback and bug reports. If you are using a public release, this blog post explains how to report the issue and what information to include.
In 2025, AppleVis launched the Community Bug Reporting Program with the goal of improving the quality and quantity of information we share with the community about bugs in Apple software releases. If you would like to contribute to this effort, please submit your reports via our Community Bug Report Form.
All reports shared with AppleVis must first be filed with Apple via Feedback Assistant. More information about the Community Bug Program is available here.
Comments
Update with eloquence
Update, in iOS 17 public Betas 2/3 eloquence now supports user community dictionarys, you can find that by going to eloquence, and then Open per-voice settings, at the bottom, next to preview settings, there is an option called community dictionary which you can toggle on and off to suit your liking, hope this helps anyone
community dictionary is great
I love the community dictionary it is wonderful
Fixed a issue with per voice settings
For some voices like Siri, and vocalizer voices that do not support Open per-voice settings, it just showed an empty menu, that issue has been fixed in iOS 17 public beta three, for example, if you go into a voice that does not support per voice settings, Siri for an example, there is no longer that awkward empty menu