- Oct 21, 2020
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Oct 20, 2020
-
-
Tim-Philipp Müller authored
From 59cb678 to a825d27
-
- Jun 07, 2020
-
-
Part-of: <!321>
-
- Jun 06, 2020
-
-
We may build this plugin with window system support but run it without window system. Without this patch, the following pipeline will trigger a segfault when running it without window system. gst-launch-1.0 filesrc location=input.264 ! h264parse ! vaapih264dec ! fakesink Part-of: <!319>
-
- Mar 06, 2020
-
-
The strides and offsets could be the same, but the allocation size might be different (e.g. alignment). Thus, ensure we also set the flag to copy from VA memory to system memory when alloc size differs. Fixes #243
-
Base class's sink pad caps are already set when calling set_format(). There's no need to call it again in gst_vaapidecode_negotiate().
-
If caps update fail a dead lock occurs since the stream mutex is not unlocked.
-
- Mar 04, 2020
-
-
If the dependent_slice_segment_flag is true, most slice info derived from last slice. So we need check the slice type after we call populate_dependent_slice_hdr
-
- Feb 14, 2020
-
-
- Feb 04, 2020
-
-
The log messages where logged in the GstBufferPool category because the instance was not properly casted. This fix that situation.
-
Before the log wasn't processed because wrong instance pointer.
-
- Jan 09, 2020
-
-
-
Some streams have error data introducing unknown NAL type. There are also kinds of NAL types we do not want to handle. The old manner will set a decoder error when encounter this, which cause a latent crash bug. The decoder may successfully decode the picture and insert it into DPB. But there are error NAL units after the AU which cause the post unit error and make that frame dropped. The later output of the picture still want to ref that frame and crash. No need to set decoder error when can not recognize or handle the NAL unit, just skip it and continue. Fix: #191
-
Víctor Manuel Jáquez Leal authored
It is requiered to know if postproc is capable to change the video direction before fixating the source caps. In order to do it, it'ss required to know if there's a functional VPP, but that's checked at create() vmethod, which occurs after caps fixating. This patch checks for a functional VPP at fixate caps and, if so, checks for the enabled filtes and later do the caps fixations.
-
The value return from GST_VAAPI_RATECONTROL_MASK will be used by GST_VAAPI_POPCOUNT32 as its inpput. GST_VAAPI_POPCOUNT32 can only deal with unsigned int. Otherwise there may be an error of out of range of integer if we define few more rate-control mode.
-
Víctor Manuel Jáquez Leal authored
Otherwise the queue will swallow all the available decoder's surfaces reaching a dead-lock. This setting might impact the bin's peformance, but it's a trade-off.
-
Víctor Manuel Jáquez Leal authored
-
Víctor Manuel Jáquez Leal authored
When the code path goes to push buffers downstream when no surface available in decoder context, and it fails the code bails out with a fatal error. That behavior is wrong, since it shouldn't be fatal. The use case is when the video stream is disabled. This patch just ignores the errors in this situation and demotes the level of a log message.
-
-
Remove useless guard of all bitrate control mode's guard except MB which is define in VA-API version 0.39.1.
-
If display size is smaller than current frame size, then the crop size will be set as display size, which either crashes the pipeline or the output MD5 does not match. Rather it should use the actual decoded size. This patch removes the cropping set. For rendering we can use aspect ratio to set display size. Fixes #175 Signed-off-by: Wang Zhanjun <zhanjunx.wang@intel.com> Signed-off-by: Xu Guangxin <guangxin.xu@intel.com>
-
For some main-10 stream, sometime the luma is 8 bits while chrome is more than 8 bits, which cause using the wrong NV12 surface as the render target and decoding error. Fix #176
-
For surfaces with different chroma type, it is prefer to initialize a format which chroma type should be same with surface chroma type instead of using fixed NV12.
-
The old mapping values return by gst_vaapi_utils_h265_get_profile_idc is wrong, though GST_H265_PROFILE_IDC_MAIN and GST_H265_PROFILE_IDC_MAIN_10 happened to be the correct value. We only support Annex A profile_idc (1-4).
-
Víctor Manuel Jáquez Leal authored
-
-
-
Víctor Manuel Jáquez Leal authored
VAEntrypointFEI appeared in libva 2.0.0 (API version 1.0.0)
-
-
- Jan 08, 2020
-
-
-
g_return_val_fail() documentations says: If expr evaluates to FALSE, the current function should be considered to have undefined behaviour (a programmer error). The only correct solution to such an error is to change the module that is calling the current function, so that it avoids this incorrect call. So it was missused in a couple parts of the H264 and H265 internal decoders. This patch changes that to plain conditionals. Also, it was included a couple code-style fixes.
-
According hevc spec, scaling_list_data is not related to chroma_format_idc.
-
gst_vaapi_video_pool_reserve_unlocked() hit an undocumented behavoir because it locks twice the same mutex. Also, n had different meanings in the current code: as an increase value and as a new total of allocated surfaces. This patche removes the undocumented behavoir (usually a deadlock) and fixes the meaning of n as the new total of allocated surfaces. Signed-off-by: Víctor Manuel Jáquez Leal <vjaquez@igalia.com>
-
-
If the allocation caps and negotiated caps are the same, then ensure any previously negotiated video info is also removed. This can occur when multi-resolution video decoding returns to it's original resolution. Fixes #170
-
Allow NULL negotiated_vinfo to be passed into gst_allocator_set_vaapi_negotiated_video_info to allow any previously set info to be removed.
-
There are many profile levels that can support more than 102400 kbps. Thus, increase the max allowed bitrate property value from 102400 kbps to 2048000 kbps (same as msdk encoder plugins).
-
- Dec 03, 2019
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-