Page 1 of 1

Aered crash fix for recent versions of Mac OS X

PostPosted: Mon Feb 04, 2019 1:25 pm
by Richard
Hi all, thanks to the help of robsprinkhuizen, we were able to track down the cause of the Aered crash that seems to happen on certain Macs with High Sierra or later.

Here is a version that fixes the issue:
http://aerodrums.com/download/Aered-no- ... g-2019.dmg

For now, anti-aliasing is disabled which means that the notation won't be rendered crisp and smooth as before but exported PDFs won't be affected by this. If the original version (https://aerodrums.com/get-aered/) still works for you then you should not install this update.

Re: Aered crash fix for recent versions of Mac OS X

PostPosted: Wed Feb 06, 2019 6:18 pm
by Richard
There was an issue with the version posted two days ago (on Feb 4th) which meant there were no trackpad (two finger gesture / swiping) or mouse wheel controls in Aered.

If you downloaded this version then please re-install it using the same link:
http://aerodrums.com/download/Aered-no- ... g-2019.dmg

Re: Aered crash fix for recent versions of Mac OS X

PostPosted: Thu Oct 03, 2019 5:59 pm
by tonspur
Hello Richard,

thanks for providing these versions of Aered.

Since I was experiencing these crashes too, I tried the no-antialiasing version with success!

Now I wonder: will there be a fixed version with font smoothing back enabled in the future?

Best regards
Ben

Re: Aered crash fix for recent versions of Mac OS X

PostPosted: Sun Oct 13, 2019 4:39 pm
by Richard
Hi Ben, we would like to release a fix for this but it is not clear right now when it will be possible. The issue only seems to affect a small number of users - at least we have not been able to reproduce it on any of the MacBooks we have tried. This makes it difficult to diagnose the problem and implement a solution.

Re: Aered crash fix for recent versions of Mac OS X

PostPosted: Sun Oct 13, 2019 7:20 pm
by charles.kline
Richard wrote:Hi Ben, we would like to release a fix for this but it is not clear right now when it will be possible. The issue only seems to affect a small number of users - at least we have not been able to reproduce it on any of the MacBooks we have tried. This makes it difficult to diagnose the problem and implement a solution.


I have this issue as well. Is there any kind of diagnostic tool I can run when it crashes to capture something useful for you?