rubato VS creek

Regarding improving the API for 0.6, something that bugs me about the current Rust audio ecosystem is that everyone is reinventing the wheel with their own audio buffer types each with their own API that downstream users have to learn. This makes it more of a hassle to pass audio data from one library to another than it should be. I've been contributing to the audio crate which provides buffer structs and traits for working with audio buffers with a common API regardless of their layout in memory. I have a work-in-progress branch for Rubato refactoring it to use the audio crate, though there's a bit more work to do in the audio crate to complete that. Would you be interested in using the audio crate in Symphonia?

If you want to change tempo and pitch together, that's resampling. You can use Rubato's asynchronous resamplers for that.

Another option is to read the file in another thread, buffer it so there's a window of samples, and sync that back to the audio thread. This is tricky, but thankfulky theres the creek crate that does this for you and has a player demo: https://github.com/MeadowlarkDAW/creek

If you're also interested in real-time disk streaming of audio then there's this crate (which uses symphonia for decoding): https://github.com/MeadowlarkDAW/creek.

Rodio is high level and likely not really suited to what you're trying to do. Rodio is nice if you just want to play sound files and don't care about the details. If you want to manipulate audio in realtime, Creek is likely a better fit. You can take a look how I am combining Creek and Rubato for realtime tempo changes in the DJ application I am writing.

I'm using this creek library from RustyDAW for realtime safe decoding of audio files. It can also record to WAV. It would likely be useful for project as well.