17393 2012-06-05 12:13:09 +0000 (UseDoubles): float/double inconsistency 2014-10-28 17:16:38 +0000 1 1 1 Unclassified AudioWG Web Audio API unspecified PC All CLOSED WONTFIX P2 normal TBD 1 mike crogers mage olivier.thereaux public-audio dave.null oldest_to_newest 68705 0 mike 2012-06-05 12:13:09 +0000 Audio-ISSUE-17 (UseDoubles): float/double inconsistency [Web Audio API] http://www.w3.org/2011/audio/track/issues/17 Raised by: Marcus Geelnard On product: Web Audio API Throughout the spec, there seems to be a preference for using float over double (though some cases of double exists). Suggest only double except for sample format. As an example, currentTime as a 32-bit float will degrade the precision to less than 1 ms after less than 5 hours, which is uncomfortably close to real-world usage. 78322 1 crogers 2012-11-14 21:25:43 +0000 For time-related values it's very important to use double-precision, for other values this is not nearly as important. Fixed: https://dvcs.w3.org/hg/audio/rev/30b04185a648 78571 2 mage 2012-11-21 13:27:24 +0000 Yes, time values are the most important. On the other hand, is there really a point in using floats for anything (except, naturally, the AudioBuffer samples that use Float32Array)? For API consistency, I think doubles are preferred over floats. 78572 3 mage 2012-11-21 13:32:13 +0000 ...also, in ECMAScript everything is double anyway, so dumbing down to float does not make much sense (at least not to me). 80346 4 olivier.thereaux 2012-12-18 13:24:47 +0000 (In reply to comment #3) > ...also, in ECMAScript everything is double anyway, so dumbing down to float > does not make much sense (at least not to me). Looks like it would make sense to reopen this based on the comment above. If there is no significant price to consistency, we should aim for it throughout the spec. 113865 5 olivier.thereaux 2014-10-28 17:13:45 +0000 Web Audio API issues have been migrated to Github. See https://github.com/WebAudio/web-audio-api/issues 114008 6 olivier.thereaux 2014-10-28 17:16:38 +0000 Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.