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!).

Thank you Ali for all your assistance, but it did not work either. I had inserted new settings in Studio 2021 already, but I gave it a try anyway. I guess the only possibility will perhaps be to export all TBs and TMs and to create new ones in Studio 2021 and then create new project templates. I will give it a try. Needless to say, I regret having upgraded, this type of issues simply should not occur, no matter what our personal settings are - I find it unacceptable that such a basic function as "Upgrade main translation memories" stops to work following an upgrade, and the same applies to term recognition. Thanks and all the best!

 Margarida Gonçalves Novo

Hi Margarida,

Is this happening with all your TMs and TBs?

Have you tried setting up a new project with a brand new TM as a test, and see if you can run your batch task to it successfully?

I work with TMs provided by the client and have no problem with old or updated TMs and regularly work with a mixture of both.

I use the batch task or I use Ctrl+Enter to confirm each segment as I go through. I've never had a problem either way.

Normally someone would have set up a case for you by now but I guess many SDL Help people are on holiday this week. You really need a help person to look at your setup remotely.

Did you try the chat service? You can access it here:

https://www.sdltrados.com/contact/chat.html

Click on 'Chat now' 

All the best,

Ali

Dear Alison, I really appreciate all you're doing to try to help me! I work predominantly for end clients, not for agencies, and fully on a stand-alone basis, so everything is done "in-house", so to speak. I'm currentlt trying to solve it the hard way, i.e. creating entirely new TMs and TBs in Studio 2021, based on files exported from Studio 2017, and then creating new project templates. I'd rather do it right away, while I have the time, rather than later. I will let you know id it worked; I really hope it will! Many thanks!

 Margarida Gonçalves Novo

Hi Margarida,

That sounds like the best way forward. I didn't realise your upgrade was from 2017.

I hope it all works well for you!

All the best,

Ali

Hi Alison, yes, it was from Studio 2017, but that should not have been/be an issue since the 2017 release was not yet discontinued. Furthermore, I paid for an upgrade from Studio 2017 (more expensive than one from Studio 2019). Actually, the only reason I upgraded was because Studio 2017 will be discontinued in the near future, but I am no longer certain that I did the right choice, and it is highly likely that I will never upgrade again. All the best and thanks again!

Where are your projects and TMs/TBs located? Do you use any cloud service to store these?

In my own pc; I do not use any cloud or external servers.

Great, this is always better.

Do you have a SSD drive in your PC? If yes, are the TMs/TBs located there? How old is your PC? Which processor do you have?

I have double checked the system requirements for Studio 2021 and my pc meets all of them. Why would a SSD instead of a HD drive or the type of processor be relevant in this case?

Studio is hungry for power, especially for HDD performance. A conventional HDD does not deliver such anymore.

The specs published by SDL are the absolute minimum. IMO you need at least i5 with at least 8 GB RAM and a SSD drive. The processor should not be older then 5th or 6th generation, the newer the better.

And if your PC is by any chance an Apple, the trouble may be caused by the virtualization software for Windows.

Studio is hungry for power, especially for HDD performance. A conventional HDD does not deliver such anymore.

The specs published by SDL are the absolute minimum. IMO you need at least i5 with at least 8 GB RAM and a SSD drive. The processor should not be older then 5th or 6th generation, the newer the better.

And if your PC is by any chance an Apple, the trouble may be caused by the virtualization software for Windows.

Dear Jerzy, I thank you very much for your information. I am appalled by what you say - if that is so, why did SDL not say it in the first place? Unbelievable! I will think about it, and what to do next if the release will not work properly after I have created new TBs and TMs. This certainly is not a good start for this release. Really, I wonder I have upgraded; I certainly will not recommend anyone to upgrade, quite the opposite. Thanks anyway and all the best!

This not about who says what, but about experience.

I may call myself a power user of Studio and have equipped my PCs with SSD drives, at least for keeping TMs/TBs there. If you use S2021, the TM is "deeply searched" and this process needs a very fast HDD. Previously I have kept my resources on an added SSD (Samsung) connected via SATA. Some time ago I moved the resources (TMs/TBs) to a M2 SSD. The speed difference is enormous. And if you're having trouble with TMs, which have been already upgraded, I can imagine the reason could be performance.

Please also check, if you have "LookAhead" activated:

If so, disable it and test.

Should your PC not be very powerful, consider also deactivating fragment matching.

Thank you for your suggestions and your help! However, if you are right (and I assume you are) all this is very sad indeed.

Sorry, but I fail to see anything sad here.

If you want to deliver taxi services, all you need is a car with 4 doors. However, if your aim is to offer better comfort, you'll most probably won't buy a Dacia... And if your services shall be fast, you will certainly chose a decent motor too.

Margarida Gonçalves Novo

Hi Margarida,

To add to Jerzy Czopik's suggestions, here is where you turn off Fragment Matching in your project settings:

It also can be disactivated via File>Options but it must be noted that project settings always overrule profile settings made via File>Options.

It's quite logical to turn off any functionality that you don't use on a huge, complex piece of software such as Studio. I have a pretty powerful system but I work with LookAhead and Fragment Matching turned off because it makes the huge, complex projects I work on more stable AND faster.

Fingers crossed this works for you - try it out, you have nothing to lose 

All the best,

Ali 

PS: If I have a really unstable job (because of its content, rather than Studio) then I find turning off syncing to OneDrive helps!

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.