diff options
author | Christoph Heinrich <christoph.heinrich@student.tugraz.at> | 2023-09-29 21:00:30 +0200 |
---|---|---|
committer | Kacper Michajłow <kasper93@gmail.com> | 2024-05-07 23:32:55 +0200 |
commit | e166ae0ed8980ac090097d81b218239723f007a0 (patch) | |
tree | d2889d0703209ee19b87bd0be9d0bf77699eb012 /DOCS/MPlayer-FAQ | |
parent | 18ed9e105a1fa20f45e3ccdcb51d5939aee4a6ee (diff) | |
download | mpv-master.tar.bz2 mpv-master.tar.xz |
scaletempo2 has this optimization where it first uses a step size of 5
together with a quadratic interpolation to quickly get the approximate
position of the best overlap and then does a more thorough search aroun
that area.
Doing the same thing in scaletempo brought a 4.8x performance
improvement, however in my measurements a step size of 3 more
consistently finds good overlaps and it's still a 2.9x improvement for
this function.
I should note that while a step size of 3 produced better numbers,
I was not actually able to hear any difference in my test.
A step size of 3 was chosen just in case it actually makes an audible
difference in some cases and the cpu usage isn't really a problem
anymore, but that can be revisited in the future.
scaletempo2 is still faster then scaletempo with a step size of 5,
which I suspect is mostly because it uses some vectorized functions and
scaletempo does not.
Diffstat (limited to 'DOCS/MPlayer-FAQ')
0 files changed, 0 insertions, 0 deletions