Age | Commit message (Collapse) | Author | Files | Lines |
|
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/826
Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/827>
|
|
More convenient and discoverable variant of the fairly widely-used
gst_buffer_new_wrapped(g_memdup(data,size),size).
Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/826>
|
|
Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/752>
|
|
* Don't mention explicitly that API is MT safe, this implies that
other API is not. GStreamer API is assumed to be MT safe, thread
safety should only be explicitly mentioned when API is *not* MT safe
* Don't repeat what annotations are stating with respect to ownership
transfer, nullability
* Document enumeration members in standalone comments, so that their
Since tag is accounted for by gobject-introspection
* Misc cleanup / typo fixes / addition of links
Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/748>
|
|
Provide non-inline version of refcounting APIs so that it can be
consumed by bindings
Fixes: https://gitlab.freedesktop.org/gstreamer/gstreamer-sharp/-/issues/46
Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/728>
|
|
Custom meta is backed by a GstStructure, and does not require
that users of the API expose their GstMeta implementation as
public API for other components to make use of it.
In addition, it provides a simpler interface by ignoring the
impl vs. api distinction that the regular API exposes.
This new API is meant to be the meta counterpart to custom events
and messages, and to be more convenient than the lower-level API
when the absolute best performance isn't a requirement.
Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/609>
|
|
remove unclear documentation about GST_BUFFER_FLAG_MARKER
|
|
Since we started depending on GLib 2.44, we can be sure this macro is
defined (it will be a no-op on compilers that don't support it). For
plugins we should just start using `G_DECLARE_FINAL_TYPE` which means
we no longer need the macro there, but for most types in core we don't
want to break ABI, which means it's better to just keep it like it is
(and use the `#ifdef` instead).
|
|
* Making sure that `static inline` function are in the GIR (by first
defining them, and make sure to mark as skiped)
* Do not try to link to unexisting symbols
* Also generate GIR information about gst_tracers
|
|
|
|
One restriction on the GBytes is that the data cannot be NULL as this is
explicitly forbidden by GstMemory.
Fixes https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/318
|
|
|
|
Basically, you can use this instead of using gst_buffer_unref (which
needs to be preceded by a NULL-check).
Also fixes #275
|
|
We need different export decorators for the different libs.
For now no actual change though, just rename before the release,
and add prelude headers to define the new decorator to GST_EXPORT.
|
|
|
|
|
|
This can be used to identify buffers for which a higher percentage
of redundancy should be allocated when performing forward error
correction, or to prevent still video frames from being dropped by
elements due to QoS.
https://bugzilla.gnome.org/show_bug.cgi?id=793008
|
|
Counts how many metas there are for a certain api type.
https://bugzilla.gnome.org/show_bug.cgi?id=791918
|
|
One omission: gst_allocator_sysmem_get_type() was
exported but never in any public header file.
|
|
This is a meta that generically allows to attach additional reference
timestamps to a buffer, that don't have to relate to the pipeline clock
in any way.
Examples of this could be an NTP timestamp when the media was captured,
a frame counter on the capture side or the (local) UNIX timestamp when
the media was captured.
https://bugzilla.gnome.org/show_bug.cgi?id=779213
|
|
This makes C++ compilers a bit more happy without having the user of the
constants cast. It also provides the correct type information to GI.
https://bugzilla.gnome.org/show_bug.cgi?id=780923
|
|
|
|
It used to work but it has broke in the 1.10 cycle.
|
|
For convenience. Pretty much every user of
gst_buffer_iterate_meta() filters for a specific
api type.
https://bugzilla.gnome.org/show_bug.cgi?id=775727
|
|
These can be used from bindings.
https://bugzilla.gnome.org/show_bug.cgi?id=768301
|
|
The alias define GST_TYPE_PARENT_BUFFER_META_API_TYPE is wrong and
breaks the usage of gst_buffer_get_parent_buffer_meta().
This patch fixes the GType alias and make another alias to keep the API
compatibility guarded by GST_DISABLE_DEPRECATED.
Also added a unit test.
https://bugzilla.gnome.org/show_bug.cgi?id=763112
|
|
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=754464
|
|
gtk-doc can handle static inline functions just fine these days,
there's no need for this stuff any more.
|
|
There is a similar explanation in gst_caps_make_writable, but the existing
documentation can be misleading since it does not define what 'is already
writable' means.
Also note when this function is meant to be used.
|
|
API: GST_BUFFER_DTS_OR_PTS
Many scenarios/elements require dealing with streams of buffers that
might have DTS set (i.e. encoded data, potentially reordered)
To simplify getting the increasing "timestamp" of those buffers, create
a macro that will return the DTS if valid, and if not the PTS
|
|
This confuse the parser, hence it does not endup in the doc and the
index properly.
|
|
A core meta which helps implement the old concept
of sub-buffering in some situations, by making it
possible for a buffer to keep a ref on a different
parent buffer. The parent buffer is unreffed when
the Meta is freed.
This meta is used to ensure that a buffer whose
memory is being shared to a child buffer isn't freed
and returned to a buffer pool until the memory
is.
https://bugzilla.gnome.org/show_bug.cgi?id=750039
|
|
There was few Since: mark missing their column. Also unify the way
we set the Since mark on enum value and structure members. These
sadly don't show up in the index.
|
|
Makes it possible to get filesink to fsync() after rendering
a buffer.
|
|
A variant of gst_buffer_copy that forces the underlying memory
to be copied.
This is added to avoid adding an extra reference to a GstMemory
that might belong to a bufferpool that is trying to be drained.
The use case is when the buffer copying is done to release the
old buffer and all its resources.
https://bugzilla.gnome.org/show_bug.cgi?id=745287
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=730957
|
|
This should help improve documentation generated for
languages other than C.
https://bugzilla.gnome.org/show_bug.cgi?id=730961
|
|
It's nicer to only have it set when something noteworthy
happened and otherwise unset.
https://bugzilla.gnome.org/show_bug.cgi?id=725862
|
|
Check if memory is writable in a buffer and thus is exclusively owned by
this buffer.
|
|
Add a flag to check if the memory changed in a buffer.
|
|
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=720029
|
|
* fix typo GstBufferFlag -> GstBufferFlags
* fix typo GstFeatures -> GstCapsFeatures
* fix typo GstAllocatorParams -> GstAllocationParams
* fix typo GstContrlSources -> GstControlSource
* do not refer to gstcheck as an object
* make references gtk_init() and tcase_set_timeout() not be references
* gst_element_get_pad() renamed gst_element_get_static_pad()
* gst_clock_id_wait_async_full() renamed gst_clock_id_wait_async()
* _drop_element() is really gst_queue_array_drop_element()
* gst_pad_accept_caps() was removed, do not refer to it
* separate GST_META_TAG_MEMORY_STR declaration from description
* do not describe removed gst_collect_pads_collect()
* correctly link to GstElementClass' virtual set_context()
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=719614
|
|
Add the a function to query the maximum amount of memory blocks that can be
added to a buffer. Also improve the docs for _insert_memory().
|
|
API: gst_buffer_extract_dup
|
|
gst_buffer_copy_into() and gst_buffer_resize_range() can now fail.
|
|
|
|
Add a buffer copy flag to force a memory copy in all cases.
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=687520
|
|
We won't be able to implement this so it's better to move it out of the way.
|