Schnittstelle MemoryFlags


public interface MemoryFlags
  • Feldübersicht Linksymbol

    Felder
    Modifizierer und Typ
    Feld
    Beschreibung
    static final int
    first flag that can be used for custom purposes
    static final int
    memory must not be shared.
    static final int
    the memory can't be mapped via
    gst_memory_map() without any preconditions.
    static final int
    the memory is physically
    contiguous.
    static final int
    memory is readonly.
    static final int
    the memory padding is filled with 0 bytes
    static final int
    the memory prefix is filled with 0 bytes
  • Felddetails Linksymbol

    • READONLY Linksymbol

      static final int READONLY
      memory is readonly. It is not allowed to map the
      memory with #GST_MAP_WRITE.
      Siehe auch:
    • NO_SHARE Linksymbol

      static final int NO_SHARE
      memory must not be shared. Copies will have to be
      made when this memory needs to be shared between buffers. (DEPRECATED:
      do not use in new code, instead you should create a custom GstAllocator for
      memory pooling instead of relying on the GstBuffer they were originally
      attached to.)
      Siehe auch:
    • ZERO_PREFIXED Linksymbol

      static final int ZERO_PREFIXED
      the memory prefix is filled with 0 bytes
      Siehe auch:
    • ZERO_PADDED Linksymbol

      static final int ZERO_PADDED
      the memory padding is filled with 0 bytes
      Siehe auch:
    • PHYSICALLY_CONTIGUOUS Linksymbol

      static final int PHYSICALLY_CONTIGUOUS
      the memory is physically
      contiguous. (Since: 1.2)
      Siehe auch:
    • NOT_MAPPABLE Linksymbol

      static final int NOT_MAPPABLE
      the memory can't be mapped via
      gst_memory_map() without any preconditions. (Since: 1.2)
      Siehe auch:
    • LAST Linksymbol

      static final int LAST
      first flag that can be used for custom purposes
      Siehe auch: