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

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.

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?

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?

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 

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 

Well, there is no such problem—or at least I have not seen it with anybody else than you. Due to the nature of software and hardware PCs from even the same brand may differ. It can be the antivirus, it can be a software for speech recognition or particularly anything else. It can also be a configuration problem within the projects,

Have you installed Studio by right-clicking the installer and chosing to run as admin? In many—if not in most—cases Studio behaves better then.

Just to update you, I've exported all the TBs and TMs from within the 2021 Studio and Multiterm versions, and then created new TBs and TMs, to which I imported the old ones. After that, I created a new project template and tried to translate a file using it. The end result is that the TMs are working and could be updated, whereas TBs still have to be "activated" each time I open the file for translation, by going to Project Settings/Termbases and clicking OK (in spite of the TBs being all already enabled). If this is the only bug, I think I can live with it. This may also be useful for people who are experiencing trouble with updating their TMs and getting the exception error. I thank you and Alison for having tried to help me and I wish you a Happy New Year!

Margarida Gonçalves Novo

Hi Margarida,

I'm glad you have everything working OK with your TMs. You've done all the right things to resolve your issues.

After all you have done, the TB problem should not exist any more. I do experience the same symptom sometimes when I open client packages. However, I remove the termbases then add them again and that stops the problem. 

Quite coincidentally, yesterday I had the problem that you had where terms weren't appearing in the Term Recognition window. I ran a Windows repair on the MultiTerm components and Studio via Control Panel > Progams... > Repair and that fixed the issue. Maybe after all the work you have done, a Windows Repair might help now?

This final issue really shouldn't be happening... Paul would you be able to resolve the issue where a locally-made and stored termbase fails to stay associated with the project after reboot?

All the best,

Ali

Thanks Ali! I agree that it should not happen, but it does :-) Right now, I'd rather not touch it anymore and wait and see what happens in future projects. All the best and Happy New Year!

Margarida Gonçalves Novo

Hi Margarida,

Happy New Year to you too!

Ali