This behaviour still exists in macOS Sequoia.
latenitefilms
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Melbourne, Australia
Post
Replies
Boosts
Views
Activity
You can learn more about FxPlug4 here:
https://fcp.cafe/developers/fxplug/
To use SF Symbols in Final Cut Pro, you'd need to build your own FxPlug4 plugin.
See: https://developer.apple.com/documentation/professional-video-applications/fxplug
Any reason you're using video0, etc?
Can you try use r1, r2, etc. as Final Cut Pro would do?
The error you're seeing is because your asset is missing a format:
<asset id="video0" name="11a(1-5).mp4" start="0s" hasVideo="1" videoSources="1" duration="6.81s">
You're using incorrectly using decimal places for the time values - i.e. 9.94s. These should be rational numbers.
Are you able to post the full crash report?
AFAIK, it's not possible to control Window properties in FxPlug4 or Workflow Extensions - Final Cut Pro controls the window, all we can do is populate the Windows with content.
AFAIK, it's not possible to control Window properties in FxPlug4 or Workflow Extensions - Final Cut Pro controls the window, all we can do is populate the Windows with content.
AFAIK, there's no means to control the Window properties - this is all handled by Final Cut Pro itself.
or is there a way to tell FCP to use a default start time independent of timecode?
No, you need to provide correct and accurate timecode values in the FCPXML.
This framework might be of use?
https://github.com/orchetect/DAWFileKit
I'm also running into the same issue on macOS Sonoma 14.3 and Xcode 15.4.
Installing the previous Xcode 15.3 fixed the issue.
xcodebuild -version
Xcode 15.4
Build version 15F31d
Sorry to dig up an old thread, but just wondering if 3 years later, anyone has any insight they can provide, as I'm seeing the same issue?
Based on the description in this header file, it certainly sounds like you can either use MPSImageLanczosScale or MPSImageBilinearScale, and MPSImageScale is not really an option:
https://github.com/xybp888/iOS-SDKs/blob/fa4a2d866231985fa9538fafc800421aa99b83f2/iPhoneOS13.0.sdk/System/Library/Frameworks/MetalPerformanceShaders.framework/Headers/MetalPerformanceShaders.h#L647
This thread keeps coming up in my Google searches. Did you ever find an answer/solution?
I saw a few posts above suggesting using altool, and after a little bit of trial and error, this seemed to work for me:
xcrun altool -t osx -f "/path/to/app.dmg" --primary-bundle-id --output-format xml --notarize-app -u apple-id-goes-here -p "app-specific-password"
...then take the RequestUUID and you can check the status using:
xcrun altool --notarization-info RequestUUID-goes-here -u apple-id-goes-here -p "app-specific-password"
...this once that's done you can staple:
xcrun stapler staple "/path/to/app.dmg"
Hope this helps others who are running into the same issue!
I'm also seeing the same issue today.
I tried to run xcrun notarytool store-credentials again, but I get:
[13:23:26.009Z] Debug [API] Received response status code: 500, message: internal server error, URL: https://appstoreconnect.apple.com/notary/v2/asp?, Correlation Key: EFNNWSQB2XZUUYA2EBWMOVQUMY