[Bug 747495] gst_base_text_overlay_push_frame() doesn't make memory copy when video buffer's memory is ready only

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=747495

--- Comment #9 from Mingke Wang <mingke.wang at freescale.com> ---
(In reply to Nicolas Dufresne (stormer) from comment #7)
> If the GstBuffer is read-only, it will replace the GstBuffer first. If it's
> writable, it will simply replace the memory. That's why your decoder need to
> track it's memory, instead of it's buffer. A buffer pool is just a cache to
> try and avoid allocation GstBuffer object over and over.

The hardware decoder need physical continuous memory. actually, the physical
memories are allocated by the hardware decoder and registered to it at the
initialization. then we implemented a alocator to wrap those memories to gst
buffer. so the GstBuffer allocation only happens at the beginning. and once
memory registered, it can't be changed on the fly unless stop and initial
again.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.