David Bryant

Very cool! What would support from within my repository look like? Would it just be another "example" plugin like the winamp plugin? Why would it belong in the WavPack repo...

The repo already uses Travis for CI, and that includes running the library test (wvtest). The only reason that other change made it through was because I didn't receive the...

When I created the low-latency version I thought that latency was the only issue (which it addresses superbly). Now I understand than in many, and perhaps most, low-latency types of...

You bring up a great point. I need to make sure that any fixes to the mainline WavPack code (which is constantly being fuzz tested) get ported into the wavpack-stream...

Yes, they share the underlying codec algorithm and, for instance, the assembly language optimizations. However it's not just the I/O on top that's different, the file format is completely different....

I'm pretty sure it would be possible to create a utility to convert a `wavpack-stream` to a regular WavPack stream/file that could be decoded by the regular library. However, the...

The low-latency packets _do_ contain that information, and in fact I used this library to create a system for reliably streaming audio over UDP. I created both a lossless and...

Hi Alessio, Interesting application! Actually a good friend of mine worked at Neuralink for a couple years, and we discussed this same thing several times! The WavPack compression library (libwavpack)...

> Glad to hear that we don't need ay modification to extend it beyond 256 channel! :) Could you point mo to the code that needs to be changed in...

> @dbry I wanted to try to use the hybrid mode via the CLI, but I cannot get it to work: > > ``` > >>> wavpack mywav.wav -bn 16...