/Waves/*/Element2.GenericMacIntel.dylib

Support
1

Hi Everyone

My paid for logic crashes approx every 20 mins, then it shows this, any ideas?

"Process: Logic Pro X [5291]
Path: /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X
Identifier: com.apple.logic10
Version: 10.5.0 (5283)
Build Info: MALogic-5283000000000000~2
App Item ID: 634148309
App External ID: 835637741
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Logic Pro X [5291]
User ID: 501

PlugIn Path: /Applications/Waves/*/Element2.bundle/Contents/MacOS/GenericMacIntel.dylib
PlugIn Identifier: GenericMacIntel.dylib
PlugIn Version: ??? (0)

Date/Time: 2020-06-14 22:55:03.671 +0100
OS Version: Mac OS X 10.14.6 (18G95)
Report Version: 12
Anonymous UUID: C11B9642-B0C5-FBE4-81F3-0CEA8C9B16E8

Sleep/Wake UUID: CD11B784-B9AC-4496-AFF4-233F4E3E6861

Time Awake Since Boot: 120000 seconds
Time Since Wake: 20000 seconds

System Integrity Protection: enabled

Crashed Thread: 9 ProcessThread2/1024

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000010
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [5

Long winded I know but someone must understand it, ( I have bought some waves inc getting the free synth( great synth but is it causing crashes?)

2

Hi @musicteccarl,

Note that Logic Pro X 10.5, is not yet Officially Supported with our plug-ins.

We are still qualifying and testing our plug-ins to support it, however, I don’t have an ETA at the moment.

Please follow the steps in this link to refresh the Waves Preferences folder and rescan Logic.

If the issue is not solved, please contact our beloved Tech Support team to advise.

:slight_smile:

3

It is odd as Waves seems to be functioning fine in 10.5 for me, well, 10.5.1. Logic itself has a few hiccups that need addressing, but so far I haven’t come across an Waves related issues.

This doesn’t mean there aren’t any issues, but I would suggest start by making sure everything is up to date. Try “rebuilding the cache”, so to speak. As that was the first thing I did after updating and could be the reason why I’m not encountering any issues. Maybe.

To do that j ust follow the directions that @OmryWaves pasted above.