Under Community Review

64-bit version of Studio

Please create a 64-bit version of Studio. At present only a 32-bit version is available, and therefore it can theoretically only access 2-3GB of system memory, meaning that upgrading your machine with more memory then this does not have any beneficial impact on Studio performance.

When handling large files & projects, allowing Studio access to all of your system's memory would make a huge difference in time and performance, and for this the app needs to be 64-bit.

Are there any plans to release a 64-bit version in future?

  • I can confirm that there is no problem with compatibility. The only thing you need to be aware of is that when importing any sdlxliff files created from Microsoft Office documents, you will get a warning (not an error) saying that a filter has been used for which MemoQ cannot display formatting and that this formatting will now be handled as tags. All this means in practice is that where you might, for example, see a part of a sentence highlighted in yellow in Studio, it will be surrounded by tags in MemoQ. Once it is exported back to Studio, it will show as yellow again.

    There is one other thing to be aware of. In Studio, auto-propagation will automatically insert changes of numbers or tags, which I consider to be Studio's unique selling point. In MemoQ these are automatically inserted as high matches but not 100%. To compensate for this in MemoQ you need to open up the TM settings and check "return an exact match if only recognized numbers are different". Then they will be automatically inserted as 100% matches or you can run pretranslate occasionally to compensate for the fact that these segments don't auto-propagate.

  • Yeah... And we're going to have to wait another 6 years for the exact same comment later on. We've heard about 64-bit Trados Studio for a couple of years now. And it always is several years ahead, you're still working on it, considering it, not disagreeing with our (users') opinions. And yet new Studio version get useless features that almost nobody uses, and the core problems are not being addressed.

    As a user that has spent close to EUR 80k on your software so far (various Professional and Freelance licenses + 3 versions of GS), I declare that I will not be spending anything more until the software is 64-bit. I have already purchased a memoQ license for myself and I am evaluating it. As soon as I deem it better and more reliable that Studio, I will make a switch for the whole company. I have had ENOUGH waiting and being lied to about your plans to update the software. Be honest, for once - have you really been working on a 64-bit version or you just tell that to people to placate them, while you do everything to rump up your bottomline, without incurring any additional costs for the "unneeded" 64-bit version? This technology is almost 20 years old and it is a JOKE that Studio does not utilize it.

    I am especially mad today, because only today my Studio crashed or simply closed down without saving my work, like 8 or 9 times. And it is just 1 pm here. I am working on large XML files that I NEED open simultaneously in order not to have to pre-translate and then recheck every single cross-file repetition that I have, and Studio is actively making my work almost impossible. And that is my everyday situation with Studio. No more euro will be spent on Studio unless it goes 64-bit and finally can use my 64GB or RAM instead of crashing at 3-4 Gigs :/

  • I already thought of doing the same, but I was not sure to be able to rely on a perfect compatibility of xliff files.

    Thank you

  • They have pretty much stopped doing any sort of core function updates, the same bugs that were present in Studio 2009 are still there. Processing sdlxliff files in memoQ is the only viable option.

  • For what it's worth, I have completely given up on this issue being resolved within my working lifetime (I'm retiring in 2026). My solution is to retain the use of Trados Studio for compatibility with the workflow of clients who use it, but to import the sdlxliff (the segmented one in the directory \projects\project name\language-variant) into MemoQ, together with the memories. This is a quick operation that means that I work in an environment that does not crash, is fast and has much better "intelligent" search and replace for faster post-editing.

    When the translation is done, just export to the same directory, open it in Trados, and deliver to your client. All QA and all other processing is done in MemoQ and XBench.

    I am currently doing a project with around 450,000 repeated segments and I dread to think of the problems it would cause in Studio.