- 30 Nov, 2015 4 commits
-
-
Mohamed Naufal authored
Additional improvements by Michael Niedermayer <michaelni@gmx.at>. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
Michael Niedermayer authored
Fixes out of array reads. Found-by: Mateusz "j00ru" Jurczyk and Gynvael Coldwind Signed-off-by: Michael Niedermayer <michaelni@gmx.at> Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 27 Jul, 2015 1 commit
-
-
Vittorio Giovara authored
Express bitfields more simply. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 14 Feb, 2015 1 commit
-
-
Diego Biurrun authored
-
- 03 Oct, 2013 1 commit
-
-
Diego Biurrun authored
-
- 08 Mar, 2013 1 commit
-
-
Anton Khirnov authored
-
- 12 Feb, 2013 1 commit
-
-
Justin Ruggles authored
-
- 04 Dec, 2012 1 commit
-
-
Anton Khirnov authored
It will be useful in the upcoming transition to refcounted AVFrames.
-
- 11 Nov, 2012 1 commit
-
-
Justin Ruggles authored
Also reorder some other #include when applicable.
-
- 25 Oct, 2012 1 commit
-
-
Diego Biurrun authored
The function is used elsewhere and does not belong with the LZO code.
-
- 24 Oct, 2012 1 commit
-
-
Anton Khirnov authored
-
- 04 Sep, 2012 1 commit
-
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 30 Aug, 2012 1 commit
-
-
Kostya Shishkov authored
-
- 14 Aug, 2012 2 commits
-
-
Mans Rullgard authored
It is impossible for bits to be 15 here so the special case is not needed. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
This function is always called with a non-negative argument, so those special cases are not needed. In the places the argument might be zero, the return value for a zero argument does not matter since it would then be used to scale an array full of zeros. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
- 13 Aug, 2012 15 commits
-
-
Mans Rullgard authored
Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
Although a reasonable compiler will probably optimise out the actual store and load, this operation still implies a truncation to 16 bits which the compiler will probably not realise is not necessary here. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
Writing the scaled excitation to a scratch buffer (borrowing the 'audio' array) instead of modifying it in place avoids the need to save and restore the unscaled values. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
Use saturating addition functions instead of 64-bit intermediates and separate clipping. This is much faster when dedicated instructions are available. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
Firstly, nothing in this function can overflow 32 bits so the use of a 64-bit type is completely unnecessary. Secondly, the scale is either a power of two or 0x7fff. Doing separate loops for these cases avoids using multiplications. Finally, since only the number of bits, not the actual value, of the maximum value is needed, the bitwise or of all the values serves the purpose while being faster. It is worth noting that even if overflow could happen, it was not handled correctly anyway. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
The operands in both cases are 16-bit so cannot overflow a 32-bit destination. In gain_scale() the inputs are reduced to 14-bit, so even the shift cannot overflow. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
The 'shift' argument is always 1 so there is no need to pass it explicitly in every call. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
The compiler performs this optimisation. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
- 10 Aug, 2012 4 commits
-
-
Mans Rullgard authored
This addition must be done as 64-bit to avoid overflow and for the subsequent clipping to be meaningful. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
In 16-bit arithmetic, x * 0xffffc is simply x * -4 with extra overflows, (and the constant was probably meant to be 0xfffc). Combined with the shift, this simplifies to -x >> 1. Finally, clearing the low two bits with a 32-bit mask and switching to a 32-bit type allows more efficient code on 32-bit machines. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
(x << 2) - x is just an optimisation of 3 * x the compiler is perfectly capable of doing on its own. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
Signed-off-by: Mans Rullgard <mans@mansr.com>
-
- 08 Aug, 2012 2 commits
-
-
Kostya Shishkov authored
It expects maximum value to be 32767 but calculations in scale_vector() which uses this function can give it ABS(-32768) which leads to wrong result and thus clipping is needed.
-
Kostya Shishkov authored
Due to some mistake LPC vector for the first subframe was used for all subframes instead of their own LPC vectors.
-
- 07 Aug, 2012 1 commit
-
-
Anton Khirnov authored
-
- 03 Aug, 2012 1 commit
-
-
Kostya Shishkov authored
-