Jetson Nano Gstreamer OpenCV stuck at NvMMLiteBlockCreate : Block : BlockType = 261

Autonomous Machines Jetson & Embedded Systems Jetson Nano
#1

Hello I have l4t 32.5.1 on Jetson Nano .

When I try to open IP camera using Gstreamer and in C++ code using OpenCV videocapture

  • pipe= “rtspsrc location=rtsp://*:@192.168.1.233:8001/0/video0 latency=10 ! application/x-rtp, media=(string)video, encoding-name=(string)H264 ! rtph264depay ! nvv4l2decoder drop-frame-interval= 3 ! nvvidconv interpolation-method=5 ! video/x-raw, format=BGRx, width=704, height=576 ! videoconvert ! video/x-raw,format=BGR ! queue ! appsink drop=true max-buffers=1”;

I get stuck at

  • NvMMLiteBlockCreate : Block : BlockType = 261

When I try as below it just works fine

  • pipe= "rtspsrc location=rtsp://:@192.168.1.233:8001/0/video0 latency=10 ! queue ! rtph264depay ! queue ! h264parse ! avdec_h264 ! videoconvert ! appsink drop=true ";

I can’t understand why I am not able to use the gpu for rtsp streaming input I have installed Deepstream. Please advice

#3

Sorry for the late response, have you managed to get issue resolved? Thanks

#4

Hi, I am still stuck there omxh264dec is working now but not nvv4l2decoder

#5

Hi,
Please check if you can run the string in gst-launch-1.0 command:

$ gst-launch-1.0 rtspsrc location=rtsp://*:@192.168.1.233:8001/0/video0 latency=10 ! application/x-rtp, media=(string)video, encoding-name=(string)H264 ! rtph264depay ! h264parse ! nvv4l2decoder ! nvoverlaysink

We suggest apply the string to gst-launch-1.0 to make sure it works first, and then apply to OpenCV code.

#6

I am using headless mode so with

$ gst-launch-1.0 rtspsrc location=rtsp://*:@192.168.1.233:8001/0/video0 latency=10 ! application/x-rtp, media=(string)video, encoding-name=(string)H264 ! rtph264depay ! h264parse ! nvv4l2decoder ! fakesink

The output is 
0:00:00.346585371 21450   0x7f80003cf0 INFO          v4l2bufferpool gstv4l2bufferpool.c:849:gst_v4l2_buffer_pool_set_config:<nvv4l2decoder0:pool:sink> can't allocate, setting maximum to minimum
0:00:00.346800063 21450   0x7f80003cf0 INFO            videodecoder gstvideodecoder.c:1330:gst_video_decoder_sink_event_default:<nvv4l2decoder0> upstream tags: taglist, video-codec=(string)"H.264\ \(Constrained\ Baseline\ Profile\)";
0:00:01.899391555 21450   0x7f9c041590 INFO               GST_EVENT gstevent.c:814:gst_event_new_caps: creating caps event application/x-rtcp
0:00:01.901335503 21450   0x7f9c041590 INFO               GST_EVENT gstevent.c:895:gst_event_new_segment: creating segment event time segment start=0:00:00.000000000, offset=0:00:00.000000000, stop=99:99:99.999999999, rate=1.000000, applied_rate=1.000000, flags=0x00, time=0:00:00.000000000, base=0:00:00.000000000, position 0:00:00.000000000, duration 99:99:99.999999999
0:00:03.731697924 21450   0x7f9c041540 INFO               rtpsource rtpsource.c:1155:update_receiver_stats: duplicate or reordered packet (seqnr 2148, expected 2152)
0:00:38.531125289 21450   0x7f9c041540 INFO               rtpsource rtpsource.c:1155:update_receiver_stats: duplicate or reordered packet (seqnr 3626, expected 3629)

I checked with another camera that also didn't work. 

If I add rtpjiiterbuffer , it still shows the same output

95:gst_event_new_segment: creating segment event time segment start=0:00:00.000000000, offset=0:00:00.000000000, stop=99:99:99.999999999, rate=1.000000, applied_rate=1.000000, flags=0x00, time=0:00:00.000000000, base=0:00:00.000000000, position 0:00:00.000000000, duration 99:99:99.999999999
0:00:17.620292712 21631   0x7f6c03c000 INFO               rtpsource rtpsource.c:1155:update_receiver_stats: duplicate or reordered packet (seqnr 9730, expected 9732)
#7

Hi,
Please check which URI is correct. The two URIs in working and non-working cases are slightly different.

#8

Yes because I am in headless mode I used fakesink instead of nvoverlaysink. But this isn’t working also.

#9

Hi,
A user has shared a sample that seem to be close to your use-case. Please take a look at:
Nvidia-desktop kernel: [407343.357549] (NULL device *): nvhost_channelctl: invalid cmd 0x80685600 - #18 by DawnMaples

It creates 16 threads and you can change to single source for a try.

#11

Thanks, I will try next week and come back.

#12

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.