setRoomProperties throws an error
See original GitHub issueThe error happens in LateReflections.prototype.setDurations
.
Per the ConvolverNode spec, you can only set the buffer once. If you try to set it a second time, it throws an InvalidStateError
. Firefox ignores this, and it is only recently implemented in Chrome, which is probably why the problem didn’t show up earlier.
I believe you’ll need to create a new ConvolverNode when you want to change the buffer.
Issue Analytics
- State:
- Created 5 years ago
- Comments:11
Top Results From Across the Web
Photon Secret Key is visible in Error Log?
Type == Create is different from the value, I throw an error. After that, I save a new roomname for the next create...
Read more >createGame throw NullPointerException - smartfoxserver.com
Hi! When i try to create Game room from extension with following settings, SmartFoxServer.getInstance().getAPIManager().getGameApi().createGame ...
Read more >vrmockupmri - Assets - Plugins - PhotonLoadbalancingApi ...
<summary>No error was tracked.</summary>. 122. None,. 123. /// <summary>OnStatusChanged: The CCUs count of your Photon Server License is ...
Read more >Randomly Photon stops working and throws photon view ID ...
I am getting an error and 2 warnings that are causing, I will attach those, please let me know if you need any...
Read more >Example usage for org.jdom2 Element getChild - Java2s.com
private void MergeACE() throws FileNotFoundException, JDOMException, ... Probably just AC error, everything should be working properly.", exception); } } ...
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 FreeTop 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
Top GitHub Comments
@brianchirls is correct.
This is because of the recent change in Chrome’s Convolver node. We (AudioWG) reverted the spec decision due to the reasonable amount of breakage. Here’s the revert CL for Chrome: https://chromium-review.googlesource.com/c/chromium/src/+/1249275
The revert patch was landed at 71.0.3569.0, so perhaps @drewbitllama needs to make a temporary fix that recreates a convolver node whenever a buffer changes. When 71 hits the stable, we can remove the temporary fix.
This line: https://github.com/resonance-audio/resonance-audio-web-sdk/blob/c69e41dae836aea5b41cf4e9e51efcd96e5d0bb6/src/late-reflections.js#L212
Can be replaced with the following:
FYI I have not tested the code locally. (traveling atm)