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
It seems to me that in commit #680ee08b87f53702e92f7b338bd785d54b9f9ce2, directional audio processing was removed (with the stated intention of modeling all sound as point source audio). However, the HRTF processing involving the direction of the listener was also discarded; this means that updating the listener's view (via update_view, for instance) does absolutely nothing.
Are there any plans to reimplement this property into the HRTF model? It's quite a critical component for simulating 3d audio. I suppose the application can manage the positions of the audio objects relative to the listener, but then it would at least make sense to remove the misleading listener direction properties and methods.
The text was updated successfully, but these errors were encountered:
somehow I missed your issue completely. It was removed as it never worked properly. I'd love to re-add it, if we figure out how to define geometry of the scene.
It seems to me that in commit #680ee08b87f53702e92f7b338bd785d54b9f9ce2, directional audio processing was removed (with the stated intention of modeling all sound as point source audio). However, the HRTF processing involving the direction of the listener was also discarded; this means that updating the listener's view (via update_view, for instance) does absolutely nothing.
Are there any plans to reimplement this property into the HRTF model? It's quite a critical component for simulating 3d audio. I suppose the application can manage the positions of the audio objects relative to the listener, but then it would at least make sense to remove the misleading listener direction properties and methods.
The text was updated successfully, but these errors were encountered: