NEXVDO SDK — 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.

Request an evaluationSee Record capabilities
Illustrative sketch - not a published API
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
MPEG2 · H.264 · H.265 · AV1
NVENC · Intel MediaSDK · AMD VCE
MP4 · TS · MPTS · M3U8

RECORD CAPABILITIES

Encode. Retain. Review.

HARDWARE PATHS

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.

RECORDING MODES

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.

PLAYBACK + PACKAGING

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.

Record codec × hardware encoder × container. Unpublished mappings remain explicit.
CodecHardware encoderContainer
MPEG2Codec-to-encoder mapping — pending publicationCodec-to-container mapping — pending publication
H.264Codec-to-encoder mapping — pending publicationCodec-to-container mapping — pending publication
H.265Codec-to-encoder mapping — pending publicationCodec-to-container mapping — pending publication
AV1Intel Media SDK · NVIDIA NVENCCodec-to-container mapping — pending publication
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

CAPTURE TO PLAYBACK

Package the stream for 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.

Match target hardware →Recording and analysis systems →
01Captured stream
02Hardware encode
03Recording mode
04Container
05Playback / edit
Illustrative Record pipeline from captured stream to playback

EVALUATION ARTIFACTS

Proof arrives with a named state.

Nothing is represented as public until it is public.

Datasheet

Datasheet — pending publication

Sample code

Sample code — published with evaluation access

Compatibility matrix

Compatibility matrix — pending publication
Browse developer resources →

NEXT MODULE

Continue through the SDK.

Capture

Bring frames from capture cards, multimedia files, and network cameras into GPU memory.

Open module →

Stream

Serve or receive video across published streaming protocol paths.

Open module →

Analysis

Run content, biometric, and behavior analysis at the edge or in the cloud.

Open module →

Buying a product?

You are building your own device — NexVDO SDK plus YUAN hardware inside your product.

Start at the SDK →

Commissioning a system?

You need an integrated stack delivered and supported — hardware, software, and integration through Neteon.

Request scoping →

Put Record on your target hardware

Included free with YUAN hardware, delivered through a supported evaluation path — engineer answer within 48 hours.

Request an evaluation

Share the codec, recording mode, container, and target hardware. An engineer answers with scope.