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

Reverb is always mono on any browser #23

Open
ogomez92 opened this issue Dec 25, 2018 · 4 comments
Open

Reverb is always mono on any browser #23

ogomez92 opened this issue Dec 25, 2018 · 4 comments

Comments

@ogomez92
Copy link

HEllo!
Reverb is mono, even with the audio demos that are provided in the SDK like room models.
IT's mono on Electron, Safari, Firefox, everywhere.

Any chance to get this fixed?

@drewbitllama
Copy link
Contributor

drewbitllama commented Feb 6, 2019 via email

@ogomez92
Copy link
Author

ogomez92 commented Feb 6, 2019 via email

@drewbitllama
Copy link
Contributor

drewbitllama commented Feb 6, 2019 via email

@Ghorthalon
Copy link

This is a very uneducated guess, but wouldn't it be enough to simply create stereo noise for the reverb tail white noise in the convolver to at least give the impression? It might not be very accurate but already sound twice as real, if not more, until a better solution can be found that computes fast enough? Maybe it could be ported from the Resonance C library and compiled to WebAssembly. Right now I always set my room materials to transparent because the reverb actually makes it more confusing to tell where something comes from, because it's limited to a mono center channel and that throws off the perception. Adding a custom convolver with a real room impulse does, sadly, sound better at this point.

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