Re: [Alsa-devel] Supported USB audio devices?

On Tue, Sep 11, 2001 at 11:54:19PM +0200, Erik Mouw wrote: > On Tue, Sep 11, 2001 at 05:02:43PM -0400, Data wrote: > > On Tue, Sep 11, 2001 at 10:33:10PM +0200, Erik Mouw wrote: > > > Oh, and speaking about high quality, Burr-Brown also has a USB audio > > > codec chip. I don't know the exact part

[Alsa-devel] (no subject)

fixed alsaconf with supported ymfpci. alsaconf-0.4.4.tar.gz

Re: [Alsa-devel] Supported USB audio devices?

On Tue, Sep 11, 2001 at 05:02:43PM -0400, Data wrote: > On Tue, Sep 11, 2001 at 10:33:10PM +0200, Erik Mouw wrote: > > Oh, and speaking about high quality, Burr-Brown also has a USB audio > > codec chip. I don't know the exact part number, but details and data > > sheets are available on their web

Re: [Alsa-devel] Supported USB audio devices?

On Tue, Sep 11, 2001 at 10:33:10PM +0200, Erik Mouw wrote: > Oh, and speaking about high quality, Burr-Brown also has a USB audio > codec chip. I don't know the exact part number, but details and data > sheets are available on their website (www.burr-brown.com). High quality? What does that have

Re: [Alsa-devel] Supported USB audio devices?

On Tue, Sep 11, 2001 at 01:11:47AM -0500, Steven Feil wrote: > In addition to these consumer devices, I also found information on an > integrated USB/CODEC chip manufactured by Philips. The most > interesting thing is that full specs are available on-line. I've been > searching for a sound "card"

[Alsa-devel] Re: [Alsa-user] snd-tea6330t.o -- unresolved symbols.

On Monday 10 September 2001 19:00, James Tappin wrote: > With the current CVS drivers, I get the following error on installation: > depmod -a > depmod: *** Unresolved symbols in /lib/modules/2.4.6/misc/snd-tea6330t.o > > I built with "./cvscompile --with-cards=ice1712,trident > --without-isapnp".

[Alsa-devel] alsa-lib fails to install.

Hello The latest CVS fails to install if directory /usr/include/alsa is not present. Cheers James -- Nothing in this world is exactly what it appears to be. ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/a

Re: [Alsa-devel] Further questions: noise on frag boundaries

On Mon, 10 Sep 2001, Paul Davis wrote: > In message <[EMAIL PROTECTED]>you write: [...] > >I get ticking and noise on the fragment boundaries. It > >gets much more noticeable with larger fragments and doesn't appear to > >depend too much on the number of fragments (or periods, as I guess is > >sa

[Alsa-devel] Why a huge asoundlib.h?

Hi, why do we have only a single huge asoundlib.h? Now we have /usr/include/alsa subdirectory, thus we can simply copy each header such as pcm.h, rawmidi.h, seq.h, etc. to there. And asoundlib.h includes all just like gtk.h. Comments? Takashi ___ A

Re: [Alsa-devel] User Space Device Driver

At Tue, 11 Sep 2001 11:39:14 -0400, Paul Davis wrote: > > >Given that, technically, I can use ALSA with a user-space device driver, am > >I right in thinking that the user-space driver must have a license that is > >GPL compatible? > > > >Or is a closed source driver allowed? > > alsalib is rele

Re: [Alsa-devel] User Space Device Driver

>Given that, technically, I can use ALSA with a user-space device driver, am >I right in thinking that the user-space driver must have a license that is >GPL compatible? > >Or is a closed source driver allowed? alsalib is released under the GPL. hence, any applications that to use it must be unde

RE: [Alsa-devel] User Space Device Driver

