Hello,

My company is writing a plugin for MC 8.4. We started the development on Windows, using the provided examples as reference.

Once we got to the point of testing, I had to port everything to Mac. To do so I had to edit some of the pre-processor directives to adapt them to modern Mac systems (Intel x86_64, clang, OS X 10.10). Once I got to the bottom of that and compiled our plugin, I found it makes MC crash at boot.

It's really hard now to work out what's going without debugging. How can I do that? Or, do you have any idea of what might be causing the crash? I'm pretty sure MC is a 64 bit system so the plugin should be compiled for that. Do I need to use gcc specifically, instead of llvm (which comes as default with OS X)?

Thanks for any help.

Hi,

LLVM should be fine for the compiler setting, and MC is a 64 bit system.  

Does the problem only happen with a debugger attached?  Also knowing whether plug-in registration succeeds or not would help in identifying the problem, even if it means printing out a couple of messages.

Thank you.

Edith Gosselin Picard  @Avid

Hi Edith,

No I didn't manage to even start debugging. I'm guessing I should tell Xcode to attach itself to a process, but MC crashes before I have the chance to do so.

I'm going to print out a few messages and see what happens.

Roberto

Hi Roberto,

Here's another option for debugging as there may be a debug trap that is preventing the attaching of a debugger.  To avoid this please try moving the AMPIPluginDSM.avx  file from the AvidMediaComposer.app package  under \Contents\SharedSupport\Private_Plug-ins to a backup location.  Then restart MC.  MC will notice that this is missing and will ask if you want to continue with reduced audio capability.  Click “ok” and continue.   That should allow you to attach a debugger and parse through the effect registration code, or to examine the call stack for problem scenarios.  Note this debug trap avoidance option only works with MC 8.4.

thx, Tim.