Note by @fastfinge

Liam Erven @lerven@tweesecake.social

So going to try this again in hopes that maybe there's a solution. As of NVDA 26 when I use the very unofficial eloquence addons, I can not use Eloquence across two configuration profiles and have separate speech parameters between profiles. No matter what settings I set for one profile, they will carry over to the switched profile. I have tried two different addons with the same result. Has anyone else tried this? I'm interested in your experiences. This is really an awful annoyance.

Timothy Wynn @twynn@mas.to

@lerven I don't use that add-on, but you already looked at the profiles stored under %AppData%\NVDA\profiles and the speech settings are definitely correct?

Liam Erven @lerven@tweesecake.social

@twynn oh yeah. just checked and profile has different speech settings.

Timothy Wynn @twynn@mas.to

@lerven As in the speech settings you wanted to be there?

Liam Erven @lerven@tweesecake.social

@twynn correct. rate is 45 on a game profile. 70 on default. switch from default to game, rate is still 70.

Timothy Wynn @twynn@mas.to

@lerven And when you do switch, the Configuration Profiles dialog says that your gaming profile is active? I'll see if I can reproduce.

Liam Erven @lerven@tweesecake.social

@twynn sure does.

Timothy Wynn @twynn@mas.to

@lerven Sorry for all the questions, but manually activating the profile also keeps the rate at 70 still, right?

Liam Erven @lerven@tweesecake.social

@twynn yep. just tested that as well just in case. Tied it to a hot key so I could flip it.

Timothy Wynn @twynn@mas.to

@lerven Hmm. I am using the Eloquence add-on from the below link, and replicated your exact settings, and it switches without issue. I'm on NVDA 2026.1.1 rc1 if that makes a difference. Have you tried a portable copy of NVDA with your settings, but just that one Eloquence add-on installed to see if that does anything?

github.com/Nick6489/Eloquence64RS/releases/tag/v19.1.1-RS

Liam Erven @lerven@tweesecake.social

@twynn 2026.1.1 (2026.1.1.55980) is what I'm on.

Timothy Wynn @twynn@mas.to

@lerven Also tried @fastfinge's version, and unfortunately can't reproduce there either:
github.com/fastfinge/eloquence_64/releases

🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca

@twynn @lerven Also seems to be working on my end. Different profiles rates are respected.

Liam Erven @lerven@tweesecake.social

@fastfinge @twynn which OS and NVDA? there's gotta be some common thread somewhere.

🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca

@lerven @twynn I'm wondering if some addon left behind a corrupted setting in your nvda.ini or one of your profiles? If you make a portable NVDA, with just the eloquence addon and absolutely nothing else, does the rate change between profiles? Also, on your current NVDA, does the rate change correctly with other tts engines? All of the different eloquence addons are based on the same original code from years and years ago, but with random differences accumulated over the decades. So we sometimes corrupt one another's settings when you switch between them, and then the corruption just never gets fixed.

Liam Erven @lerven@tweesecake.social

@fastfinge @twynn I actually completely wipe dout my NVDA settings and started fresh and had no luck. unless there's another set of settings I missed. I could even just rip out NVDA completely, but I want to make sure I get everything.

🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca

@lerven @twynn No, that would have done it. The only issue I've encountered before is that if you have an installation of NVDA that's many years old, nvda.ini just grows and grows and grows. Because when you remove an addon from NVDA, anything it put in nvda.ini is never deleted. So I've encountered people with nvda.ini files that are several megs in size. And as you might expect that can cause issues.

Timothy Wynn @twynn@mas.to

@lerven Can you uninstall the add-on, make sure %AppData%\NVDA\addons\Eloquence doesn't exist, and reinstall the add-on to see if that makes any difference? @fastfinge

Liam Erven @lerven@tweesecake.social

@twynn @fastfinge giving the portable thing a shot because if that doesn't work then it's some other odd issue

🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca

@twynn @lerven And might also be useful to open nvda.ini, and find and remove any eloquence sessions. You'll probably have two. One like this: [[eloquence]]
voice = 65536
variant = 1
pitch = 65
inflection = 30
volume = 100
rgh = 0
bth = 0
rate = 80
backquoteVoiceTags = False
capPitchChange = 30
sayCapForCapitals = False
phrasePrediction = False
pauseMode = 2
And another like this: [eloquence]
dictionary_name = IBM TTS Dictionaries
dictionary_url = github.com/eigencrow/IBMTTSDictionaries

🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca

@fastfinge @twynn @lerven Also you should have at most two, one like each of those. If you have three, that's a problem. If you only have one, it should be like the first example, not the second.

Munchkinbear @munchkinbear@mastodon.stickbear.me

@lerven what's weird is, on my primary machine, I can't reproduce the rate thing, but on my primary machine, if I set, for example, a different synth on my default profile, then switch to a profile that uses another synth, (note: doesn't matter the synth), the synth doesn't change, and nobody else can reproduce that one for love nore money, just like I can't reproduce the rate thing on the primary machine. @fastfinge @twynn

Timothy Wynn @twynn@mas.to

@munchkinbear Are you sure the problematic config profile has the synth parameter, e.g., synth = deadbeef? @lerven @fastfinge

Munchkinbear @munchkinbear@mastodon.stickbear.me

@twynn oh, of course the damn thing prooves me fucking wrong when I create a test profile, and set it and go back to normal the synth changes. and it's holding the rate stuff just fine across profiles and taking them as required as I swap stuff out, liam, check the profiles in question and make sure it says something like rate=45, are you saving hte config after you make the changes so the thing saves to the profile? @lerven @fastfinge

Pratik Patel @ppatel@mstdn.social

@twynn I used to see this problem all the time. I think I got rid of it by removing couple of add-ons. I can't remember which ones though. I think they had to do with sound and/or synth switching. @munchkinbear @lerven @fastfinge