
NexVDO SDK · Module A/02
Record
Recording that survives the hours nobody watches. Encode MPEG2, H.264, H.265, or AV1. Run synchronous, time-shift, 3D, encrypted, or pre-record modes, then package output as MP4, TS, MPTS, or M3U8.
- MPEG2 · H.264 · H.265 · AV1
- NVENC · Intel MediaSDK · AMD VCE
- MP4 · TS · MPTS · M3U8
Capture to playback
Package the streamfor the way it will be used.
Select a published codec, hardware path, recording mode, and container. The module supports synchronous, time-shift, 3D, encrypted, and pre-record workflows.
Playback can move frame by frame, support editing, and rewind. YUAN added AV1 to the SDK in January 2023, with Intel Media SDK and NVIDIA NVENC named as the hardware paths.
captured_stream
-> codec: MPEG2 | H.264 | H.265 | AV1
-> hardware_path: NVIDIA NVENC | Intel MediaSDK | AMD VCE
-> mode: synchronous | time_shift | 3D | encrypted | pre_record
-> container: MP4 | TS | MPTS | M3U8// Illustrative sketch — not a published API
- 01
Captured stream
- 02
Hardware encode
- 03
Recording mode
- 04
Container
- 05
Playback / edit
Illustrative Record pipeline from captured stream to playback.
Record capabilities
Encode. Retain. Review.
Use the published acceleration paths
The module lists NVIDIA NVENC, Intel MediaSDK, and AMD VCE for hardware acceleration. AV1 is specifically supported by Intel Media SDK and NVIDIA NVENC.
Keep the moments around the event
Use synchronous, time-shift, 3D, encrypted, or pre-record modes. Select the mode around the capture and review workflow.
Review and package the result
Move through recorded material frame by frame. Edit at frame level and rewind playback. Package output as MP4, TS, MPTS, or M3U8.
Published surface
Four codecs. Three acceleration paths. Four containers.
YUAN publishes the codec, hardware-acceleration, and container sets. Only AV1 has a published codec-to-hardware mapping. Other pairings remain pending publication.
| Codec | Hardware encoder | Container |
|---|---|---|
| MPEG2 | Codec-to-encoder mapping — pending publication | Codec-to-container mapping — pending publication |
| H.264 | Codec-to-encoder mapping — pending publication | Codec-to-container mapping — pending publication |
| H.265 | Codec-to-encoder mapping — pending publication | Codec-to-container mapping — pending publication |
| AV1 | Intel Media SDK · NVIDIA NVENC | Codec-to-container mapping — pending publication |
Record codec × hardware encoder × container. Unpublished mappings remain explicit.
- Published module surfaceNVIDIA NVENC · Intel MediaSDK · AMD VCEMP4 · TS · MPTS · M3U8
- Audio codecsAudio codecs — pending publicationAudio container mapping — pending publication
- Bitrate and profile specificsBitrate specifics — pending publicationProfile specifics — 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 Record on your target hardware
Included free with YUAN hardware, delivered through a supported evaluation path — engineer answer within 48 hours. Share the codec, recording mode, container, and target hardware. An engineer answers with scope.
- Engineer reply in 48h
- Ships from U.S. stock
- Free with YUAN hardware