Hi Karel Tatranský

Have  you updated MultiTerm to the latest version as well as Studio? You can do this by opening MultiTerm and going to the Help Tab and clicking 'Check for Updates'. It's always important with Studio 2019 to have MultiTerm as up-to-date as Studio is.

Something else that might help, especially since  you've been reinstalling, is to run a Windows Repair on Studio (and on MultiTerm if you want to):

1. Close all SDL applications.
2. Open the Control Panel:
   • Windows Vista/7: Start > Control Panel > Programs > Programs and Features.
   • Windows 8: Right-click on the screen at bottom-left corner and choose Control Panel > Uninstall a Program.
   • Windows 10: Right-click on Start > Control Panel > Select View by: Small Icons > Programs and Features
   • - or type 'Control Panel' in the search line on your bottom Windows toolbar.
3. Click/highlight the relevant SDL product from the list (e.g. SDL Trados Studio 2019 SR2) and click 'Repair' or 'Uninstall/Change' (then Yes then Repair) either on the top toolbar or on the right-click dropdown menu.
4. Restart Studio/MultiTerm.

I hope this helps...

All the best,

Ali

Thanks for the reply, Alison. I am using the latest version of MultiTerm. Re-installing Studio was one of the things I tried. Just to be on the safe side, I just tried repairing it, too. Unfortunately, it did not help.

Hi Karel Tatranský

OK, if you've already tried reinstalling, then you have the right to contact Installation Help free of charge, here:

installation and licensing help

Select 'Installation' from the 'Case type' dropdown menu.

Someone will help in the next day or two if you give your correct email address.

All the best,

Ali :)

Thank you, Alison!

Hi Karel,

Do you have LookAhead enabled? If so, maybe you could try disabling it and see if that makes any difference?

Hi Paul, thanks, I tried disabling LookAhead, no difference :(.

Karel Tatranský

Are you backing up any of your files (inc. TMs or Termbases) to a shared drive as you work... OneDrive for example?  That could be the cause of a problem like this, especially with large resources.

What happens if you disconnect your TMs and TBs... is the performance still slow?

Thanks for the suggestion, Paul. None of the TMs/TBs in this project are on a cloud drive. I even tried removing all memories and termbases, it still takes forever.

I noticed one thing: At the beginning of the file, it takes just a few seconds to switch for example from segment no. 3 to segment no. 4. As I progress further, it takes longer and longer. The 15 seconds I mentioned in my first post, is time it takes Studio to become responsive after moving to another segment close to the end of the file. It's a document with about 10k words and 2,300 segments, the SDLXLIFF is 6.5MB in size. I tried with other projects – with larger files/projects, the lags are longer.

I have a remote support session with SDL tomorrow and I sure hope that they will be able to help because Studio is unusable in the current state.

Thanks for the suggestion, Paul. None of the TMs/TBs in this project are on a cloud drive. I even tried removing all memories and termbases, it still takes forever.

I noticed one thing: At the beginning of the file, it takes just a few seconds to switch for example from segment no. 3 to segment no. 4. As I progress further, it takes longer and longer. The 15 seconds I mentioned in my first post, is time it takes Studio to become responsive after moving to another segment close to the end of the file. It's a document with about 10k words and 2,300 segments, the SDLXLIFF is 6.5MB in size. I tried with other projects – with larger files/projects, the lags are longer.

I have a remote support session with SDL tomorrow and I sure hope that they will be able to help because Studio is unusable in the current state.

Karel Tatranský

Let us know how you get on... will be good to see what's causing this because you seem to have exhausted anything I would of suggested in your initial post!

Karel Tatranský

Hope technical support can sort out the problem, but as a workaround you could use a tool like the Community Advanced Display Filter to split your SDLXLIFF into two or more parts and translate those, then use them to pretranslate the actual source file, preferably with PerfectMatch. There are some caveats with this method, so it would be better if this was not necessary.

You are not working with merged files, are you?

Daniel

Thanks for the suggestion, Daniel!

Studio is in the current state slow even with smaller files so this is not really an option :(. As a workaround, I create the project in Studio and then translate with MemoQ and import the finished SDLXLIFF back to Studio (my primary CAT tool). It's annoying, but at least it does not kill my productivity.

And no, the file mentioned in my original post is not merged, it's a single SDLXLIFF.

Problem solved by uninstalling the Record Source TU (https://appstore.sdl.com/language/app/record-source-tu/504/) plug-in.