- This topic has 5 replies, 4 voices, and was last updated 1 week, 2 days ago by
tbskoglund
Eventide Staff.
-
AuthorPosts
-
-
October 7, 2025 at 3:21 pm #192498
Hi. I’m running Logic Pro 11.2.2 on MacOS 15.6.1 on an M4 Mini.
Temperance Lite initially worked fine on first installation but now crashes Logic entirely (Logic immediately disappears) when clicking to open an instance of Temperance Lite that I’d already placed on a channel when it was working, and also if trying to insert a new instance of Temperance Lite. It’s registered on iLok successfully and iLok is running. It appears in Logic Plugin Manager as compatible and ticked. I’ve tried reinstalling but no change.
Grateful for any help.
-
October 8, 2025 at 2:17 pm #192515
Hi, sorry to hear you’re having trouble with it. Please email support@eventideaudio.com and we can assist you further.
Could you also send along the text of the crash report it produces? When the “Logic crashed” message comes up, if you click “Send To Apple” you can get the log out of the window that appears before sending, and you can just copy and paste that into your email.
Sometimes clearing Logic’s caches resolves issues like this. This post has instructions on how to do that.
-
October 8, 2025 at 4:12 pm #192520
Thanks. Clearing the cache hasn’t helped unfortunately so I’ll email support.
-
October 24, 2025 at 4:10 pm #192983
The problem, or a similar one, appears to be consistent. I can confirm that Temperance light crashes Logic 11. It’s validated. Funny fact: there’s no crash report. Logic just shuts down. If Temperance is deactivated, Logic runs stable as usual.
-
October 27, 2025 at 3:12 pm #193040
Sorry to hear you are also experiencing this issue.
What version of Logic and macOS are you using?
Please email support@eventideaudio.com and we can troubleshoot the issue further there.
-
-
October 25, 2025 at 3:16 am #192988
Exactly the same for me. I have a partially responded to ticket in with support but I haven’t heard from them in a while.
-
-
AuthorPosts
- You must be logged in to reply to this topic.