All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: Re: alsa-lib has anyone ever looked at taking it cross platform?
Date: Fri, 25 Jul 2008 10:28:46 +0100	[thread overview]
Message-ID: <g6c6ce$ssl$2@ger.gmane.org> (raw)
In-Reply-To: <e7d8f83e0807250049h60fabd30x295d739ee6f21e98@mail.gmail.com>

Peter Dolding wrote:
> This would kinda make logical sence.
> 
> Alsa-lib plugin system in theory should be able to take any kind sound
> output under it.   Simplify development of all applications on top of
> it.  If alsa was cross platform why would you use something else as a
> middle body wrapper when you port.
> 
> Windows and Mac support could be done as plugins.
> 
> Or is there something that is in the alsa-lib that is a problem?
> 
> Its all about reducing distance between application and hardware and
> reduce amount of coding.

I'd rather see pulseaudio go fully cross platform. It's got some older 
windows ports but if pulse were to get a push in the right direction for 
windows and OSX then this lets alsa get on with the job of interfacing 
with the audio on linux (that's what the L stands for after all), and 
let higher level applications work with a more appropriate system with 
more appropriate interfaces for practical use.

Just a thought...

Col

  reply	other threads:[~2008-07-25  9:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25  7:49 alsa-lib has anyone ever looked at taking it cross platform? Peter Dolding
2008-07-25  9:28 ` Colin Guthrie [this message]
2008-07-25 14:16 ` Timur Tabi
  -- strict thread matches above, loose matches on Subject: below --
2008-07-25 10:51 Peter Dolding
2008-07-25 12:49 ` Colin Guthrie
2008-07-25 12:57   ` Rene Herman
2008-07-30 19:07 ` Aaron J. Grier
2008-07-26  2:56 Peter Dolding
2008-07-26  4:43 ` Sean McNamara

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='g6c6ce$ssl$2@ger.gmane.org' \
    --to=gmane@colin.guthr.ie \
    --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 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.