{"id":42966685,"url":"https://github.com/robolaunch/deepstream-test5-playground","last_synced_at":"2026-01-31T00:01:10.485Z","repository":{"id":239142249,"uuid":"792216458","full_name":"robolaunch/deepstream-test5-playground","owner":"robolaunch","description":null,"archived":false,"fork":false,"pushed_at":"2024-05-10T07:39:03.000Z","size":250,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2024-05-10T09:42:22.734Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/robolaunch.png","metadata":{"files":{"readme":"README","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2024-04-26T08:03:02.000Z","updated_at":"2024-05-10T09:42:25.412Z","dependencies_parsed_at":"2024-05-10T09:42:25.134Z","dependency_job_id":"8fe20d24-315d-4123-838f-3d171b08ea70","html_url":"https://github.com/robolaunch/deepstream-test5-playground","commit_stats":null,"previous_names":["robolaunch/deepstream-test5-playground"],"tags_count":1,"template":false,"template_full_name":null,"purl":"pkg:github/robolaunch/deepstream-test5-playground","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/robolaunch%2Fdeepstream-test5-playground","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/robolaunch%2Fdeepstream-test5-playground/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/robolaunch%2Fdeepstream-test5-playground/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/robolaunch%2Fdeepstream-test5-playground/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/robolaunch","download_url":"https://codeload.github.com/robolaunch/deepstream-test5-playground/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/robolaunch%2Fdeepstream-test5-playground/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28923736,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-30T22:32:35.345Z","status":"ssl_error","status_checked_at":"2026-01-30T22:32:31.927Z","response_time":66,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2026-01-31T00:01:09.587Z","updated_at":"2026-01-31T00:01:10.475Z","avatar_url":"https://github.com/robolaunch.png","language":"C","funding_links":[],"categories":[],"sub_categories":[],"readme":"*****************************************************************************\n* Copyright (c) 2018-2023 NVIDIA Corporation.  All rights reserved.\n*\n* NVIDIA Corporation and its licensors retain all intellectual property\n* and proprietary rights in and to this software, related documentation\n* and any modifications thereto.  Any use, reproduction, disclosure or\n* distribution of this software and related documentation without an express\n* license agreement from NVIDIA Corporation is strictly prohibited.\n*****************************************************************************\n\n*****************************************************************************\n                     deepstream-test5-app\n                             README\n*****************************************************************************\n\n===============================================================================\n1. Prerequisites:\n===============================================================================\n\nPlease follow instructions in the deepstream_sdk_release_package/README on how\nto install the prerequisites for Deepstream SDK, the DeepStream SDK itself and\nthe apps.\n\nAdditionally you must have the following development packages installed\n\n    GStreamer-1.0\n    GStreamer-1.0 Base Plugins\n    GStreamer-1.0 gstrtspserver\n    X11 client-side library\n    Glib json library - json-glib-1.0\n    yaml-cpp\n\nTo install these packages, execute the following command:\n$ sudo apt-get install libgstreamer-plugins-base1.0-dev libgstreamer1.0-dev \\\n   libgstrtspserver-1.0-dev libx11-dev libjson-glib-dev libyaml-cpp-dev\n\nAlso refer ../deepstream-test4/README for detailed Dependencies for the various\nsupported IoT protocols\n\n===============================================================================\n2. Purpose:\n===============================================================================\n\nThis document shall describe about the sample deepstream-test5 application.\n\nThis sample builds on top of the deepstream-app sample to demonstrate how to:\n\n* Use \"nvmsgconv\" and \"nvmsgbroker\" plugins in the pipeline.\n* Create NVDS_EVENT_MSG_META type of meta and attach to buffer.\n* Use NVDS_EVENT_MSG_META for different types of objects e.g. vehicle, person etc.\n* Provide copy / free functions if meta data is extended through \"extMsg\" field.\n\n\"nvmsgconv\" plugin generates the \"DeepStream Schema\" payload in Json format using\n1) NVDS_EVENT_MSG_META type of metadata from the buffer\n   OR\n2) NvDsFrameMeta and NvDsObjectMeta structures from NvDs metadata\n\nStatic properties of schema are read from configuration file in the form of key-value pair.\nCheck dstest5_msgconv_sample_config.txt for reference. Generated payload is attached\nas NVDS_META_PAYLOAD type metadata to the buffer.\n\n\"nvmsgbroker\" plugin extracts NVDS_META_PAYLOAD type of metadata from the buffer\nand sends that payload to the server using protocol adaptor APIs.\n\nGenerating custom metadata for different type of objects:\nIn addition to common fields provided in NvDsEventMsgMeta structure, user can\nalso create custom objects and attach to buffer as NVDS_EVENT_MSG_META metadata.\nTo do that NvDsEventMsgMeta provides \"extMsg\" and \"extMsgSize\" fields. User can\ncreate custom structure, fill that structure and assign the pointer of that\nstructure as \"extMsg\" and set the \"extMsgSize\" accordingly.\nIf custom object contains fields that can't be simply mem copied then user should\nalso provide function to copy and free those objects.\n\nRefer generate_event_msg_meta() to know how to use \"extMsg\" and \"extMsgSize\"\nfields for custom objects and how to provide copy/free function and attach that\nobject to buffer as metadata.\n\nJson \u0026 Protobuf payload formats are supported.\nChoose config options as below, refer to config files here:\n  configs/test5_dec_infer-resnet_tracker_sgie_tiled_display_int8.txt\n  configs/test5_dec_infer-resnet_tracker_sgie_tiled_display_int8.yml\n\nPAYLOAD_DEEPSTREAM - Full message schema with separate payload per object (Default)\nPAYLOAD_DEEPSTREAM_MINIMAL - Minimal message with multiple objects in single payload.\nPAYLOAD_DEEPSTREAM_PROTOBUF - Protobuf encoded message with multiple objects in single payload.\n\n===============================================================================\n3. To compile:\n===============================================================================\n\n  $ Set CUDA_VER in the MakeFile as per platform.\n      For both Jetson \u0026 x86, CUDA_VER=12.2\n  $ sudo make (sudo not required in case of docker containers)\n\nNOTE: To compile the sources, run make with \"sudo\" or root permission.\n\n===============================================================================\n4. Usage:\n===============================================================================\nThe application supports txt/yml config files -\n\n$ ./deepstream-test5-app -c configs/test5_config_file_src_infer.txt -p 1\n$ ./deepstream-test5-app -c configs/test5_dec_infer-resnet_tracker_sgie_tiled_display_int8.txt -p 0\n\n$ ./deepstream-test5-app -c configs/test5_config_file_src_infer.yml -p 1\n$ ./deepstream-test5-app -c configs/test5_dec_infer-resnet_tracker_sgie_tiled_display_int8.yml -p 0\n\n===============================================================================\n5. Config files provides with this package\n===============================================================================\n1) test5_config_file_src_infer.txt(.yml) -\nA 4 X File(mp4) stream analytics pipeline config\n2) test5_dec_infer-resnet_tracker_sgie_tiled_display_int8.txt(.yml) -\nA 2 X RTSP Camera analytics pipeline config\n3) test5_config_file_src_infer_tracker_sgie.txt(.yml) -\nA 4 X File(mp4) stream analytics pipeline config with SGIE usage\n\nPlease provide message broker connection string in [sink1] section\n\n===============================================================================\n5.1 IoT Protocols supported and cloud configuration\n===============================================================================\nDetails on the IoT Protocols (like KAFKA, Azure, AMQP, etc)\nsupported by nvmsgbroker plugin is listed in the DeepStream Plugin Manual.\n\nDeepStream Public documentation may be referred to setup IoT hubs/servers/brokers\nspecific to the protocol in use.\n\n[sink] group keys associated with type=6 for nvmsgconv and nvmsgbroker\nconfiguration are discussed in the DeepStream_Development_Guide -\u003e\nReference Application Configuration -\u003e Configuration Groups.\n\n===============================================================================\n6. Option -p [Default=0]\n===============================================================================\n\n  6.1 -p 0 (PLAYBACK=0)\n  (Base UTC timestamp for meta-data from RTCP SR for RTSP Sources\n              only; any sources other than type=4 will default to PLAYBACK=1)\n  $ ./deepstream-test5-app -c test5_dec_infer-resnet_tracker_sgie_tiled_display_int8.txt -p 0\n  ==============================================================================\n  NOTE 1: For RTSP Streams, Config file shall use 'type=4'(NV_DS_SOURCE_RTSP)\n  in [source] groups\n  ==============================================================================\n  NOTE 2: If the RTSP Camera/Server does not send RTCP Sender Report - or until\n  the first Sender Report arrive, the buffer/metadata timestamps sent out by\n  nvmsgbroker will be based on the initial timestamp as zero.\n  ==============================================================================\n\n  6.2 -p 1 (PLAYBACK=1)\n  (Base UTC timestamp from filename of format - *__M_DD_YYYY_H_MIN_SEC_MSEC_AM/PM_UTC\u003cOffset\u003e.mp4)\n  Means - the first video frame timestamp is embedded in the URI.\n  Example: VideoFileSavedFromCamera__4_11_2018_4_59_59_433_AM_UTC-07_00.mp4\n  $ ./deepstream-test5-app -c test5_dec_infer-resnet_tracker_sgie_tiled_display_int8.txt -p 1\n  =============================================================================\n  NOTE: If URI does not have original timestamp embedded, a WARNING will be\n  thrown to user and current system time will be used as base time for all metadata\n  ==============================================================================\n\n===============================================================================\n7. Option -m [Default=0]\n  PGIE Model used; {0 - Unknown [DEFAULT]}, {1: Resnet 4-class [Car, Bicycle, Person, Roadsign]}\n===============================================================================\n\n  This option is to demonstrate the code which can read\n  PGIE, Tracker, and SGIE Metadata from NvDsBatchMeta and fill\n  NvDsEventMsgMeta in bbox_generated_probe_after_analytics()\n  for the nvmsgconv schema and JSON-metadata-generation.\n  For more details run the below command on terminal post DS installation:\n  gst-inspect-1.0 nvmsgconv\n  ==============================================================================\n  NOTE: Customers using `-m 0` with custom PGIE, SGIE models,\n  please read the documentation under \"IMPORTANT Note 1\" tag\n  in deepstream_test5_app_main.c for changes in code required\n  to relay SGIE Classifier-Metadata to nvmsgconv\n\n  7.1 -m 0 (Model(s) used are unknown)\n  $ ./deepstream-test5-app -c test5_dec_infer-resnet_tracker_sgie_tiled_display_int8.txt -m 0\n\n  7.2 -m 1 (Analytics Model(s) used are:\n            resnet(4-class model) -\u003e Tracker (Optional) -\u003e SGIE0 (Vehicle-type)\n            -\u003e SGIE1 (Vehicle-Color) -\u003e SGIE2 (Vehicle-Make))\n  $ ./deepstream-test5-app -c test5_dec_infer-resnet_tracker_sgie_tiled_display_int8.txt -m 1\n\n===============================================================================\n8. Option -o\n   GIE Model update configuration override file; {provide path of override config file}\n\n   This option is used to demonstrate the on-the-fly model update feature.\n   deepstream-test5-app to be launched with -o \u003cota_override_file\u003e option to test\n   on-the-fly OTA functionality.\n\n   Steps to test the OTA functionality\n   1) Run deepstream-test5-app with -o \u003cota_override_file\u003e option\n   2) While DS application is running, update the \u003cota_override_file\u003e with new model details\n      and save it\n   3) File content changes gets detected by deepstream-test5-app and then it starts\n      model-update process\n\n   Currently only model-update feature is supported as a part of OTA functionality.\n   Assumption for On-The-Fly model updates are as below:\n\n   1) New model must have same network parameter configuration as of previous model\n     (e.g. network resolution, network architecture, number of classes)\n   2) Engine file or cache file of new model to be provided by developer\n   3) Other primary gie configuration parameters like group-threshold, bbox color, gpu-id,\n      nvbuf-memory-type etc updated parameters if provided in the override file,\n      will not have any effect after model switch.\n   4) Secondary gie model-update is not validated, primary model-update is validated\n   5) No frame drop / frames without inference should be observed during on-the-fly\n      model update process\n   6) In case of model update failure, error message will be printed on the console and\n      pipeline should continue to run with older model configuration\n   7) config-file parameter is needed to suppress the config file parsing error prints,\n      values from this config file are not used during model switch process\n\n===============================================================================\n9. Multiple broker sinks\n===============================================================================\n   Multiple broker sinks might be required for sending a message to multipe\n   backends simultaneously or to send specific message to particular backend.\n\n   By default sink of type = 6 adds message converter and message broker\n   components in the pipeline.\n   In case of multiple brokers [message-converter] group can be used to add\n   single message converter in the pipeline with multiple sinks of type = 6\n   having disable-msgconv set to 1.\n\n   If multiple message converters are also required along with multiple brokers\n   then \"msg-conv-comp-id\" and \"msg-broker-comp-id\" should be set properly to\n   avoid duplicate messages. These fields force converter / broker components to\n   process only those messages having same value for componentId field and ignore\n   other messages. User should modify the application to fill componentId field of\n   NvDsEventMsgMeta structure.\n\n===============================================================================\n10. Smart Record - Event based recording\n===============================================================================\n   Event based recording can be enabled by setting \"smart-record\" under [sourceX]\n   group. Currently only source type = 4 (RTSP) is supported.\n   There are two ways in which smart record events can be triggerd.\n   1) Through cloud messages.\n      set smart-record=1 and configure [message-consumerX] group accordingly.\n      Refer deepstream_c2d_msg_utils.c for format of cloud message to trigger\n      the smart record start / stop events.\n   2) Through local events.\n      set smart-record=2, this will enable smart record through cloud messages\n      as well as local events.\n      To demonstrate the event based recording through local events, application\n      by default triggers start / stop events every ten seconds.\n      This interval and other parameters are configurable.\n\n   Please refer plugin manual and gst-nvdssr.h header file for more details about\n   smart record.\n\n===============================================================================\n11. Message consumer\n===============================================================================\n    deepstream-test5-app can be configured to work as message consumer for\n    cloud messages. After parsing the received message and based on the content\n    of the message specific action(s) can be triggered.\n    e.g. NvDsSrcParentBin*, which holds the smart record context, is passed as an\n    argument in start_cloud_to_device_messaging() that is then used to trigger\n    start/stop of smart record.\n\n    By default, event based recording has been implmented to demonstrate the\n    usage of message consumer.\n    User need to implement the custom logic to work on other types of received\n    messages.\n\n    Following minimum json message is expected to trigger the start / stop\n    of smart record.\n      {\n        command: string   // \u003cstart-recording / stop-recording\u003e\n        start: string     // \"2020-05-18T20:02:00.051Z\"\n        end: string       // \"2020-05-18T20:02:02.851Z\",\n        sensor: {\n          id: string\n        }\n      }\n\n    To subscribe to cloud messages configure the [message-consumer] group(s)\n    accordingly.\n\n===============================================================================\n\nNOTE:\n-----\n\n#Rebuilding the Deepstream based Docker image:\n----------------------------------------------\n\nIn order to extend DeepStream docker image with your modified config file settings,\nfollow instructions listed in the \"Docker Containers\" section of the DeepStream Plugin\nManual, for creating your own docker image based on DeepStream.\n\nThe associated steps are shown below specifically for the test5 usecase for convenience:\n\nStep 1: Modify test5 config file as required; assume new config file is named test5_config_new.txt\nStep 2: Create Dockerfile for building new DeepStream docker image for jetson which includes modified config file\n\n$ cat \u003c\u003cEOF \u003e Dockerfile\n#==============================================================================\nFROM nvcr.io/nvidia/deepstream-l4t:\u003ctag\u003e\nADD test5_config_new.txt /opt/nvidia/deepstream/deepstream/sources/apps/sample_apps/deepstream-test5/configs/\nCMD [\"/bin/bash\"]\nWORKDIR /opt/nvidia/deepstream/deepstream/\n#==============================================================================\nEOF\n\nStep 3: Rebuild new docker image\n$ docker build -t ds_test5:1 .\n\n#Run deepstream-test5-app as Azure iotedge module:\n--------------------------------------------------\n  # Refer to sections within DS_PACKAGE_DIR/sources/libs/azure_protocol_adaptor/module_client/README to:\n    1. Create azure IotHub\n    2. Register a new Azure IoT Edge device from the Azure portal\n    3. Setup and install Azure Iot Edge on your machine\n    4. Install dependencies\n    5. Specify connection string\n    6. Use cfg file (optional)\n    7. Install \u0026 setup nvidia-docker\n    8. Deploy a iotedge module\n    9. Start the edge runtime\n\n  # On Azure iothub deployment page, use the information below as an example to use deepstream-test5-app using\n    * sample config file \"test5_config_file_src_infer_azure_iotedge.txt\"\n    * to send messages with minimal schema\n    * with display disabled\n    * Message topic = mytopic\n    (Note: Message topic cant be empty)\n\n  Deployment of a Module:\n  -----------------------\n\n  On the Azure portal, Click on the Iot edge device you have created and click Set Modules:\n\n  Container Registry Settings:\n        Name:       NGC\n        Address:    nvcr.io\n        User Name:  $oauthtoken\n        Password:   \u003cpassword (or API key) from your NGC account\u003e\n\n  Deployment modules:\n  Add new module:\n  - Name:    ds_test5\n\n  - Image URI:\n         For x86:     nvcr.io/nvidia/deepstream:\u003ctag\u003e\n         For jetson:  nvcr.io/nvidia/deepstream-l4t:\u003ctag\u003e\n\n  - container Create options:\n    {\n      \"HostConfig\": {\n        \"Runtime\": \"nvidia\"\n      },\n      \"WorkingDir\": \"/opt/nvidia/deepstream/deepstream/sources/apps/sample_apps/deepstream-test5/configs/\",\n      \"ENTRYPOINT\": [\n        \"/usr/bin/deepstream-test5-app\",\n        \"-c\",\n        \"test5_config_file_src_infer_azure_iotedge.txt\",\n        \"-p\",\n        \"1\",\n        \"-m\",\n        \"1\"\n      ]\n    }\n\n  - specify route options for the module:\n\n    option 1) Default route where every message from every module is sent upstream\n    {\n      \"routes\": {\n        \"route\": \"FROM /messages/* INTO $upstream\"\n      }\n    }\n\n    option 2)  you can mention specific routes where messages sent upstream based on topic name\n    ex: in the sample test programs, topic name \"mytopic\" is used for the module name ds_test5\n    {\n      \"routes\": {\n        \"route\": \"FROM /messages/modules/ds_test5/outputs/mytopic INTO $upstream\",\n      }\n    }\n\n  Start the edge runtime and verify if modules are running:\n  ---------------------------------------------------------\n\n  #Restart the iotedge on your system\n  sudo systemctl restart iotedge\n\n  #Give it a few seconds\n\n  #check edge runtime status\n  systemctl status iotedge\n\n  #List the modules running\n  sudo iotedge list\n\n  #check output from the modules\n  sudo iotedge logs ds\u003cds-version\u003e_test5\n\n===============================================================================\nFAQ\n===============================================================================\n\n1) I see the following WARNING:\nWARNING; playback mode used with URI [file:///.../streams/sample_720p.mp4] not conforming\nto timestamp format; check README; using system-time\n===============================================================================\n\nAnswer:\nThe file URI does not have the base timestamp (first video frame timestamp in\nthe format discussed above in Section 5.2\n\n2) I see the following WARNING:\nnvmsgbroker queue overrun; Older Message Buffer Dropped; Network bandwidth might be insufficient\n===============================================================================\n\nAnswer:\nThe GstQueue just before nvmsgbroker is set to hold a max number of buffers (say 20).\nThis means - if the network bandwidth is not enough to scale and send the\nmetadata over nvmsgbroker overflowing this queue, the queue will leak\n(older buffers will be dropped with this WARNING).\nYou could change this number at ../../apps-common/src/deepstream_sink_bin.c\nIn function - create_msg_conv_broker_bin() -\ng_object_set(G_OBJECT(bin-\u003equeue), \"max-size-buffers\", 20, NULL);\n\n3) What do I need to change in the test5_config_file_src_infer.txt or\ntest5_dec_infer-resnet_tracker_sgie_tiled_display_int8.txt config?\n===============================================================================\n\nAnswer:\ni) [sinkN] group config with type=6\nneeds to be reconfigured.\nMain change required are:\na) msg-broker-proto-lib - KAFKA/Azure\nb) msg-broker-conn-str - The broker-connection-string\nc) topic\nFor more details on these configs check documentation with:\n`gst-inspect-1.0 nvmsgbroker`\n\nExample:\n[sink1]\nenable=1\n#Type - 1=FakeSink 2=EglSink 3=File 4=UDPSink 5=nvdrmvideosink 6=MsgConvBroker\ntype=6\nmsg-conv-config=dstest5_msgconv_sample_config.txt\nmsg-broker-proto-lib=/opt/nvidia/deepstream/deepstream/lib/libnvds_kafka_proto.so\nmsg-broker-conn-str=host;port;example-topic\ntopic=example-topic\n\nii) [sourceN] for RTSP cameras/streams\nThe streams provided in config are placeholders;\nUser needs to change these for IP cameras or streams in use\n\n4) I see a WARNING log similar to the one below:\n%3|1560387814.967|FAIL|rdkafka#producer-1| [thrd:kafka.broker.host:9092/1021]: kafka.broker.host:9092/1021: Receive failed: Disconnected\n%3|1560387814.967|ERROR|rdkafka#producer-1| [thrd:kafka.broker.host:9092/1021]: kafka.broker.host:9092/1021: Receive failed: Disconnected\n===============================================================================\n\nAnswer:\nJust shows that TCP connection got disconnected after a period of inactivity.\nBut it will get reestablished when there are messages to be sent.\n\n5) I see a lot of artifacts/video-glitches on the decoded stream\n(when tiler + display) is enabled.\n===============================================================================\n\nAnswer:\nIf using RTSP Cameras, network latency above a configurable threshold causes\nRTP buffer drops.\nPlease fine tune your camera's [source] group configuration in the\nDeepStream config file using the \"latency\" config key.\nThe rtp-jitterbuffer shall drop buffers when its buffering\nmore than the configured latency.\nA sample usage with details on the latency key provided below.\n\n[source0]\nenable=1\n#Type - 1=CameraV4L2 2=URI 3=MultiURI\ntype=4\nuri=rtsp://foo.com/sample1.mp4\nnum-sources=1\ngpu-id=0\nnvbuf-memory-type=0\n#max Latency of rtp buffers to\n#buffer at the source in ms (milliseconds)\n#Default=100ms\nlatency=100\n\nAdditional info: `$gst-inspect-1.0 rtspsrc`\n\n6) How does the data in nvmsgconv config file (say - dstest5_msgconv_sample_config.txt)\nspecified in [sink1] msg-conv-config key\nmap with the streams specified in DeepStream config file (say -\ntest5_dec_infer-resnet_tracker_sgie_tiled_display_int8.txt) ?\n===============================================================================\n\nAnswer:\n[config-group-index] shall be the same among these config files\nfor a particular source.\nExample:\n[source0] in DeepStream config maps to:\n[sensor0], [place0], [analytics0] groups in the nvmsgconv config file\n[source1] in DeepStream config maps to:\n[sensor1], [place1], [analytics1] groups in the nvmsgconv config file\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Frobolaunch%2Fdeepstream-test5-playground","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Frobolaunch%2Fdeepstream-test5-playground","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Frobolaunch%2Fdeepstream-test5-playground/lists"}