Please provide complete information as applicable to your setup.
Platform: Jetson TX2
plugin containing the issue: nvstreammux
it’s not possible to disable scaling.
- gst-inspect and deepstream web documentation mention “0” as a valid value for Width and Height
deepstream web documenation even mentions:
If non-zero, muxer scales input frames to this width.
If non-zero, muxer scales input frames to this height.
Doing so (set to 0) results in the error that nvstreammux cannot be set to playing state.
The caller is forced to set non-0 values and scaling will thus always be done, even if it’s totally not wanted/required.
Also setting Width and Height so it matches the resolution of the input stream will still enable scaling.
This can easily be observed by a large increase in CPU usage as also CPU is the default method for scaling …
When using eg. uridecodebin plugin to fetch a stream from a web source, the input resolution also is not always known in advance.
- using “0” for both Width and Height should disable scaling as documented
- If a resolution must be set to perform internal buffer allocation, a separate option is needed to indicate that scaling should be disabled.
- gst-inspect nvstreammux shows that Width and Height are mandatory values, but they are also defaulted to ‘valid value’ “0” … so they should not be mandatory …