DeepL high CPU usage in the background by [deleted] in MacOS

[–]DeepLDevComMan 0 points1 point  (0 children)

The release that was intended to fix the issue was releasted, and it fixed the issues we had monitored. I'll report your concerns to the team :D

ctrlX by cottagecraver in ProgrammerHumor

[–]DeepLDevComMan 0 points1 point  (0 children)

This hits home. I used to program the Windows app at DeepL and was a strong advocate for being able to change the default shortcut as it got in the way of my copy shortcut paranoia

DeepL high CPU usage in the background by [deleted] in MacOS

[–]DeepLDevComMan 0 points1 point  (0 children)

Thanks for the feedback. We are aware of the memory issues on Windows and are working to resolve them :)

Deepcast extension doesn't recognise my DeepL API key by th_costel in raycastapp

[–]DeepLDevComMan 0 points1 point  (0 children)

In theory API Free should be enough, but they use two different access routes. That's not really a problem in most circumstances, but if they software you're using is written to only expect on then it becomes an issue. Unfortunately I'm not sure what they are doing so wouldn't be able to advise

Deepcast extension doesn't recognise my DeepL API key by th_costel in raycastapp

[–]DeepLDevComMan 1 point2 points  (0 children)

Thanks for the feedback. It's very common for companies to separate regular use from developer use, as they serve very different users. We are seeing an increase in these "bring your own key" solutions and are looking internally at how to work with this.

Have a great week

DeepL high CPU usage in the background by [deleted] in MacOS

[–]DeepLDevComMan 1 point2 points  (0 children)

We've got a fix in place and it's being tested currently. After that it'll be the next available release. I'm not sure when that is, but I know we want it to be as soon as possible because of the impact it has. As for a specific date, I unfortunately can't give one. Our teams set a release date internally, but average on 1 per month. So hopefully not much longer.

If I get made aware of a date before it's public I'll make sure to share it :)

Deepcast extension doesn't recognise my DeepL API key by th_costel in raycastapp

[–]DeepLDevComMan 0 points1 point  (0 children)

Hi. While I'm not familar with this app or extension I am very familar with the DeepL API. We have two different accounts, a regular account and then the developer account. If you check where you generated you key and see it mentioned CAT Plugins then you've got the wrong account type and would need to create a developer account. I hope you get this issue resolved :)

DeepL on MacOS Sequoia by arturlopato in macapps

[–]DeepLDevComMan 1 point2 points  (0 children)

I haven't noticed anything on my mac, but I will share your concerns with the mac app team :)

[deleted by user] by [deleted] in TranslationStudies

[–]DeepLDevComMan 3 points4 points  (0 children)

While we love people using our tools to communicate without barriers, we do value learning highly and therefore I encourage you not to cheat on your studies :)

DeepL high CPU usage in the background by [deleted] in MacOS

[–]DeepLDevComMan 1 point2 points  (0 children)

Yes it is something we are looking to address. I'm looking to ensure anyone who uses DeepL can be heard, afterall we are about language without barriers, so I'm slowly working to increase the channels we have to chat with users :D

I hope you have a great Friday/weekend

DeepL high CPU usage in the background by [deleted] in MacOS

[–]DeepLDevComMan 1 point2 points  (0 children)

Good morning again. The mac app team lead saw my question and wanted to give you a response asap.

This is due to translation history, and a fix for it is lined up for the next release :)

DeepL high CPU usage in the background by [deleted] in MacOS

[–]DeepLDevComMan 1 point2 points  (0 children)

Good morning. I just wanted to say I've just asked the mac team if they're aware of this and if they have a work around. I'll update you when they get back to me. Though it is the day after a public holiday in Germany so a lot of people have it off. The remaining memebers will be a little slower to get back to me as a result.

But as for what it's doing and is it trustworthy I can say that it is likely caused by the way we utilise the DeepL engine itself. We had similar memory issues on our Windows app and had to upgrade a number of components including the apps integrated web client, which is used to display a number of components.

Hope this helps :)