For embedded video equipment, UAV payloads, vehicle systems, industrial cameras and other specialized applications, customers sometimes need much more than a standard video encoder or DVR board.
A typical requirement may involve two independent CVBS video inputs, simultaneous video processing, picture-in-picture (PIP), video overlay, customized OSD, real-time recording and external telemetry data integration — all within a compact standalone PCB.
At Onvon, possiamo fornire OEM/ODM customization based on existing video-processing platforms, allowing customers to modify a proven hardware platform instead of developing an entire video-processing system from scratch.
Typical Custom Video Processing Requirement
One recent type of project requires the following operating workflow:
Ingresso CVBS 1 + Ingresso CVBS 2 → Simultaneous Processing → PIP / Overlay / Fusion → OSD → Recording + Uscita video
The important point is that both video inputs must be processed simultaneously.
This is different from a simple two-camera video switcher, where only one video source is selected and displayed at a time.
The target system needs to keep both video streams available for real-time processing and combine them into the final output image.
1. Dual CVBS Video Inputs
The customized PCB can be designed around two independent analog video inputs.
Typical requirements include:
- 2 × independent CVBS inputs
- AMICO 720 × 576 supporto
- NTSC support where required
- Simultaneous processing of both video inputs
- No simple video switching
- Real-time PIP or overlay processing
This type of architecture can be useful when two cameras need to remain active simultaneously.
Per esempio:
Telecamera 1 → Main Video
Telecamera 2 → Secondary PIP Video
The final processed image can then be displayed, recorded and transmitted through the selected video output interface.
2. Real-Time PIP and Video Overlay
Picture-in-picture is one of the key requirements for this type of project.
The secondary video image may need adjustable:
- Position
- Width and height
- Scaling
- Overlay mode
- Transparency
- Display area
A typical application may require the second video window to be moved to different locations on the main video image.
Per esempio:
Main CVBS Video + Secondary CVBS Video → PIP Output
Where supported by the selected processor/platform, transparency or alpha-blending functions can also be considered.
If true alpha blending is not available on the existing platform, the available overlay and PIP modes can be evaluated during the customization stage.
The exact PIP capability depends on the selected processor, video decoder and existing firmware architecture.
3. OSD and External Data Integration
Another important requirement is customizable OSD.
The system may need to display information such as:
- Battery voltage
- Battery percentage or estimated battery level
- Compass heading
- Magnetic or geographic heading
- Coordinate GPS
- Date and time
- User-defined text
- Other telemetry information
External data can potentially be received through interfaces such as:
- UART
- RS232
- RS422
- USB
- GPIO
- ADC
Per esempio, a customer’s external controller could send GPS, compass and battery information through UART.
The video-processing firmware can then use this data to generate the corresponding OSD information on the live video.
A typical data flow could be:
GPS / Compass / Battery Sensor → UART / External Interface → Video Processing PCB → OSD → Video Output + Registrazione
The exact interface and protocol can be customized according to the customer’s equipment.
4. Real-Time Video Recording
For many embedded applications, recording is not an optional feature.
The required architecture may be:
Two CVBS Inputs → PIP / Overlay / OSD → Final Video → H.264/H.265 Encoding → SD Card / eMMC
The customer may require:
- Real-time continuous recording
- H.264 or H.265 encoding
- SD card recording
- eMMC recording
- Automatic file segmentation
- Recording recovery after power interruption
- Recording of the final processed image
- OSD included in the recorded video
The key requirement is that the processed PIP/overlay image must be recorded, rather than simply recording one of the original camera inputs.
This makes the system suitable for standalone embedded operation without requiring a PC.
5. Uscita video
Depending on the project, different video output interfaces can be considered.
Possible interfaces include:
- CVBS PAL output
- HDMI
- BT.656
- MIPI
- Other digital video interfaces
For some embedded applications, CVBS remains preferable because it can be connected directly to existing displays, transmitters or video systems.
For other applications, HDMI or a digital video interface may be more appropriate.
The output interface can therefore be selected according to the customer’s existing system architecture.
6. Compact Embedded PCB Design
The target size for this type of project is often less than:
100 × 100 mm
A smaller PCB may be possible depending on the processor, decodificatore, encoder, memoria, storage and interface requirements.
The final board can be supplied as a bare PCB or embedded module, without an enclosure.
This makes it suitable for integration into:
- UAV payload equipment
- Vehicle video systems
- Industrial equipment
- Portable monitoring systems
- Robotica
- Specialized camera systems
- Custom DVR equipment
- OEM video products
7. 12V DC Power Supply
For this type of application, the customer may require a DC input in the range of 5–12V.
For some existing platforms, Tuttavia, 12V DC is required.
Power consumption depends on the selected processor, video encoder, storage device, output interface and peripheral configuration.
During the OEM/ODM evaluation, we can provide the expected typical and maximum power consumption based on the final hardware configuration.
8. Firmware Customization
Hardware is only one part of a customized video-processing solution.
The firmware may also need to be modified for the customer’s application.
Possible firmware customization includes:
- PIP configuration
- Video overlay
- OSD layout
- OSD data protocol
- UART command interface
- External telemetry integration
- Recording configuration
- File segmentation
- Startup configuration
- Video output configuration
- Firmware upgrade functions
Where available, SDK/API documentation can also be provided for further customer-side development.
The final system is intended to operate as a standalone embedded video-processing module, without requiring a PC during normal operation.
9. Existing Platform vs. New Development
For OEM projects, starting with an existing proven platform can significantly reduce development risk compared with developing the entire system from zero.
Instead of designing:
Decodificatore video + Processor + Encoder + Magazzinaggio + OSD + Interfacce + Firmware
from scratch, we can evaluate an existing video-processing PCB and determine which functions can be retained and which functions need customization.
The development process may include:
- Customer provides detailed technical requirements.
- We identify the closest existing hardware platform.
- Engineering evaluates processor, decodificatore, encoder and memory resources.
- Existing PIP/overlay/OSD/recording functions are evaluated.
- Hardware interfaces are confirmed.
- Firmware customization requirements are defined.
- Prototype or sample units are prepared.
- Customer performs functional testing.
- Firmware and hardware are refined if required.
- Customized production begins after approval.
This approach is particularly suitable when the customer wants to develop a specialized product but does not want to start the entire hardware and firmware development process from zero.
10. Example OEM/ODM Requirement
A typical project specification may look like this:
| Funzione | Typical Requirement |
|---|---|
| Ingresso video | 2 × independent CVBS |
| Video Standard | AMICO 720 × 576, NTSC optional |
| Processing | Simultaneous dual-channel processing |
| PIP | Necessario |
| Overlay | Necessario |
| PIP Position | Regolabile |
| PIP Size | Regolabile |
| Transparency | Preferably adjustable |
| OSD | Necessario / personalizzabile |
| Registrazione | Necessario |
| Codec | H.264 / H.265 |
| Magazzinaggio | Scheda SD / eMMC |
| Recording Mode | Continuo |
| Produzione | CVBS / HDMI / digital interface |
| External Data | UART / RS232 / RS422 / USB / GPIO / ADC |
| Energia | 12V DC for selected platform |
| PCB Size | Preferably below 100 × 100 mm |
| Firmware | Personalizzabile |
| SDK/API | Depending on platform |
The final specification is determined after engineering evaluation of the selected hardware platform.
11. Dual-Camera and Thermal Imaging Applications
The same type of video-processing architecture can also be used with dual-camera systems.
Per esempio, a visible-light camera and thermal imaging camera can be combined into a single embedded video-processing system.
640×512 Dual-Light Thermal Imaging Module
Our dual-light camera solutions can combine thermal imaging and visible-light imaging and may be suitable for applications requiring day/night or multi-sensor video.
For certain customized camera systems, the video input architecture and control interface can also be evaluated according to the customer’s application.
12. OEM/ODM Video Processing PCB Development
If your project requires a customized embedded video-processing board, we can evaluate whether an existing platform can be used as the hardware foundation.
Typical customization projects may involve:
Dual CVBS Input
→ Decodifica video
→ PIP / Overlay / Fusione
→ OSD
→ H.264/H.265 Encoding
→ SD Card / eMMC Recording
→ CVBS / HDMI / Digital Video Output
with external interfaces for GPS, compass, battery and other telemetry information.
The actual processor, video decoder, encoder, memoria, storage, interfacce, PCB dimensions and firmware functions depend on the selected platform and project requirements.
Contact Us for a Custom Video Processing PCB
Please provide your required:
- Video input format
- Video output format
- PIP requirements
- Recording requirements
- OSD information
- External data interfaces
- Storage requirements
- Alimentazione elettrica
- Dimensioni del circuito stampato
- Expected quantity
- Firmware customization requirements
Our engineering team can then evaluate the closest existing platform and determine what can be customized for your application.
OEM/ODM projects are welcome for prototype development and customized production.
Fai una domanda
Grazie per la risposta. ✨