Optimize loading of HRTF database |
||||
Issue descriptionWhile working on issue 629858 , I did some quick experiments. It seems as if the HRTF database is not ready for upto 215 rendering quanta (about 630 ms at a sample rate of 44.1kHz). This seems really slow. We should measure this more carefully and look into seeing if this can be optimized. Now that we delay loading of the data base until the panner (or the panning model is set to HRTF), this long delay has an impact on the initial audio quality.
,
Jul 24 2017
We still want to do this. Changing status back to Available.
,
Jul 25
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 8
Still want to do this. |
||||
►
Sign in to add a comment |
||||
Comment 1 by sheriffbot@chromium.org
, Jul 24 2017Status: Untriaged (was: Available)