If you try replacing the 0 time values with 1, does that fix it? That has been a recent fix for open-ended responses and movie files also. It seems in some (as yet unpredictable) cases, the 0 value is taken perhaps too seriously and is causing problems. We are working on this but switching the 0ms TIME value to a 1ms value has seemed to help. However, I'd also point out that I haven't heard of this yet with sound.