Age | Commit message (Collapse) | Author | Files | Lines |
|
Some check where incorect and also unsafe. The only reliable information
in get_buffer2 is the picture width/height really. The side effect is
that the width/height of the internal pool endup padded, so when we
switch we also need to switch to the a new width/height, hence we save
the pool info.
https://bugzilla.gnome.org/show_bug.cgi?id=753869
|
|
|
|
This is achieved by using a tempory internal pool. We can then switch to a
downstream pool if the downstream pool buffer have matching strides.
https://bugzilla.gnome.org/show_bug.cgi?id=752802
|
|
It is faster than doing a query that propagates downstream and
should be enough
|
|
use template subset check for accept-caps
It is faster than doing a query that propagates downstream and
should be enough
|
|
It just calls the exact same function as the default handler
|
|
It just calls the exact same function as the default handler
|
|
Avoids repeating the same handling in many decoders
|
|
Avoids repeating the same handling in many decoders
|
|
|
|
Avoid doing downstream caps queries when accept-caps should just
do a shallow caps check on the element itself
https://bugzilla.gnome.org/show_bug.cgi?id=753623
|
|
Avoid doing downstream caps queries when accept-caps should just
do a shallow caps check on the element itself
https://bugzilla.gnome.org/show_bug.cgi?id=753623
|
|
Update to the metadata API ffmpeg has had in
place for a long time now, and reenable output
of GStreamer tags from the demuxer.
https://bugzilla.gnome.org/show_bug.cgi?id=566605
|
|
This parameter has been always false for a long time.
|
|
The size in the AVFrame in get_buffer2 don't match the output size,
instead they match ffmpeg's memory requirements, so we can't compare
them from the values of the output AVFrame. Those are comparable to
the values in the passed AVCodecContext.
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=753189
|
|
ffmpeg doesn't provide the final's image width & height in the get_buffer2()
callback, so it's not possible to create an output state for GstVideoDecoder
at this stage. So only try to do direct rendering if the buffer pool has already
been negotiated based on the final decoded size.
This partially reverts the effects of 2e621f8db
https://bugzilla.gnome.org/show_bug.cgi?id=752802
|
|
flags"
This reverts commit ac3437153dc6cb3d82cdda0d1f60ffc5600fdf67.
Doesn't actually make sense as it will put the (uninstalled) library paths
into the installed .la files. How does this all work?
|
|
|
|
Code was executed only on the first iteration, so just pull it out
of the loop entirely. This makes it clear it has nothing to do with the loop.
|
|
If it is created earlier and the stride is invalid, then the frame
will be freed and it won't be possible to use it in the fallback path.
Not doing this causes a segfault because it will try to use
already freed memory.
|
|
|
|
If there is no layout, just read the channel count from the
channels field.
https://bugzilla.gnome.org/show_bug.cgi?id=752186
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=752800
|
|
Those fields are documented to only be safe to access using
accessors as their position is not part of the ABI.
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=732682
|
|
In case of real videos, slice_offset is being allocated,
but the same is not being freed.
https://bugzilla.gnome.org/show_bug.cgi?id=752404
|
|
|
|
It's needed only for subtitle charset conversion, and we don't
use the ffmpeg subtitle support anyway.
Also disable d3d11va and dxva2 support, we don't use the hardware
codec support.
|
|
From f74b2df to 9aed1d7
|
|
VideoDecodeAcceleration framework is deprecated in 10.11, and currently
cuases linker errors when compiling on OSX. Oddly, --disable-hwaccels
did not also disable h264_vda already.
https://bugzilla.gnome.org/show_bug.cgi?id=751838
|
|
licensed version
|
|
|
|
ffmpeg seems to be the one of the two forks, which is most widely used by
Linux distributions and in general. Also Google is using it for e.g. Chrome
and has engineers working on finding and fixing security issues in it.
https://bugzilla.gnome.org/show_bug.cgi?id=751607
|
|
class
|
|
which is required by avcodec_decode_audio4 ()
|
|
The comma confuses our code, e.g. it's not a valid element name or structure
name.
|
|
gstavvidenc.c: In function 'gst_ffmpegvidenc_flush_buffers':
gstavvidenc.c:733:7: error: ISO C90 forbids mixed declarations and code [-Werror=declaration-after-statement]
GstFFMpegVidEncClass *oclass =
^
cc1: all warnings being treated as errors
|
|
They will get overridden by av_frame_unref() with the defaults.
|
|
libav might still have references to the buffers itself and uses a writability
system similar to ours based on reference counts.
|
|
|
|
|
|
|
|
|
|
libav always uses planar audio formats nowadays, not much use in
us trying to allocate anything here until we add support for planar
aka non-interleaved audio formats at least in audioconvert.
|
|
|
|
Who knows, maybe freeing the frame calls cleanup inside the codec.
|
|
|
|
|
|
And do the frame reference counting by adding AVBufferRefs to the frame.
|