Github messages for voidlinux
 help / color / mirror / Atom feed
From: pbui <pbui@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qt5-webengine: audio playback does not always use PulseAudio, instead capturing raw ALSA devices
Date: Sun, 20 Dec 2020 22:42:39 +0100	[thread overview]
Message-ID: <20201220214239.jWHTIk64qL8bv8B6FcPgA_5eu3mI1uxXjif0B3lUHwo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25906@inbox.vuxu.org>

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

New comment by pbui on void-packages repository

https://github.com/void-linux/void-packages/issues/25906#issuecomment-748674774

Comment:
Using the qt5.15.2 that I built from #26574, qutebrowser is able to play audio normally via pulseaudio (it does not go to ALSA).  I also tested playing audio with mpv, mpd, and qutebrowser at the same time and it behaved normally.  Therefore, this problem looks resolved with that update (especially since it appears that sndio is now OFF by default).

Just a few notes: 1. I had to rebase and remove `srcpkgs/qt5-webengine/patches/0200-nullptr-rtcpeerconnectionhandler.patch`, 2. the build for qt5-webengine warned about `use_sndio=true` not being recognized (by default the build option is OFF, but the configuration arguments still specify it).

  parent reply	other threads:[~2020-12-20 21:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 23:38 [ISSUE] " klardotsh
2020-10-27  9:18 ` minikN
2020-10-28  6:31 ` travankor
2020-10-28 18:20 ` Johnnynator
2020-10-28 18:21 ` Johnnynator
2020-11-21 20:55 ` Johnnynator
2020-12-07  4:53 ` travankor
2020-12-20 13:01 ` travankor
2020-12-20 13:08 ` travankor
2020-12-20 21:42 ` pbui [this message]
2021-01-20 20:52 ` ericonr
2021-01-20 20:57 ` pbui
2021-01-20 20:57 ` ericonr
2021-01-20 20:57 ` [ISSUE] [CLOSED] " ericonr

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20201220214239.jWHTIk64qL8bv8B6FcPgA_5eu3mI1uxXjif0B3lUHwo@z \
    --to=pbui@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).