- Dec 29, 2017
- 3,524
- 6,235
- 676
That's completely fine.
It's just about personal preference. Who cares what tool is used as long as the result is a working translation.
My tool is free and open source. There's no premium features or something like that. I don't gain anything from someone using it.
I'm collecting translations as the head moderator of the translation section of anime-sharing. I'm in contact with a lot of people using a lot of different translation methods.
For example I have explicit re-upload permissions from dazedanon, Muninkai, fantasmic, BluLatex, YokoSan, vvf77235, Surgy, Panelgamer and archedio.
But of course SLR Translator is what I'm personally going to recommend and use, and so if someone uses something else they will also have to provide support themselves.
The DSLR translation engine can work with any openai "like" endpoint (basically any api url that can end with 'v1/chat/completions') including LM Studio for local models. The SugoiV4 SLR stuff is kinda obsolete at this point, it's mostly still there because it can run on a toaster.
I personally use DeepSeekV3.1-Terminus for translation as a premium model, and for free offline translations I switched to the abliterated Qwen3-VL-Instruct family.
And not really for you, but just to mention it again as a general note, because it's something that actually kinda annoys me:
"Technically" SLR Translator is directly compatible with LinguaGacha because I'm using the ".trans" file type, and apparently quite a few people use it that way after it was recommended in a popular discord, but using LinguaGacha to translate a .trans file generated by SLR Translator completely bypasses my script protection system. All my systems to ensure that games work properly are no longer involved.
Meaning the resulting files are entirely dependent on LinguaGacha output, have basically nothing to do with my tool, and I will not provide any support in case of problems.
It's honestly weird, that I even have to mention that...
