Closed daveisfera closed 1 year ago
@daveisfera ,
Thank you for reporting this @daveisfera . We will look into what needs to be done to get this updated.
To try and isolate the problem a bit more, I built gstreamer
from source on Debian Bullseye and 1.16.3 is working just fine, but 1.18.0 doesn't work and doesn't log anything, but then 1.18.5 doesn't work either but outputs an error.
There's only a few tags for 1.17, but I can't build 1.17.1 and 1.17.2 has the same problem as 1.18.0 and then 1.17.90 is basically just 1.18.0, so that didn't reveal much other than I assume the tag numbers mean that it was a change made very early in the development of 1.17 that caused the problem.
Here's the logs from 1.18.5 with GST_DEBUG=3
:
0:00:06.581641656 7 0x55fec649b120 WARN rtspsrc gstrtspsrc.c:5886:gst_rtspsrc_reconnect:<rtspsrc0> warning: Could not receive any UDP packets for 5.0000 seconds, maybe your firewall is blocking it. Retrying using a tcp connection.
WARNING: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0: Could not read from resource.
Additional debug info:
../gst/rtsp/gstrtspsrc.c(5886): gst_rtspsrc_reconnect (): /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0:
Could not receive any UDP packets for 5.0000 seconds, maybe your firewall is blocking it. Retrying using a tcp connection.
Redistribute latency...
0:00:07.139854649 7 0x55fec635aa70 WARN bin gstbin.c:2811:gst_bin_do_latency_func:<pipeline0> did not really configure latency of 0:00:00.000000000
0:00:07.140734066 7 0x55fec635aa70 WARN bin gstbin.c:2811:gst_bin_do_latency_func:<pipeline0> did not really configure latency of 0:00:00.000000000
Redistribute latency...
0:00:07.232383789 7 0x7fbd2402a5e0 FIXME rtph265depay gstrtph265depay.c:1284:gst_rtp_h265_depay_process:<rtph265depay0> Assuming DONL field is not present
... <DONL log repeated a lot>
INFO - kinesisVideoStreamFormatChanged(): Stream format changed.
2021-12-18 05:20:23 [140450061088512] WARN - Dropping frame with flag: 1600
2021-12-18 05:20:23 [140450061088512] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000040, Next state: 0x0000000000000080
2021-12-18 05:20:23 [140450061088512] INFO - putStreamResultEvent(): Put stream result event. New upload handle 0
2021-12-18 05:20:23 [140450061088512] WARN - notifyDataAvailable(): Failed to un-pause curl with error: 43. Curl object 0x7fbd0801acd0
2021-12-18 05:20:23 [140450061088512] DEBUG - stepStateMachine(): State Machine - Current state: 0x0000000000000080, Next state: 0x0000000000000100
2021-12-18 05:20:23 [140450061088512] INFO - writeHeaderCallback(): RequestId: cfef91a9-b7c7-c3b8-95d8-e0717744d22d
@daveisfera ,
I have not had the chance to get to this ticket. Will update once I have something.
You may have already noticed, but 1.20 was released: https://gstreamer.freedesktop.org/releases/1.20/
Hi @niyatim23, Is this issue fixed? I am still facing issue with 1.20 version when running the below pipeline:
gst-launch-1.0 --gst-debug-level=3 rtspsrc location=rtsp://admin:Password@10.10.8.51:8554/recorded/4784640?start_time=2022-07-25T00:00:00Z ! rtph264depay ! h264parse ! decodebin ! kvssink stream-name=demo storage-size=512
@ajith-karkera your pads are incorrect, you should not link decodebin to kvssink, remove that element and try again. @daveisfera Your issue is "failed delayed linking some pad of GstRTSPSrc named rtspsrc0 to some pad of GstRtpH264Depay named rtph264depay0"
As always, please test your gstreamer pipelines with a filesink
. If it works with a filesink, but doesn't work with kvssink, then please reopen the ticket and we can help.
Yes, recording to filesink
works just fine. It's only an issue when using kvssink
. I've provided the Dockerfile
to test this with, but please let me know what else I can do to help resolve this issue.
Can you share logs & pipeline that works with filesink
but doesn't work with kvssink
? All the logs you've shared prior show a failure to link rtspsrc
to rtph264depay
, which kvssink
doesn't play any role in.
I just rebuilt with 3.3.1 and Debian as a base, and using filesink
and kvssink
is working with 1.18.6 and 1.22.0. The playback on the test page pauses and won't resume at times, but it appears that it's at least building and running now.
Logging Fedora 29 with 1.14.4 (this version of gstreamer works with Debian Buster):
Fedora 31 and Fedora 32 with 1.16.2 (Fedora 30 has 1.16 and has the same sort of error):
Fedora 33 with 1.18.2:
Fedora 34 with 1.18.4:
Fedora 35 with 1.19.3
gst-launch-1.0 --version
just hangs and won't output anythingDescribe the bug It appears that
kvssink
is not compatible with version 1.17 or 1.18 ofgstreamer
and with the announcement of Fedora becoming the upstream for amazonlinux, this will be an issue in the futureTo Reproduce Steps to reproduce the behavior:
kvssink
Expected behavior
kvssink
would work with currentgstreamer
SDK version number 3.2.0
Open source building N/A
Platform (please complete the following information):
Additional context Found while getting H.265 to work
Here's the
Dockerfile
I used to build and run these tests: