VK_ERROR_VIDEO_PROFILE_CODEC_NOT_SUPPORTED_KHR, which drivers return for a codec profile they have no notion of, such as H.264 High 4:2:2, fell through to a silent generic failure.
I am listed as maintainer for vf_*_d3d12.c.
MP4RA registers 'dav1' as a variant of 'av01' that signals Dolby Vision.
The VARC draft permits static fonts without a 'fvar' table to retain 'gvar' or 'CFF2' variation data for component-internal coordinates.
Add NEON implementation using LD3 to load 48 bytes with de-interleaving using which 6 bits are extracted using USHR and SLI to get 4 registers, which is used as a index into lookup table using TBL with 4 registers to translate into the 64-byte output, which is written using ST4 to interleave.
The D3D11 header is conditional, but the context members and frame processing helpers using its types are not.
sr1-1 and point need a packed RGB surface.
amf_setup_input_output_formats() builds both negotiated lists from output_pix_fmts and ignores its input_pix_fmts argument, so the input lists have never been used and have drifted from what the filters handle. None of them lists AV_PIX_FMT_D3D11 or AV_PIX_FMT_DXVA2_VLD even though amf_avframe_to_amfsurface() wraps both.
amf_setup_input_output_formats() built both negotiated lists from output_pix_fmts, so every filter's input_pix_fmts argument was dead and the input link only ever offered what the filter could output. For vpp_amf, whose input list is deliberately wider than its output list, libavfilter therefore inserted a software conversion in front of the filter for any input format missing from the output list.
amf_init_filter_config() falls back to outlink->format for the output frames context when no format is requested.
The AMF filter components read their input with a shader and reject a texture created without D3D11_BIND_SHADER_RESOURCE, which is what a D3D11VA decoder pool provides.
The AMF filters ran off a filter_frame callback, which has no way to tell a component that no more input is coming.
The shared output path retags every frame from the filter's color_profile unless that is AMF_VIDEO_CONVERTER_COLOR_PROFILE_UNKNOWN, which is -1.
CreateSurfaceFromDX11Native() and CreateSurfaceFromDX9Native() wrap the texture without taking a reference on anything FFmpeg owns.
With skip_frame at AVDISCARD_ALL the parameter set and SEI NAL units are still decoded, and as long as no decoded frame has configured the decoder, the parameters of the SPS activated by the first slice are exported.
Ported the x86 AES-NI implementation to aarch64 NEON using AES extension.
uart_init() cannot tell its caller that the UART the user asked for did not come up: every failure path only printks.
When creating a domain on ARM, and passing XEN_DOMCTL_CONFIG_GIC_NATIVE for the gic_version field in the struct xen_arch_domainconfig, arch_sanitise_domain_config() resolves this to the approrpiate GIC_V2 or GIC_V3 version the domain actually has, based on the host's gic_hw_version().
In the process, also add the range assumption and cast to the detect_alpha intermediates, which seems to help codegen: checkasm:- CPU: AMD Ryzen 9 9950X3D 16-Core Processor (00B40F40)- Timing source: x86 (rdtsc)- Bench duration: 100000 µs per function (442374016 cycles)- Random seed: 2809724650 Benchmark results: (old) name cycles (vs ref) detect_alpha_8_full_c: 7582.7 detect_alpha_8_full_off_c: 7587.4 detect_alpha_8_limited_c: 13306.7 detect_alpha_16_full_c: 3482.5 detect_alpha_16_full_off_c: 3480.4 detect_alpha_16_limited_c: 8055.1 detect_range_8_c: 1271.4 detect_range_16_c: 1213.0 Benchmark results: (new) name cycles (vs ref) detect_alpha_8_full_c: 4716.6 detect_alpha_8_full_off_c: 4715.4 detect_alpha_8_limited_c: 7943.2 detect_alpha_16_full_c: 2920.2 detect_alpha_16_full_off_c: 2918.9 detect_alpha_16_limited_c: 9952.0 detect_range_8_c: 1253.1 detect_range_16_c: 1194.8 The ~20% slowdown for detect_alpha_16_limited_c is because the previous version of the code short-circuited this condition, which is faster when the compiler is not able to vectorize the loop body and falls back to a pure scalar loop. However, I don't think optimizing around this is necessary as it's a pure compiler optimization question.
This allows the shared: cache protocol to ignore errors in the underlying URL (e.g.
This can only ever be a lower bound in theory, because a process could crash exactly in between committing the cached block and updating the count, though that edge case is incredibly rare. This is a backwards-compatible addition so it doesn't require a cache version update.
This allows users to limit the amount of cached data.