Please provide the following info (check/uncheck the boxes after creating this topic):
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
Target Operating System
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
SDK Manager Version
Host Machine Version
native Ubuntu 18.04
I needed some help to understand how to use APIs available in the DRIVE OS set of libraries to update parameters of necessary sensors and the output of what comes through a related DriveWorks call.
For example, I am working with a camera constellation which has a mix of Sekonix and Entron cameras. We use
dwSensorSerialzer_ methods to compress camera frames before they are pusblished to the rest of the system. However, we currently require updating the default compression parameters so we can experiment with parameters available in NvMedial APIs (been looking at nvmimg_enc etc.).
Since our current application code completely uses DriveWorks calls we only have access to essentially update the bitrate through the serializer params objects, but we need to play with more parameters (for H264 compression). Ideally we would still want to continue using those calls, but just update the configurations so the same
dwSensorSerializer_* calls just uses parameters that we want, instead of the default ones.
Is that possible? From my understanding since DriveWorks is a layer on top of NvMedia (and other DRIVE OS components), in my mind theoretically this should be possible. Or would we need to refactor our application code to directly use DRIVE OS libraries and avoid using DriveWorks?
Please correct me if my understanding is incorrect, or if I missed documentation about this.