There is no magic, macOS just checks which version of the SDK was used when compiling the app, if the SDK version is 26 or higher, it will make it go through the new UI path, if not it will get the previous UI.
I don't know how the Python bridge works, but it clearly needs to be updated or recompiled with the new SDK.
Apple made no announcement about the removal of OpenGL, so no, it won't be removed in version 26 of Apple operating systems.
And for the future, there is no way to know until they say something.
Show an NSOpenPanel, and ask the user to open the Documents folder, then store the security scoped bookmark.
Anyway, please don't litter the Documents folder with unwanted things.
Do you set the CMSampleBuffer kCMSampleBufferAttachmentKey* keys for keyframes? I don't think AVAssetWriter will scan the bitstream for that info, it's something you will have to provide yourself.
There is no magic, macOS just checks which version of the SDK was used when compiling the app, if the SDK version is 26 or higher, it will make it go through the new UI path, if not it will get the previous UI.
I don't know how the Python bridge works, but it clearly needs to be updated or recompiled with the new SDK.
Apple made no announcement about the removal of OpenGL, so no, it won't be removed in version 26 of Apple operating systems.
And for the future, there is no way to know until they say something.
Show an NSOpenPanel, and ask the user to open the Documents folder, then store the security scoped bookmark.
Anyway, please don't litter the Documents folder with unwanted things.
Do you set the CMSampleBuffer kCMSampleBufferAttachmentKey* keys for keyframes? I don't think AVAssetWriter will scan the bitstream for that info, it's something you will have to provide yourself.