Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sound component not loading audio in Firefox #3868

Open
dsinni opened this issue Nov 15, 2018 · 3 comments
Open

sound component not loading audio in Firefox #3868

dsinni opened this issue Nov 15, 2018 · 3 comments

Comments

@dsinni
Copy link
Contributor

dsinni commented Nov 15, 2018

Description:

Using the current A-Frame master, when trying to auto play audio with the sound component using autoplay: true, either the loading screen times out and the audio doesn't play, or the loading screen skips and the audio doesn't play.

This seems to be affecting Firefox on pretty much every platform I've tested. In Chrome, everything loads almost immediately and the audio plays as expected.

In Firefox, console says:

components:sound:warn Sound not loaded yet. It will be played once it finished loading 

The audio never plays.

If I try document.querySelector('audio'), play(), it will play, but it appears the sound component gets hung up.

document.querySelector('[sound]').components.sound.playSound() throws the same console message.

I processed the audio with ffmpeg in the second demo, to make sure it wasn't an encoding issue, but no dice.

  • A-Frame Version: master 826e983d989312fe7cd75b9cc92e58b7a5cc195f
  • Platform / Device: Firefox on Windows/Mac/Android...
  • Reproducible Code Snippet or URL:

https://bunker-bake.glitch.me
https://spiral-lipstick.glitch.me

@dsinni
Copy link
Contributor Author

dsinni commented Nov 20, 2018

I'm finding that using <a-asset-item response-type="arraybuffer" ... > works, but using <audio> doesn't.

Any ideas why that would be?

@PlumCantaloupe
Copy link

PlumCantaloupe commented Dec 17, 2020

I still have this issue on the most recent versions of Aframe (1.1). Has anyone come up with a "best-practise" of how to workaround this issue?

@lijualivenow
Copy link

I still have this issue on the most recent versions of Aframe (1.1). Has anyone come up with a "best-practise" of how to workaround this issue?

Still in version 1.2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants