You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the recent Chrome 69 update, the buffer property on a ConvolverNode can't be set twice. This is used in LateReflections.setDurations(), which is used by Room.setProperties(), which is used by ResonanceAudio.setRoomProperties().
The error (accompanied by the above stacktrace):
Uncaught (in promise) DOMException: Failed to set the 'buffer' property on 'ConvolverNode': Cannot set buffer to non-null after it has been already been set to a non-null buffer
The development team has several demos listed on the 'getting started' page, which link to the demo page found here. Of those demos, the two that use ResonanceAudio.setRoomProperties() give the mentioned error. The 'Hello World' demo shows the error right after clicking 'Play', while the 'Room Models' demo shows it after playing one of the sounds and then changing the room dimensions or the wall materials (both resulting in a call to ResonanceAudio.setRoomProperties()).
The text was updated successfully, but these errors were encountered:
Oh nvm, I see it was already reported here. Still, I'd recommend giving this some priority to prevent a Firefox requirement for a fair amount of VR applications.
Since the recent Chrome 69 update, the
buffer
property on aConvolverNode
can't be set twice. This is used inLateReflections.setDurations()
, which is used byRoom.setProperties()
, which is used byResonanceAudio.setRoomProperties()
.The error (accompanied by the above stacktrace):
The development team has several demos listed on the 'getting started' page, which link to the demo page found here. Of those demos, the two that use
ResonanceAudio.setRoomProperties()
give the mentioned error. The 'Hello World' demo shows the error right after clicking 'Play', while the 'Room Models' demo shows it after playing one of the sounds and then changing the room dimensions or the wall materials (both resulting in a call toResonanceAudio.setRoomProperties()
).The text was updated successfully, but these errors were encountered: