Different buffer types returned in different contexts
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 101
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
When I run locally, I get a UInt8Array, but then when I run on gh-pages I'm getting Buffer objects, and then the AudioContext.decodeAudioData method complains that it isn't a proper buffer array.
Any idea why the context would change the return type?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the difference between the local run and the gh-pages demo at http://flyswatter.github.io/web-mpd/, then inspect the value passed to AudioContext.decodeAudioData in each context. Done means the HTTP client exposes the same buffer type in both environments and decodeAudioData accepts it without complaint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100