niedev

6 ms·

1.
by niedev 2y ago
Feedback are always helpful, thank you.
2.
by niedev 2y ago
Thank you! Just tested with Turkish and yes the quality doesn't seem to be the best, however in the future I plan to add translation models with higher quality, so I hope that those will do better with this language.
3.
by niedev 2y ago
The position sent to Google is an error that I didn't see (I will correct it in 5 minutes), the rest, as I say in the readme, is due to the fact that the privacy policy used for RTranslator 2.0 for now is the same as RTranslator 1.0 (t
4.
by niedev 2y ago
Unfortunately you are not the only one having this problem ( https://github.com/niedev/RTranslator/issues/8 ), these days I will try to solve this bug, for now it has top priority.
5.
by niedev 2y ago
With a Snapdragon 8 Plus Gen 1, I measured about 2 seconds for speech recognition of 30s of audio (although for shorter durations it takes not much less than 2s), while for translation about 2 seconds for a text of 300 characters (in this c
6.
by niedev 2y ago
Thank you for the feedback! In a little while I plan to redo the entire graphic interface, and yes a method to make it clearer when the microphone is listening is already in the plans. As for the cutting of sentences you can probably solve
7.
by niedev 2y ago
That would be the end goal (very far :D). But yeah, joking aside, I aim to make the translation better and better as technology advances, the current level is a usable start but maybe one day it will be truly seamless.
8.
by niedev 2y ago
Really cool tutorial! When/if I start developing for iOS this will be really useful, thanks!
9.
by niedev 2y ago
I think it is too long for the preface, but I will better specify that my code is open source in the libraries and models section, thank you for the suggestion and the appreciation!
10.
by niedev 2y ago
Thank you, you are right, I will do that.
11.
by niedev 2y ago
Yes I agree with you, moreover for now I am much better as a Java or C developer than as a web developer, so for me the native approach is also simpler. However, yes, I practically never use the emulator even for Android precisely because
12.
by niedev 2y ago
Ok, I think I found the perfect solution, In the readme I added near open-source "(almost)" with a link to the libraries and models section when I explained clearer what components are open-source, closed-source, and cc-by-nc.
13.
by niedev 2y ago
it's the closest, but it's a very broad and not so well known term, maybe defining my app open source is not technically a perfect term, but it's the clearest in describing it (considering that in the libraries and models sec
14.
by niedev 2y ago
Thank you! The app can be used on any device that has more than 6GB of RAM, with a phone with the right amount of RAM but a slower CPU the only effect is that the app takes longer to perform the translation and voice recognition (at least f
15.
by niedev 2y ago
Thank you! I've done the launch on ProductHunt years ago, when the app still used Google APIs and required the developer key, I'll make another one soon. Regarding the release of the iOS version for now it's not in my plans,
16.
by niedev 2y ago
Samsung TTS? That's strange
17.
by niedev 2y ago
Thank you, for now it's not in my plans, but if the app is successful and I make enough money with donations in the future I might consider it (since I would have to buy a Mac and at least 2 iPhones to test the Conversation mode), and
18.
by niedev 2y ago
Meta defines NLLB as open source, but assuming it isn't (I know Meta It's not a company that has a problem with lying), my code is open source, so how should I define my app? I personally make a distinction between open source an
19.
by niedev 2y ago
For now I have tested the app with Samsung's and Google's TTS, and with these 2 it should work, I am investigating the problem and if possible I will add support for other TTS engines.
20.
by niedev 2y ago
I was considering adding it in the future but I don't know if it meets all the necessary conditions given that uses Ml-kit (closed source) for language recognition in the WalkieTalkie mode.
21.
by niedev 2y ago
I tested the app with the Google and Samsung TTS, in these days I will also test with other TTS including the 2 mentioned here and I will try to solve it, I will update you in the issue you opened.
22.
by niedev 2y ago
Thank you. I'll probably make one these days.
23.
by niedev 2y ago
I know that, but since I make money only from donations without giving anything in return of the money I am considered non commercial. For now I decided to use NLLB instead of Opus because it has good quality and is a single model for all l
24.
by niedev 2y ago
Yeah, for short inputs the models are not that precise, but for long and complicated ones they work quite good, probably NLLB has been trained with very few short texts.
25.
Show HN: I made an open source and local translation app(github.com)
236 points by niedev 2y ago|56 comments