GNOME Bugzilla – Bug 793423
default video-frame.c:175: gst_video_frame_map_id: invalid buffer size
Last modified: 2018-05-07 09:56:49 UTC
The following pipeline: /usr/local/bin/gst-launch-1.0 -v shmsrc socket-path=/tmp/mixer1 do-timestamp=true is-live=true ! \ video/x-raw, format=BGRA, pixel-aspect-ratio=\(fraction\)1/1, interlace-mode=progressive, framerate=30/1, width=1280, height=720 ! \ queue ! \ videoconvert ! \ x264enc bitrate=4000 key-int-max=60 bframes=0 byte-stream=false aud=true tune=zerolatency ! \ h264parse ! \ video/x-h264,level=4.1,profile=main ! \ queue ! \ mux. fdsrc fd=0 ! \ audio/x-raw, format=S16LE, endianness=1234, signed=true, width=16, depth=16, rate=44100, channels=2 ! \ queue ! \ faac bitrate=128000 ! \ aacparse ! \ audio/mpeg,mpegversion=4,stream-format=raw ! \ queue ! \ flvmux streamable=true name=mux ! \ queue ! \ rtmpsink "location=rtmp://rtmp_location live=1 flashver=FME/3.0%20\(compatible;%20FMSc%201.0\)" ... produces the following error: /GstPipeline:pipeline0/GstVideoConvert:videoconvert0.GstPad:sink: caps = video/x-raw, format=(string)BGRA, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, framerate=(fraction)30/1, width=(int)1280, height=(int)720 0:00:00.094788052 12372 0x20d95e0 ERROR default video-frame.c:175:gst_video_frame_map_id: invalid buffer size 2359296 < 3686400 WARNING: from element /GstPipeline:pipeline0/GstVideoConvert:videoconvert0: Internal GStreamer error: code not implemented. Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer. Additional debug info: gstvideofilter.c(290): gst_video_filter_transform (): /GstPipeline:pipeline0/GstVideoConvert:videoconvert0: invalid video buffer received
That means that the buffers coming through shmsrc are of the wrong format, most likely. The buffer sizes don't agree with what would be required for that format you specified in the caps. What does the other side of the pipeline with the shmsink look like? Also please try to simplify your pipelines as much as possible before reporting bugs, e.g. in your case the audio and RTMP parts are probably completely unrelated to the problem that is happening. See http://sscce.org