Eloquence 64-bit for NVDA now supports a 44 kHz mode.
-
@amir The hell? Why? How? Doesn't that just do the exact same resampling pass that the mixer system does before it hits the audio device?
@x0 I don't know the trick behind it as my war-affected internet doesn't allow more analysis. But it sounds great and offers much clearer speech quality compared with 11 kHZ.
-
@x0 I don't know the trick behind it as my war-affected internet doesn't allow more analysis. But it sounds great and offers much clearer speech quality compared with 11 kHZ.
@amir Do you know if the add-on supports 2025.x NVDA at all and/or can coexist with IBMTTS?
-
@amir Do you know if the add-on supports 2025.x NVDA at all and/or can coexist with IBMTTS?
@x0 Hmm. As far as I know, it doesn't support 2025.x NVDA releases. And IBMTTS and Eloquence have never been able to coexist unless one is disabled. But Eloquence 64-bit now offers all text-processing fixes and crash-proof strings once only provided by IBMTTS, and it also offers the required libraries as well as direct access to the community dictionaries.
-
Eloquence 64-bit for NVDA now supports a 44 kHz mode. It’s currently in preview and still being fine-tuned.
You can use the Sample Rate combo box in the Voices dialog to increase the default rate from 11 kHz to 44 kHz for clearer speech.
Unlike the 22 kHz mode in IBMTTS and ViaVoice, this mode doesn’t introduce pops, jitters, or unexpected voice resets.
Try the 16.1 upsampling preview release:
https://github.com/hozosch/eloquence_64/releases/tag/upsampling_preview
For more on the upsampling preview and author discussions check here:
https://github.com/fastfinge/eloquence_64/issues/88#issuecomment-4091293709@amir Hey, does this support custom dictionaries?
-
@amir Hey, does this support custom dictionaries?
@mckensie Sure it does.
-
@amir The hell? Why? How? Doesn't that just do the exact same resampling pass that the mixer system does before it hits the audio device?
@x0 For more on that and author discussions check here: https://github.com/fastfinge/eloquence_64/issues/88#issuecomment-4091293709
-
@x0 For more on that and author discussions check here: https://github.com/fastfinge/eloquence_64/issues/88#issuecomment-4091293709
@amir Oh God, dude rolled his own resampling algorithm with AI? At least 44100 is integer upsampling which is by far easier than fractional upsampling or downsampling, but why not a known open one? R8Brain free, for example. Sinc interpolation giving too ideal upsampling to keep it sounding dull I guess?
-
@amir Oh God, dude rolled his own resampling algorithm with AI? At least 44100 is integer upsampling which is by far easier than fractional upsampling or downsampling, but why not a known open one? R8Brain free, for example. Sinc interpolation giving too ideal upsampling to keep it sounding dull I guess?
@x0 He knows what he's doing and properly tests every step of the way. Honestly I don't see any issues with AI as the code is clearly presented. As for his upsampling approach, he apparently tested a couple of them, but this one produced the best quality without known speech jitters affecting IBMTTS with ViaVoice's 22 kHZ mode.
-
@x0 He knows what he's doing and properly tests every step of the way. Honestly I don't see any issues with AI as the code is clearly presented. As for his upsampling approach, he apparently tested a couple of them, but this one produced the best quality without known speech jitters affecting IBMTTS with ViaVoice's 22 kHZ mode.
@amir Huh. IBM must have implemented that one incorrectly. It's required to use the watson voice, though, and that one doesn't jitter.
-
Eloquence 64-bit for NVDA now supports a 44 kHz mode. It’s currently in preview and still being fine-tuned.
You can use the Sample Rate combo box in the Voices dialog to increase the default rate from 11 kHz to 44 kHz for clearer speech.
Unlike the 22 kHz mode in IBMTTS and ViaVoice, this mode doesn’t introduce pops, jitters, or unexpected voice resets.
Try the 16.1 upsampling preview release:
https://github.com/hozosch/eloquence_64/releases/tag/upsampling_preview
For more on the upsampling preview and author discussions check here:
https://github.com/fastfinge/eloquence_64/issues/88#issuecomment-4091293709@bmoore123 @amir Problem is, you'll never improve audio quality by upsampling.
-
@amir Huh. IBM must have implemented that one incorrectly. It's required to use the watson voice, though, and that one doesn't jitter.
@x0 The ViaVoice jitter with 22 kHZ is a known issue, and affects certain letters, like t, in certain situations. It's actually a speech pop rather than a jitter. Also getting IBMTTS to use 22 kHZ in ViaVoice is quite burdensome whereas Eloquence 64-bit handles it without requiring extra steps.
-
@x0 The ViaVoice jitter with 22 kHZ is a known issue, and affects certain letters, like t, in certain situations. It's actually a speech pop rather than a jitter. Also getting IBMTTS to use 22 kHZ in ViaVoice is quite burdensome whereas Eloquence 64-bit handles it without requiring extra steps.
@amir Oh? What's burdensome about it besides the engine actually trying to predicate on supported versions? If you try to force something that doesn't support it you get fast forward speech.
-
@bmoore123 @amir Problem is, you'll never improve audio quality by upsampling.
@Bruce @bmoore123 But 44 kHZ does improve it whereas the 8 kHZ mode does reduce the audio quality.
-
@bmoore123 @amir Problem is, you'll never improve audio quality by upsampling.
-
@amir Oh? What's burdensome about it besides the engine actually trying to predicate on supported versions? If you try to force something that doesn't support it you get fast forward speech.
@x0 No. The burdensome issue is finding the proper DLL from an older ViaVoice release which does support the 22 kHZ mode properly. The newer DLL which is installed by ViaVoice doesn't support it. Also IBMTTS does have its random voice resets to default with ViaVoice and nothing can be done about it.
-
@x0 No. The burdensome issue is finding the proper DLL from an older ViaVoice release which does support the 22 kHZ mode properly. The newer DLL which is installed by ViaVoice doesn't support it. Also IBMTTS does have its random voice resets to default with ViaVoice and nothing can be done about it.
@amir Huh. The always send current speech settings is supposed to fix that but IBM DLLs typically have that off because the annotations cause pauses, I think? The setting is a fix for the rate bug.
-
@amir Huh. The always send current speech settings is supposed to fix that but IBM DLLs typically have that off because the annotations cause pauses, I think? The setting is a fix for the rate bug.
@x0 Yeah it's supposed to fix that. But here checking or unchecking it doesn't fix the voice parameter resets at all.
-
Eloquence 64-bit for NVDA now supports a 44 kHz mode. It’s currently in preview and still being fine-tuned.
You can use the Sample Rate combo box in the Voices dialog to increase the default rate from 11 kHz to 44 kHz for clearer speech.
Unlike the 22 kHz mode in IBMTTS and ViaVoice, this mode doesn’t introduce pops, jitters, or unexpected voice resets.
Try the 16.1 upsampling preview release:
https://github.com/hozosch/eloquence_64/releases/tag/upsampling_preview
For more on the upsampling preview and author discussions check here:
https://github.com/fastfinge/eloquence_64/issues/88#issuecomment-4091293709@amir actually, it does sounds a lot clearer. better thn I expected.
-
@amir Oh? What's burdensome about it besides the engine actually trying to predicate on supported versions? If you try to force something that doesn't support it you get fast forward speech.
@x0 Also IBMTTS has issues with my own add-on, Typing & Spelling Rate, whereas these have been fixed in Eloquence 64-bit. If you use my add-on and spell something via a higher rate for spelling, or type via a higher rate for typing, IBMTTS's speech rate won't be decreased for other non-spelling and non-typing tasks.
-
@x0 Also IBMTTS has issues with my own add-on, Typing & Spelling Rate, whereas these have been fixed in Eloquence 64-bit. If you use my add-on and spell something via a higher rate for spelling, or type via a higher rate for typing, IBMTTS's speech rate won't be decreased for other non-spelling and non-typing tasks.
@amir Huh. Before the bridge? That's odd, I knew it had issues with indexing but I thought without the bridge embedded commands worked just fine, after all MathML does it all the time.
