I have a werid case that shouldn't happen according to https://forums.developer.apple.com/forums/thread/706390 I have an audio unit which runs in FCP and I want it to launch a sandboxed app as a child process. If I sign the child app with just "com.apple.security.app-sandbox" entitlement it crashes with SYSCALL_SET_PROFILE error. According to the article referenced above: "This indicates that the process tried to setup its sandbox profile but that failed, in this case because it already has a sandbox profile." This makes sense because audio units run in a sandboxed environment (in AUHostingService process). So I added "com.apple.security.inherit" to the entitlements plist and now I get "Process is not in an inherited sandbox." error. According to the article referenced above: "Another cause of a trap within _libsecinit_appsandbox is when a nonsandboxed process runs another program as a child process and that other program’s executable has the com.apple.security.app-sandbox and com.apple.security.inherit entitlements. That is, the child process wants to inherit its sandbox from its parent but there’s nothing to inherit." And this doesn't make sense at all. The first error indicates the child process is trying to create a sandboxed environment within a parent sandboxed environment while the second error indicates there's no a parent sandboxed environment... I specifically checked the child process has "com.apple.security.app-sandbox" and "com.apple.security.inherit" entitlements only. If I remove all entitlements from the child process it launches and runs fine from the audio unit plugin. And if I remove "com.apple.security.inherit" but leave "com.apple.security.app-sandbox" I can successfully launch the app in standalone mode (in Finder). For the testing puroses I use a simple Hello World desktop application generated by XCode (Obj-C). Does anybody have an idea what can be the reason for such a weird behavior?

Hi all,I'm not sure if I'm posting to the right forum, but I haven't found the forum specific to FxPlug SDK and I hope somebody here could help me.I have a problem with FxOnScreenControl behavior. I'm writing a plugin that displays some controls over video. It works in kFxDrawingCoordinates_OBJECT coordinate space. Things work just fine in FCPX 10.1.4. But if I switch to FCPX 10.2.1 then all coordinates I get in my implementation of FxOnScreenControl are stretched.The documentation states that with this coordinate space all coordinates should be normalized and be in a range of [0;1], it is so in FCPX 10.1.4, but in FCPX 10.2.1 I get coordinates in a range of [-0.25;1.25] in functions like mouseDragged, mouseDown, mouseUp. At the same time the drawOSC still expects the drawing coordinates to be in the range of [0;1]I've made a quick test and it looks like mouse coordinates and drawing cordinates lay in the same space if I switch to kFxDrawingCoordinates_CANVAS.Is it a bug in FCPX or should there be any ways I could use to normalize coordinates?