4 ms·
I hit this bug just the other night, and I think what caused it was accidentally sending NaNs to the audio API. That bypassed whatever clamping functions were i
by user-the-name 5y ago
I hit this bug just the other night, and I think what caused it was accidentally sending NaNs to the audio API. That bypassed whatever clamping functions were in place, and just produced an ear-piercing shriek. Very unpleasant.
- mojuba 5y agoNo, it's not just NaN's, see my reply above.
- user-the-name 5y agoJust tried it and yeah, I can reproduce. That is pretty bad!