[Webkit-unassigned] [Bug 250279] New: Use correct HRTF elevation response for negative elevations

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=250279

            Bug ID: 250279
           Summary: Use correct HRTF elevation response for negative
                    elevations
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Web Audio
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: ahmad.saleem792 at gmail.com
                CC: cdumez at apple.com

Hi Team,

While going through Blink's commit, I came across following commit, where it seems to be an issue to due to handling of negative elevation.

Test Case (from Chrome Bug) - http://vm-1015-user.virt.ch.bbc.co.uk/binaural/panner_test/

STEPS TO REPRODUCE (Copied from Chrome Bug - https://bugs.chromium.org/p/chromium/issues/detail?id=412442):

1. Go to - http://vm-1015-user.virt.ch.bbc.co.uk/binaural/panner_test/
2. Click "Play" and move the elevation slider.
3. Listen over headphones.

What is the expected behavior?
Elevation > 0, moves the sound higher, above your head. Elevation < 0 moves the sound lower, below your head.

What went wrong?
When elevation goes below -29, the sound jumps to the top.

_________________

Blink Commit: https://src.chromium.org/viewvc/blink?view=revision&revision=181986

WebKit Source - https://github.com/WebKit/WebKit/blob/1105db4ef4beff2c87fbe05387c58123ee89ff97/Source/WebCore/platform/audio/HRTFElevation.cpp#L151

_______

I am not sure whether we have anything special that we don't get impacted by this but since we have same code, just wanted to raise this and ask someone with headphones to see if this is reproducible. I have USB-A headphones from work (don't work on MacBook Pro). :-(


Just wanted to raise to get input.

Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230107/78084f46/attachment-0001.htm>