Note by @fastfinge

Tamas G @Tamasg@mindly.social

5mo

I don't know. My partner (Jess) asked if I'm building this for other people or myself. I feel like I'm building it for other people but I really should be happy with it for myself at least. My only goal was to get this thing working in modern NVDA. Then US English lead us to other languages, people asked if they can have theirs, and then it turned into this big sad project. But maybe I shouldn't feel so sad over it. For myself, it sounds nearly there. Yes some words are off, and some things still stick out a bit sharp, like the word words, ironically. But I can understand and use it, probably 80% of the time I am instead of Eloquence. In that way, mission accomplished, and we have a big robust frontend to tune, so I probably should feel less sad about it.

8

1

0

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

5mo

@Tamasg The key is to realize this can't be only your project. Think of it like you're founding an organization that needs to persist over the years. You're already doing that work, by documenting everything really well, and giving lots of people other features they can use. As well as creating tools. But your goal should be getting it into a state you, personally, like, and then in moving towards having other people in charge of different things. So all you do is final tests and sign off on releases.

1

0

Tamas G @Tamasg@mindly.social

5mo

@fastfinge I just made a massive tools update, formant_trajectory.py and the frame inspector use lang_pack.py and a simple_yaml.py to parse it in a less strict way. So now it's really solid on tooling. People can do tests against them, and build languages easier. I think you're right, hopefully it can get to a point where I'm sitting back and accepting PRs from people tuning phonemes, and carefully weighing bigger changes to anything with the community, liaison for improving it. But this is so so far away from that, although interest is definitely picking up and the more I can simplify tools and add them in many ways I'm hoping the flexibility will make it shine for it. Whether you use the phoneme editor, the frame inspector / trajectory tool, now you really have a way to dig into the rules.

3

1

0

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

5mo

@Tamasg So one thing to think about: If people change settings in the NVDA addon, then you release an update, it looks like there settings aren't always updated. And it's really, really easy to break subtle things. If I were you I might consider adding a reset to defaults button in the addon. Because otherwise you're going to get feedback from people who toggled a checkbox like co-articulation without thinking about any of the associated settings and now wonder why everything sounds bad.

1

0

1

0

Tamas G @Tamasg@mindly.social

5mo

@fastfinge I think we can. If we shipped a .defaults folder with the untouched language files, then the person just hits "reset to defaults" in the NV Speech Player panel, and boom. We just copy over the files from .defaults and they have unchanged settings. But sadly it can't live in the voice panel, because you cannot put buttons there. So it has to live in the NV Speech Player settings area near the top.

2

0

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

5mo

@Tamasg It's probably a good idea. Just so that if someone is giving feedback, or complaining about something, that you can't hear or reproduce, it's easy to say "Please press reset and make sure you still have this problem."

0