Problem beim Dekodieren von h.264 mit GstreamerLinux

Linux verstehen
Guest
 Problem beim Dekodieren von h.264 mit Gstreamer

Post by Guest »

Ich habe ein Problem mit der Dekodierung der h.264-Datei. Die Gstreamer-Pipeline schlägt mit der folgenden Meldung fehl:

Code: Select all

...................
0:00:01.968415100  2374   0x3fa0000b70 DEBUG           v4l2videodec gstv4l2videodec.c:1156:gst_v4l2_vidRedistribute latency...
eo_dec_sink_getcaps: Returning sink caps video/x-h264, width=(int)[ 48, 4096 ], height=(int)[ 16, 2304 ], framerate=(fraction)[ 0/1, 2147483647/1 ], stream-format=(string)byte-stream, alignment=(string)au, level=(string){ 1, 1b, 1.1, 1.2, 1.3, 2, 2.1, 2.2, 3, 3.1, 3.2, 4, 4.1, 4.2, 5, 5.1 }, profile=(string){ baseline, constrained-baseline, main, high }, colorimetry=(string){ bt709, bt601, smpte240m, 1:3:5:1, 2:4:5:2, 2:4:5:3, 1:4:7:1, 2:4:7:1, 2:4:12:8, bt2020, 2:0:0:0 }, parsed=(boolean)true
0:00:01.969251400  2374   0x3fa0000b70 DEBUG              h264parse gsth264parse.c:1897:ensure_caps_profile: Setting compatible profile high to the caps
/GstPipeline:pipeline0/GstH264Parse:h264parse0.GstPad:src: caps = video/x-h264, width=(int)320, height=(int)240, framerate=(fraction)0/1, coded-picture-structure=(string)frame, chroma-format=(string)4:2:0, bit-depth-luma=(uint)8, bit-depth-chroma=(uint)8, colorimetry=(string)2:4:5:4, parsed=(boolean)true, stream-format=(string)byte-stream, alignment=(string)au, profile=(string)high, level=(string)1.3
0:00:01.970644300  2374   0x3fa0000b70 DEBUG           v4l2videodec gstv4l2videodec.c:1156:gst_v4l2_video_dec_sink_getcaps: Returning sink caps EMPTY
0:00:01.971063200  2374   0x3fa0000b70 LOG                h264parse gsth264parse.c:2657:gst_h264_parse_get_timestamp: Upstream ts 0:00:00.000000000
0:00:01.971347300  2374   0x3fa0000b70 DEBUG              h264parse gsth264parse.c:2674:gst_h264_parse_get_timestamp: unable to compute timestamp: timing info not present
0:00:01.971434900  2374   0x3fa0000b70 DEBUG              h264parse gsth264parse.c:2575:gst_h264_parse_get_duration: unable to compute duration: timing info not present
0:00:01.972205200  2374   0x3fa0000b70 DEBUG           v4l2videodec gstv4l2videodec.c:1156:gst_v4l2_video_dec_sink_getcaps: Returning sink caps EMPTY
0:00:01.972825600  2374   0x3fa0000b70 DEBUG              h264parse gsth264parse.c:3268:gst_h264_parse_pre_push_frame: Inserting AUD into the stream.
0:00:01.972947300  2374   0x3fa0000b70 DEBUG              h264parse gsth264parse.c:225:gst_h264_parse_reset_frame: reset frame
0:00:01.973267700  2374   0x3fa0000b70 DEBUG           v4l2videodec gstv4l2videodec.c:1156:gst_v4l2_video_dec_sink_getcaps: Returning sink caps EMPTY
0:00:01.973586100  2374   0x3fa0000b70 DEBUG           v4l2videodec gstv4l2videodec.c:1156:gst_v4l2_video_dec_sink_getcaps: Returning sink caps EMPTY
ERROR: from element /GstPipeline:pipeline0/GstH264Parse:h264parse0: Internal data stream error.
Additional debug info:
../gstreamer-1.22.12/libs/gst/base/gstbaseparse.c(3699): gst_base_parse_loop (): /GstPipeline:pipeline0/GstH264Parse:h264parse0:
streaming stopped, reason not-negotiated (-4)
ERROR: pipeline doesn't want to preroll.
0:00:01.974780200  2374   0x3fa0000b70 DEBUG           v4l2videodec gstv4l2videodec.c:1156:gst_v4l2_vidSetting pipeline to NULL ...
eo_dec_sink_getcaps: Returning sink caps EMPTY
Befehl ausführen:

Code: Select all

export GST_DEBUG=h264parse:7,v4l2videodec:7
gst-launch-1.0 -vvv --no-fault filesrc location=./test-25fps.h264 num-buffers=10 ! h264parse ! v4l2h264dec ! video/x-raw,format=I420 ! filesink location=./out.yuv
Es scheint, dass der Gerätetreiber die Farbmetrik 2:4:5:4 nicht unterstützt, was
entspricht

Code: Select all

colorimetry.range     = GST_VIDEO_COLOR_RANGE_16_235;
colorimetry.matrix    = GST_VIDEO_COLOR_MATRIX_BT601;
colorimetry.transfer  = GST_VIDEO_TRANSFER_BT709;
colorimetry.primaries = GST_VIDEO_COLOR_PRIMARIES_SMPTE170M;
[Link zum GST-Quellcode: https://gitlab.freedesktop.org/gstreame ... /gst-libs/ gst/video/video-color.h?ref_type=heads#L42]
Aber ich habe keine Ahnung, was ich zur Unterstützung in meinem Treiber reparieren oder implementieren muss 2:4:5:4 Farbmetrik. Ich habe kein Handle gefunden, um diese Parameter wie für unterstützte Ebenen und Profile durch Erstellen geeigneter Strg-Befehle zu verwalten.

Quick Reply

Change Text Case: 
   
  • Similar Topics
    Replies
    Views
    Last post