Julio César Rocha

Does this support AIFF-C (.aifc) files?

Has this been implemented yet (as of boost 1.68)? If not, when is message compression used in a Beast WebSocket client?

It certainly does. If I got this correctly, by default, a Beast WS client stream has compression (per-message deflate) enabled, pending other conditions (server negotiation). Thanks.

> Hi @JunielKatarn that sounds pretty interesting! We already looked into WSL some time back. But back then we quickly ran into problems with the ffmpeg build scripts. I think...

> The changes ARE minimal, but I got a lot of backlash from the FFmpeg owners when I tried to submit the change due to some old-school bureaucratic conventions. When...

> Hi @JunielKatarn that sounds pretty interesting! We already looked into WSL some time back. But back then we quickly ran into problems with the ffmpeg build scripts. I think...

> I don't think that WSL will help here. Then problem is the autoconfig build system that just does not support MSVC toolchain at all. There is a PR open...

In that case, we should consider forking libass, and producing a separate NuGet package ourselves, in my opinion.

Understood! Though now I see libass is not related to building under WSL, I know Visual Studio ships with a Clang compiler toolset that should be compatible (linkable) with MSVC....

> Now that I think of it, do we really need the build to be done by MSVC? I'd expect a linker to be able to link against a lib...