Skip to main content

Overview

v4l2vp9dec is a hardware-accelerated video decoder that uses the Video4Linux2 (V4L2) stateful decoder API to offload VP9 video decoding to the Qualcomm Video Processing Unit (VPU). This plugin is provided and maintained by the GStreamer community. This document focuses on its usage in conjunction with Qualcomm-specific QIM SDK GStreamer plugins, along with relevant use cases and internal architectural considerations. v4l2vp9dec is typically used to decode VP9 streams provided by:
  • File sources (WebM, Matroska/MKV containers)
  • RTSP sources
  • HLS/HTTP streaming sources (e.g., YouTube, web video)
The element is responsible only for decoding video frames. It does not demux or parse streams on its own — those operations must be handled by peer GStreamer elements upstream (e.g., matroskademux).
VP9 frames are self-contained and self-framing. Unlike H.264/H.265, no separate parse element (e.g., vp9parse) is required between the demuxer and v4l2vp9dec.

Example Pipeline

1

Download Required Files

vp9_1080p.webm file is used here as an example.
2

Copy files to device

3

Connect to device

4

Set environment variables

Run below command on your device
5

Run the pipeline

Key Responsibilities

v4l2vp9dec is responsible for:
  • Hardware acceleration — offloads VP9 decoding to the dedicated VPU
  • V4L2 state management — manages the V4L2 stateful decoder state machine (device open, buffer allocation, stream on/off)
  • Buffer I/O management — handles buffer exchange between GStreamer and the V4L2 driver using DMABuf, MMAP, or UserPtr modes
  • Format negotiation — negotiates raw output formats supported by the hardware, including UBWC-compressed formats (NV12_Q08C, NV12_Q10LE32C) for reduced memory bandwidth
  • Multi-stream support — supports multiple concurrent decoder instances (subject to hardware resource limits)
  • Error handling — supports decoder error controls such as max-errors and corrupted-frame discard behavior

Hierarchy

GObject
   GstObject
      GstElement
         GstVideoDecoder
            GstV4l2VideoDec
               v4l2vp9dec

Pad Templates

sink

src

The exact set of profiles reported depends on what the underlying V4L2 driver enumerates via V4L2_CID_MPEG_VIDEO_VP9_PROFILE (or V4L2_CID_MPEG_VIDEO_VPX_PROFILE). VP9 does not define decoder levels in the V4L2 API; therefore, no level probing is performed.

Element Properties

I/O Mode Values

Both capture-io-mode and output-io-mode accept the same GstV4l2IOMode enumeration:

Internal Architecture

v4l2vp9dec operates using two V4L2 queue objects internally:
  • Output queue (V4L2_BUF_TYPE_VIDEO_OUTPUT) — receives compressed VP9 frame buffers from upstream
  • Capture queue (V4L2_BUF_TYPE_VIDEO_CAPTURE) — produces decoded raw video frames for downstream

State Transitions

Dynamic Resolution Change

v4l2vp9dec supports mid-stream dynamic resolution changes without requiring a pipeline restart, handled through the V4L2 source change event mechanism:
  1. At initialization, the decoder subscribes to V4L2_EVENT_SOURCE_CHANGE events on the capture queue.
  2. When the driver detects a resolution change in the bitstream, it signals the event.
  3. The decoder stops the capture queue, discards the existing buffer pool, re-negotiates format via VIDIOC_G_FMT, sets a new output state with updated dimensions, and reallocates the capture buffer pool.
This allows seamless decoding of adaptive bitrate VP9 streams and content with embedded resolution changes.

Memory and Buffer Management

DMABuf Usage

Setting capture-io-mode=4 exports decoded frame buffers as DMABuf file descriptors. These can be imported directly by waylandsink or qtivcomposer without CPU memory copies, enabling zero-copy pipelines.

Alignment Requirements

Decoded buffers follow Qualcomm hardware alignment requirements (e.g., 128-byte stride alignment).

Format Support

Standard NV12 is common. UBWC (Universal Bandwidth Compression) is supported through formats like NV12_Q08C to reduce memory bandwidth.

Codec Header Initialization

VP9 is a frame-based codec — each VP9 frame is self-contained and does not require a separate out-of-band codec header. The first input buffer is used directly as the initialization data. If the input caps contain codec_data (e.g., VP9 codec private data from a WebM container), that data is sent first.

Latency

The decoder computes and reports pipeline latency based on the minimum number of capture buffers required by the driver and the frame duration:

Drain and Flush

  • Drain — sends V4L2_DEC_CMD_STOP to signal end-of-stream; waits for all remaining frames to be produced
  • Flush — stops both queues, resets buffer pools, and restarts streaming; used during seek operations

Usage

Ensure you have followed the prerequisites before continuing

Decode VP9 from a WebM File and Display

Demonstrates hardware-accelerated VP9 decoding from a WebM file with DMABuf zero-copy for Wayland preview.

Four-Stream Side-by-Side Composition

Demonstrates decoding four VP9 input streams using four hardware decoder instances, arranging them in a 2×2 grid using qtivcomposer, and displaying the composed frame.