Closed cwardcode closed 3 years ago
@cwardcode ,
The logs do not give information about what could be causing it. Besides, it might also not be related to KVS. To verify this, can you run with fakesink
instead of kvssink
to see if you notice any crash?
Also, I assume it is a typo here for h264parse
in this pipeline: (there is a space)
videoconvert ! x264enc bframes=0 key-int-max=45 bitrate=512 ! video/x-h264,profile=baseline,stream-format=avc,alignment=au,width=640,height=480,framerate=30/1 ! _**h264pars e**_ ! kvssink stream-name=test-stream storage-size=512 aws-region="us-east-1" retention-period=1
One more thing you can do is run the pipeline with GST_DEBUG=4
or GST_DEBUG=5
to get information on why the GStreamer pipeline crashes.
Seems like your device does not support unaligned access. You will need to build PIC with only aligned memory access.
In order to prove this. Can you run your solution on a device that does support unaligned access and ensure you don't get bus exception.
Check out the instructions for aligned mem only. https://github.com/awslabs/amazon-kinesis-video-streams-pic#note-on-alignment
You need to specifyDALIGNED_MEMORY_MODEL=TRUE
Hi @disa6302 and @MushMal, thanks for the quick replies!
The extra space in the command I previously posted was just a typo.
I just tested fakesink
and it worked as intended. Enabling GST_DEBUG=4
showed the continual flow of information. Here is some of the output.
I would post the output, but I would like to try @MushMal's suggestion first before flooding the comments with the tons of output that come from the DEBUG flag. I'm in the middle of recompiling with the latest kernel to see if there's any improvement there, so I'll try compiling with DALIGNED_MEMORY_MODEL=TRUE
right after.
@MushMal
You need to specify DALIGNED_MEMORY_MODEL=TRUE
This got it, thanks! I had actually read the readme for the PIC repo the other day but for some reason it never clicked. Thanks again for the quick responses!
I'm trying to stream anything from a Tegra TK1 SOC but I am having an issue where after a couple of seconds, GStreamer crashes with a bus error.
Commands ran:
gst-launch-1.0 videotestsrc do-timestamp=TRUE ! video/x-raw,width=640,height=480,framerate=30/1 ! videoconvert ! x264enc bframes=0 key-int-max=45 bitrate=512 ! video/x-h264,profile=baseline,stream-format=avc,alignment=au,width=640,height=480,framerate=30/1 ! h264pars e ! kvssink stream-name=test-stream storage-size=512 aws-region="us-east-1" retention-period=1
gst-launch-1.0 rtspsrc location="rtsp://192.168.1.238/extron1" short-header=TRUE ! rtph264depay ! video/x-h264, format=avc ! h264parse ! kvssink stream-name="test-stream" aws-region="us-east-1" retention-period=1
Logging From running the rtsp source, I receive:
I do notice that in dmesg I get a new entry each time after running for an alignment trap error:
I receive almost identical logs when using
videotestsrc
as well.Any design considerations/constraints The stream is currently set at 1080p@30fps.
If I run any of the above commands in an infinite while-loop, it will stream to KVS, however the video feed is very choppy and not suitable for a production scenario.
I'm running a buildroot-based distro that's based on the 2020.02.3 release. This is using the linux kernel pubished by toradex for this TK1 SOC (located here with version
Apalis-TK1_LXDE-Image_2.8b6.184-20190401
.If you would not like to open an issue to discuss your solution in open-platform, please email your question to kinesis-video-support@amazon.com