From: "Keith A. Milner" <maillist@superlative.org>
To: alsa-devel@alsa-project.org
Cc: Carl Canuck <carl.canuck.official@gmail.com>
Subject: Re: Documentation Request
Date: Thu, 05 Sep 2013 13:13:10 +0100 [thread overview]
Message-ID: <2721149.ZQhlgxxYbu@kamdesktop> (raw)
In-Reply-To: <CAPOzVs45RCTiY4ykUmugVMViu6wj1KT_W8vcrpFHSVeQLAfy4A@mail.gmail.com>
On Wednesday 04 Sep 2013 09:20:23 Carl Canuck wrote:
> > Thanks for your response, but I think that is a very poor solution.
> > [ignorant blah]
>
> Ignorant? You do realize that Jack has captured the hearts and minds of
> exactly zero world renowned audio professionals, despite being
> "professional grade" according to it's developers?
>
You do realise that native ALSA music production apps have captured an even
smaller number of those hearts and minds...
And of the many people who do use Linux for music production (professional or
otherwise), native ALSA apps have captured very close to zero percent of their
hearts and minds.
Amongst the Linux audio production market Jack is, far and away, the most
popular approach both amongst app developers and users. It is the de-facto
standard. Part of this is because Jack enables your app to work well with
others, whereas ALSA on it's own does not.
If you want people in this market to use your app, then you shouldn't even be
considering not using Jack.
Unless, of course, you are trying to consign your app to obscurity to give
you another reason to denigrate Linux and it's users.
> Do you think that could
> possibly be a problem with Jack, or did everybody just not give it enough
> of a chance?
Have you considered that it could be other factors, such as Linux only having
a few percent of the desktop market (where audio production sits) or that none
of the "brand name" software vendors produce software for it, or that people
in that industry are not generally very computer-literate and may not have
even heard of Linux, yet alone know you could produce music on it or are
willing to take the risk on using a new, unknown platform.
All of the above are good reasons. I have worked with ALSA and Jack for
several years and you are the only person in this time I have heard suggest
the root cause for lack of Linux penetration in the audio production market is
due to Jack. It's a crazy suggestion and, unless you have some firm evidence
backing this up, ignorance really is the only explanation for such a
suggestion.
In looking to write a native ALSA music production app you were on completely
the wrong path. This community has, generously, offered you advice to steer you
onto the correct path. I recommend you swallow your pride, and follow this
sage advice.
Cheers,
Keith
prev parent reply other threads:[~2013-09-05 12:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 0:32 Documentation Request Carl Canuck
2013-09-04 0:58 ` Eliot Blennerhassett
2013-09-04 1:45 ` Carl Canuck
[not found] ` <CACckToUBiwJg1TUMuw3eFws_rvf9qc3ZPfSzy7MRCB8b0JEnRg@mail.gmail.com>
[not found] ` <CAPOzVs4+Sd=UXZ3gMGSNwMk1EW_yKPK+7dTo_vuWD_acyrWw6g@mail.gmail.com>
2013-09-04 3:15 ` Carl Canuck
2013-09-04 6:04 ` Felix Homann
2013-09-04 7:58 ` Clemens Ladisch
2013-09-04 8:18 ` Florian Faber
2013-09-04 13:20 ` Carl Canuck
2013-09-04 14:04 ` Felix Homann
2013-09-04 14:05 ` Clemens Ladisch
2013-09-04 14:30 ` Carl Canuck
2013-09-04 17:21 ` Joël Krähemann
2013-09-05 12:13 ` Keith A. Milner [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=2721149.ZQhlgxxYbu@kamdesktop \
--to=maillist@superlative.org \
--cc=alsa-devel@alsa-project.org \
--cc=carl.canuck.official@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.