Github messages for voidlinux
 help / color / mirror / Atom feed
From: Johnnynator <>
Subject: Re: [ISSUE] [CLOSED] Godot is missing pulseaudio support, cannot play audio smoothly on PipeWire
Date: Sun, 13 Nov 2022 16:54:29 +0100	[thread overview]
Message-ID: <20221113155429.YKZ9ar-aaEIojQRk67umH1MFcsRyMG1nPfoabCAkjHk@z> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1614 bytes --]

Closed issue by nyanpasu64 on void-packages repository

### Is this a new report?


### System Info

Void 5.19.14_1 x86_64 GenuineIntel uptodate rFFFFFFFFF

### Package(s) Affected

godot-3.5_1 (technically outdated, 3.5.1 is out upstream but not in void-packages)

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Godot plays audio without stutters, mixed with audio from PipeWire apps. This is achieved by Flathub Godot on Void Linux.

### Actual behaviour

Godot is built with `pulseaudio=no` (, leaving it with only an ALSA backend.

- When it outputs to the system ALSA device, it prevents PipeWire apps from playing audio simultaneously.
- When it outputs to the alsa-pipewire package set as the default ALSA device, audio stutters continuously. (Is this a pipewire-alsa or a godot bug, and should it be reported there? PipeWire upstream discourages using ALSA's pipewire plugin, saying to prefer the PulseAudio API instead.)

Is there a technical packaging reason I'm unaware of, that `pulseaudio=no` is necessary?

### Steps to reproduce

1. Install and run PipeWire. Optionally install `alsa-pipewire` and run `sudo ln -s /usr/share/alsa/alsa.conf.d/50-pipewire.conf /usr/share/alsa/alsa.conf.d/99-pipewire-default.conf /etc/alsa/conf.d/`
2. Run Godot and start a game that plays audio.
3. Try to play audio from another PipeWire app while audio is playing.

      parent reply	other threads:[~2022-11-13 15:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13 17:07 [ISSUE] " nyanpasu64
2022-10-13 18:39 ` paper42
2022-10-14 13:04 ` nyanpasu64
2022-10-14 13:05 ` nyanpasu64
2022-10-14 13:09 ` nyanpasu64
2022-10-14 15:05 ` classabbyamp
2022-10-14 21:09 ` paper42
2022-11-13 15:54 ` Johnnynator [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221113155429.YKZ9ar-aaEIojQRk67umH1MFcsRyMG1nPfoabCAkjHk@z \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).