A stack with animation has a whistle.wav audioClip imported. When the animation gets to a certain position the sound is supposed to play.
It has been working fine for a considerable time on my old laptop (Windows 10, 32 bit, LC 9.0). I just tried it on a new laptop (Windows 10, 64 bit, LC 9.0) and when the animation reaches the trigger point, everything stops and hangs for 3 or 4 seconds before the sound plays, the animation is halted and then starts again with a jerk once the whistle sound starts.
The code is very simple, just
The same happens with
I have used this short uncompressed sound as an imported audioClip for some time, as the overhead is minimal and packaging simple, specifically because I have heard in the past about the delay in a player object buffering up the file before sound emerges, while the audioClip is instant. This seems to be the case no longer on a more modern machine. Any explanation and workaround? I can't have everything stop for tea before the whistle blows.