Developer Documentation issue with FxPlug4 with Downloaded SDK and Xcode #322
Replies: 6 comments 44 replies
-
I'm not really sure I understand your question? I explain FxPlug in more detail here: https://fcp.cafe/news/20231212/
What do you mean exactly?
Again, I'm not really sure what you mean. FxPlug is basically filters and generators for Apple Motion. You can't directly access an FxPlug from Final Cut Pro. You can create Motion Templates in Apple Motion for Final Cut Pro which can contain any combination of FxPlug filters and generators. Xcode is only used to create FxPlug's. You basically need to build a "Wrapper" application, which contains the FxPlug extension. When you run the Wrapper application, macOS detects the embedded extension and notifies Apple Motion that it exists. The XML data in a Motion project is proprietary, and there's no public documentation about it. FxPlug has an API for doing on-screen controls. See: |
Beta Was this translation helpful? Give feedback.
-
System Log: MacBook-Pro DEAD_PROCESS: 43204 ttys000 Handled all the "Console" crash dumps...clicked on Motion...Opened Motion Project...no FxPlug behavior of any type. FCPX is the end game...Got Motion "Rigging","Widgets", "Publishing" and stuff working but just wanting a little insight to FxPlug4 (because FxPlug3 honestly scared me). Went back to Development Documentation...Xcode...built FxPlug4.xcodeproj...ran it...Console Crash Report....(fat file, but missing compatible architecture (have 'i386,x86_64', need 'arm64'...figured that "old PluginManager" out ....and current FxPlug4 examples solved that issue ....drum roll...and STILL can't get the current examples to interact with Motion! |
Beta Was this translation helpful? Give feedback.
-

This is my screen after Xcode run of FxGradientCheckerboard.xcodeproj
… On Jan 9, 2024, at 4:38 PM, Chris Hocking ***@***.***> wrote:
I'm still confused by your messages. I was under the impression that when you built the Wrapper App in Xcode, it correctly showed in Motion? Is that not the case?
I would ignore any Console messages for now - there's lot of irrelevant Console spam in FxPlug and Final Cut Pro.
The FxPlug examples in the FxPlug SDK should all work out-of-the-box with no changes required. Just build the sample project's Wrapper Application, run it, THEN open Motion and the filter or generator should be listed.
—
Reply to this email directly, view it on GitHub <#322 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEC7OJCR2XG6B4WTX2UUPSTYNXBFHAVCNFSM6AAAAABBTED4MGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DANZSGM4DG>.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
-
Yes...Closed and Opened Motion multiple times....
… On Jan 9, 2024, at 5:09 PM, Mike Kuhnkey ***@***.***> wrote:
<Screenshot 2024-01-09 at 5.06.34 PM.png>
This is my screen after Xcode run of FxGradientCheckerboard.xcodeproj
> On Jan 9, 2024, at 4:38 PM, Chris Hocking ***@***.***> wrote:
>
>
> I'm still confused by your messages. I was under the impression that when you built the Wrapper App in Xcode, it correctly showed in Motion? Is that not the case?
>
> I would ignore any Console messages for now - there's lot of irrelevant Console spam in FxPlug and Final Cut Pro.
>
> The FxPlug examples in the FxPlug SDK should all work out-of-the-box with no changes required. Just build the sample project's Wrapper Application, run it, THEN open Motion and the filter or generator should be listed.
>
> —
> Reply to this email directly, view it on GitHub <#322 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEC7OJCR2XG6B4WTX2UUPSTYNXBFHAVCNFSM6AAAAABBTED4MGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DANZSGM4DG>.
> You are receiving this because you authored the thread.
>
|
Beta Was this translation helpful? Give feedback.
-

This is copy of FxGradientCheckerboard "Build Phases" from Xcode.....xcodebuild -project FxGradientCheckerboard.xcodeproj -showBuildSettings shows "TARGET_BUILD_DIR" and "FRAMEWORKS_FOLDER_PATH". These "Preferences" are not jiving with "DerivedData" in Xcode.
So, I thought it would be helpful, from "Developer Perspective" to identify how xcodebuild 'preferences' mapped to Xcode button presses and checkboxes?....cause I don't understand how it works for you but not for me...
… On Jan 9, 2024, at 5:31 PM, Mike Kuhnkey ***@***.***> wrote:
Yes...Closed and Opened Motion multiple times....
> On Jan 9, 2024, at 5:09 PM, Mike Kuhnkey ***@***.***> wrote:
>
> <Screenshot 2024-01-09 at 5.06.34 PM.png>
> This is my screen after Xcode run of FxGradientCheckerboard.xcodeproj
>
>> On Jan 9, 2024, at 4:38 PM, Chris Hocking ***@***.***> wrote:
>>
>>
>> I'm still confused by your messages. I was under the impression that when you built the Wrapper App in Xcode, it correctly showed in Motion? Is that not the case?
>>
>> I would ignore any Console messages for now - there's lot of irrelevant Console spam in FxPlug and Final Cut Pro.
>>
>> The FxPlug examples in the FxPlug SDK should all work out-of-the-box with no changes required. Just build the sample project's Wrapper Application, run it, THEN open Motion and the filter or generator should be listed.
>>
>> —
>> Reply to this email directly, view it on GitHub <#322 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEC7OJCR2XG6B4WTX2UUPSTYNXBFHAVCNFSM6AAAAABBTED4MGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DANZSGM4DG>.
>> You are receiving this because you authored the thread.
>>
>
|
Beta Was this translation helpful? Give feedback.
-
Don't know how IQ goes, but you are definitely beyond "gifted", and have a knack for explaining things. Haven't made it to CommandPost...but looking into it.
… On Jan 9, 2024, at 5:31 PM, Mike Kuhnkey ***@***.***> wrote:
Yes...Closed and Opened Motion multiple times....
> On Jan 9, 2024, at 5:09 PM, Mike Kuhnkey ***@***.***> wrote:
>
> <Screenshot 2024-01-09 at 5.06.34 PM.png>
> This is my screen after Xcode run of FxGradientCheckerboard.xcodeproj
>
>> On Jan 9, 2024, at 4:38 PM, Chris Hocking ***@***.***> wrote:
>>
>>
>> I'm still confused by your messages. I was under the impression that when you built the Wrapper App in Xcode, it correctly showed in Motion? Is that not the case?
>>
>> I would ignore any Console messages for now - there's lot of irrelevant Console spam in FxPlug and Final Cut Pro.
>>
>> The FxPlug examples in the FxPlug SDK should all work out-of-the-box with no changes required. Just build the sample project's Wrapper Application, run it, THEN open Motion and the filter or generator should be listed.
>>
>> —
>> Reply to this email directly, view it on GitHub <#322 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEC7OJCR2XG6B4WTX2UUPSTYNXBFHAVCNFSM6AAAAABBTED4MGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DANZSGM4DG>.
>> You are receiving this because you authored the thread.
>>
>
|
Beta Was this translation helpful? Give feedback.
-
Is it too off topic to discuss how/why down loaded FxPlug4 examples are overridden by default xcodebuild on MacOS? Maybe a "Down-in-the-Weeds" or "Rabbit Hole"? Specifically Developer Documentation using Xcode --> FxPlug project to manually install and make FxPlug template somehow overrides "Examples" downloaded with FxPlug4 SDK from Apple Developer website.
Specifically interested in "chaining together" Xcode-->FxPlug-->Motion-->FCPX "templates". Also would like to understand "ozscene XML" in Motion and "On-Screen-Editing Controls" in the chain? I could buy the plug-ins...but would like to understand the system.
Beta Was this translation helpful? Give feedback.
All reactions