CafeTran

Okay, here we are.

• Alt key stops working. As reported here, the Alt key suddenly stops working, now confirmed on a new, system (only CT, Office and Java installed). This concerns navigation and any command with the Alt key involved. Who can be the culprit now?
• Opening of Studio packages makes CT freeze. These packages can only be opened in the exceptional case of not having a TM inside.
• Creation of projects makes CT freeze. I only try to change the default location of the project files. Even with the default setting the same thing happens. Indeed the folder and the xlf are created and they can be opened after restarting CT (via Open project, of course the project itself is not inside the dropdown list)
  
• Opening of resources makes CT freeze. Not always, but always enough (when a file/project is already opened and a resource is selected via the menu, e.g. when another resource windows is opened and not visible, but also when it is visible, preferably with DeepL being one of them and being joined).
• Matchboard is sometimes slow. While the MT windows always pop up, the rest of the resources needs sometimes between some and 20 seconds to pop up (and these resources are not so big).
  

I am really a fan of CT, but this is a bit too much. I would have loved to unleash the power of CT with a new machine, but this is disappointing. As stated above, this is High Sierra with 8 GB allocated (and 16 GB for the whole machine). At this moment I switch back to memoQ and only work on mqxliff files, hoping that the Alt key keeps working and that I do not need to open resources.

Any chances to get these things resolved?

On my systems (the old and the new) both Alt keys stop working.

Concerning the other symptoms, that's quite a pity, as they (too) make many features of the program unusable.

 

 > They stop working after pressing the right alt. Press the left one instead.

Nope, this has no influence. so even an amputation of my right arm (that I could perhaps consider otherwise) would not help here.

> It makes me wonder why it kept working for you just fine for so long and all of the sudden, those issues appear in your system without any change to CT in the last few weeks.

If you read the postings more carefully, you would see we are talking about a new machine with High Sierra (the elder one had 'only" Sierra) and much more RAM. This is also the reason why I chose the title.

Just one more symptom:

• work on a sdlxliff file
• finish and close
• reopen the file (to make corrections) -> CT freezes

Must be a kind of RAM allocation in High Sierra or in Java (just an assumption, maybe a custom rise of RAM makes the program stall). It would be nice to have these symptoms taken serious. This is a basic, untweaked macOS. I did not switch to a newer, more powerful machine just to be brutally slowed down by this kind of things.

 

With what specs (RAM etc.) are you testing files under High Sierra?

 

Torsten: ...a newer, more powerful machine

Would that be the 2017 27" iMac? Fusion Drive or SSD? I want to buy the latter, but I still can't get it here. The SSD version could be part of the problem:

I still use the late 2009 27" iMac with an external, FW800 SSD. It runs under High Sierra, but it wouldn't change the file system of the SSD to APFS while installing HS. Java 1.9. And no problems here.

I wouldn't be surprised if the file system caused the problems, or rather, that His Igorness didn't test Akua on a Mac with the new file system.

H.

2017 27" iMac Fusion Drive (I wonder whether this is different to SSD, as AFAIK frequently used apps will be administrated on SSD).

 

Switching resources on and off on the Dashboard (DeepL, perhaps also others) results in a higher frequency of successfully opened projects. Maybe a problem with the internal browser and its RAM usage.

When I change the RAM in Preferences, the cafetran.conf in the Package remains unchanged. Is this correct?

Torsten: Fusion Drive (I wonder whether this is different to SSD, as AFAIK frequently used apps will be administrated on SSD).

The new file system can't be installed on the Fusion Drive. That's why. That also means it can't be the problem...

H.

Torsten: When I change the RAM in Preferences, the cafetran.conf in the Package remains unchanged. Is this correct?

Torsten: ...as AFAIK frequently used apps will be administrated on SSD

It's dynamic, so macOS decides ad hoc what should be on the SSD. The SSD will always be fully utilised. If you have the 1TB fusion drive, everything that would benefit from storage on SSD for a particular activity will be on the 32GB SSD. That's usually good enough for translators, but for video-editing and things, a larger SSD would be preferable to a fusion drive, although a 2TB (and more) FD comes with a 128GB SSD. To be on the safe side, I want the iMac with SSD only (but you can't always get what you want, says Mick)

H.

IK: There is no way to fix something easily which does not occur in my systems

That's the problem. If you sell an app for all operating systems, you should check it on all operating systems. And preferably before they are released, which isn't a huge problem for macOS because there are betas at least a year before the launch. The hardware can be another problem, but it's your problem.

H.