Struct WlEncodeControls 

pub struct WlEncodeControls {
    pub(crate) rate_dirty: AtomicBool,
    pub(crate) bitrate_kbps: AtomicI32,
    pub(crate) vbv_mult_milli: AtomicI32,
    pub(crate) fps_bits: AtomicU64,
    pub(crate) link_kbps: AtomicI32,
    pub(crate) force_idr: AtomicBool,
    pub(crate) scanout_refused: AtomicBool,
    pub(crate) scanout_planes: AtomicU32,
    pub(crate) reference_reports: Mutex<Vec<ReferenceReport>>,
    pub(crate) tunables_dirty: AtomicBool,
    pub(crate) tunables: Mutex<Option<LiveTunables>>,
}

Cross-thread controls for the Wayland encode thread, the X11 Controls scheme: the UpdateRate handler stores the current values then flips rate_dirty with Release; the encode thread swaps it with Acquire and re-reads the payload, never seeing it half-applied. force_idr is swapped just before each encode, so an on-demand keyframe lands on the frame ALREADY in flight instead of waiting one pipeline stage for the next publish. reference_reports are what clients said of frames (lost, or held by every one of them), drained ahead of the same encode.

Fields

rate_dirty: AtomicBool

bitrate_kbps: AtomicI32

vbv_mult_milli: AtomicI32

fps_bits: AtomicU64

link_kbps: AtomicI32

The rate the path carries (CaptureSettings::video_link_kbps), read every frame.

force_idr: AtomicBool

scanout_refused: AtomicBool

The zero-copy session refused a client’s buffer handed to it as it stood (a layout its driver does not import), so the capture composites every frame from then on.

scanout_planes: AtomicU32

The planes of one client dmabuf the session’s encoder imports as it stands (FrameEncoder::dmabuf_planes), published by the encode thread; a buffer of more planes is composited.

reference_reports: Mutex<Vec<ReferenceReport>>

tunables_dirty: AtomicBool

Pending per-frame tunables for the encode thread (mutex, not atomics: one struct, set rarely, read only when the dirty flag says so).

tunables: Mutex<Option<LiveTunables>>

Implementations

impl WlEncodeControls

pub(crate) fn new() -> Self