- Aug 20, 2022
- 32
- 139
You haven't asked for any information but sure thanks anyway.Well good luck with that.
I'm done playing the guessing game without getting any proper information.
You haven't asked for any information but sure thanks anyway.Well good luck with that.
I'm done playing the guessing game without getting any proper information.
You haven't asked for any information but sure thanks anyway.
Do you actually mean in Translator++, or in general?
Also you have python installed right? There's different python installation types. (Depending on if you choose install for all users, or not, and they conflict with each other.)
And now the latest ones:What operating system are you even using? Windows 10?
Why do you even need torch?
Or bothering to actually give any information, or screen how it is not working. If there's an error or whatever.Is the Translator++ addon RedSugoi not working?
Just some notes, this is actually a fairly known problem that will happen if.... ironically enough, you have the latest version of python.Trying to install pip gives me this message ''Error: Could not find a version that satisfies the requirement torch ( from versions: none)
''Error: No matching distribution found for torch
Yet another roadblock for me.
I've hoped that maybe python was the issue but it didn't end up fixing much. I managed to install torch but Sugoi Translator still doesn't work in Translator++. I installed the sugoitransfix, sugoi_gpu_cuda, the cuda_flaskserver and the end result was a window saying ''Modulenotfounderror: No module named 'flask'Just some notes, this is actually a fairly known problem that will happen if.... ironically enough, you have the latest version of python.
Basically the newest version of python doesn't have packages for all the versions of torch+cuda that pip is asking for.
And it's hard to say if the maintainers of the packages would add these older versions to it in the future.
It's been a while but if I'm not mistaken pytorch+cuda NEEDS to have python at least 3.8, but less than 3.11.
You might want to try either python 3.9 or python 3.10.9. You can download then from the python archive.
This should most likely solve the problems with the dependencies not installing.
---
Also note, that even if you didn't managed to install pytorch+cuda correctly, the translator++ would still work, it would only default to the CPU instead.
--
Lastly
I did go through a whole journey to make sugoiTrans work with translator++.
The latest free version of T++ with SugoiTrans addon(the last time I checked) didn't actually worked. And it didn't had support for GPU.
The addon was based on a really old version of sugoiTrans and the paths were all wrong for the new version, which made it not work at all.
I make a few fixes and documented here and there what I did to make it work, with GPU and with T++.
It might be a bit of a mess to check all the posts but it starts about here(https://f95zone.to/threads/translator-4-9-28-standard-version-developer-version.60101/post-9052503) and spans several threads.
I even made a custom sugoiTrans addon(named SugoiTrans Gold) at the end to help fix some issues I was having and to avoid edit too many files to fix the issue.
I think I originally used miniConda to install another version of python but that was totally unnecessary, I just needed the right version of python installed in the first place.
-
Good luck
Btw in case that makes things easier, I personally think currently, for Japanese to English, a completely offline Translator++ version would basically have the same value as an online one.Yes, I have the "latest" (or close to it) build.
Personally I would have no problems sharing it, but would prefer having the OK from my source, as a safety measure against account banning basically, especially if what you say (belllow) is true.
No, I don't have the crack for that "latest" version, just the same one for the build v4.9.28, which as I said before doesn't work (as it is) for the "latest" build, thus sharing what I got now is pointless until we get the crack.
>apparently if you download Tranlator++ from the patreon it's purposely missing files, and you would download those files depending on your account when you launch it.
>Those files used to be in the main folder and now they've either moved to the Appdata folder, or those are now additional ones.
Umm I truly don't know because I would have to see how a fresh unaltered build looks, but honestly I don't think there exist a way to connect the files from your Translator++ folder to your account once you already got them, there may be but it is unlikely.
Furthermore, when I compared files between Translator++ v4.9.28 and the ones in the "latest" build I got, the amount of files count is similar (barely a few new ones), main changes are found in that (several) files got updated, most files between builds remained unchanged.
All this is talking about the builds in the form we (I) got shared, which I am guessing are already complete, as opposed to how they may be without "filling" them in first with the files from patreon (a subject I know nothing about).
Good news is that I got an idea and if it works, as I think it should, then we may get the "latest" build working, but I am waiting for my source to test it first from his side, for now we will have to wait (either days or a couple of weeks).
In the meantime we got v4.9.28 working, up from v4.8.31, so that's something already
I looked at it just now and it seems like a decent way to automatically clean up an mtl. We'd probably have to wait until an API gets released (if at all). It seems a bit more handy for people who want to release something in English but aren't native speakers. Y'know, smooth the edges a bit without needing to find and wrangle a copy-editor.Two questions, has anyone heard of the new Deepl WriteYou must be registered to see the links. And do you think we'll get an add-on to use it in T++?
yes, the MTL to Deepl Write is not so big an improvement but for actual translations (as in, a manual translation) it becomes a very good tool.I looked at it just now and it seems like a decent way to automatically clean up an mtl. We'd probably have to wait until an API gets released (if at all). It seems a bit more handy for people who want to release something in English but aren't native speakers. Y'know, smooth the edges a bit without needing to find and wrangle a copy-editor.
I ran a random chunk of Japanese through Deepl Write to see what happened:
I think it's a little better after Deepl Write and if the chain of JP->MTL->Deepl Write can be automated then it'd probably be a decent option.You don't have permission to view the spoiler content. Log in or register now.
Thanks for the answer.old Rename to #old . After translating back to old.
Change everything in 30 seconds? How?With me it takes 30 sec. to change everything. With Notepad++ no problem.