From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Use sndio as first preference in PortAudio, enable PortAudio for spotifyd
Date: Sun, 26 Jul 2020 14:56:31 +0200 [thread overview]
Message-ID: <20200726125631.qXHYeN4lMiXC37gTPHixtYUNMRtYNFglz14CBfBKpAI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23838@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/pull/23838#issuecomment-663984647
Comment:
with this portaudio patch audio does not work on non sndio systems
```
PortAudio Test: output sine wave. SR = 44100, BufSize = 64
ALSA lib pcm_dsnoop.c:642:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1090:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_dmix.c:1090:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
couldn't open play stream: No such file or directory
An error occured while using the portaudio stream
Error number: -9999
Error message: Unanticipated host error
```
It seems the portaudio patches does not really test if sndio exists, only when creating a stream. Currently investigating how the fallback stuff in portaudio is supposed to work.
next prev parent reply other threads:[~2020-07-26 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 2:18 [PR PATCH] " ericonr
2020-07-26 12:56 ` Johnnynator [this message]
2020-07-26 17:57 ` ericonr
2020-07-26 21:21 ` [PR PATCH] [Updated] " ericonr
2020-07-28 9:41 ` [PR PATCH] [Merged]: " Johnnynator
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=20200726125631.qXHYeN4lMiXC37gTPHixtYUNMRtYNFglz14CBfBKpAI@z \
--to=johnnynator@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).