@rexrainbow you shouldn't modify the built-in plugins - it will make your project totally unportable to other installations other than your own, which could make bug reporting and sharing projects difficult in future. Also, for legal reasons, strictly speaking I don't think we should be using your code. So I'll see if I can get this in to a future build, but it may be incompatible with the changes you have already made.Ashley2012-02-06 16:02:08
@smitchell the Audio object actually now uses 4 different audio APIs under the hood because audio support is very patchy and we have to use different engines on different platforms. I think only one of them supports getting the time like that. So it would not be well supported at all. Whenever we add features that aren't supported everywhere people come back and report the fact they don't work as bugs when it's just not supported on the platform they happen to be using. So I would prefer not to add it. Audio support is very rough in HTML5 and unfortunately the current state of the audio object is about as far as it will stretch without almost everything being broken somewhere.
You can work around it by measuring the time since you played the sound yourself.