Custom Dual CVBS Video Processing PCB with PIP, OSD and Recording

Many embedded video applications require more than a standard video encoder or DVR board.

An OEM project may require two independent CVBS video inputs, simultaneous video processing, picture-in-picture (PIP), video overlay, customizable OSD, real-time H.264/H.265 recording, and live video output in one compact embedded PCB.

OnVon provides OEM and ODM video processing solutions based on existing video-processing platforms and can evaluate hardware and firmware customization for specific applications.

The goal is to use a proven video-processing platform wherever possible instead of developing the entire system from scratch.

Dual CVBS Video Processing PCB for OEM Applications

A typical application architecture is:

CVBS Input 1 + CVBS Input 2 → Simultaneous Processing → PIP / Overlay / Fusion → OSD → Recording + Video Output

The important difference between this type of system and a conventional video switcher is that both video inputs need to remain available for simultaneous processing.

The final processed image can then be displayed, recorded, or transmitted to another system.

1. Two Independent CVBS Video Inputs

A customized dual CVBS video processing board can be designed around two independent analog video inputs.

Typical requirements include:

  • 2 × independent CVBS video inputs
  • PAL 720 × 576 support
  • NTSC support where required
  • Simultaneous processing of both video sources
  • Real-time PIP or overlay
  • No simple one-channel-at-a-time video switching

This architecture can be used when two cameras must remain active simultaneously.

For example:

Camera 1 → Main Video

Camera 2 → Secondary PIP Video

The two sources are processed by the video-processing system and combined into a final output image.

2. Real-Time PIP and Video Overlay

Picture-in-picture is a key function for many dual-camera video systems.

The secondary video window may require adjustable:

  • Position
  • Width
  • Height
  • Scaling
  • Overlay mode
  • Display area
  • Transparency

For example, the secondary video can be displayed in a corner of the main video image.

Main CVBS Video + Secondary CVBS Video → PIP Output

Where supported by the selected processor and video-processing platform, alpha blending or transparency control can also be considered.

If true alpha blending is not available, the available overlay and PIP modes can be evaluated during the engineering stage.

The exact functionality depends on the selected video processor, decoder, memory architecture and firmware.

3. Video Overlay and OSD

A customized video processing PCB may also need to add information directly onto the live video.

Typical OSD information can include:

  • Battery voltage
  • Battery percentage
  • Estimated battery level
  • Compass heading
  • Magnetic heading
  • Geographic heading
  • GPS coordinates
  • Date and time
  • User-defined text
  • Custom telemetry information

The OSD can be generated after the two video sources are combined.

A typical processing path is:

Dual CVBS Input → PIP / Overlay → OSD → Final Video

This allows the same processed image to be used for both live display and recording.

4. External Telemetry and Data Interfaces

For applications requiring battery, GPS or compass information, the video-processing PCB needs an external data interface.

Depending on the selected platform, interfaces may include:

  • UART
  • RS232
  • RS422
  • USB
  • GPIO
  • ADC

For example:

GPS / Compass / Battery Sensor → UART → Video Processing PCB → OSD

The external telemetry protocol can be customized according to the customer’s equipment.

This is particularly useful for embedded systems where the video-processing module needs to combine camera images with real-time system information.

5. Real-Time Video Recording Is a Core Requirement

For many OEM applications, recording is not optional.

The required processing path may be:

CVBS 1 + CVBS 2 → PIP / Overlay → OSD → H.264/H.265 Encoding → SD Card / eMMC

Potential recording functions include:

  • Continuous recording
  • H.264 recording
  • H.265 recording
  • SD card storage
  • eMMC storage
  • Automatic file segmentation
  • Recording recovery after power interruption
  • Recording of the final processed image
  • OSD included in the recorded video

An important requirement is that the PIP/overlay/OSD processed image should be available for recording during live operation.

The system should not depend on playback of previously recorded video files to perform PIP processing.

6. Live Video Output

The final processed video can be provided through one or more supported output interfaces.

Possible options include:

  • CVBS PAL
  • HDMI
  • BT.656
  • MIPI
  • Other digital video interfaces

CVBS output can be particularly useful when the customized PCB needs to integrate with an existing analog video system.

HDMI or digital video interfaces may be more suitable for newer embedded systems.

The appropriate output interface depends on the target system and selected hardware platform.

7. H.264 and H.265 Video Processing

For recording and digital video applications, hardware H.264/H.265 encoding can reduce storage requirements compared with uncompressed video.

OnVon already provides compact CVBS-to-IP encoder platforms supporting H.264/H.265 encoding and PAL/NTSC video input. For example, one existing CVBS encoder platform uses an SSC335-based main control platform and measures approximately 38.8 × 38.8 mm.

However, a dual-input PIP recording application has different requirements from a conventional single-channel CVBS-to-IP encoder.

For an OEM project, the existing hardware and firmware architecture must therefore be evaluated before confirming the final configuration.

8. Compact Embedded PCB Design

A target PCB size below:

100 × 100 mm

is suitable for many embedded applications.

Depending on the processor, video decoder, encoder, memory, storage and interface requirements, a smaller PCB may also be possible.

A bare PCB or module can be supplied without an enclosure.

Potential applications include:

  • Embedded camera systems
  • Vehicle video systems
  • Robotics
  • Industrial monitoring
  • Portable video equipment
  • UAV payload equipment
  • Specialized DVR systems
  • Multi-camera systems
  • OEM video products

9. 12V DC Power Supply

Power requirements depend on the selected processor, video decoder, encoder, memory, storage and peripheral interfaces.

For some existing platforms, 12V DC input is required.

For a customized project, the engineering team can evaluate the required power architecture and provide typical and maximum power consumption based on the final configuration.

Low-power operation can also be considered during hardware selection and PCB development.

