lazka
Joined 7 years ago
Joined 7 years ago
$ flac --version
flac 1.5.0
$ hyperfine -r5 "flac -f -8 a.wav a.flac" "flac -j16 -f -8 a.wav a.flac"
Benchmark 1: flac -f -8 a.wav a.flac
Time (mean ± σ): 13.148 s ± 0.194 s [User: 12.758 s, System: 0.361 s]
Range (min … max): 12.934 s … 13.318 s 5 runs
Benchmark 2: flac -j16 -f -8 a.wav a.flac
Time (mean ± σ): 2.404 s ± 0.012 s [User: 14.126 s, System: 1.355 s]
Range (min … max): 2.395 s … 2.425 s 5 runs
Summary
flac -j16 -f -8 a.wav a.flac ran
5.47 ± 0.09 times faster than flac -f -8 a.wav a.flac"I decided that analysis should focus on the higher, more conventional rates – 48k and 44k1" - opus is always 48khz, so that doesn't mean much.
> Huh. Yeah, that does seem odd - is it a result of MSYS2 being oriented at devs who need compatible libraries?
Yeah, we are oriented at devs that re-package our binaries and also want to be a development environment for upstreams, and also a testbed for toolchains. So we provide x86/x64/arm64, then ucrt/msvcrt, and llvm/gcc. I wouldn't blame anyone for finding this confusing. It's described here: https://www.msys2.org/docs/environments
For ffmpeg, since it was mentioned as an example, this looks like: https://packages.msys2.org/base/mingw-w64-ffmpeg
You can still force it via `pip install --break-system-packages ...` if needed.