bfirsh / bfirsh/dynamicaudio.js
New buffer is created on every write
- Dominant language
- JavaScript
- Stars
- 172
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
When using the Web Audio API, a new buffer is created on every write. This sucks, and means it's practically impossible to play sound than is longer than the length of the write.
Ideally, we should have a callback for filling the buffer, like the Web Audio API. As an interim solution, dynamicaudio.js should maintain its own buffer somehow.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading dynamicaudio.js, focusing on the write path and how it uses the Web Audio API and Flash shim. Determine how buffer lifetime currently relates to each write and how a persistent buffer or filling callback should behave. Done means longer audio can be played without creating a new buffer for every write, with behavior consistent across supported backends.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100