Enable AudioIPC builds on Windows aarch64
Categories
(Core :: Audio/Video: cubeb, enhancement, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox113 | --- | verified |
People
(Reporter: kinetik, Assigned: kinetik)
References
Details
Attachments
(1 file)
Windows AudioIPC started landed in bug 1512445. Unfortunately, it is build time disabled on Windows aarch64 due to legacy winapi 0.2.x dependencies. See bug 1512445 comment 8 for more.
Updated•5 years ago
|
Comment 1•3 years ago
|
||
FWIW: the 2 projects linked in the above comment use winapi 0.3 since a while.
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 2•1 year ago
|
||
Depends on D134931
Pushed by mgregan@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6ea529a8a1ab Enable AudioIPC on Windows arm64. r=cubeb-reviewers,padenot
Comment 4•1 year ago
|
||
bugherder |
Comment 5•1 year ago
|
||
Does this need manual QA? Note that we're not running any Windows ARM64 tests in CI anymore.
Assignee | ||
Comment 6•1 year ago
|
||
I've done some manual testing locally on a Surface Pro X (SQ1), with everything (audio related) working as expected. More testing would be appreciated if resources permit, though.
Updated•1 year ago
|
Comment 7•1 year ago
|
||
Do we need to test something specific or some sanity/exploratory testing around basic audio functionality on top sites, maybe including some WebRTC coverage is enough? Thank you!
Assignee | ||
Comment 8•1 year ago
|
||
Just sanity/basic audio testing would be enough I think, thanks!
Comment 9•1 year ago
|
||
I've run an audio sanity check on RC 113 with Windows 10 ARM. I've used several popular websites providing media content (youtube, facebook, netflix, twich, spotify, tunein, hypem), a WebRTC call (jitsi meet) and several different audio format (MP3, OGG, FLAC, ACC). I didn't encountered any issue, therefore, I will mark this work as verified fixed.
Description
•