From: "Patrick Shirkey" <pshirkey@boosthardware.com>
To: alsa-devel@alsa-project.org
Subject: Re: Application development
Date: Tue, 29 Apr 2014 19:07:51 +1000 (EST) [thread overview]
Message-ID: <59564.86.107.254.57.1398762471.squirrel@boosthardware.com> (raw)
In-Reply-To: <535F5775.7080504@amsat.org>
On Tue, April 29, 2014 5:40 pm, Rob Janssen wrote:
> A week and a half ago I asked some questions about application development
> using alsa ("Control the exact moment of output"), but it appears this
> list is more
> about development of alsa itself.
>
> Is there another place where discussions about using alsa are more
> appropriate,
> and/or a place where documentation can be found that goes a bit further
> than a
> plain list of function names and parameter lists?
> I.e. a more general description about how one structures an application
> that uses
> alsa, and how timing fits in that picture.
>
Hi Rob,
This list is more focused on driver development. At the moment the
official documentation is sparse. There is a lot of example code available
in open source applications.
What exactly are you looking to achieve?
FYI, most professional audio application developers tend to work with JACK
rather than ALSA directly. There is also Pulse-Audio and gstreamer.
You might find that you have more luck discussing application development
on the LAD list.
There is also the JACK-devel list.
--
Patrick Shirkey
Boost Hardware Ltd
prev parent reply other threads:[~2014-04-29 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 7:40 Application development Rob Janssen
2014-04-29 9:07 ` Patrick Shirkey [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=59564.86.107.254.57.1398762471.squirrel@boosthardware.com \
--to=pshirkey@boosthardware.com \
--cc=alsa-devel@alsa-project.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