Holoscan Camera Overview
🚧 Documentation is under development
The Holoscan SDK guide is currently under active development. Some sections may be incomplete or change without notice.
Questions? Contact RidgeRun or email to support@ridgerun.com.
-
Overview
-
Build, Run, and Validate
-
Core Concepts
-
Operators and Graphs
-
Tensor Data and Memory
-
Interprocess Communication
-
-
Application and Operator Development
- Building an HSDK Application
- Writing a Minimal Operator
- Typed Parameters and Configuration
- Reading, Writing, and Forwarding Data
- Writing Tensor Operators
- Complete Operator Patterns
- Authoring Runtime Behavior
- Runtime Parameter Updates
- Lifecycle Callbacks and Restart Control
- Performance and Debugging
- SDK Source Map
-
Operator Reference
-
Core Operators
-
Holoscan Camera
-
Holoscan RidgeRun
- Overview
- Build and Installation
- ArgusCameraOp
- V4L2SourceOp
- V4L2UserPtrSourceOp
- BgraToPlanarTensorOp
- RawBayerToBgraOp
- RawBayerToYoloTensorOp
- YuyvToBgraOp
- TensorRtInferenceOp
- DrmDisplayOp
- DrmBgraDisplayOp
- X11DisplayOp
- CudaCompositorOp
- DepthColorizerOp
- FakesinkOp
- FrameSkipperOp
- InterprocessSrcOp
- TestPatternOp
-
-
Migration from Holoscan 4.x
-
Examples
-
Core
-
Holoscan Camera
-
Holoscan RidgeRun
-
-
Benchmark and Use Cases
-
Holoscan vs GStreamer
- Overview
-
Capture and Display
-
Capture and Inference
- Compare the workloads
- Implemented Applications
- Framework Selection
- Interprocess
-
Holoscan Camera Overview
Holoscan Camera provides two capture paths for bringing Linux video devices and SIPL camera rigs into an HSDK application. Use the comparison below to choose the path that fits your camera stack and the processing stage that will consume its frames.
Choose a Capture Path
| Path | Platform and device | Published data | Memory placement | Good starting point for |
|---|---|---|---|---|
| V4L2CaptureOp | A Linux V4L2 device exposed through a video device node. | Packed YUYV in an image payload. | Host, pinned host, or CUDA device memory. | A camera or video source that already exposes a V4L2 mode. |
| SIPLCaptureOp | A camera rig managed by the NVIDIA SIPL stack. | RAW10 or NV12 image data plus per-frame sensor metadata. | Host, pinned host, or CUDA device memory. | A configured sensor rig that needs camera indices, metadata, or multi-camera capture. |
Both operators publish the SDK's typed image payload. Its descriptor carries the image format and geometry, while the Tensor storage carries the bytes consumed by the next operator. The selected memory placement becomes part of the graph contract, so choose it according to the first consumer that needs the frame.
Follow the Camera Path
Start with Build and Installation to build the module against the SDK installation used by your application.
Continue with V4L2CaptureOp when the source is a Linux video device. Continue with SIPLCaptureOp when the source is a configured SIPL rig.
The SIPL Frame Saver Example and SIPL Stereo Monitor Example are hardware-dependent paths for inspecting captured data and comparing two streams. For the broader SDK setup and API route, see the NVIDIA Holoscan SDK User Guide.