NexVDO SDK · Module A/01
Capture
Frames in GPU memory, in your first session. Ingest capture cards, multimedia files, and network cameras. Move frames through GPUDirect DMA, then render, compose, or hand them to the next module.
- Capture cards · files · network cameras
- GPUDirect DMA to GPU memory
- Windows · Linux · embedded
Source to output
Keep the frameon the fast path.
The capture path starts with a card, file, or network camera. GPUDirect DMA places the image in GPU memory. The frame is then ready for rendering or encoding.
YUAN’s Capture module page states: “only 4 APIs, allowing you to capture video and audio within just five minutes.”
source = capture_card | multimedia_file | network_camera
frame = dma_capture(source, destination = gpu_memory)
adjust(frame, brightness, hue, contrast, saturation)
transform(frame, scale, crop, rotate)
output(frame, render_or_encode)// Illustrative sketch — not a published API
- 01
Source
- 02
DMA
- 03
GPU memory
- 04
Render / encode
Illustrative Capture pipeline from source to render or encode.
Capture capabilities
Move the frame. Keep control.
Capture into GPU memory
NVIDIA GPUDirect enables high-performance DMA capture direct to GPU memory. It removes a later memory-transfer step from the pipeline.
Shape the frame before output
ThumbDraw supports multi-screen rendering. Adjust brightness, hue, contrast, and saturation. Scale, crop, and rotate with CPU or GPU processing.
Carry overlays and imaging data
Use ChromaKey, OSD, layouts, and XML-driven animation. DICOM, PACS, WORKLIST, and HL7 support clinical imaging workflows.
Published surface
Three input paths. Four referenced frameworks.
YUAN publishes the input classes, framework surface, and operating-system surface. The per-input compatibility mapping has not been published.
| Input path | Framework | Operating system |
|---|---|---|
| Capture cards | Input-to-framework mapping — pending publication | Per-input OS support — pending publication |
| Multimedia files | Input-to-framework mapping — pending publication | Per-input OS support — pending publication |
| Network cameras | Input-to-framework mapping — pending publication | Per-input OS support — pending publication |
Capture input paths × framework × operating system. Unpublished mappings remain explicit.
- Published module surfaceDirectShow · Media Foundation · V4L2 · GStreamerWindows · Linux · embedded
- Resolution and format matrixResolution matrix — pending publicationFormat matrix — pending publication
Evaluation artifacts
Proof arrives with a named state.
Nothing is represented as public until it is public.
- DatasheetDatasheet — pending publication
- Sample codeSample code — published with evaluation access
- Compatibility matrixCompatibility matrix — pending publication
Next module
Continue through the SDK.
Buying a product?
You are building your own device — NexVDO SDK plus YUAN hardware inside your product.
Start at the SDK01Commissioning a system?
You need an integrated stack delivered and supported — hardware, software, and integration through Neteon.
Request scoping02Need a human?
Engineers answer evaluation requests within 48 hours. Business and hardware questions route to Neteon — YUAN’s U.S. front door.
Put Capture on your target hardware
Included free with YUAN hardware, delivered through a supported evaluation path — engineer answer within 48 hours. Share the source, target platform, and output path. An engineer answers with scope.
- Engineer reply in 48h
- Ships from U.S. stock
- Free with YUAN hardware