JoergAtGithub

Compiling this without -ffast-math as for FpClassify would remove the errors of cause. But I don't think this is a proper fix, as there seems to be no need to...

I agree with @Swiftb0y here, moving the code to fpcallsify.cpp would be an ugly workaround and no proper fix. It's our own code, that uses INF - therefore we can...

Let me try to write it in other words: -The Microsoft Visual C++ Redistributable toolsets are backward compatible -The Github runner image Windows-2019 contains: --Full VS2019 incl. the 14.4 toolset...

The only thing I know, is that VisualStudio use ClangFormat, but not at opening of a file. Only if you edit a line. Could it be, that Gits automatic EOL...

I saw a post on Reddit where a user struggled with it, and refered to this manual example: https://www.reddit.com/r/MIXXX/comments/1hmwvbt/lot_of_latency_when_using_laptop_external_audio/

I can confirm that this occur much more often in recent 2.6 builds. This needs to be fixed before a release. I increase the priority accordingly therefore.

It happens randomly, after some minutes of Mixxx usage.

Sure: https://github.com/JoergAtGithub/vcpkg/blob/80bfc3a5a1b8d747ac9d39ef67e79969a790b28a/ports/sleef/portfile.cmake#L14-L26

Here is a zip with all logs from the failing run of the VCPKG CI run. The failure message is in `install-arm64-osx-dbg-out.log`: [failure logs for arm64-osx.zip](https://github.com/user-attachments/files/19499824/failure.logs.for.arm64-osx.zip)

This is a known limitation of the reconstructor: All bits in the feature report are const, and Windows removes any information about const caps during the pre-parsing step. The reconstructor...