tesselode
tesselode
@djgaven588 My Arch install didn't have `/etc/asound.conf` or `~/.asoundrc`, and my audio worked fine*. (*on pulse audio, it bypassed the system volume control, but I still had audio at least)
Changing volume instantaneously will result in an audible click because you're creating a discontinuity in the audio waveform. That's why `Tween::default` has a duration of 10ms - it's fast enough...
@DaforLynx my apologies, I didn't read the issue closely enough. Currently, parameters like volume and panning are updated once per buffer, and the value for each sample is interpolated from...
Older versions of Kira had problems when setting volumes every frame, but recent ones should be fine.
That sounds believable. Is there a reason why you can't create the spatial track with the correct position in the first place?
Everything you do on the main thread is async - positions and playback states will only update the next time the audio thread runs. I could potentially change it so...
@muja that's intentional, the sound has a good number of samples queued up at all times. Currently it's hardcoded to 16384 samples. I wouldn't mind making that customizable.
Thanks for the PR! Can you post an example m4a that didn't load correctly before this change?
Looks good, thank you!
Can you show an example of how this would be used for UI?