From: mtboehlke <mtboehlke@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: libopenal: update to 1.21.1 and import fixes to sndio backend
Date: Fri, 29 Apr 2022 17:45:08 +0200 [thread overview]
Message-ID: <20220429154508.MEN8SOC4krPhtWv7FiGu7rqMJFPzjzjTFfaEllvlnmY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35594@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1614 bytes --]
There's a closed pull request on the void-packages repository
libopenal: update to 1.21.1 and import fixes to sndio backend
https://github.com/void-linux/void-packages/pull/35594
Description:
Patches to fix the issue reported at https://github.com/kcat/openal-soft/issues/591
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
I encountered the problem described in the linked issue when playing around with wildmidi. I was hoping to have wildmidi use sndio by compiling without direct alsa support, and then rely on libopenal to use sndio. When libopenal was configured for sndio, playback stopped immediately with the error message: `[ALSOFT] (EE) Error stopping device`. Playback worked as expected with sndio after including these upstream patches.
prev parent reply other threads:[~2022-04-29 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 20:22 [PR PATCH] " mtboehlke
2022-03-16 19:04 ` [PR PATCH] [Updated] " mtboehlke
2022-04-19 16:15 ` mtboehlke
2022-04-29 15:45 ` mtboehlke [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:
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=20220429154508.MEN8SOC4krPhtWv7FiGu7rqMJFPzjzjTFfaEllvlnmY@z \
--to=mtboehlke@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).