Releases: GoogleChrome/omnitone
Releases · GoogleChrome/omnitone
Release v1.3.0
Release v1.2.5
- Update NPM packages to resolve security vulnerability and installation problem.
- Fix the code according to the updated ESLint package.
- Regenerated library files and documentations.
Release v1.2.4
- Minor maintenance: add WebPack4's new
development
build option. - Version updated to 1.2.4.
Release v1.2.3
- Make the rotation mechanism identical between FOA and HOA renderer. With this change, the rotator directly can take the matrix from Three.js.
- Updated npm packages: Upgraded to Node 9 + WebPack 4.
- Modified Travis config file for Node 9.
Release v1.2.1
- Fixed: The rejection handler from
FOA/HOARenderer.initialize().then()
promise doesn't get invoked correctly. - All source codes will have @license tag for JSDoc purpose.
- These tags will be stripped out at the compilation, and a banner license will be added to the result of compilation.
Release v1.2.0
- FOADecoder is deprecated in favor of FOARenderer.
- Old HRIR files in PCM audio file format were removed. Omnitone does not rely on PCM audio file or XHR for loading HRIRs.
Release v1.0.6
- HRIR data for 2nd order ambisonic is added.
- Explicit multi-channel management of renderer's input.
- Both renderers clamp number of channels in the input stream.
(FOA: 4ch SOA: 9ch, TOA: 16ch)
- Both renderers clamp number of channels in the input stream.
Release v1.0.5
- Synchronous resource loading: Base64-encoded HRIR
- FOARenderer is in "ready" state 2x faster.
- HOARenderer (TOA) is in "ready" state 7x faster.
Release 1.0.2
- Removed Gstatic CDN reference.
- Updated README.
Release 1.0.1
- Added
eslint
into the build system to enforce Google JS style. - Modified Travis CI config to automate the linting task.
- Fixed Safari 10
let
iterator bug.