• State Suggested Answer
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 21 subscribers
  • Views 1995 views
  • Users 0 members are here
Options
Related

Very disappointed in Trados

Nico

Just a general post to state my overall extreme disappointment in Trados Studio, which sums up my feelings for it for as long as I have been using it over the past decade. It runs so slow, with terrible feedback, long lags constantly. When I start it up, it takes longer to load than any other application I use.

I recently upgraded to Studio 2022. I also just bought a brand-new PC, a pretty decent one (Microsoft Surface laptop), to try to get better performance than on my old PC. It is barely any better. The file I am currently translating is not even that big (22 mb), but it easily takes several seconds to progress from one segment to the next. Just incredible productivity loss with this time-wasting program.  Please do not tell me the problem is my hardware; my new PC works fine with other apps.

I just find it shocking how poor this product is and has always been, considering the high price tag and the coercitive upgrades required every couple years. If there is one point of solace I can take in the fact that the AI robots will replace us translators very soon is that at least then I won't be coerced into having to upgrade to a poor but pricy new version of Trados every few years.

Do other people have similar issues? I have trouble believing some translators get lightning-fast speed with Trados.
emoji
Rate translation
×
Suggest better translation
×
Parents
  • 0

    When I had this problem some time ago, it turned out to be a problem with my TM.

    However, it would be wise to first follow the instructions in the KB article that Paul linked to.

    If doing all that doesn't fix the problem, try launching the "translate single document" option with one single, very short Word document, a new, empty translation memory, no termbase and no add-ins. If that works at a sensible speed, then the problem is probably with your translation memory, termbase or document.

    If this minimalist experiment is successful, progressively try ...

    1. Your real document, but still with a new, blank translation memory

    If that works OK, it's your TM or termbase.

    2. Your real document, with your real translation memory.

    If that works OK, it's your termbase. If not, it's your TM. Try upgrading it and reindexing it.

    3. Adding your termbase to the project.

    Logically, everything will now slow down again. If it does, try reorganizing your termbase.

    No guarantee that the above will help, but I can assure you that painfully slow operation is not just "typical Studio". I translate Word documents of several tens of megabytes, and a couple of thousand translation units, and Studio reacts faster than I can keep up with (apart from about half a second's lag for term recognition). So don't lose hope!
    emoji
Reply
  • 0

    When I had this problem some time ago, it turned out to be a problem with my TM.

    However, it would be wise to first follow the instructions in the KB article that Paul linked to.

    If doing all that doesn't fix the problem, try launching the "translate single document" option with one single, very short Word document, a new, empty translation memory, no termbase and no add-ins. If that works at a sensible speed, then the problem is probably with your translation memory, termbase or document.

    If this minimalist experiment is successful, progressively try ...

    1. Your real document, but still with a new, blank translation memory

    If that works OK, it's your TM or termbase.

    2. Your real document, with your real translation memory.

    If that works OK, it's your termbase. If not, it's your TM. Try upgrading it and reindexing it.

    3. Adding your termbase to the project.

    Logically, everything will now slow down again. If it does, try reorganizing your termbase.

    No guarantee that the above will help, but I can assure you that painfully slow operation is not just "typical Studio". I translate Word documents of several tens of megabytes, and a couple of thousand translation units, and Studio reacts faster than I can keep up with (apart from about half a second's lag for term recognition). So don't lose hope!
    emoji
Children
No Data