From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] [drawterm] Pulse audio output and input
Date: Tue, 10 Dec 2019 02:16:24 +0100 [thread overview]
Message-ID: <B849DDAF8ECB981D015BADB790F4AE1C@felloff.net> (raw)
In-Reply-To: CA+gzr0L6eTqcAa4i=hx3drL_vYqr5-nmHQKAsdpMmVEfaXRcDQ@mail.gmail.com
i'm not an expert on current linux audio interfaces.
can you explain why this is a good idea to link against pa?
i dont like having a separate Make.pulse for it as this
will just end up with combinatorial explosion. maybe we
should have it changable at the make command line or
use it as a default as linux has no support for /dev/dsp
anymore?
is oserror() the right thing for error handling? it appears
to return its own error code but we'r not using it?
also, how is buffering handled? how much will be buffered
by this interface when you write to it? this is important
as games use /dev/audio for synchronization.
--
cinap
next reply other threads:[~2019-12-10 1:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 1:16 cinap_lenrek [this message]
2019-12-10 7:11 ` Nick Owens
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=B849DDAF8ECB981D015BADB790F4AE1C@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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).