Introduce Audio PanningQuality preference #5454
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #5278
WebAudio
andThree.js
usesHRTF
panning model for Panner audios by default. ButHRTF
is said to be better quality but much more costly than another pannind modelequalpower
. Some users, especially low-end or mobile device users, may think they want to setequalpower
panning model for better performance by sacrificing the audio panning quality.This PR introduces Audio PanningQuality preference. The high quality corresponds to
HRTF
while the low quality corresponds toequalpower
.Additional Context
HRTF
so far. We may think we want to setequalpower
(on mobile devices) by default. But I want to think of the appropriate default value after testing across the devices.