When you want to change Eloquence's speed to %49 or lower, it automatically jumps to %50 and that is incredibly slow. In other voices it's not happening. By incredibly slow, I mean between %0 and %10.
By BlackCat, 25 August, 2022
Forum
Apple Beta Releases
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
Rate
Do not get why they did not use the sane way it is done for jaws at windows PC. The quality of eloquence is not that good at this time in iOS. I use it in my PC with jaws and is great.
I notice this, too
I notice this, too. don’t know what to say in a Feed bacck report so Apple can fix this. has it been happening on previous betas, or just beta 7. not sure what the public beta number is, I pay for a developer membership, so only use developer betas.
E
I am not using it. Did not care for the quality of the sound, could be do the spekers or something else. Using Evan voice at this time.
a few things going on here
This is what others need to send to apple. "Mixed-case processing" is currently disabled in Eloquence for iOS, and that
results in words such as "iPhone," "iTunes" "gmail" and "iMessage" being mispronounced. As such, "mixed-case processing" should be enabled for Eloquence - its
Windows and non-iOS counterparts do support this. 4. As things stand right now, Eloquence has serious pronunciation issues and this stands in sharp contrast
with other voices provided by iOS. To handle this, would it be possible to integrate the following comprehensive dictionary set into Eloquence for iOS?
https://github.com/thunderdrop/IBMTTSDictionaries
Eloquence pronouncing those words correctly in iOS 16 Bev 7/PB 5
I typed the words "iPhone" "iTunes" "gmail" and "iMessage" into an edit field and eloquence read them correctly. It would appear that they have enabled mixed case processing finally.
they haven't enabled it
They haven't enabled it I say this because if you go into mail and select someone with an gmail email address it doesn't read it proper.
Tried it and still reads correctly for me
I just tried composing an email and sending it to someone with a GMail address and Eloquence pronounced it as expected. I'm using an iPhone SE3 on iOS 16 Dev beta 7 which is the same as iOS 16 PB 5, which as of this writing, is the latest. Make sure you're running one of these as well. If you are, then I don't know why you're getting different results.
Mixed case processing is definitely disabled
Running the latest iOS beta, it's clear that Apple hasn't yet enabled mixed case processing for Eloquence. That is, while Apple-related terms like iPhone are now read properly as they might have been fixed by Apple themselves through the internal pronunciation facility or something akin to that, mixed case processing doesn't work for other words. Try iMart, iMessage, etc., with an uppercase "M" and a lowercase "i".
To be honest, what irks me the most about Eloquence on iOS is its noticeably lower sample rate compared with Eloquence for NVDA or JAWS or the now defunct Eloquence for Android. For the sake of comparison, I could even get higher audio quality out of Eloquence on my old N82 Symbian Nokia phone. And the fact that the lower quality stands in sharp contrast to the quality of, say, Alex or Siri voices makes me switch to them as I can't tolerate it. This needs more work on the part of Apple if people send more feedback.
I agree with Amir
I completely agree with Amir.
Amir is right and I stand corrected on mixed case pronounciation
I tried iMart and eloquence didn't pronounce as expected but iMessage , because it is an Apple thing, does. I definitley agree that the overall quality of eloquence on iOS needs to be brought up to par with that of what's offered on other platforms. I have submitted the suggestion via feedback that they should offer the 11khz version as standard and 16 khz as enhanced, as is available on Android, similar to what they do with other voices like Samantha. Despite these issues, I still use Eloquence because for me, it's performance overall is still the best.