@FrankSchlegel for some reason the forum doesn't let me reply directly to your input: Yes, we work with the same work arounds at the moment. We are just confused regarding the communication, as Apple strongly suggests support for iOS. Not only in their documentation, but also their WWDC talks: "In iPadOS and iOS 26, your continued processing tasks can also benefit from background GPU access on supported devices." Which is confusing because there just are no supported devices on iOS 26. Trying to keep the user on the app during a video export task always felt hacky and suspending and restarting comes with its own issues. Especially since Apple deprecated CIKL a while ago and I don't know another way to have a Filter with CPU fallback. We were just happy to see a well implemented path for this use case. I am also happy to accept if this is technically not feasible at the moment or Apple is moving in a different direction. I would just appreciate clarity, as their documentation and WWDC inputs are confusing/misleading.