Not really 🙂 I just picked a couple of sample DNGs from the Adobe DNG SDK to trigger CIRAWFilter.outputImage. In my case the camera supports multiple output sizes, so it’s hard to find (and bundle) matching DNGs for every resolution. Even if I did, it would increase the app size, and resizing DNGs doesn’t feel right since it alters the raw structure. That’s why I’m hoping there’s a more general way to warm up the CIRAW pipeline.

Not really 🙂 I just picked a couple of sample DNGs from the Adobe DNG SDK to trigger CIRAWFilter.outputImage. In my case the camera supports multiple output sizes, so it’s hard to find (and bundle) matching DNGs for every resolution. Even if I did, it would increase the app size, and resizing DNGs doesn’t feel right since it alters the raw structure. That’s why I’m hoping there’s a more general way to warm up the CIRAW pipeline.

Thanks for the clarification. I’ll put together a small reproducible Xcode project focusing on the first-time CIRAWFilter.outputImage latency and submit it via Feedback. I’ll share the Feedback number here once it’s filed.

Thanks for the clarification. I’ll put together a small reproducible Xcode project focusing on the first-time CIRAWFilter.outputImage latency and submit it via Feedback. I’ll share the Feedback number here once it’s filed. Thanks for taking a look on your side.

Feedback number - FB21351687