Re: [linux-audio-dev] Re: [Alsa-devel] ALSA homepage redesign

2002-04-18 Thread Fred Gleason
On Thu, 18 Apr 2002, Joern Nettingsmeier wrote: > N. could we please please please annihilate every last little > trace of alsa 0.5.x from that page ? I'd like to add my vote for this here too. The whole 0.5.x vs. 0.9.x thing is *hugely* confusing -- to me, to programmers, and to end users.

Re: [linux-audio-dev] Re: [Alsa-devel] ALSA homepage redesign

2002-04-18 Thread Fred Gleason
On Thu, 18 Apr 2002, James Tappin wrote: > Is it perhaps time for an alsa-0.9.rc1 many people will be frightened off > by the beta designation, and certainly mislead into thinking that 0.5 is > the "safer" option. My understanding is that SuSE 8.0 is shipping with 0.9.0beta12. That's starting

Re: [Alsa-devel] PCM API questions

2002-06-24 Thread Fred Gleason
On Monday 24 June 2002 10:17, Paul Davis wrote: > >the names above are not defined on all cards (except for default). > >i think we need a kind of config database for each card. > >this is useful not only for pcm but also for parsing the mixer > >structure. > > i think this is the wrong solution.

Re: [Alsa-devel] Mixer sanity

2004-06-05 Thread Fred Gleason
On Saturday 05 June 2004 09:51, Owen Fraser-Green wrote: > Now, I know an envy24mixer exists to make life easier for me but surely > it would be a bit nicer if the mixer interface provided a more > consistent abstraction. In my situation, I want my software to be useful > without a screen so the e

Re: [Alsa-devel] Re: How to support multiple open in low-level driver

2003-01-06 Thread Fred Gleason
On Sunday 05 January 2003 10:05, Jaroslav Kysela wrote: > Well, you're talking about PCM devices (subdevices are one level after > devices): > > cards -> pcm devices -> pcm subdevices What are the differences between a "device" and a "subdevice" in general? Is this indicative of some underlying

Re: [Alsa-devel] Fwd: RE: To ESS Tech Support

2003-06-18 Thread Fred Gleason
On Wednesday 18 June 2003 11:39, Paul Davis wrote: > why not just quote to them the list of audio interface manufacturers > and chipset makers who have provided the necessary information, and > then ask them if they want to part of that list or marked as > "unsupportable". the list is determinable

Re: [Alsa-devel] AudioScience driver

2003-06-24 Thread Fred Gleason
On Tuesday 24 June 2003 01:14, Eliot Blennerhassett wrote: > I have attached a patch against alsa-driver-0.9.4 > But I'm not sure if this is the desired form, or whether I have located the > driver in the correct part of the tree. I've tried building things with the patch, and have some questions

Re: [Alsa-devel] (no subject)

2003-06-25 Thread Fred Gleason
On Wednesday 25 June 2003 20:40, Eliot Blennerhassett wrote: > Try aplay -Dhw:0,0,1 Works, as does hw:0,0,2 and hw:0,0,3. Curiously, hw:0,0,4 returns EBUSY, not ENODEV as I would have expected. Is this a normal feature of ALSA? > For ALSA the card has one device, and multiple subdevices. > T

[Alsa-devel] Test Report: snd-asihpi with an ASI6114

2003-06-26 Thread Fred Gleason
I've got things working with my ASI6114. Playback works well. Alsamixer shows me a bewildering array of controls, few of which seem to do anything. How do I control stream levels? Cheers! |-| | Frederick F. Gleason,

Re: [Alsa-devel] AudioScience driver

2003-07-01 Thread Fred Gleason
On Monday 30 June 2003 09:26, Takashi Iwai wrote: > > Good idea. > > how about /usr/include/asihpi/hpi.h > > well, assuming the certain header location is not recommended. > > basically, the kernel sources must not refer to the standard header > files for user-space. if you need a header file for