Regression: Sound component not playing audio asset across multiple entities in 0.8.*
See original GitHub issueDescription:
When multiple entities utilize the sound component, and use the same audio asset source, only one instance of audio is created in 0.8.*.
This does work as expected in 0.7.* as long as an <audio> element is used rather than an <a-asset-item>.
In 0.8.*, only the first entity of its kind in the code emits audio and TypeError: Argument of AudioContext.decodeAudioData can't be a detached buffer - three.js:37939:18 is thrown.
As I expected, poolSize has no effect, I’m assuming due to the fact that this is across multiple instances of the sound component and not contained within one component.
- A-Frame Version:
0.8.0and0.8.1 - Platform / Device: Chrome, Firefox, Edge on Windows 10 (all I’ve tested thus far)
- Reproducible Code Snippet or URL: https://codepen.io/dansinni/pen/yKOjem
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:22 (16 by maintainers)
Top Results From Across the Web
sound - A-Frame
The sound component defines the entity as a source of sound or audio. The sound component is positional and is thus affected by...
Read more >Part 2: Playing, Pausing, Stopping Audio - Frame VR
I'm going to add the sound component to the parent entity for the music player I made in Part 1. In the HTML...
Read more >Silhouette Classification Using Pixel and Voxel Features for ...
Abstract— We present a method for improving human segmentation results in calibrated, multi-view environments using features derived from both pixel (image) ...
Read more >Cross-Country Comparisons of Corporate Income Taxes
NBER working papers are circulated for discussion and comment purposes. ... recently, the UK has seen several companies leave for domiciles in tax...
Read more >Discontinuation List - Labels - 3M
3, 3M™ 5770FL, 2.3 mil, Matte, White, Thermal Transfer Printable Polyester, 0.8 mil, 550 High Stability Acrylic, 2 mil, Polyester Film, 5770 or...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@dsinni - fork A-Frame & edit the dist code directly to reflect the changes made in this PR
if you’re importing it as a node module, be sure to update
dist/aframe-master.js.if you want 0.8.2, i’d branch from commit
#46b1362to play it safe, as the commit log around the release looks a little messy.for what it’s worth, we’re using commit
#d5bb456(A-Frame 0.8.2 + Three.js R92) in production without any issues, but we’re only targeting the Oculus Browser with the GearVR so I can’t verify other platforms.additionally, it seems like my PR will be part of Three.js R93, but I don’t know when that will be wrapped up into A-Frame.
@dsinni - the PR can be found here. Not certain it’ll be accepted, as it might be more of a workaround rather than a fix.
We fork A-Frame to hack in some fixes specific to our project’s implementation, and have temporarily modified the
build/aframe-master.jswith those changes just to get up and running. Given that A-Frame uses a fork of three, this seemed like the best (temporary) approach for us as we don’t want to fork of that too.@ngokevin - is there any information/advice/direction you can offer here?