[Bug 747495] gst_base_text_overlay_push_frame() doesn't make memory copy when video buffer's memory is ready only
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Tue Jul 28 12:32:40 PDT 2015
https://bugzilla.gnome.org/show_bug.cgi?id=747495
Nicolas Dufresne (stormer) <nicolas.dufresne at collabora.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|gst-plugins-base |don't know
--- Comment #5 from Nicolas Dufresne (stormer) <nicolas.dufresne at collabora.co.uk> ---
(In reply to Mingke Wang from comment #2)
> ERROR default video-frame.c:141:gst_video_frame_map_id:
> failed to map video frame plane 0
>
> Did i missed something? or is there any interface need to be implemented?
This can fail in two ways, you can get this information if you enable
GST_DEBUG="2,videometa:7".
a) "plane %u, no memory at offset %" G_GSIZE_FORMAT,
That would mean no GstMemory could be found at the expected offset for this
plane. This could indicate that upstream element (you didn't mention which one)
didn't set the offset[] array of the videometa properly, or that the memory
dimensions are not set properly.
b) "cannot map memory range %u-%u", idx, length);
That would indicate that the memory could not be map, even for read + copy.
This would indicate that the memory is already mapped WRITE only by an upstream
element.
In both cases it's not textoverlay's fault. I would like you to provide
information about the entire pipeline you are running, as the problem is more
likely in the element the provides these buffer/memory.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list