We encountered the same issue when using DS 7.0 with the custom model. Will later DS version resolve this issue? Or any work around can be used, or just go back to DS 6.1.1?
Our system setup:
HW: Orin NX 16GB
Deepstream: 7.0
Custom model: trained and exported as ONNX file by Custom Vision from Microsoft Azure, used for human detection similar to PeopleNet
Issue description: Output dynamic num values
Understood, thanks for your instant reply. Our current issue looks DS could not accept dynamic dimensions value, is it? Is it caused by the custom model which was trained by Custom Vision? If using TAO it will not have this issue? If it is not caused by the model, any way to resolve this dynamic ‘num’ issue? Thanks.
No matter with which tool you train and generate the ONNX model, you need to change the model’s output. The first dimension will be considered as batch size, it can be dynamic. The other dimensions can’t be dynamic for DeepStream does not support it.
Where and how did you generate the “/opt/nvidia/deepstream/deepstream-7.0/samples/models/custom_model/model.engine” you used in the nvinfer configuration?
We use trtexec to generate model.engine from model.onnx. Now we use modified config and script files, and the model works now. Thank you very much for your great help!