dx-agent-stream-validate

Validates dx_stream GStreamer pipelines through static analysis, property checks, and smoke tests.

3|5|Updated Jan 21, 2025
One-click install
npx skills add https://github.com/DEEPX-AI/dx_stream --skill dx-agent-stream-validate-deepx-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dx-agent-stream-validate
Source: https://github.com/DEEPX-AI/dx_stream/tree/main/.deepx/skills/dx-agent-stream-validate
Command: npx skills add https://github.com/DEEPX-AI/dx_stream --skill dx-agent-stream-validate-deepx-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building Vision AI pipelines with DX-Stream GStreamer elements is error-prone: mismatched preprocess-id/inference-id values, missing queue elements, wrong postprocess libraries, and incorrect paths cause deadlocks, segfaults, and silent failures that are hard to diagnose. ## Core Features & Use Cases - Static Analysis Without Hardware: Check shell/Python syntax, GStreamer element registration, postprocess library exports, and path resolution without needing an NPU. - Property Validation: Verify preprocess-id and inference-id consistency across DxPreprocess, DxInfer, and DxPostprocess elements, confirm queue placement between dx elements, and ensure model and library paths are absolute. - Smoke and Performance Testing: Run limited-frame pipeline tests on NPU hardware, validate headless/DISPLAY fallback behavior, and measure FPS and latency with GStreamer tracers. - Use Case: After writing a new object detection pipeline script, run the validation checks to catch a missing queue between dxinfer and dxpostprocess before it deadlocks in production. ## Quick Start Validate my dx_stream pipeline script run_yolov5s.sh for correctness and runtime readiness.

Frequently Asked Questions about dx-agent-stream-validate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a GStreamer dx_stream pipeline before running it?▼

Run static analysis checks first: verify shell syntax with bash -n, confirm element registration with gst-inspect-1.0, and check that postprocess libraries export the PostProcess symbol. These checks work without NPU hardware.

How to check preprocess-id and inference-id matching in dx_stream pipelines?▼

Extract properties from each dxpreprocess, dxinfer, and dxpostprocess element in the pipeline string, then verify every preprocess-id has a matching DxInfer and every inference-id has a matching DxPostprocess. Mismatched IDs cause silent failures with no detections.

Why does my GStreamer pipeline deadlock with x264enc?▼

The pipeline deadlocks because x264enc is missing the tune=zerolatency setting. Add tune=zerolatency to the x264enc element to prevent the encoder's internal buffering from blocking the pipeline.

Can I test dx_stream pipelines without NPU hardware?▼

Yes, Level 1 static analysis and Level 3.5 headless validation run without an NPU. These cover syntax checks, element registration, path resolution, and DISPLAY fallback behavior. Only Level 3 smoke tests require actual NPU hardware.

Why does my dx_stream pipeline show no detections?▼

Missing detections usually come from a preprocess-id mismatch between DxPreprocess and DxInfer, or an inference-id mismatch between DxInfer and DxPostprocess. Verify the IDs match across all connected elements in the pipeline.