# latency

A tracing module that determines src-to-sink latencies by injecting custom events at sources and process them at sinks. This elements supports tracing the entire pipeline latency and per element latency. By default, only pipeline latency is traced. The 'flags' parameter can be used to enabled element tracing and/or the latency reported by each element.

The measurements are emitted as structured tracer events. Enable the `log` tracer alongside it so they are rendered into the `GST_TRACER` debug category:

    GST_TRACERS="latency(flags=pipeline+element+reported);log" GST_DEBUG=GST_TRACER:7 ./...

## Named constants

### Latency-tracer-flags

#### Members

`pipeline` (0x00000001) – Trace pipeline latency
`element` (0x00000002) – Trace per-element latency
`reported` (0x00000004) – Trace reported element latency

Since : 1.16

## GstLatencyTracer

    GObject
        ╰──GInitiallyUnowned
            ╰──GstObject
                ╰──GstTracer
                    ╰──GstLatencyTracer

Opaque GstLatencyTracer data structure

Since : 1.8

### Properties

#### flags

    “flags” Latency-tracer-flags *

Flags to control what latency measurements to perform

Flags : Read / Write / Construct Only

Default value : pipeline

The results of the search are