Problem attaching XCode to Ableton

SDK for VST 3 audio plug-in and host development.
Post Reply
midiosh
Posts: 8
Joined: Fri Feb 07, 2020 8:40 pm

Problem attaching XCode to Ableton

Post by midiosh »

Up until recently I have been developing my VST Plugins in Windows using Visual Studio. When debugging, I have attached the Visual Studio Debugger to Ableton by setting the debug "command" to Ableton Live 10 executable -- This worked no problem, allowing me to debug my plugin while running on the host (set breakpoints, read values, ...)

Now I have switched over to Mac and am trying to do the same thing, but haven't been able to get it to work...
In XCode, I setup the XCode Scheme Settings (Product->Scheme->"Edit Scheme"->Run->info) to use Ableton Live 10 as shown in the attached screenshot.
When hit "run" in Xcode It builds successfully and then immediately says "Finished Running Live", without launching Ableton.

When I do the same thing using reaper instead as the host, it works: I click "run", it builds successfully, then reaper launches and I'm able to use breakpoints.

Has anyone else had issues connecting XCode to Ableton? Any tips on getting around this?
You do not have the required permissions to view the files attached to this post.

sgretscher
Posts: 21
Joined: Tue Jul 05, 2016 6:30 pm

Re: Problem attaching XCode to Ableton

Post by sgretscher »

I don't have Live installed on this machine so I can't check, but it's likely related to GateKeeper and the permissions Live grants.
Here's Apples docs what they would need to do for this to work on recent MacOS versions:
https://developer.apple.com/documentati ... jc#3087731
Note:
To enable debugging a plug-in in the context of a host executable, the host can include the com.apple.security.get-task-allow entitlement if it also includes the Disable Library Validation Entitlement. Don’t disable library validation for executables that don’t host plug-ins because library validation protects them from loading untrusted code.
Recent Cubase versions set this accordingly, and Studio One will follow suite in their next update.
Here's how to check from the command line:
codesign -d --entitlements - /Applications/whatever_app_you_want_to_check.app
the key to look for are:
<key>com.apple.security.cs.disable-library-validation</key>
<true/>
<key>com.apple.security.get-task-allow</key>
<true/>

Post Reply