On Tue, 18 May 2004, Manuel Jander wrote:
> Yes, i think that the hardware constraint scheme of ALSA is very
> powerful, but the problem is that it fails. It would be great if it
> could be mopified to be failproof, that is, allow the application to
> work somehow regardless of what restrictions m
Hi,
On Tue, 2004-05-18 at 17:00 +0200, Takashi Iwai wrote:
> At Tue, 18 May 2004 09:30:54 -0400,
> Manuel Jander wrote:
> >
> > Hi,
> >
> > On Tue, 2004-05-18 at 15:46 +0200, [EMAIL PROTECTED] wrote:
> > > On Thu, 13 May 2004, Adam Tla/lka wrote:
> > >
> > > > On Wed, May 12, 2004 at 05:40:55PM
At Tue, 18 May 2004 09:30:54 -0400,
Manuel Jander wrote:
>
> Hi,
>
> On Tue, 2004-05-18 at 15:46 +0200, [EMAIL PROTECTED] wrote:
> > On Thu, 13 May 2004, Adam Tla/lka wrote:
> >
> > > On Wed, May 12, 2004 at 05:40:55PM +0200, Clemens Ladisch wrote:
> > >
> > > ALSA is complicated and we have no
Manuel Jander wrote:
As the main author of the Aureal Vortex driver, its very stupid having
to handle arbitrary period sizes, introducing a lot of overhead and
complexity in the driver, while the hardware just is not designed to
handle period sizes that are not powers of two, due to page boundary
o
Hi,
On Tue, 2004-05-18 at 15:46 +0200, [EMAIL PROTECTED] wrote:
> On Thu, 13 May 2004, Adam Tla/lka wrote:
>
> > On Wed, May 12, 2004 at 05:40:55PM +0200, Clemens Ladisch wrote:
> >
> > ALSA is complicated and we have no good manual describing proper use
> > of its api. You can easily prove this
On Thu, 13 May 2004, Adam Tla/lka wrote:
> On Wed, May 12, 2004 at 05:40:55PM +0200, Clemens Ladisch wrote:
> > Ronald S. Bultje wrote:
> > > for a given alsa device ("default", "dmix", "plughw:N", "hw:N,M",
> > > "dspN", etc.), how do I automatically obtain the right device to use as
> > > a audi
Ronald S. Bultje wrote:
> is it possible for me to get the cardnumber (and thereby the hw:N
> entry) for a given non-hw device (e.g. dspN, hw:N,M, dmix, ...)?
Try something like this:
/* Get the slave pcm of a pcm node. Caller must free the result. */
static snd_config_t *get_pcm_slave_pcm(snd_c
On Wed, 2004-05-12 at 17:40, Clemens Ladisch wrote:
> Ronald S. Bultje wrote:
> > for a given alsa device ("default", "dmix", "plughw:N", "hw:N,M",
> > "dspN", etc.), how do I automatically obtain the right device to use as
> > a audio mixer with that device?
>
> Depends on your definition of "rig
On Thu, May 13, 2004 at 06:28:17PM +0200, Giuliano Pochini wrote:
> Good question. The current approach is based on the control
> names but sometimes they're not enough. What do you suggest ?
I am testing changed aoss lib which uses dmix plugin
to play simultaniously many stereo sound sources.
Now
On 13-May-2004 Adam Tla/lka wrote:
>> What do you want to do with the mixer?
> Hmm - typically people just want to control PCM volume.
> When using OSS you can just do mixer ioctl's on the opened PCM fd.
> Simple and clear.
No, it's not simple, unless the driver makes it simple
removing some cap
>When using OSS you can just do mixer ioctl's on the opened PCM fd.
When using OSS, you can't model a lot of the functionality present in
contemporary audio interface hardware mixers.
So there's a choice: a limited, simple API that fails to support card
features, or a complex API that over time g
On Wed, May 12, 2004 at 05:40:55PM +0200, Clemens Ladisch wrote:
> Ronald S. Bultje wrote:
> > for a given alsa device ("default", "dmix", "plughw:N", "hw:N,M",
> > "dspN", etc.), how do I automatically obtain the right device to use as
> > a audio mixer with that device?
>
> Depends on your defin
Ronald S. Bultje wrote:
> for a given alsa device ("default", "dmix", "plughw:N", "hw:N,M",
> "dspN", etc.), how do I automatically obtain the right device to use as
> a audio mixer with that device?
Depends on your definition of "right device". In the general case
this isn't possible because man
13 matches
Mail list logo
