Hi there mate,
Thank you so much for purchasing my app and giving me all these suggestions & feedback, invaluable!
I have actually had Regex options in the pipeline since Early 2023 (took a 1.5-year complete break from the app), but never implemented it. It does certainly have its use for this app, but the reason it is still not implemented is just that I realized that a very small percentage of all users would know how to write regex lines themselves and most people would not even bother even if they knew how to do it.
It would certainly not require too much dev time to implement this, but I also think I have much more important things to address at the moment, unfortunately.
Regarding new, heavier models - Using CUDA or other similar tech is definitely possible and 100% worth looking into, which, in fact, I have actually already done. In that case, it was in regard to speeding up OCR. The attempt came to a halt due to some issues I had with the implementation. Can't remember off the bat what it was. But it is certainly something I will look into again in the future.
The tech we use for CPU translations is already pretty damn wicked fast, even on older hardware. Although the models themselves could of course do with much better quality output. The thing is, I am currently trying to focus on tech that can support as many devices as possible, as more paying customers means more development time & increased quality of the app, as well as bigger organic growth. Niche or top end hardware focus is not a priority, but be assured that these will be addressed too, in time.
Could you for testing purposes please get a free DeepL API key and see if the translation quality is much improved? It could very well be that it is the OCR and not the translations that are at fault, most of the time.
Thank you once again, I will respond to the rest of your feedback in other threads as time allows! :)