Last year, I imported a multi-sample chiptune beep instrument and was quickly disappointed by a bug, where the engine would play the full sound from the beginning for specific sample splits, even though its loop and playback regions were being set correctly…
I think the issue was that the Properties pane rounded the sound length up and you set the end of the loop region to that. A friend of mine did that recently and we had to lower the loop region end to a tiny fraction of a second before the actual sound length.
Glad that won’t be necessary anymore!
Yep! The bug was similar to what @Bergan mentioned.
There’s some number of samples in a file; so e.x. a 1-second-long audio file at a sample-rate of 44.1kHz contains exactly 44100 samples.
Internally, the audio engine tracks loop points in samples; so if you wanted to loop the first half (0.5 seconds) of that 1-second-long audio file, the loop points would be placed at sample 0 and sample 22050 internally.
But, since the LoopRegion property is in seconds, there’s a conversion from seconds → samples that happens under the hood.
Taking the same example, if you wanted to loop the second half of the file, the loop points should be 22050 and 44100 – but sometimes, floating point is weird, and this would end up placing the loop points at e.x. 22049, or 44101. The audio engine interpreted loop points that are “out of bounds” as invalid, and ignored them completely – even if it was just minor rounding errors like this 
CreateEditableImageAsync rbxthumb support is now released!
I’ve been waiting so long on the Humanoid.Seated fix. I can’t wait for it to go live.
so when will it finally be gone? every time i do playtests my console gets flooded with warnings from that storybook plugin which makes debugging an absolute nightmare
Let’s say that I save a local audio file and access it through rbxasset://.
I make sure that the file has a sample rate which is an exponent of 2. Perhaps 32768 samples per second.
If I were using a version of Rōblox older than 655, could that bug still appear with round LoopRegion values such as 1 or 0?
It’s been 2 months since the release notes and I’m still unsure whether the Humanoid.Seated fix is live given it’s still showing as pending.
When can I be certain I can utilize this fix?
