# Read RTSP give the output when used GPU decoder nvv4l2decoder stuck in loop at certain timestamp forever

**URL:** <https://forums.developer.nvidia.com/t/read-rtsp-give-the-output-when-used-gpu-decoder-nvv4l2decoder-stuck-in-loop-at-certain-timestamp-forever/231131>\
**Category:** DeepStream SDK\
**Created:** [October 18, 2022, 1:18pm UTC](https://forums.developer.nvidia.com/t/read-rtsp-give-the-output-when-used-gpu-decoder-nvv4l2decoder-stuck-in-loop-at-certain-timestamp-forever/231131 "2022-10-18T13:18:47Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![trild-vietnam](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/trild-vietnam/32/126326_2.png) [@trild-vietnam](https://forums.developer.nvidia.com/u/trild-vietnam)\
**Post date:** [October 18, 2022, 1:18pm UTC](https://forums.developer.nvidia.com/t/read-rtsp-give-the-output-when-used-gpu-decoder-nvv4l2decoder-stuck-in-loop-at-certain-timestamp-forever/231131/1 "2022-10-18T13:18:47Z")

</div>

Please provide complete information as applicable to your setup.

**• Hardware Platform (/ GPU)**  
**• DeepStream Version: 6.0.1**  
**• Issue Type(bugs)**  
**• How to reproduce the issue ? (This is for bugs. Including which sample app is using, the configuration files content, the command line used and other details for reproducing)**

I run the bellow pipeline: and get output video sink loop in the certain timestamp forver. What is the root cause of this issue?

This pipeline auto choose the decoder is nvv4l2decoder

```auto
gst-launch-1.0 rtspsrc location="rtsp://URI" protocols=4 short-header=1 ! decodebin ! queue ! nvvideoconvert ! nvv4l2h264enc ! h264parse ! matroskamux ! filesink location=nvv4l2dec_gpu_loop.mp4

```

But I tried the pipeline with CPU decoder without the loop issue:

```auto
gst-launch-1.0 rtspsrc location="rtspt://URI" protocols=tcp short-header=1 ! rtph264depay ! h264parse ! avdec_h264 ! nvvideoconvert ! nvv4l2h264enc ! h264parse ! matroskamux ! filesink location=out_cpu.mp4

```

This is output have the loop issue. Could you Nvidia developer check the bugs and let me know what is the root cause?

[https://global.discourse-cdn.com/nvidia/original/3X/d/1/d127fb68b697e78c63c368759dd782438353900c.mp4](https://global.discourse-cdn.com/nvidia/original/3X/d/1/d127fb68b697e78c63c368759dd782438353900c.mp4)

[test\_cam74.log](https://forums.developer.nvidia.com/uploads/short-url/jUFraqnH0VQwihquJixAi2Yrmiy.log) (49.6 MB)

---

<div class="post-metadata">

**Author:** ![trild-vietnam](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/trild-vietnam/32/126326_2.png) [@trild-vietnam](https://forums.developer.nvidia.com/u/trild-vietnam)\
**Post date:** [October 18, 2022, 1:21pm UTC](https://forums.developer.nvidia.com/t/read-rtsp-give-the-output-when-used-gpu-decoder-nvv4l2decoder-stuck-in-loop-at-certain-timestamp-forever/231131/2 "2022-10-18T13:21:46Z")

</div>

Video spec:

Video: h264 (High) yuv420p(tv progressive) 1280x960 5 fps 5 tbr 90k tbn 10 tbc

---

<div class="post-metadata">

**Author:** ![yuweiw](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/yuweiw/32/101255_2.png) [@yuweiw](https://forums.developer.nvidia.com/u/yuweiw)\
**Post date:** [October 19, 2022, 2:53am UTC](https://forums.developer.nvidia.com/t/read-rtsp-give-the-output-when-used-gpu-decoder-nvv4l2decoder-stuck-in-loop-at-certain-timestamp-forever/231131/4 "2022-10-19T02:53:44Z")

</div>

You can try to update the deepstream to 6.1.1. It seems like the topic below:  
[https://forums.developer.nvidia.com/t/nvv4l2decoder-breaks-on-some-h-264-streams/213827](https://forums.developer.nvidia.com/t/nvv4l2decoder-breaks-on-some-h-264-streams/213827)

---

<div class="post-metadata">

**Author:** ![trild-vietnam](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/trild-vietnam/32/126326_2.png) [@trild-vietnam](https://forums.developer.nvidia.com/u/trild-vietnam)\
**Post date:** [October 19, 2022, 2:56am UTC](https://forums.developer.nvidia.com/t/read-rtsp-give-the-output-when-used-gpu-decoder-nvv4l2decoder-stuck-in-loop-at-certain-timestamp-forever/231131/5 "2022-10-19T02:56:28Z")

</div>

Thank you could you give me the root cause or release note for this issues? @yuweiw

---

<div class="post-metadata">

**Author:** ![trild-vietnam](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/trild-vietnam/32/126326_2.png) [@trild-vietnam](https://forums.developer.nvidia.com/u/trild-vietnam)\
**Post date:** [October 19, 2022, 3:14am UTC](https://forums.developer.nvidia.com/t/read-rtsp-give-the-output-when-used-gpu-decoder-nvv4l2decoder-stuck-in-loop-at-certain-timestamp-forever/231131/6 "2022-10-19T03:14:35Z")

</div>

@yuweiw Incase we could not update the version deepstream. Could we know the root cause and have workaround with it?

Does it necessary need to modified the nvv4l2decoder to get fix?

---

<div class="post-metadata">

**Author:** ![yuweiw](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/yuweiw/32/101255_2.png) [@yuweiw](https://forums.developer.nvidia.com/u/yuweiw)\
**Post date:** [October 19, 2022, 7:36am UTC](https://forums.developer.nvidia.com/t/read-rtsp-give-the-output-when-used-gpu-decoder-nvv4l2decoder-stuck-in-loop-at-certain-timestamp-forever/231131/7 "2022-10-19T07:36:31Z")

</div>

Yes, it needs to modify the nvv4l2decoder. The root cause related to the compatibility between h264 protocols and nvv4l2decoder lib. So it’s hard to provide the workround.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\
**Post date:** [November 2, 2022, 7:37am UTC](https://forums.developer.nvidia.com/t/read-rtsp-give-the-output-when-used-gpu-decoder-nvv4l2decoder-stuck-in-loop-at-certain-timestamp-forever/231131/8 "2022-11-02T07:37:25Z")

</div>

Closed on November 2, 2022, 7:37am UTC

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