You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-11Lines changed: 4 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,15 +17,15 @@ web audio API player is published to the [npm registry](https://npm.im/web-audio
17
17
18
18
This player has two modes, SOUND_MODE_AUDIO which uses the audio element to load sounds via the audio element and SOUND_MODE_FETCH to load sounds via the web audio API. Here are some of the differences between the two:
19
19
20
-
### the web audio API
20
+
### the web audio API (SOUND_MODE_FETCH)
21
21
22
22
* No support for streaming
23
23
* Files get loaded using fetch, the loading progress is in percent and it is a single value between 0 and 100 percent loaded
24
24
* A song has to be fully fetched before it can be turned into a buffer and hence before the playback can start
25
25
26
26
For a more complete list of features, check out the w3c [web audio API features list](https://www.w3.org/TR/webaudio/#Features) in their [candidate recommendation document](https://www.w3.org/TR/webaudio/#Features)
27
27
28
-
### the audio element
28
+
### the audio element (SOUND_MODE_AUDIO)
29
29
30
30
* Support for streaming
31
31
* Files get loaded using the audio element, the loading progress is not just a single value, it can be split into multiple parts (time ranges), so for example the start of a song from 0 to 10 percent got loaded, then there is a blank of not yet loaded data and then also the part from 35 to 60 percent has been loaded
@@ -87,7 +87,7 @@ update npm to latest version
87
87
88
88
install the dependencies
89
89
90
-
`npm install`
90
+
`npm i`
91
91
92
92
to build the distributions
93
93
@@ -140,14 +140,6 @@ Unfortunatly the defined window does not have AudioContext:
140
140
check out [[open] github ticket (as of 06/2019)](https://github.com/microsoft/TypeScript/issues/31686)
141
141
the current [dom.d.ts on github](https://github.com/microsoft/TypeScript/blob/master/src/lib/dom.generated.d.ts)
142
142
143
-
### linting setup notes
144
-
145
-
TSlint will be deprecated [github ticket](https://github.com/palantir/tslint/issues/4534)
146
-
147
-
> we plan to deprecate TSLint and focus our efforts instead on improving ESLint’s TypeScript support
148
-
149
-
Their [blog post](https://medium.com/palantir/tslint-in-2019-1a144c2317a9) announcing that [TSLint](https://github.com/palantir/tslint) will be deprecated in 2019 and you should switch to [ESLint](https://github.com/eslint/eslint) when TSLint is officially deprecated
* add an option that uses the visibility API to automatically mute and unmute a sound when the visibility changes
225
217
* rewrite how the audiocontext is created, for browser that enforce that a user interaction has taken place before a context can be running
226
218
* add option to persist the user volume choice using the localstorage
219
+
* switch from tslint to eslint with typescript-eslint plugin / parser: TSlint will be deprecated [github ticket](https://github.com/palantir/tslint/issues/4534), read their [blog post](https://medium.com/palantir/tslint-in-2019-1a144c2317a9) and then switch to [ESLint](https://github.com/eslint/eslint)
0 commit comments