| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
We now negotiate subframe mode through the caps. To enabled subframe
mode, the caps need to specify alignment=nal:
... ! omxh264enc ! video/x-h264,alignment=nal ! ...
... ! omxh265enc ! video/x-h265,alignment=nal ! ...
|
|
|
|
| |
Use subframe base class support.
|
| |
|
|
|
|
| |
Fix warning when building using version 2019.2 of OMX headers.
|
|
|
|
| |
Adds load-qp-absolute and load-qp-relative qp-modes
|
|
|
|
|
| |
Stride of input buffer may be different from
that of omx input port even if both sizes are the same.
|
|
|
|
|
|
|
|
|
|
| |
By passing the expected video buffer layout, the upstream producer
may be able to produce buffers fitting those requierements allowing
gst-omx to use dynamic buffer mode rather than having to copy each input
buffer.
This is particularly useful with v4l2src as it can request the capture
driver to produce buffers with the required paddings.
|
|
|
|
|
|
|
| |
Tell buffer consumer about our paddings.
v4l2src can now uses these paddings information when trying to import
buffers to configure the v4l2 driver accordingly.
|
|
|
|
|
| |
Use the actual OMX buffer size rather than the info.size as OMX
may require larger buffer if the port requires some padding.
|
| |
|
| |
|
|
|
|
|
| |
My latest patch introduces some regressions which I have no time to
debug properly at the moment so just revert it for now.
|
|
|
|
|
|
|
|
|
| |
Fixing a regression introduced in my previous patch
(7c40a91c31aa4bcbb191f7c6a5d222edf9dfd9d1).
The ALLOCATION query needs to be handled by GstVideoEncoder (to call
propose_allocation()) so chain up the query handling rather than early
returning.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ensure that the encoder releases all its input buffers when requested by
upstream. Encoder input buffers may be shared with downstreaming (when
using dmabuf), upstream may then request the encoder to
drain when reconfiguring before destroying its buffers.
Also drain on ALLOCATION query as we already do in kmssink as that
notify of a format change.
Fix "decoder ! encoder" pipeline when decoding a file with different
resolutions on Zynq.
|
| |
|
| |
|
|
|
|
| |
Make it easier to debug dynamic format changes.
|
|
|
|
|
| |
When importing dmabuf, UseBuffer() has to be called with the fd as
pBuffer rather than the mapped address of the buffer.
|
|
|
|
|
|
|
| |
When importing dmabuf from downstream, we want the allocator to be in
OTHER_POOL mode despite output_mode being DMABUF.
So check first if other_pool is set before checking for pool's
output_mode.
|
| |
|
|
|
|
|
| |
Can be useful when debugging to check the caps supported by the decoder
before filtering.
|
|
|
|
| |
After handling codec config, codec frame should be unreffed.
|
|
|
|
|
| |
This has proven to be very useful when debugging to detect bugs where we
match the wrong gst frame with an output OMX buffer.
|
|
|
|
|
|
| |
Those debug infos have proved to be very helpful when debugging
timestamp issues. They are often linked to gst-omx picking the wrong
frame when trying to map from OMX.
|
|
|
|
|
| |
If decoder outputs internal buffer and not use OMX_UseBuffer,
downstream bufferpool should be stopped.
|
|
|
|
|
|
| |
Add a property to control the number of frames for reference.
Min and max value is based on OpenMAX IL 1.2.0 Specification.
|
|
|
|
|
|
|
| |
This means we can use some newer features and get rid of some
boilerplate code using the G_DECLARE_* macros.
As discussed on IRC, 2.44 is old enough by now to start depending on it.
|
| |
|
|
|
|
| |
They are no longer used anywhere
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
One big restriction of the OMX buffer pool has always been
that the GstMemory objects were flagged with NO_SHARE.
This was because the buffer pool needed to be sure that when
a buffer returned to the pool, it would be safe to release the
OMX buffer back to OpenMAX.
With this change, this is no longer a restriction. What this
commit introduces is a new allocator that allows us to track
the GstMemory objects independently. Now, when a buffer returns
to the pool, it is not necessary for the memory to be released
as well. We simply track the memory's ref count in the allocator
and we return the OMX buffer back when the memory's ref count
drops to 0.
The reason for doing this is to allow implementing zero-copy
transfers in situations where we may need to copy or map a
certain region of the buffer. For instance, omxh264enc ! h264parse
should be possible to be zero-copy by using an OMX buffer pool
between them.
|
|
|
|
|
|
|
|
|
| |
gst_memory_map() is already adding the offset to the mapped pointer.
Doing it in the memory implementation was resulting in the offset being
accounted twice.
It doesn't matter yet as we are only creating memory without offset for
now but it will once we'll start sharing OMX memories.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
gstomx.c:1405:10: error: ‘OMX_IndexParamCustomContentPipe’ undeclared (first use in this function)
case OMX_IndexParamCustomContentPipe
Some enums have been deprecated in 1.2.0
https://gitlab.freedesktop.org/gstreamer/gst-omx/issues/27
|
|
|
|
|
| |
Use pkg-config to detect and configure rpi specific libs used in testegl
rather than hardcoding their flags.
|
|
|
|
| |
Neded for the declaration of eglSaneChooseConfigBRCM().
|
|
|
|
|
| |
We need to define __VCCOREVER__ and disable redundant-decls before
including the egl.h from the pi.
|
| |
|
| |
|
|
|
|
|
|
|
| |
gstomxvideoenc.c:2874:7: error: "USE_OMX_TARGET_ZYNQ_USCALE_PLUS" is not defined, evaluates to 0 [-Werror=undef]
#elif USE_OMX_TARGET_ZYNQ_USCALE_PLUS
Works on meson because it doesn't use -Wundef
|
|
|
|
|
|
|
|
|
|
|
| |
This commit adds a .gitlab-ci.yml file, which uses a feature
to fetch the config from a centralized repository. The intent is
to have all the gstreamer modules use the same configuration.
The configuration is currently hosted at the gst-ci repository
under the gitlab/ci_template.yml path.
Part of https://gitlab.freedesktop.org/gstreamer/gstreamer-project/issues/29
|
|
|
|
|
| |
No need to create debug structs which won't be used as DEBUG macros are
no-op.
|
|
|
|
| |
Extend OMX_API_TRACE by logging component configuration calls.
|
|
|
|
|
|
|
|
|
|
| |
This was the single place where this category was used in gst-omx so
most users, including me, are generally not turning it and were missing this
important information from logs.
The copying code uses gst_video_frame_copy() which is already logging
with CAT_PERFORMANCE so we can still have this information when using
only this debug category.
|
|
|
|
|
| |
We were silently ignoring the pool which was pretty confusing when
debugging.
|
| |
|
|
|
|
|
|
|
| |
Add more warnings flags and disabled unused variable warnings if gst
debug system is disabled.
Copied from gst-plugins-good/meson.build
|
| |
|
| |
|
|
|
|
| |
requirement
|