Ruud van Asseldonk
Ruud van Asseldonk
Could you elaborate? The only reference to “marker” on the linked page is > 65534 | A special marker value, indicating that this is an "extended" wave file.
Ah, that makes sense. I just merged #27 which allows writing arbitrary chunks, which enables this, although it is a bit low-level. It would be nice to have special support...
At the moment there is still no high-level API for writing cue points, the best you can do at this time is to write the chunk manually.
The reader returns the raw data from the file. What I would do for this case is match on the sample format, and apply a normalizing factor when it’s an...
> but shouldn't `WavReader.samples::()` return a normalized result? I’m not sure, there are good arguments to be made for both sides. * If we scale to [-1, 1] when reading...
What do you want to achieve exactly? Do the samples ever end, and should the output be a valid wav file at that point? Is there a specific reason for...
I just published version 3.0.0, which improves write performance a lot by adding a dedicated writer for a certain sample type. I think we can do the same for reads,...
Thank you for taking the time to open a pull request. Do you have any details about why libc 2.86 is needed for aarch64 support? Could you please avoid introducing...
I pushed an alternative to master that bumps libc without reformatting code, and removes some outdated things from `Cago.toml`. Can you confirm that it works? If it does, I’ll make...
I’m going to assume the bump resolved this.