GStreamer Qt Overlay for Embedded Systems - Similar Solutions

From RidgeRun Developer Wiki


Previous: Performance/pc Index Next: Troubleshooting





Similar Solutions

At RidgeRun, we know how important it is to perform content overlaying by taking advantage of the platform resources, in particular, having minimum impact on the systems so that other applications are unaffected in performance. Because of that, RidgeRun has three content overlay solutions to cope with the exigencies of the market in embedded systems:

With various video overlay options available, we've created a comparison table that highlights the key features and benefits of each option.

Fast Embedded Overlay QtOverlay HTML Overlay
CPU-only GPU-accelerated GPU-accelerated
Basic shapes: two texts, a logo and a date. Complex contents in QML: fonts, texts, images, shapes, animations. Complex graphics in local or remote HTML: fonts, texts, images, shapes, animations.
Content update matching the framerate. Content update matching the framerate. Content update asynchronous at a different rate (<= 30 Hz).
Dynamic contents through GStreamer properties Dynamic contents using QML attributes through GStreamer properties Dynamic contents from the web using JavaScript through the web service
Focus on consuming low resources. Focused on speed and balance. Focused on the complexity of the contents.
YUV input formats RGBA input formats (NV12 in Jetson) RGBA input formats
Optimised for small devices with CPU only Optimised for x86, NVIDIA Jetson and NXP i.MX Optimised for x86, NVIDIA Jetson and NXP i.MX
Low computational resources Balanced computational resources Computational resources proportional to opening a webpage
Dependencies are under LGPLv2 and permissive licenses. Dependencies are under LGPLv2. Qt components are either under LGPLv2, LGPLv3 or permissive. Dependencies are under LGPLv2 and permissive licenses.


Previous: Performance/pc Index Next: Troubleshooting