libretro / libretro/RetroArch

WASAPI with multi channel audio causes sync issue

Open
#16,938 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

First and foremost consider this:

  • Only RetroArch bugs should be filed here. Not core bugs or game bugs
  • This is not a forum or a help section, this is strictly developer oriented

Description

WASAPI with multi-channel audio causes sync issue (about 75% underrun). If sound device is set to output 2 channels, the problem will disappear, everything is fine.
RetroArch Screenshot 2024 08 29 - 00 46 29 04

Expected behavior

WASAPI with multi channel audio with 0% underrun.

Actual behavior

WASAPI with multi channel audio with 75% underrun.

Steps to reproduce the bug
  1. set audio device to output multi channels (ie. 5.1)
  2. run any game with any core.
  3. reproduce the bug.
Bisect Results

RetroArch 1.16 and newer

Version/Commit
  • RetroArch: 1.19.1 Stable
  • OS: Windows 11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with RetroArch's WASAPI audio path on Windows and reproduce the issue using a 5.1 output device with RetroArch 1.19.1 or newer. Compare behavior with two-channel output and test across a game and core; done means multi-channel output no longer produces the reported 75% underrun while two-channel output remains functional.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
audio-video-rtc
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.