Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-base gst-plugins-base
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 641
    • Issues 641
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 80
    • Merge requests 80
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamerGStreamer
  • gst-plugins-basegst-plugins-base
  • Issues
  • #341
Closed
Open
Issue created Mar 03, 2017 by Bugzilla Migration User@bugzilla-migration

buffer with video meta information do not support memory split buffers

Submitted by Frediano Ziglio @fziglio

Link to original bug (#779524)

Description

Try to avoid some clipping of images and pass DRM primes to GStreamer I tried to use gst_buffer_add_video_meta_full functions. This worked well on textures (DRM primes) and frames composed by a single memory chunk but with frames (that is GstBuffer) having multiple memory chunks (GstMemory) you get memory errors.
This is due to the fact that gst_video_frame_map_id (called internally by GStreamer) assume that if there are video meta information attached there is a single chunk of memory.
This behaviour is not documented for gst_buffer_add_video_meta_full or GstVideoMeta and having multiple GstMemory is supported normally so for me is an API or documentation bug.
Looking at git master code there are no changes (either implementation or documentation) in this respect.

Assignee
Assign to
Time tracking