DeepStream Reference Designs/Customizing the Project/Implementing Custom Media: Difference between revisions

It is well known that any Media application that involves Computer Vision and AI processing tasks may require the use of different types of cameras that capture the input information to the system. That is why the design of this system provides flexibility in the section that involves selecting the camera type. As previously indicated and shown in the class diagram, each instance of Media created by the Custom Factory uses a Media Descriptor as an input parameter. Using this descriptor it is possible to abstract the camera component used. For example, in the [https://developer.ridgerun.com/wiki/index.php/DeepStream_Reference_Designs/Reference_Designs/Automatic_Parking_Lot_Vehicle_Registration APLVR Reference Design], a URL is used as a central component of the descriptor that refers to a camera that transmits via RTSP, which is adapted to the context of a monitoring system in a parking lot with several cameras. This description is used by the Gstreamer Daemon plugin (custom component used in APLVR to create Media instances), which creates a Gstreamer pipeline that encapsulates the flow of information received.

If you want to support another type of camera, such as receiving information through the nvarguscamerascr module with cameras directly connected to the Jetson, it would suffice to modify the Media Descriptor and reuse the custom Media implementation. Of course, we remember that the specific implementations of both the module in charge of abstracting the Media, as well as the type of camera indicated in the descriptor, are left to the user decision who uses this reference design as a basis for other applications.