Audio Issue - with Assets Manager?

[JackFalcon]

Hello, 

Possible Bug in Assets Manager Audio.

QUESTIONS: Is this a bug, is it related to M64 and M65, does anyone have any insight on M64 and M65?

STEPS:   1) Run the Audio test (https://www.babylonjs-playground.com/#PCY1J#8) from these docs (https://doc.babylonjs.com/how_to/playing_sounds_and_music) and no audio.

Reproduced in Dev environment. Along with interesting deprecation messages in the console. below... (maybe not related?):

 

[Deprecation] GainNode.gain.value setter smoothing is deprecated and will be removed in M64, around January 2018. Please use setTargetAtTime() instead if smoothing is needed. See

[Deprecation] AudioParam value setter will become equivalent to AudioParam.setValueAtTime() in M65, around March 2018  See https://webaudio.github.io/web-audio-api/#dom-audioparam-value for more details.

Interesting.

 

NOTE: Possible bug behavior  seems limited to AssetsManager, as I can still use direct load sound and it works.

QUESTIONS: Is this a bug, is it related to M64 and M65, does anyone have any insight on M64 and M65?

ping @davrous ... : )

Thanks,    

 

[davrous]

Hello,

Well, this sample doesn't work anymore because the files aren't on the host anymore. Probably during one of our migration process, we forgot to move those files.

The basic samples from the PG still works: https://playground.babylonjs.com/?22 as well as demos using Web Audio on babylonjs.com.

We decided to ignore those Chrome warnings for now. Google has decided to move to this path alone, as usual I'd say unfortunately. We're not using the smoothing feature of Chrome so there is no impact for our users, this warning message is then totally useless in our case. We decided to just wait for those warnings to disappear on a next build of Chrome rather than modifying the complete audio engine just for Chrome. 

Thanks!

David

[JackFalcon]

Awesome! Thank you...