Dear Margarida Gonçalves Novo,

For the termbases, I would recommend that in a first step, you remove the termbases from your project settings in Studio, close Studio, open the TBs in MultiTerm and then reorganize them. Then restart Studio and add the TBs to your project settings. This often helps if no terms are recognized.
If this is to no avail, you can export the contents of each TB into an xml file, create a new TB and then import the xml. Make sure to use the "Import based on entry number" option in order not to loose any terms.

I hope this helps.

Best regards
Annette (from Manfred's account)

Thank you for your suggestion. I had tried to reorganise the TMs and it worked, though not immediately and today it is not working anymore.

Having said that, I think it is a pity that recognised terms are no longer highlighted in editor but appear only in the "term recognition window". Insofar as I am concerned, this solution is worse - instead of seeing immediately if any terms are contained in the TB, we have to look at the window...

Furthermore, I wonder how can a new release of Studio be rolled-out with this sort of issues in TBs (and TMs!).

Let's get this right - if a software needs certain requirements to operate properly, it MUST state them, not just the "barely minimum". That's all there is to say about this, from both a commercial and a legal point of view.

Thanks Alison! Isn't it funny to perhaps be forced to turn-off features so that this software works properly, in spite of my pc meeting the specs?

Any software vendor I know states the minimum requirements for work. This is nothing new - look at the specs for Windows 10 and try to use a PC with an older processor and not much RAM then. I know what I am talking about, as we have some really old "precious" things here. They are fine for a patience game used by my mother, but I would never dream of using such a machine for work.

As a rule of thumb I change my laptop/PC more or less all 4 years. When ordering a new one, I always try to get one with top specs, not an average model. Buying an average PC of 2020 will mean, that it is fully underpowered in 2-3 years, while a top model my be sufficient for even 5-6 years, depending on the usage. And we all translators with CAT tools are power user of PCs. We are not office users, we use database driven software with huge hunger for power.

TBH, your views are really strange to me. What kind of legal consequences shall a requirement from 2017 or 2019 re PC specs have nowadays? The specs for Studio published 2020 will be fully outdated by mid 2021 due to the development in hardware and software. 10 years ago a 1 TB HDD was far too expensive for our use, today you pay more or less 100 EUR for 1 TB M2 SSD... From commercial point of view only giving the minimum specs makes sense, especially if you address translators, who—in my experience—are more than reluctant to invest in good hardware (Mac is an exception—but also a Mac needs power, if you want to use it with Studio).

BTW, here are the hardware requirements (highlighting by myself):

SDL Trados Studio 2021 will work on Windows 7*, Windows 8.1 and Windows 10. We recommend Windows 10.

As a minimum requirement, we recommend an Intel or compatible CPU-based computer with 8 GB RAM and a screen resolution of 1024x768.

For optimum performance, we recommend a 64-bit operating system, 16 GB RAM, an SSD drive and a recent Intel or compatible CPU. Full support for 4K hi-resolution screens is planned and will be implemented incrementally in future releases. You can find more information on how to deal with display issues in this Knowledge Base (KB) article or by running an application from the SDL AppStore which implements a fix, mentioned in the KB article. SDL Trados Studio 2021 uses .Net Framework 4.8

*Please Note: Microsoft has recently stopped support for Windows 7 and as a result, we are no longer testing Studio on Windows 7. Studio continues to work on Windows 7, so you can still install and use it with this Windows version, however to work with GroupShare and Language Cloud projects on Windows 7, make sure to first enable TLS 1.2 as default secure protocol. Language Cloud and GroupShare 2017 SR1 and later only accept TLS 1.2 connections. This is to ensure the highest data security when sharing projects on SDL servers.

So SDL clearly states, that the use of SSD is preferable. Thus my posting shouldn't really be any surprise to you.

Margarida Gonçalves Novo

Hi Margarida,

It may seem crazy but I posted the suggestion on the SDL Trados Ideas page that the 'new' features in Studio be turned OFF by default so that people can just turn on the features they wish to use. That seems logical to me. We can't all afford to buy a new computer or more RAM when installing a heavy-duty piece of software so if the program was less heavy-duty by default, users who don't understand how to streamline the program's functionality wouldn't have so many problems.

Here's something else you can turn off by unticking it under File>Options, that may help stabilise things:

I verify at the end of the job, I don't want to be interrupted by false positives each time I confirm a segment, i.e. things that the software flags up that I know are OK.

There are other features that can be turned off to streamline the product, too. It all depends on what you need the software to do. A project manager, for example, wouldn't need the same tools 'switched on' as a translator, or a proofreader (which is most of my work, in Review mode). I'm not being divisive, just trying to be logical. I work full-time using Studio and MultiTerm and I love them! 

All the best,

Ali 

I am not talking about "performance"; I am talking about the software working properly or not in a pc that meets the specs. There's a huge difference. BTW, I checked the requirements before upgrading, and I have double checked today, so I am fully familiar with them.

Thank you Alison! I also turn off several features myself because I simply don't want to be bothered by things that are useless to me, but this a different issue - there's no reason one should be forced to turn-off features so that things as basic as TBs and TMs function properly while translating.

Oh, they do. With more or less all bells & whistles turned on here.

I have my main TMs and all TBs stored on a M2 SSD, while all projects including project TMs are on a NAS. And even though my data is being accessed via network, I can work on projects with 50,000+ words and TMs with far over 300,000 TUs. My biggest TM has over 1,5 million TUs and is still usable, however the performance with smaller TMs is better.

To make sure, your Studio is working properly, you should use a completely new user profile, create all templates from scratch, upgrade and reorganize your TMs and so on. Should your PC have performance problems, you can tune up the TMs from accuracy to speed:

Thank you very much for all your assistance! For all that is worth, due to the nature of my work, I do not need any of that - all my TBs and TMs are mine and local, there is no network at all, I do not work on the cloud, I do not use automated translation servers or interfaces with external databases and most of the files I translate are plain text files. Therefore, I do not need a super machine for what I do; your case is a very different one. Therefore, if Strudio 2021 cannot work properly in such a low-requirement environment as mine, in spite of my pc meeting (and exceeding!) the specs, I think there's a problem. BTW, it is not that the TMs are slow, I simply cannot update them. As for the TBs, they shutdown every time I close the file I am translating; I have to "open" them again, in spite of Studio showing that they are unable. It looks to me that there is a problem with the interfaces of both TBs and TMs. Thanks anyway!

Margarida Gonçalves Novo

Hi Margarida,

Sorry, I must clarify... nobody at SDL would force you to turn anything off. It's my suggestion entirely because it works for me. Particularly because most of my work is proofreading translations in Studio, I don't need LookAhead or Fragment Matching. I have other things turned off too, such as Tracked Changes. I have added stuff too, plug-ins that are useful to me. Customisation of the software makes my job easier and more efficient.

Anyway, I'm really sorry that I haven't been able to solve your problem. If you contact the Chat Desk as I suggested, somebody @SDL will be able to set up a case for you to investigate this and find a solution for you. 

All the best,

Ali 

Margarida Gonçalves Novo

Hi Margarida,

Sorry, I must clarify... nobody at SDL would force you to turn anything off. It's my suggestion entirely because it works for me. Particularly because most of my work is proofreading translations in Studio, I don't need LookAhead or Fragment Matching. I have other things turned off too, such as Tracked Changes. I have added stuff too, plug-ins that are useful to me. Customisation of the software makes my job easier and more efficient.

Anyway, I'm really sorry that I haven't been able to solve your problem. If you contact the Chat Desk as I suggested, somebody @SDL will be able to set up a case for you to investigate this and find a solution for you. 

All the best,

Ali