# Camera metadata
Source: [https://docs.qualcomm.com/doc/80-70022-50/topic/gst-camera-metadata-example.html](https://docs.qualcomm.com/doc/80-70022-50/topic/gst-camera-metadata-example.html)
The **gst-camera-metadata-example** application starts with a menu that allows you
to choose between multiple properties of the camera plugin such as
`video-metadata`, `static-metadata`, and
`image-metadata`.
A practical use case for this application is handling camera metadata such as white
balance, International Organization for Standardization (ISO) sensitivity, and
exposure to tune the camera.
The following figure shows the execution of appsink when a new sample is available in the
pipeline. The application is run from the command-line with specific options for custom
pipeline, display type, and timestamp location.
For information about the plugins used in this pipeline, see [Pipeline flow](https://docs.qualcomm.com/doc/80-70022-50/topic/gst-camera-metadata-example.html#gst-camera-metadata-example__section_cgf_tpf_4bc).
Figure : gst-camera-metadata-example pipeline
## Run the application
1. Ensure that you complete the [Prerequisites](https://docs.qualcomm.com/doc/80-70022-50/topic/mm_sample_apps_prerequisites.html).
2. In the terminal of the target device, run the respective command for any of
the following use cases:
- Camera metadata use case with output on Waylandsink
:
gst-camera-metadata-exampleCopy to clipboard
- Camera metadata use case without Waylandsink
:
gst-camera-metadata-example -d 0Copy to clipboard
- Dump metadata of
saturation
gst-camera-metadata-example -d 0 -r org.codeaurora.qcamera3.saturation use_saturationCopy to clipboard
- Dump metadata of
exposureTime
gst-camera-metadata-example -d 0 -r spectra.sensor exposureTimeCopy to clipboard
3. To stop the use case, use CTRL +
C.
4. In the terminal of the target device, run the following command in the SSH
shell to display the available help
options:
gst-camera-metadata-example --helpCopy to clipboard
## Expected output
- During the execution, the application requires the command-line options to
output the camera metadata and options available to set or get the vendor
tags.
- On successful execution of the application, you can find and dump the respective
metadata information.
Figure : Expected output for gst-camera-metadata-example application
## Pipeline flow
The following table lists the plugins used in the camera metadata
pipeline:
| Plugin | Description |
| --- | --- |
| [qtiqmmfsrc](https://docs.qualcomm.com/doc/80-70022-50/topic/qtiqmmfsrc.html) | Captures the camera feed and sends it into the capsfilter. |
| Capsfilter | Passes the feed to [Waylandsink](https://docs.qualcomm.com/doc/80-70022-50/topic/waylandsink.html) for display. |
| Capsfilter | If display option isn't provided, passes the feed to appsink. |
| | |
The application extracts the buffer from the sample for further processing. During
execution, the application expects an argument on which the following options should
be displayed on the console.
- Video metadata
- Image metadata
- Static metadata
- Session metadata
Based on the options selected, the application displays the output on the
console.
## Known issue
When the GetTag menu option is selected,
the capture options don't work.
**Parent Topic:** [Run sample applications for a camera](https://docs.qualcomm.com/doc/80-70022-50/topic/camera-sample-applications.html)
Last Published: Feb 20, 2026
[Previous Topic
Camera frame processing](https://docs.qualcomm.com/bundle/publicresource/80-70022-50/topics/gst-appsink-example.md) [Next Topic
Camera stream configuration](https://docs.qualcomm.com/bundle/publicresource/80-70022-50/topics/camera-stream-configuration.md)