In this case, How can I use RTSPSRC for TensorRT Input in command line?
And, How can I use H/W accelerated H264/265 decoder in command line?
Thank you.
Hi,
There are many must-have properties you have to configure in running a deep learning interference usecases. We would suggest you run deepstream-app and modify config file to run RTSP source. You may run the default config file first and then change to RTSP source. The document is in https://docs.nvidia.com/metropolis/deepstream/dev-guide/index.html
Opening in BLOCKING MODE
0:00:00.323555289 21733 0x7f540045e0 WARN v4l2 gstv4l2object.c:4408:gst_v4l2_object_probe_caps:<nvv4l2decoder0:src> Failed to probe pixel aspect ratio with VIDIOC_CROPCAP: Unknown error -1
0:00:00.323639645 21733 0x7f540045e0 WARN v4l2 gstv4l2object.c:2370:gst_v4l2_object_add_interlace_mode:0x7f380cb280 Failed to determine interlace mode
NvMMLiteOpen : Block : BlockType = 261
NVMEDIA: Reading vendor.tegra.display-size : status: 6
NvMMLiteBlockCreate : Block : BlockType = 261
0:00:00.430607942 21733 0x7f540045e0 WARN v4l2 gstv4l2object.c:4408:gst_v4l2_object_probe_caps:<nvv4l2decoder0:src> Failed to probe pixel aspect ratio with VIDIOC_CROPCAP: Unknown error -1
0:00:00.430748749 21733 0x7f540045e0 WARN v4l2 gstv4l2object.c:2370:gst_v4l2_object_add_interlace_mode:0x7f380cb280 Failed to determine interlace mode
Creating LL OSD context new
0:00:00.491547065 21733 0x7f540045e0 WARN v4l2videodec gstv4l2videodec.c:1557:gst_v4l2_video_dec_decide_allocation:<nvv4l2decoder0> Duration invalid, not setting latency
0:00:00.498622854 21733 0x7f540045e0 WARN v4l2bufferpool gstv4l2bufferpool.c:1062:gst_v4l2_buffer_pool_start:<nvv4l2decoder0:pool:src> Uncertain or not enough buffers, enabling copy threshold
0:00:00.646034399 21733 0x7f381ca0a0 WARN v4l2bufferpool gstv4l2bufferpool.c:1526:gst_v4l2_buffer_pool_dqbuf:<nvv4l2decoder0:pool:src> Driver should never set v4l2_buffer.field to ANY
0:00:01.146280946 21733 0x7f540045e0 WARN v4l2bufferpool gstv4l2bufferpool.c:1482:gst_v4l2_buffer_pool_dqbuf:<nvv4l2decoder0:pool:sink> v4l2 provided buffer that is too big for the memory it was writing into. v4l2 claims 64 bytes used but memory is only 0B. This is probably a driver bug.