10. Firmware Customization

A successful OEM video-processing project normally requires both hardware and firmware evaluation.

Possible firmware customization includes:

  • PIP configuration
  • PIP position
  • PIP size
  • Overlay mode
  • OSD layout
  • OSD data protocol
  • UART command interface
  • Telemetry integration
  • Recording configuration
  • File segmentation
  • Video output configuration
  • Startup configuration
  • Firmware upgrade functions

Depending on the selected platform, an SDK or API may also be available for further customer development.

The final device can be designed as a standalone embedded video-processing module without requiring a PC during normal operation.

11. Existing Platform or New Custom Development?

Not every OEM project needs a completely new PCB.

Where possible, using an existing video-processing platform can reduce development effort and provide a proven starting point.

Instead of developing all of the following from zero:

Video Decoder + Processor + Encoder + Storage + OSD + Interfaces + Firmware

the engineering team can first evaluate whether an existing platform can provide the required foundation.

The typical development process is:

  1. Customer provides technical requirements.
  2. Existing platforms are evaluated.
  3. Processor and video decoder architecture are checked.
  4. Video input and output interfaces are confirmed.
  5. PIP and overlay functions are evaluated.
  6. Recording architecture is evaluated.
  7. OSD and telemetry requirements are defined.
  8. Hardware modifications are designed if necessary.
  9. Firmware customization is developed.
  10. Prototype samples are tested.
  11. Production configuration is finalized.

This approach can be particularly useful for customers developing a specialized embedded video product.

12. Dual-Camera and Thermal Imaging Applications

Dual-video processing can also be used with visible-light and thermal imaging cameras.

For applications requiring simultaneous visible and thermal imaging, a dual-light camera can provide two complementary video sources for further processing.

Related product:

640×512 Dual-Light Thermal Imaging Module

Depending on the application, the camera interface, video processing architecture and external control interface can be evaluated as part of an OEM project.

13. OEM/ODM Video Processing PCB Development

OnVon provides customized video hardware and firmware development for projects requiring functions beyond standard encoder or decoder products.

A typical customized architecture may include:

2 × CVBS Input

↓

Video Decoding

↓

PIP / Overlay / Fusion

↓

OSD

↓

H.264 / H.265 Encoding

↓

SD Card / eMMC Recording

↓

CVBS / HDMI / Digital Video Output

External interfaces can be added for:

GPS + Compass + Battery + Telemetry

The exact processor, decoder, encoder, memory, storage, interfaces and firmware functions depend on the selected platform and final project requirements.

14. What Information Should You Provide for an OEM Project?

To evaluate a custom video-processing PCB efficiently, please provide:

  • Number of video inputs
  • CVBS / HDMI / SDI / other video formats
  • PAL / NTSC requirements
  • Required video resolution and frame rate
  • PIP requirements
  • PIP position and size
  • Transparency or alpha-blending requirements
  • Video output interface
  • Recording requirement
  • H.264 or H.265 preference
  • SD card or eMMC storage
  • OSD information
  • GPS / compass / battery data requirements
  • UART / RS232 / RS422 / USB / GPIO / ADC requirements
  • Power supply
  • Target PCB dimensions
  • Operating temperature
  • Prototype quantity
  • Expected production quantity
  • Firmware customization requirements
  • SDK/API requirements

With this information, we can evaluate the closest existing platform and determine which functions can be used directly and which functions require customization.

FAQ: Dual CVBS Video Processing PCB

Can two CVBS video inputs be processed simultaneously?

Yes, a customized video-processing platform can be evaluated for simultaneous processing of two independent CVBS inputs. The exact capability depends on the selected processor and video decoder architecture.

Can the PCB perform PIP in real time?

Real-time PIP can be implemented on suitable video-processing platforms. PIP position, size and available overlay modes depend on the selected hardware and firmware.

Can the PIP image be recorded?

The target architecture can be designed so that the final processed image, including PIP and OSD, is encoded and recorded. The exact recording method depends on the selected platform.

Can H.264 or H.265 be used for recording?

H.264 and H.265 hardware encoding are available on selected video-processing platforms. The final codec should be confirmed during the platform evaluation.

Can OSD display GPS and compass information?

Yes, GPS, compass, battery and other telemetry information can potentially be received through an external interface such as UART and displayed through the customized OSD.

Can battery voltage be displayed on the video?

Battery voltage can be integrated into the OSD when the required battery data is provided through a suitable external interface such as ADC or telemetry input.

Is alpha blending supported?

Alpha blending or adjustable transparency depends on the selected processor and existing video-processing architecture. If true alpha blending is unavailable, other PIP or overlay modes can be evaluated.

Can the PCB be smaller than 100 × 100 mm?

The target size can be below 100 × 100 mm. The achievable dimensions depend on the selected processor, decoder, encoder, memory, storage and required interfaces.

Is 12V power supported?

Some existing platforms require 12V DC input. The power architecture can be evaluated according to the customer’s final requirements.

Can the firmware be customized?

Yes. Firmware customization can be considered for PIP, OSD, telemetry, recording, interfaces, startup behavior and other application-specific functions.

Is an SDK or API available?

SDK/API availability depends on the selected hardware platform and project requirements. It can be evaluated during the OEM/ODM technical review.

Request a Custom Video Processing PCB

If you are looking for a dual CVBS video processing PCB, PIP recording board, custom video encoder board or embedded video-processing solution, send us your technical requirements.

Our engineering team can evaluate an existing platform first and determine whether it can be adapted to your application.

OEM and ODM projects are welcome from prototype quantities to customized production.

Contact OnVon with your video inputs, PIP requirements, recording requirements, OSD data, interfaces, power supply, PCB size and expected quantity.

Scroll to Top