Go to the documentation of this file.
26 const float g0 = gains[0];
27 const float g1 = gains[1];
28 const float g2 = gains[2];
35 for (
int i = 0;
i <
len;
i++) {
50 for (
int i = 0;
i <
len;
i++)
static float deemphasis_c(float *y, float *x, float coeff, const float *weights, int len)
av_cold void ff_opus_dsp_init_aarch64(OpusDSP *ctx)
static void postfilter_c(float *data, int period, float *gains, int len)
void ff_opus_dsp_init_riscv(OpusDSP *ctx)
it s the only field you need to keep assuming you have a context There is some magic you don t need to care about around this just let it vf default minimum maximum flags name is the option keep it simple and lowercase description are in without period
Undefined Behavior In the C some operations are like signed integer dereferencing freed accessing outside allocated Undefined Behavior must not occur in a C it is not safe even if the output of undefined operations is unused The unsafety may seem nit picking but Optimizing compilers have in fact optimized code on the assumption that no undefined Behavior occurs Optimizing code based on wrong assumptions can and has in some cases lead to effects beyond the output of computations The signed integer overflow problem in speed critical code Code which is highly optimized and works with signed integers sometimes has the problem that often the output of the computation does not c
#define i(width, name, range_min, range_max)
static const int weights[]
void ff_opus_dsp_init_x86(OpusDSP *ctx)
av_cold void ff_opus_dsp_init(OpusDSP *ctx)
static const double coeff[2][5]