@fastfinge The openevv project now has a PR to take care of the sample rate issues. Could you please incorporate it into Eloquence 64's openevv section for testing? Add a wideband voice, and do everything above 11,025 in whole numbers: github.com/Mudb0y/openevv/actions/runs/37492982819
@amir Is there any reason this has a checkbox? I'm struggling to understand why anyone would set a sample rate above 11025 kHz and want wideband off? I don't even understand why openEVV made this a setting. Is there any reason to not just have it always on?
@fastfinge There is one, I repeat, one, edge case where you might do this - You have a DAC that has terrible resampling and you want the 11 KHZ sound to not alias. Some integrated systems qualify. @amir
@amir@nick My worry is that too many checkboxes will confuse 99 percent of users, and then we get to spend the rest of our lives answering questions about why resampling doesn't work, or what that checkbox is for.
@fastfinge Which is why if I were you, I wouldn't implement it in the Eloquence addon. What lives in EVV upstream doesn't have to live in the addon. @amir
@fastfinge@nick Oh yeah! Damned got it! But compared with what we already have in other Eloquence 64 variants, or even in the older IBMTTS driver with ViaVoice, it's terrible.
@fastfinge@nick Honestly - and as I see it now and even as someone who sort of likes higher sample rates, the major issue holding openevv back is related to maddeningly troublesome ViaVoice quirks. Oddly enough, some appear to prefer ViaVoice to Eloquence. But I'm not one of them.
@amir@nick Same. I was sort of hoping that the ViaVoice quirks would either be fixed or made configurable, before any sample rate stuff happened. I think mudb0y just has so many people asking for so many different things right now, but hasn't quite developed the skill to say "no" or "later" to anyone. If I were him, I'd work with someone (even a non-programmer) to help him prioritize all the different things, develop a roadmap, and be the one to say "we're not doing this now, see the roadmap" for him, so he can focus on the actual work.
@fastfinge I really want to be wrong. Amir, you might actually be the most discipline out of the lot of us in documenting Eloquence behaviors, as it's part of your roll re: community dictionary. Can you write up all the differences you can find? It might be a good idea to create these in an issue and call them as regressions - given what Sam's Dad has to say about working at IBM, I'm comfortable with that designation. @amir
@nick@fastfinge Update: my first draft documenting 7 issues is ready. Of course, the first glitch sort of affects both of them in different ways. I'm sure there are other ViaVoice glitches, but I wanted to get the ball rolling. It would be great to also have others contribute to this. If you also give me hints here, I'll expand them for the document. Let me know if this format is suitable. Behavioral Differences Between Original ETI Eloquence and IBM ViaVoice wormhole.app/mMaK60#FC46fwVcmoKoTImQM-5Tew
@nick@amir This is exactly what's needed. Should be easy for whomever has the tokens first to get this into AI, have it create test plans for all the issues, then start working on fixes. Test plans should probably involve generating samples for humans to listen to and compare, as well as its own testing. I'm out of Claude tokens until Monday, sadly. So it won't be me yet.
