GNOME Bugzilla – Bug 751711
GstVaapiVideoMemory doesn't allow GST_MAP_WRITE mapping
Last modified: 2018-11-03 15:47:16 UTC
Trying to map the buffer in GST_MAP_READ | GST_MAP_WRITE mode fails with gst.vaapivideomemory unsupported map flags (0x3) at gstreamer-vaapi/gst/vaapi/gstvaapivideomemory.c:436. Is there any particular reason why gst_vaapi_video_memory_map() doesn't just use the same kind of mapping it does for GST_MAP_READ? LibVA documentation [1] doesn't seem mention that vaMapBuffer-mapped buffers shouldn't be tampered with... [1] http://01org.github.io/libva_master_doxygen/group__api__core.html#gaf14c698af1d0920f4aeb5eb11f81b6aa
Thanks for taking the time to report this. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. The particular answer are here: https://bugzilla.gnome.org/show_bug.cgi?id=704078#c2 and https://bugzilla.gnome.org/show_bug.cgi?id=704078#c4 If you disagree, please reopen the bug. *** This bug has been marked as a duplicate of bug 704078 ***
Thanks for pointing to bug 704078. However, I'm getting this error despite the bug 704078 fix (I'm using a month old master, particularily 619058b5). Therefore, let me reopen this bug. It looks to me like it was fixed only for accessing the buffer memory as GstVideoFrames via gst_video_frame_map() (like e.g. VideoFilter does). However, if a downstream element uses raw gst_buffer_map(), it gets this error.
Moving to Product:GStreamer, Component:gstreamer-vaapi
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/34.