[alsa-devel] Documentation Request

[Carl Canuck]

Hi Eliot,

Thanks for your response, but I think that is a very poor solution.  Jack
is problematic on many configurations, and I have no intention of modifying
this app to rely on Jack Transport or any Jack session manager in order to
play nicely with the rest of the Jack ecosystem, nor do Jack's features add
value to my application.  Therefore, it makes little sense to use Jack or
accept it's additional bugs and CPU overhead, no more than it makes sense
to use Pulseaudio for high performance, low latency audio applications,
adding another layer over ALSA can only result in more bugs and more
overhead, not less.

Surely an experienced core ALSA developer could create such a demo of how
the API is meant to be used in less than an hour.  This would save numerous
ALSA-curious developers like myself countless hours of reverse engineering
other applications and scouring alsa-devel mailing list posts attempting to
understand how ALSA is meant to be used.  I understand that writing
documentation isn't fun, but after my first 2 weeks of trying I have to
believe that countless developers have probably given up on ALSA (and Linux
by extension) due to the cryptic documentation and lack of simplest-case
example code.  With the example I proposed, I could've been productive from
day one.

Thanks,
Carl


On Tue, Sep 3, 2013 at 8:58 PM, Eliot Blennerhassett <
eliot at blennerhassett.gen.nz> wrote:

> On 04/09/13 12:32, Carl Canuck wrote:
> > especially for one of
> > the most important use-cases of all:  the full on digital audio
> workstation.
>
> The stock answer for this use case is
> "Don't use ALSA directly; use JACK" http://jackaudio.org/
>
>
>
>