@amir@fastfinge It's crazy that everyone is layering it in wrappers nowadays. Do you know if codefactory are doing the same with their new android build?
@FreakyFwoof@cachondo@amir You should be able to get either Gemini or Codex to help you, depending on what AI you have access to. The workflow would be: 1. download gemini-cli or codex-cli, and get them installed and configured. 2. clone all of the sourcecode from github.com/fastfinge/eloquence_64/ 3. Delete the tts.txt and tts.pdf files, so you don't confuse it with incorrect documentation. 4. Find any API documentation for orphius that's available, and add it into the folder. 4. Run codex-cli or gemini-cli, and tell it something like: "Using the information about how to develop NVDA addons you can find in agents.md, and the information about the Orphius API I've provided in the file Orphius-documentation-filename.txt, I would like you to modify the code in this folder to work with Orpheus instead of eloquence."
It will go away for five or ten minutes, ask you for permission to read and write the files it's interested in, and then give you something that mostly works. Now, build the addon, run it, and tell it about the errors and problems you have and ask it to fix them. In the case of errors, include the error right from the NVDA log, and for bugs and problems, tell it exactly what it's doing wrong, and exactly what you want it to do instead. Keep doing this until you wind up with a working addon.
Think of AI as a particularly stupid programmer, and you're the manager in charge of the project. You should be able to get this done without paying anyone.
@fastfinge@cachondo@amir Well there's already a 32-bit addon for Orpheus floating about. I'd still rather pay someone competent to do it, even if they use AI. Proper programming terms would help narrow down the broken bits. I'm just an audio guy.
@FreakyFwoof@cachondo@amir Yeah, you can get AI to modify the 32-bit addon for you. That's how I got the first two eloquence prototypes; it helped me understand the problem and what approaches would work and what wouldn't. If you give it the 32-bit orphius addon, and the 64-bit eloquence addon, it should be able to understand the working approach to make an addon 64-bit, and make the modifications itself. The reason to give it the 64-bit eloquence addon as an example is so it doesn't decide to go down the GRPC route and include protobuf and a bunch of other nonsense.