Monitor key events during capture to provide feedback in your camera UI.
Capturing a photo with an iOS device camera is a complex process involving physical camera mechanisms, image signal processing, the operating system, and your app. While it's possible for your app to ignore many stages of this process and simply wait for a final result, you can create a more responsive camera interface by monitoring each step.
After you call
capture, your delegate object can follow along with five major steps in the process (or more, depending on your photo settings). Depending on your capture workflow and the capture UI you want to create, your delegate can handle some or all of these steps:
Result data delivery
The capture system provides an
AVCapture object at each step in this process. Because multiple captures can be in progress at the same time, each resolved photo settings object has a
unique whose value matches the
unique of the
AVCapture you used to take the photo.
Get Resolved Capture Settings
When you specify the settings for a photo, some of the settings you choose can be automatic, left for the capture system to decide at precisely the moment of capture. For example, you can choose
AVCapture flash mode, allowing the camera itself to determine based on scene lighting whether to fire the flash when exposing the photo.
Just before starting the exposure, the photo output calls your delegate's
photo method, whose
resolved parameter tells you the actual settings for that capture. For example, if you chose
AVCapture flash mode, the resolved settings object tells you whether the flash is in use for the current capture—you could use this information to show in your UI that the flash was used.
Handle Exposure Start
When the exposure time begins, the photo output calls your delegate's
photo method. In traditional photography, this moment is equivalent to the opening of the camera shutter. The system also automatically plays a shutter sound at this time.
In your UI, you can respond to this method to display a shutter animation or some other indicator that the requested photo is being taken.
Handle Exposure End
The photo output calls your delegate's
photo method as soon as the exposure time completes. The system still needs time to process camera data before providing an image to your app, but you can use this moment to display in your UI that the exposure is complete. For example, you can simulate a shutter effect by hiding the camera preview in the
will method and showing it again in the
Handle Photo Results
When the photo output has image data available for your app, it calls your delegate's
photo method. Depending on your photo settings, the photo output may call this method multiple times:
If you request bracketed capture, this method fires (at least) once for each exposure in the bracket, providing the image for that exposure.
If you request capture in both RAW and processed formats (such as HEIF/HEVC or JPEG), this method fires (at least) once for each format.
For example, if you request RAW+HEIF capture in a three-exposure bracket, the photo output calls your delegate's
did method six times (2 formats × 3 exposures), providing six
AVCapture objects. To keep track of multiple results, compare the
photo from each photo to the
expected of your resolved settings.
Clean Up When Capture Is Complete
When all of the system's work for a capture is complete, the photo output calls your delegate's
photo method. You can use this moment to finish your app's part of the capture process:
If your capture expects multiple results, cache those in your
Output(_: did Finish Processing Photo: error:)
photo) methods, then save results to local storage or add them to the Photos library in your
Output(_: did Finish Processing Live Photo To Movie File At: duration: photo Display Time: resolved Settings: error:)
If your capture process manages other resources, clean up those resources in your
didmethod. If you use a separate photo capture delegate object for each capture, this is a good time to remove any strong references to such objects.
The code below shows one way to manage multiple photo capture delegate objects: