I haven’t made a generator since FCP 7 days. Unfortunately I can’t figure out how to make anything useful. I create a generator template in Motion and publish the parameters, say using a 4K settings like UHD. Motion adds width and height parameters but I’m not publishing those (FCP’s generators don’t have those after all). Then when I apply my generator in FCP it’s clearly rendering 4K with that fixed aspect ratio, so it doesn’t even fill the image if the aspect ratio is different. Am I missing anything here? This makes FxPlug generators completely useless in FCP. I also just noticed that Motion 5.2 creates template that FCP 10.1 can’t load. So I’ll keep Motion 5.1 around, but I fear that someday we’ll need a new feature (like the 4K Ready flag) but at the same time Motion will write files that older versions of FCP don’t like. Is it worth putting in a feature request like Xcode’s deployment target (minimum required version of FCP)? Or can we just have FCP load FxPlugs without templates? I also noticed that FCP calls finishInitialSetup: on generators only but it’s not on the main thread so setParameterFlags: can’t be used. We’d like a new API in a future FxPlug update to set the enabled states of parameters in response to external data (like hardware). AE has PF_Cmd_UPDATE_PARAMS_UI (which gets called very frequently… we’d be okay with the initial application or loading a project). Updated 16168064. Let me know if I should file a feature request for this generator / template stuff. Thanks, Garrick _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com