tesselode
tesselode
The start times are quantized to the internal buffer size in general.
I've discussed this a bit in the Bevy discord, but there's some considerations for a feature like this: - Which volume do we report - the actual volume as last...
Indeed, that is an oversight. I'm not sure if there's any realistic scenarios where a decoder returns an error, but it can still continue decoding. So it might be best...
If you're doing realtime synthesis, I'd recommend implementing the `Sound` trait directly. Streaming sounds are more for streaming sounds from files.
Yes, `SoundData` splits into a `Sound` implementation and a corresponding handle upon passing it into a `play` function.
I want to keep Kira's built-in features game-focused. I don't think media players would necessarily benefit from the same kind of API a game needs and vice versa. That being...
I wrote that code with the assumption that a stream would stop after one error. What a fool I was! Would it make sense to add a `pop_error` function to...
What do you mean by "the error callback should be cold"? I'd be down to add a growable ringbuffer type if you can find a way to not allocate on...
Thanks for pointing this out. I'm thinking about APIs that would help resolve this.
For the time being, you could try fading out the first sound with `Easing::OutPowf(0.15)` and fading in the second with `Easing::InPowf(0.15)`. 