Given that, technically, I can use ALSA with a user-space device driver, am I right in thinking that the user-space driver must have a license that is GPL compatible? Or is a closed source driver allowed? Thanks, Phil > -Original Message- > From: Jaroslav Kysela [mailto:[EMAIL PROTECTE

RE: [Alsa-devel] Device naming in alsa09

The reason I ask for this is as follows: - On my SB Live, using "default" outputs sound on all outputs. (Front and rear). I have an application (DVD player) which I want to output only on the front speakers of every sound card, if the user only wants stereo. I do not want output on front and rear

Re: [Alsa-devel] Device naming in alsa09

On Tue, 11 Sep 2001, James Courtier-Dutton wrote: > I was wondering if device names like "default" "front" "surround40" work on > all hardware devices. The "default" works in all cases. > It would be nice if "front" at least worked on all sound cards. > This does not seem to be the case current

[Alsa-devel] Device naming in alsa09

I was wondering if device names like "default" "front" "surround40" work on all hardware devices. It would be nice if "front" at least worked on all sound cards. This does not seem to be the case currently. Is there any documentation on /usr/share/alsa/* Cheers James -- Nothing in this world is

Re: [Alsa-devel] Header files locations

Hi, > What about giving a deprecation warning with "#warning This header is > deprecated, use alsa/soundlib.h instead." when including the sys/asoundlib.h? Hmm, ok this is probably better than an error. Cheers, Alex -- For years a secret shame destroyed my peace-- I'd not read Eliot, Auden or

RE: [Alsa-devel] Header files locations

> > > I agree also that /usr/include/alsa is better place to go, except for > > > (again) compile problem. How about to put a single line header > > > '#include ' to sys/asoundlib.h to keep away from > > > thousands bugreports? > > > > Done. > > Nooo. What about adding a one liner: > #error asoun

Re: [Alsa-devel] Header files locations

Hello together, > > I agree also that /usr/include/alsa is better place to go, except for > > (again) compile problem. How about to put a single line header > > '#include ' to sys/asoundlib.h to keep away from > > thousands bugreports? > > Yeah, but no one will actually notice the change. And so

Re: [Alsa-devel] Header files locations

> > I agree also that /usr/include/alsa is better place to go, except for > > (again) compile problem. How about to put a single line header > > '#include ' to sys/asoundlib.h to keep away from > > thousands bugreports? > > Done. Nooo. What about adding a one liner: #error asoundlib.h now reside

Re: [Alsa-devel] Header files locations

> Looks like you convinced Jaroslav, judging from the latest cvs changes > :) > > I agree also that /usr/include/alsa is better place to go, except for > (again) compile problem. How about to put a single line header > '#include ' to sys/asoundlib.h to keep away from > thousands bugreports? Yeah

Re: [Alsa-devel] Header files locations

On Tue, 11 Sep 2001, Takashi Iwai wrote: > At Tue, 11 Sep 2001 10:01:36 +0200 (CEST), > Alexander Ehlert wrote: > > > > Hi, > > > > > No, /usr/include/sound/* belong only to kernel stuffs, and > > > > yeah sure, thats what I said. > > > > > sys/asoundlib.h is for API. For compiling usual apps, y

Re: [Alsa-devel] Header files locations

At Tue, 11 Sep 2001 10:01:36 +0200 (CEST), Alexander Ehlert wrote: > > Hi, > > > No, /usr/include/sound/* belong only to kernel stuffs, and > > yeah sure, thats what I said. > > > sys/asoundlib.h is for API. For compiling usual apps, you don't have > > Exactly, but I just wanted to point out

Re: [Alsa-devel] RTC what is needed?

Chuck Busby wrote: > > Where is the patch or how do I test it? The patch is in alsa-driver/utils/patches/. You may have to adapt it to your kernel version. If you have trouble, ask Takashi Iwai. Matthias -- Matthias Pfisterer Take into account

Re: [Alsa-devel] Header files locations

Hi, > No, /usr/include/sound/* belong only to kernel stuffs, and yeah sure, thats what I said. > sys/asoundlib.h is for API. For compiling usual apps, you don't have Exactly, but I just wanted to point out that sys is not the right location to put asoundlib.h. Because all other files in there