Thanks, I've done so.

Thanks for the update, glad you fixed the padding bug. Regarding the drawingGroup(): I'm running this on a playground on Xcode 11.5 or the current (first) Xcode 12 beta. See below for screenshots: With drawingGroup: https://www.dropbox.com/s/w2xec3a35r1ggvf/Screenshot%202020-07-01%20at%2014.12.27.png?dl=0 Without drawingGroup: https://www.dropbox.com/s/mg4hl2amb94u9df/Screenshot%202020-07-01%20at%2014.12.36.png?dl=0 This seems to be specific to LinearGradient; it doesn't happen with something like Color.red, and also doesn't happen with the subview (a Path with a solid colour) that I'm masking in the actual app I'm developing.

Sure thing, just done that.

Thank you for your reply. I did implement it as suggested, and for the most part it works great. However, I believe I found a problem and potential bug when a UIViewPropertyAnimator is configured in didMoveToWindow in a view that is being presented in a popover. This bug can be reproduced in the following example code: https://github.com/tcwalther/PropertyAnimatorPresent/tree/29812e53a8b6d413a156d26de3fe3c01792df9a9 In this code, there are two view controllers. The first one contains a button that presents the second view controller as a popover. The second view controller contains one view of type AnimatedView. The AnimatedView has a UIViewPropertyAnimator that is being configured on didMoveToWindow. When that configuration is called, the property animation works fine, but the popover presentation animation is broken. Have a look at the following screenshots: Can you advise me how to fix the popover animation?

Thanks, I didn’t know about AVAssetWriter. I‘ll try it out. On a first glance, movieFragmentInterval looks like it’s only relevant for QuickTime, not MPEG. However, shouldOptimizeForNetworkUse should do the trick - that should put the moov atom at the beginning of the container. I‘ll report back once I tried it. Edit: accidentally posted this from my private apple Id but I‘m the OP