All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: "Adam Tlałka" <atlka@pg.gda.pl>
Cc: ak@suse.de, linux-kernel@vger.kernel.org,
	alsa-devel@alsa-project.org, perex@suse.cz,
	alan@lxorguk.ukuu.org.uk
Subject: Re: [Alsa-devel] OSS driver removal, 2nd round (v2)
Date: Mon, 10 Jul 2006 19:51:44 -0400	[thread overview]
Message-ID: <1152575505.19047.52.camel@mindpipe> (raw)
In-Reply-To: <44B2E4FF.9000502@pg.gda.pl>

On Tue, 2006-07-11 at 01:38 +0200, Adam Tlałka wrote:
> Użytkownik Lee Revell napisał:
> > On Mon, 2006-07-10 at 13:28 +0200, Adam Tlałka wrote:
> >> >From my point of view ALSA has many advantages if you want to dig in
> >> the card driver buffers/period etc. settings but lacks ease of use and
> >> some of simple in theory functionality is a pain - device enumeration
> >> or switching output mode/device without restarting apps or rewritting
> >> them so they have special function for that purpose.
> >>
> > 
> > Does any available sound driver interface allow switching output devices
> > with no help from the app and without having to restart playback?  OSS
> > does not, and every Windows app I've used has a configuration option to
> > set the sound device, and you must stop and start playback for it to
> > take effect.
> 
> Sorry but is a Windows solution the best on the whole world?
> Is there any problem to imagine an abstract sound device which virtually 
> always works but uses real device chosen by user, network redirection or 
>   emulating work and we have some control panel/app which can control 
> connections/plugins/redirections etc. (also this can be done by some 
> kind of daemon responding to hw change events)?
> Do we really need to program every sound app to have device setting code?
> 

The problem is you trade ease of development for performance, penalizing
the users to save developer time.  Your proposals would require every
app to go through a software buffering layer.

Of course, you're free to develop a system like this.

> >> esd, arts, jackd, polypd and other prove that ALSA is not enough
> >> and its functionality is far from perfect.
> >>
> > 
> > esd and artsd are no longer needed since ALSA began to enable software
> > mixing by default in release 1.0.9.
>  >
> 
> So why they are still exist in so many Linux distributions?
> 

Backwards compatibility, bugs still being worked out, waiting for
upstream to catch up, etc.  Same reason that distros never have the very
latest version of every app.

> > As for jackd and other apps that
> > provide additional functionality - no one ever claimed ALSA would handle
> > every audio related function imaginable.  It's just a low level HAL.
> 
> Format changing, resampling, mixing and supporting additional plugins
> does not seems to be just low level HAL for hw device. It creates some 
> kind of virtual functionality which means more then this provided by 
> hardware device itself.

OK, but my point is that it does not make sense to put every imaginable
audio feature in ALSA.

Lee


  parent reply	other threads:[~2006-07-10 23:51 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07 23:17 OSS driver removal, 2nd round (v2) Adrian Bunk
2006-07-07 23:50 ` Andi Kleen
2006-07-08  0:00   ` Adrian Bunk
2006-07-08  0:00   ` Adrian Bunk
2006-07-08  1:30   ` Jeff Garzik
2006-07-08  1:30   ` Jeff Garzik
2006-07-09 15:18   ` Lee Revell
2006-07-09 15:18   ` [Alsa-devel] " Lee Revell
2006-07-09 16:08     ` Olivier Galibert
2006-07-09 16:08     ` Olivier Galibert
2006-07-10 11:28     ` Adam Tlałka
2006-07-10 11:28       ` [Alsa-devel] " Adam Tlałka
2006-07-10 13:18       ` James Courtier-Dutton
2006-07-10 13:18         ` [Alsa-devel] " James Courtier-Dutton
2006-07-10 13:57       ` Adrian Bunk
2006-07-10 13:57       ` [Alsa-devel] " Adrian Bunk
2006-07-10 22:48       ` Lee Revell
2006-07-10 22:48         ` [Alsa-devel] " Lee Revell
2006-07-10 23:38         ` Adam Tlałka
2006-07-10 23:38           ` [Alsa-devel] " Adam Tlałka
2006-07-10 23:51           ` Cloning sound output [was Re: [Alsa-devel] OSS driver removal, 2nd round (v2)] J.A. Magallón
2006-07-10 23:51           ` OSS driver removal, 2nd round (v2) Lee Revell
2006-07-10 23:51           ` Lee Revell [this message]
2006-07-10 23:59           ` Olivier Galibert
2006-07-10 23:59             ` [Alsa-devel] " Olivier Galibert
2006-07-11  0:39             ` Lee Revell
2006-07-11  0:39               ` [Alsa-devel] " Lee Revell
2006-07-11  6:59               ` Adam Tlałka
2006-07-11  6:59                 ` [Alsa-devel] " Adam Tlałka
2006-07-11  7:02                 ` Andi Kleen
2006-07-11  7:02                   ` [Alsa-devel] " Andi Kleen
2006-07-11  7:58                 ` Jaroslav Kysela
2006-07-11  7:58                   ` [Alsa-devel] " Jaroslav Kysela
2006-07-11  9:08                   ` Adam Tlałka
2006-07-11  9:08                     ` [Alsa-devel] " Adam Tlałka
2006-07-11  9:52                     ` Jaroslav Kysela
2006-07-11  9:52                       ` [Alsa-devel] " Jaroslav Kysela
2006-07-11 11:18                       ` Diego Calleja
2006-07-11 11:18                         ` [Alsa-devel] " Diego Calleja
2006-07-11 11:29                       ` Adam Tlałka
2006-07-11 11:29                         ` [Alsa-devel] " Adam Tlałka
2006-07-11 10:28                     ` Adrian Bunk
2006-07-11 10:28                       ` [Alsa-devel] " Adrian Bunk
2006-07-11  2:09           ` Valdis.Kletnieks
2006-07-11  2:09             ` [Alsa-devel] " Valdis.Kletnieks
2006-07-11  6:15             ` Adam Tlałka
2006-07-11  6:15               ` [Alsa-devel] " Adam Tlałka
2006-07-11 14:30               ` Valdis.Kletnieks
2006-07-11 14:30                 ` [Alsa-devel] " Valdis.Kletnieks
2006-07-11 16:57                 ` Lee Revell
2006-07-11 16:57                   ` [Alsa-devel] " Lee Revell
2006-07-11 22:31                   ` Adam Tlałka
2006-07-11 22:31                   ` [Alsa-devel] " Adam Tlałka
2006-07-12  0:58                     ` Lee Revell
2006-07-07 23:50 ` Andi Kleen

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=1152575505.19047.52.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=ak@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=atlka@pg.gda.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    /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.